Author Topic: debugging Irkalla Passes for CT27  (Read 133 times)

0 Members and 1 Guest are viewing this topic.

Offline CT27

  • 210
debugging Irkalla Passes for 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.



 

Offline CT27

  • 210
Re: debugging Irkalla Passes for CT27
One more thing Goober, here's the mission file you asked about earlier:


 

Offline Goober5000

  • HLP Loremaster
  • Administrator
  • 214
    • Goober5000 Productions
Re: debugging Irkalla Passes for 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'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

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

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

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

 

Offline CT27

  • 210
Re: debugging Irkalla Passes for CT27


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.


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?

« Last Edit: October 01, 2017, 11:59:52 pm by CT27 »

 

Offline Goober5000

  • HLP Loremaster
  • Administrator
  • 214
    • Goober5000 Productions
Re: debugging Irkalla Passes for CT27
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).

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

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?

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

 

Offline CT27

  • 210
Re: debugging Irkalla Passes for CT27
Well, I tried your new update.  The ISF ships don't bump into each other anymore but the Mentu class Khitteb still  gets in the node and just stops (its "Time to" clock gets to zero and then its speed goes to zero).  Like before since it doesn't go the Hilmotep and Halifax don't move either after the Irkalla leaves.

I do appreciate all the help you've given on this (and I'll try and get you another debug log tomorrow).



At least I got to see the ending with the GTVA branch (so I know what the final mission is like...and I kind of prefer the GTVA one anyway).

 

Offline Goober5000

  • HLP Loremaster
  • Administrator
  • 214
    • Goober5000 Productions
Re: debugging Irkalla Passes for CT27
Hmm.  Tell you what, play the mission again, wait till the Khitteb gets to the node and stops, then ~K the Khitteb.  Then the mission should complete normally, allowing you to proceed.  After you've gone on to the next mission, tell me whether the Khitteb shows up or not.  This will determine whether the problem is due to the event not firing (Khitteb won't show up in m2_02), or the event firing but the Khitteb not being able to depart for whatever reason (Khitteb will show up in m2_02).

Also, after you've completed the mission, look in AppData/HLP/scroll/data/scripts and upload the m2_01_to_m2_02 checkpoint file.

By the way, if you haven't replayed m2_02 in a while, you're in for a treat.  I decided m2_02 was too underwhelming with all of the escort warships destroyed, so I turned off the persistent events and gave them all new names.

EDIT:

At least I got to see the ending with the GTVA branch (so I know what the final mission is like...and I kind of prefer the GTVA one anyway).

Why do you prefer the GVTA one?  The final mission, The Tablet of Destinies, is the same in both cases, unless you are comparing one playthrough before I removed the persistent ships to another one after.  Or are you referring to the conversations in Irkalla Passes that only happen if you come from the GVTA branch?

EDIT2: When you say the Khitteb's navigation is "healthy", is it above 30%?
« Last Edit: October 02, 2017, 09:46:03 pm by Goober5000 »

 

Offline CT27

  • 210
Re: debugging Irkalla Passes for CT27
I'll try your technical advice later but to answer your questions:

-When I said I liked the GTVA's branch overall more, I mean the whole GTVA path after the branch point selection.  I wasn't just referring to the final two missions both sides get.  The ISF path (aside from the technical difficulties I'm having) was excellently designed, I just liked the GTVA path missions better.  Admittedly I could have worded that better, I meant to say I enjoyed the GTVA path a bit more (not the GTVA "ending"...since both paths have the same ending).  Does that kind of clear it up?


-As for the Khitteb's nav system, it was at 71% or 81% (I don't remember the exact number now but it was a high number)

 

Offline Goober5000

  • HLP Loremaster
  • Administrator
  • 214
    • Goober5000 Productions
Re: debugging Irkalla Passes for CT27
I'll try your technical advice later but to answer your questions:

