[HAZARDLEADER]

Going to try this build, hopefully it works...

[Rodo]

double ets here, do I need to do something to make it go away, or is it a code error?

[Iss Mneur]

double ets here, do I need to do something to make it go away, or is it a code error?

Data problem. See the previous thread.

Chief, I think we need to put that (or a summary) into the OP because this is just going to keep coming up.

[chief1983]

Was there some recommended hud_gauge.tbl that many users downloaded, which is now obsoleted?

[mjn.mixael]

I really hate that "fix"...

The HUD issue is due to outdated hud_gauges.tbls (likely in the MediaVPs 3.6.12). We'll need to put up a new table I suppose.

[AV8R]

Wow, nice work guys. Took it for a spin and everything works well. I only ran into one issue and it turns out it was video card related.

When I first ran the new RC with vsync turned on, my frame rates were choppy (screen stuttering) during general play - no animations or anything else going on at the time. I turned on the FPS display and saw that framerates would not keep steady - the framerates quickly vacillated between 30fps and 75fps causing jumpiness and stuttering while turning (turning made it easy to see against the background star field). If I turned off vsync then the frame rates would hold steady at 120FPS and I would have smooth play.

On a whim I decided to try some of my other games (Descent 1 & 2 Rebirth) and strangely, they were experiencing the same FPS choppiness with vsync turned on. I checked the video card settings, especially the one controlling vsync for programs and the setting was correct (application controlled) and no other settings seemed to make a difference.

So I went to AMD's website and downloaded the latest drivers for my ATI FirePro 3D v4800 card and installed them and, surprise, now everything is smooth as glass again with vsync turned on (in all of my games). Very oddly coincidental that it started happening when I switched out the Freespace EXE's (I'm not at all blaming the FS exe - the timing was just surprising).

So remember to update your video card drivers too folks, just to make sure all of your bases are covered. 

[mralexs]

Code: [Select]

Malloc Failed!

ntdll.dll! ZwWaitForSingleObject + 21 bytes
kernel32.dll! WaitForSingleObjectEx + 67 bytes
kernel32.dll! WaitForSingleObject + 18 bytes
fs2_open_3_6_14_RC8.exe! <no symbol>
fs2_open_3_6_14_RC8.exe! <no symbol>
fs2_open_3_6_14_RC8.exe! <no symbol>
fs2_open_3_6_14_RC8.exe! <no symbol>
fs2_open_3_6_14_RC8.exe! <no symbol>
fs2_open_3_6_14_RC8.exe! <no symbol>
fs2_open_3_6_14_RC8.exe! <no symbol>

get this error on the mission after defeating The Roman's Blunder

[Cobra]

God damnit people when are you going to make 3.7

[niffiwan]

I really hate that "fix"...

The HUD issue is due to outdated hud_gauges.tbls (likely in the MediaVPs 3.6.12). We'll need to put up a new table I suppose.

I don't believe the MediaVPs 3.6.12 include a hud_gauges.tbl. I think people have downloaded their own tbl from one of the many threads about it (e.g. ant7 release thread).

Updated tables for mediavps / blueplanet2 / fsport are attached to this mantis issue (the mediavps table didn't include 4:3 res settings, I've added the settings from here, updated for the change, and given it a quick test)

[Androgeos Exeunt]

God damnit people when are you going to make 3.7

Galemp mentioned on Facebook that we should be at 4.x by now. I think he was joking.

[TopAce]

This build works fine on my end, but I get the impression that 'R' still doesn't target the nearest attacker. Sometimes it does target someone that is attacking me, but sometimes it just doesn't change target, despite the warning gauge flashing.

[Goober5000]

The modifications to targeting keys were reverted to retail behavior because there are still some discussions that need to take place.

[Echelon9]

Code: [Select]

Malloc Failed!

ntdll.dll! ZwWaitForSingleObject + 21 bytes
kernel32.dll! WaitForSingleObjectEx + 67 bytes
kernel32.dll! WaitForSingleObject + 18 bytes
fs2_open_3_6_14_RC8.exe! <no symbol>
fs2_open_3_6_14_RC8.exe! <no symbol>
fs2_open_3_6_14_RC8.exe! <no symbol>
fs2_open_3_6_14_RC8.exe! <no symbol>
fs2_open_3_6_14_RC8.exe! <no symbol>
fs2_open_3_6_14_RC8.exe! <no symbol>
fs2_open_3_6_14_RC8.exe! <no symbol>

get this error on the mission after defeating The Roman's Blunder

Can you try to reproduce this crash when using a Debug build? It will give us more info.

[mralexs]

It won't happen in the debug, It just crashes with no warning   

[z64555]

It won't happen in the debug, It just crashes with no warning   

Does it immediately CTD when you open up the debug build, or does it crash as soon as you reach the mainhall?

[mralexs]

crashes when i either A.) Manage to get the mission up then restart, or B.) crashes while the mission is loading

[headdie]

In that case the debug log is active and will hopefully be recording that is going off

[chief1983]

The modifications to targeting keys were reverted to retail behavior because there are still some discussions that need to take place.

Actually, there were no modifications made to the R key in .14, there was an inadvertent commit that was reverted but it wasn't the fix for 2659.  That was just decided not to be backported at all because it was a retail bug and R is rarely used as it is.  The change to fix R and make it cycle will probably be left in trunk, but no changes are being made in 3.6.14.

[Cyborg17]

Hey guys.  I just got found a bug that should be simple to fix.  When you start the game with volume on, go to the options screen from the mainhall, and then switch volume off, the music will keep playing until you attempt to start a mission. 

[Cobra]

because it was a retail bug and R is rarely used as it is.

I use it extensively.