[SirKnightly]

Here is the nightly for Windows on 11 Jul 2011 - Revision 7343

Group: Inferno
fso-WIN-Inferno-20110711_r7343.7z
MD5Sum

Group: Inferno_SSE
fso-WIN-Inferno_SSE-20110711_r7343.7z
MD5Sum

Group: Inferno_SSE2
fso-WIN-Inferno_SSE2-20110711_r7343.7z
MD5Sum

Code: [Select]

------------------------------------------------------------------------
r7339 | Zacam | 2011-07-10 12:05:57 -0500 (Sun, 10 Jul 2011) | 2 lines
Changed paths:
   M /trunk/fs2_open/code/ai/ai_profiles.cpp

From Valathil: ai_profiles tbl/tbm will now parse set_flags and warn on unrecognized declarations when found.
Credits to Spoon and WoD for unveiling this over-sight.
------------------------------------------------------------------------
r7340 | Zacam | 2011-07-10 12:21:33 -0500 (Sun, 10 Jul 2011) | 1 line
Changed paths:
   M /trunk/fs2_open/code/ai/ai_profiles.cpp

Additional warning messaging for parsing the ai_profiles.tbl or -aip.tbm.
------------------------------------------------------------------------
r7341 | Goober5000 | 2011-07-10 21:05:27 -0500 (Sun, 10 Jul 2011) | 1 line
Changed paths:
   M /trunk/fs2_open/code/ai/ai_profiles.cpp

Valathil's method will fail on a string that is less than 60 chars and does not contain a :, so use memset, which is the historical technique
------------------------------------------------------------------------
r7342 | Goober5000 | 2011-07-10 21:10:48 -0500 (Sun, 10 Jul 2011) | 1 line
Changed paths:
   M /trunk/fs2_open/code/globalincs/def_files.cpp

deal with string truncation on MSVC6
------------------------------------------------------------------------



[Timerlane]

Something seems seriously broken(presumably AI-related?). As far I can see, nothing recharges(guns/AB, and presumably shields), and AI fighters are going berserk(doing crazy-fast/jerky spins) and firing their Subachs at insane rates of fire.

[attachment deleted by ninja]

[Jeff Vader]

I noticed the gun/afterburner thing too. They recharge at a really, really slow rate, regardless of how the ETS is set up.

[Zacam]

That would have been my fault. The update to the ai_profiles for catching invalid settings was mistakenly set to divide parameters it shouldn't have been.

Please update to Nightly 7344 and verify that the issue has been corrected, please and if you happen to notice any remaining peculiar behaviour.