-When I said I liked the GTVA's branch overall more, I mean the whole GTVA path after the branch point selection.  I wasn't just referring to the final two missions both sides get.  The ISF path (aside from the technical difficulties I'm having) was excellently designed, I just liked the GTVA path missions better.  Admittedly I could have worded that better, I meant to say I enjoyed the GTVA path a bit more (not the GTVA "ending"...since both paths have the same ending).  Does that kind of clear it up?

Ah, I misunderstood what you wrote then.  Glad to have the feedback. :)

Quote
-As for the Khitteb's nav system, it was at 71% or 81% (I don't remember the exact number now but it was a high number)

Ok.

 

Offline CT27

  • 210
Re: debugging Irkalla Passes for CT27
Just now I tried the mission again to try your suggestion, and it's probably me not understanding your suggestion right...but nothing happened.


After the Khitteb got to the node and stopped, I tried your button combination suggestion but nothing happened.
I tried pressing "~" and then "K" but nothing happened (and the same occurred when I pressed both buttons at the same time).  FYI I had the Khitteb targeted while I tried both combinations.

Am I doing something wrong?

 

Offline CT27

  • 210
Re: debugging Irkalla Passes for CT27
Never mind, I figured it out.


I completed the campaign.  In "Irkalla Passes", I did your suggestion on the Khitteb and then the Halifax and Hilmotep jumped out and I was able to complete the mission.


