Hosted Projects - FS2 Required > The Scroll of Atankharzim

debugging Irkalla Passes for CT27

(1/5) > >>

CT27:
Unfortunately, I ran into another technical issue:

In your 'branch' campaign, on the ISF path, on "Irkalla Passes"...after the Shivan forces leave, most of the ISF force goes through the node but then the ISF Mentu cruiser just goes in the node and sits there (like the corvettes did on that GTVA path issue I had earlier).  So I can't seem to complete the mission on this path either right now.


I got this message:
Assert: "order != -1"
File: hudsquadmsg.cpp
Line: 2461

ntdll.dll! ZwWaitForSingleObject + 10 bytes
KERNELBASE.dll! WaitForSingleObjectEx + 156 bytes
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
[...]
[ This info is in the clipboard so you can paste it somewhere now ]


Use Debug to break into Debugger, Exit will close the application.

ntdll.dll! ZwWaitForSingleObject + 10 bytes
KERNELBASE.dll! WaitForSingleObjectEx + 156 bytes
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
kernel32.dll! BaseThreadInitThunk + 13 bytes
ntdll.dll! RtlUserThreadStart + 33 bytes



Also, here's a log if it helps.


CT27:
One more thing Goober, here's the mission file you asked about earlier:

Goober5000:

--- Quote from: CT27 on September 30, 2017, 09:06:58 pm ---Unfortunately, I ran into another technical issue:

In your 'branch' campaign, on the ISF path, on "Irkalla Passes"...after the Shivan forces leave, most of the ISF force goes through the node but then the ISF Mentu cruiser just goes in the node and sits there (like the corvettes did on that GTVA path issue I had earlier).  So I can't seem to complete the mission on this path either right now.
--- End quote ---

I've never had that happen, and I can't see what in the mission could have caused it.  It's possible the navigation subsystem was destroyed, but there are sexps that should guard against that.  Make another attempt (might as well download the update first, see below) and see if it happens again.


--- Quote ---I got this message:
Assert: "order != -1"
File: hudsquadmsg.cpp
Line: 2461
--- End quote ---

I've fixed that and uploaded a new scroll-root, but that's benign and shouldn't affect anything.


--- Quote from: CT27 on September 30, 2017, 09:08:45 pm ---One more thing Goober, here's the mission file you asked about earlier:
--- End quote ---

Thanks.  That confirms you received the fixed mission, so the loadout error was probably caused by FSO not updating the cache.

CT27:

--- Quote from: Goober5000 on October 01, 2017, 01:09:56 pm ---

I've never had that happen, and I can't see what in the mission could have caused it.  It's possible the navigation subsystem was destroyed, but there are sexps that should guard against that.  Make another attempt (might as well download the update first, see below) and see if it happens again.


--- End quote ---

I'm sorry to report I tried it again after doing the update and the problem is still there.  The GVC Khitteb moves to the node and when it gets in there it just sits there and never jumps out (I checked its NAV subsystem to see if that had got to 0% but it was healthy.  The GTC Pallas jumped out before it but the ISF AWACS ship jumps out after the Khitteb (in fact the AWACS ran into the Khitteb and pushed it forward a little before the AWACS jumped out).

Since the Khitteb doesn't jump out, the Himoltep and Halifax end up not moving toward the node either.  I tried jumping out myself to see what would happen, and I got the usual debriefing text and "We have no recommendations for you" but it said I couldn't advance since I failed the mission.


I tried to do a debug build again to get a log but got this now:

Warning: Couldn't find event name "continue campaign" in mission sa_g1_07.fs2.
Returning false for event_status function.
File: sexp.cpp
Line: 13771

ntdll.dll! ZwWaitForSingleObject + 10 bytes
KERNELBASE.dll! WaitForSingleObjectEx + 156 bytes
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
kernel32.dll! BaseThreadInitThunk + 13 bytes
ntdll.dll! RtlUserThreadStart + 33 bytes


However, this time I was also able to get the mission itself.  A log is attached.
I don't know if it will help but I've also attached the mission "Irkalla Passes".  Maybe something went wrong with my copy.  Better to give you a little too much rather than you say I didn't give you enough info (better safe than sorry) right?

Goober5000:

--- Quote from: CT27 on October 01, 2017, 11:26:47 pm ---I'm sorry to report I tried it again after doing the update and the problem is still there.  The GVC Khitteb moves to the node and when it gets in there it just sits there and never jumps out (I checked its NAV subsystem to see if that had got to 0% but it was healthy.  The GTC Pallas jumped out before it but the ISF AWACS ship jumps out after the Khitteb (in fact the AWACS ran into the Khitteb and pushed it forward a little before the AWACS jumped out).
--- End quote ---

I still can't reproduce this.  But I made another update that separates the waypoints for the individual ISF ships.  This should prevent any possibility of them interfering with one another.


--- Quote ---I tried to do a debug build again to get a log but got this now:

Warning: Couldn't find event name "continue campaign" in mission sa_g1_07.fs2.
Returning false for event_status function.
File: sexp.cpp
Line: 13771
--- End quote ---

As I said before, this is expected.  It is an unavoidable consequence of the fact that this is the mission where two separate branches of the campaign merge together.


--- Quote ---Better to give you a little too much rather than you say I didn't give you enough info (better safe than sorry) right?
--- End quote ---

Yup.  But try the new update and see if it helps at all.

Navigation

[0] Message Index

[#] Next page

Go to full version