Hey All,
FSO Inventory:
FSO: 3.6.18
FSPort: 3.4
MVPs: 3.6.12
I'm having some strange things happen when I run FSPort 3.4 and play some of the original single missions. It seems when I first start FSO and start a mission (like "Loner" for example) the first time I play through with the skill level set on Easy, my wingmates seem to be very lacsidasical in their engagement - often getting whacked by the Shivans or the HOL ships quite readily - which shouldn't happen on Easy. If I move over to another mission (such as Order of the Eye), the same thing happens. After giving the "Engage Enemy" command I've later seen some fighters just sitting in space doing nothing and unless tell their wing to do something, they'll end up being canon-fodder for the enemy. Also I'll have to keep reminding them to press an attack (on a cruiser, for example) or they'll just move onto something else/get distracted after a minute or so, or worse, even ignore my orders (ie: I tell a wing to ignore a target and they'll attack it anyway!).
Now if I exit from the program and the launcher and re-enter FSO and play the same mission, it seems to work better - wingmen are on point and get the job done without nagging - it's like night and day. I've gotten into the habit of starting FSO after a fresh boot and starting a mission, exiting out, restarting FSO and restarting the mission to get the AI to react correctly. Very odd.
Another issue is with secondaries. The missions seems to remember the ships and secondaries I chose last time I played but doesn't reset them when starting the mission. While convenient, this has the side effect of ending up with negative numbers for missiles (-200 Hornets!) and having to hit the reset button to fix the condition and reassign primaries/secondaries.
So, as a test, I tried rebooting and started FSPort 3.4 in Debug mode and started "Loner" again (this time the missile counts were OK), but when I hit Commit FSPort crashed to the desktop with the following error:
For asteroid 'Small Asteroid', detail level
mismatch (POF needs 3)
ntdll.dll! KiFastSystemCallRet
kernel32.dll! WaitForSingleObjectEx + 67 bytes
kernel32.dll! WaitForSingleObject + 18 bytes
fs2_open_3_6_18_DEBUG.exe! SCP_DumpStack + 354 bytes
fs2_open_3_6_18_DEBUG.exe! Warning + 416 bytes
fs2_open_3_6_18_DEBUG.exe! asteroid_load + 424 bytes
fs2_open_3_6_18_DEBUG.exe! asteroid_create_all + 311 bytes
fs2_open_3_6_18_DEBUG.exe! game_post_level_init + 80 bytes
fs2_open_3_6_18_DEBUG.exe! game_start_mission + 373 bytes
fs2_open_3_6_18_DEBUG.exe! game_enter_state + 464 bytes
fs2_open_3_6_18_DEBUG.exe! gameseq_set_state + 310 bytes
fs2_open_3_6_18_DEBUG.exe! game_process_event + 242 bytes
fs2_open_3_6_18_DEBUG.exe! gameseq_process_events + 152 bytes
fs2_open_3_6_18_DEBUG.exe! game_main + 782 bytes
fs2_open_3_6_18_DEBUG.exe! WinMain + 330 bytes
fs2_open_3_6_18_DEBUG.exe! __tmainCRTStartup + 358 bytes
fs2_open_3_6_18_DEBUG.exe! WinMainCRTStartup + 15 bytes
kernel32.dll! BaseThreadInitThunk + 18 bytes
ntdll.dll! RtlInitializeExceptionChain + 239 bytes
ntdll.dll! RtlInitializeExceptionChain + 194 bytes
Attached is the log file for your enjoyment. I'm not so much concerned with the Asteroid error as much as I'm concerned about the AI behavior.
BTW, I'm getting this with a fresh pilot file. Anything you guys would suggest?
[attachment deleted by ninja]