In the final mission of the campaign ("Tablet Of Destinies"), the Khitteb did show up and came in at 63% (I can't remember if that's the exact health of the ship when I did `K on it in the previous mission though).


Unfortunately I couldn't do your final suggestion.  When I looked in AppData/HLP, I had no "Scroll" folder there.
Sorry I couldn't be of more help in that particular area.

 

Offline AdmiralRalwood

  • 211
  • Mister Subspace Strikes
    • Skype
    • Steam
    • Twitter
Re: debugging Irkalla Passes for CT27
When I looked in AppData/HLP, I had no "Scroll" folder there.
To be clear, you're looking in %APPDATA%\HardLightProductions\FreeSpaceOpen\ and the folder exists and contains things (including fs2_open.ini), just not a \scroll\ folder?
Ph'nglui mglw'nafh Codethulhu GitHub wgah'nagl fhtagn.

schrödinbug (noun) - a bug that manifests itself in running software after a programmer notices that the code should never have worked in the first place.

When you gaze long into BMPMAN, BMPMAN also gazes into you.

"I am one of the best FREDders on Earth" -General Battuta

<Aesaar> literary criticism is vladimir putin

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. :P
<MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".
(the very next day)
<MageKing17> this ****ing code did it to me again
<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."
<MageKing17> **** ME
<MageKing17> THE REASON IS PEOPLE ARE STUPID
<MageKing17> ESPECIALLY ME

<MageKing17> God damn, I do not understand how this is breaking.
<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.
<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"
(...)
<MageKing17> so
<MageKing17> more than two hours
<MageKing17> but once again we have reached the inevitable conclusion
<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!
* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.

 

Offline Goober5000

  • HLP Loremaster
  • Administrator
  • 214
    • Goober5000 Productions
Re: debugging Irkalla Passes for CT27
I omitted some steps that I thought could be inferred from the context.  A prerequisite to ~K is enabling cheat codes.  And as AdmiralRalwood noted, there are more folders in the AppData path.  The full path you should look in is:

%APPDATA%\Roaming\HardLightProductions\FreeSpaceOpen\scroll\data\scripts

Your experience tells me that the departure conditions fired successfully, but the Khitteb for whatever reason refused to jump.  Normally this can only happen if it is disabled, has 0% nav, or has the no-subspace-drive flag.  But none of these circumstances apply, so I'm rather perplexed.  I'll be interested to see what the checkpoint file might contain.

 

Offline AdmiralRalwood

  • 211
  • Mister Subspace Strikes
    • Skype
    • Steam
    • Twitter
Re: debugging Irkalla Passes for CT27
%APPDATA%\Roaming\HardLightProductions\FreeSpaceOpen\scroll\data\scripts
%APPDATA% includes the \Roaming\ part.
Ph'nglui mglw'nafh Codethulhu GitHub wgah'nagl fhtagn.

schrödinbug (noun) - a bug that manifests itself in running software after a programmer notices that the code should never have worked in the first place.

When you gaze long into BMPMAN, BMPMAN also gazes into you.

"I am one of the best FREDders on Earth" -General Battuta

<Aesaar> literary criticism is vladimir putin

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. :P
<MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".
(the very next day)
<MageKing17> this ****ing code did it to me again
<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."
<MageKing17> **** ME
<MageKing17> THE REASON IS PEOPLE ARE STUPID
<MageKing17> ESPECIALLY ME

<MageKing17> God damn, I do not understand how this is breaking.
<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.
<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"
(...)
<MageKing17> so
<MageKing17> more than two hours
<MageKing17> but once again we have reached the inevitable conclusion
<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!
* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.

 

Offline Goober5000

  • HLP Loremaster
  • Administrator
  • 214
    • Goober5000 Productions
Re: debugging Irkalla Passes for CT27
You're right, I just tried it.  I stand corrected.

 

Offline CT27

  • 210
Re: debugging Irkalla Passes for CT27
I looked just now and there was no "scroll" folder.  The "Roaming" folder is usually 'hidden' so I had to type in "%appdata%" in the search programs section of the start menu.

I looked in "AppData/Roaming/HardLightProductions/FreespaceOpen"  and there was no folder called "scroll" there.


EDIT:  I just thought of something.  I'm playing on 3.8.0 (64bit) and in "Advanced Settings" under "Launcher" I have "Store config in portable location" checked.  Could that be why "Scroll" isn't in the location you guys have mentioned?  I was told a while ago to check that if I wanted my pilot files to be kept in the usual location (Games/Freespace2/data/players).
« Last Edit: October 03, 2017, 07:00:47 pm by CT27 »

 

Offline Goober5000

  • HLP Loremaster
  • Administrator
  • 214
    • Goober5000 Productions
Re: debugging Irkalla Passes for CT27
Oh, in that case, yes.  Look in Games/Freespace2/scroll/data/scripts.

 

Offline CT27

  • 210
Re: debugging Irkalla Passes for CT27
I found the file you were asking about (m2_01_to_m2_02) in the correct location. 

I clicked "Attachments and other options" and added it but when I clicked 'post' it wouldn't let me post it.  It said this type of file extension wasn't supported.

When I was in Games/Freespace2/scroll/data/scripts, it said the type of this file was literally "file".  So unfortunately, I'm not sure how to get this to you now since this site won't let me add it as an attachment.

 

Offline AdmiralRalwood

  • 211
  • Mister Subspace Strikes
    • Skype
    • Steam
    • Twitter
Re: debugging Irkalla Passes for CT27
I found the file you were asking about (m2_01_to_m2_02) in the correct location. 

I clicked "Attachments and other options" and added it but when I clicked 'post' it wouldn't let me post it.  It said this type of file extension wasn't supported.

When I was in Games/Freespace2/scroll/data/scripts, it said the type of this file was literally "file".  So unfortunately, I'm not sure how to get this to you now since this site won't let me add it as an attachment.

Make a copy; rename the copy to "m2_01_to_m2_02.txt". You should now be able to attach it.
Ph'nglui mglw'nafh Codethulhu GitHub wgah'nagl fhtagn.

schrödinbug (noun) - a bug that manifests itself in running software after a programmer notices that the code should never have worked in the first place.

When you gaze long into BMPMAN, BMPMAN also gazes into you.

"I am one of the best FREDders on Earth" -General Battuta

<Aesaar> literary criticism is vladimir putin

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. :P
<MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".
(the very next day)
<MageKing17> this ****ing code did it to me again
<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."
<MageKing17> **** ME
<MageKing17> THE REASON IS PEOPLE ARE STUPID
<MageKing17> ESPECIALLY ME

<MageKing17> God damn, I do not understand how this is breaking.
<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.
<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"
(...)
<MageKing17> so
<MageKing17> more than two hours
<MageKing17> but once again we have reached the inevitable conclusion
<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!
* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.

 

Offline CT27

  • 210
Re: debugging Irkalla Passes for CT27
Thanks for the advice.

Here's the file (renamed as per AdmiralRalwood's suggestion).