[Dragon]

I've been encountering this bug on various private testing missions, but until now, I've never nailed it on a released, otherwise working campaign. Now I found it on DE.
The build is the latest on from BP SVN, but this bug was there for quite some time.

It occurs when you go into a mission, quit it using the pause menu, then reenter it and try to go to either ship or weapon loadout selection.
I don't know when it first appeared, but I remember isolated instances happening a really long time ago. I suspect it's related to the way mission saves the loadout the player selected, since making even a minor edit to the mission (thus resetting the loadout) also "resets" it.
It doesn't matter if the mission in question is the part of the campaign. It also should be noted that this bug is not DE-exclusive, it's just the first released campaign I've managed to consistently replicate it on, as it doesn't seem to appear everywhere.

Here's the error message I've got:

Code: [Select]

Invalid model number -1 requested. Please post the call stack where an SCP coder can see it.

ntdll.dll! KiFastSystemCallRet
kernel32.dll! WaitForSingleObject + 18 bytes
fs2_open_3_6_13d_SSE2_BP.exe! <no symbol>
fs2_open_3_6_13d_SSE2_BP.exe! <no symbol>
fs2_open_3_6_13d_SSE2_BP.exe! <no symbol>
fs2_open_3_6_13d_SSE2_BP.exe! <no symbol>
fs2_open_3_6_13d_SSE2_BP.exe! <no symbol>
fs2_open_3_6_13d_SSE2_BP.exe! <no symbol>
fs2_open_3_6_13d_SSE2_BP.exe! <no symbol>
fs2_open_3_6_13d_SSE2_BP.exe! <no symbol>
fs2_open_3_6_13d_SSE2_BP.exe! <no symbol>
fs2_open_3_6_13d_SSE2_BP.exe! <no symbol>
fs2_open_3_6_13d_SSE2_BP.exe! <no symbol>
fs2_open_3_6_13d_SSE2_BP.exe! <no symbol>
fs2_open_3_6_13d_SSE2_BP.exe! <no symbol>
kernel32.dll! BaseThreadInitThunk + 18 bytes
ntdll.dll! RtlInitializeExceptionChain + 99 bytes
ntdll.dll! RtlInitializeExceptionChain + 54 bytes
Log is in the attachments.

[attachment deleted by a ninja]

[niffiwan]

I may also have seen this in BP - am I right in saying that after you've restarted the mission, when you enter the ship or weapon loadout screens FSO crashes, but if you just enter the mission from the  briefing screen then it's all OK? 

If that's correct, could you please mantis the issue?

[Dragon]

Not after restarting it, quitting it from the "escape" menu and reentering. Normal restarting (from debriefing) doesn't cause this. Restarting from escape menu might, but I don't know.
I'll try inputting it into Mantis, but the system doesn't seem to like me. I had a lot of problems with logging into it. Scratch that, it seems that it works again. Mantised.
http://scp.indiegames.us/mantis/view.php?id=2649

[niffiwan]

thanks - and I meant what you said about the restart, i.e. in mission press escape, select quit, enter mainhall, re-enter mission briefing (I was being lazy with my previous description )

edit: Actually - which mantis did you put it in?  I can't see it in the SCP mantis here

[Dragon]

The one linked in the "Master Sticky". Try refreshing, I was finalizing the report as I wrote the post.

[niffiwan]

thanks - I was too impatient...

[Dragon]

So, any clue on what it may be? I'd really appreciate it getting fixed.