Author
Topic: Just Another Troubleshooting Thread (Read 10565 times)

Re: Just Another Troubleshooting Thread

I think I found another bug in Get Revengeance (sorry...). You can jump to the junkyard multiple times but when you are already there and jump to it again then you break the mission.

Spoiler:

The storage station is present in the distance but nothing happens when I fly there.

Also, I encountered a CTD when

Spoiler:

fighting against Henrietta (is that her name? You know, the one with the pink ships) in the same mission.

I tried to reproduce it with an attached debugger but it didn't happen again. The last thing I saw before the crash was a HUD gauge with the title "Messages" and that may be related to the crash. Do you have such a HUD gauge and if yes, how do I trigger its activation?

Re: Just Another Troubleshooting Thread

AKA [`_`]Inferno: It's the I in Inferno / It's the beam spam delight / Risin' up to a shock jump arrivaaaaaalBetween The Ashes: Look just a really cool and neat thing, OK?The Last Stand: A very episodic capship command mini-campaignDimesional Eclipse: An experiment gone horribly right Breakthrough: A pretty standard but not really capship command mission

Re: Just Another Troubleshooting Thread

I found a couple arcade related bugs. The first is in the endless gauntlet if I take the Iapetus with a cloaking device in the third secondary slot I still get the lightning sword(spear?), and while the name of it doesn't change at max berserk tier I get a version that has the damage, charge up time, and visual effect of the max upgraded version with the lock on time and reload speed of the base version (all while having the cloaking device).

The other was that the HAXase virus secondary doesn't seem to work on anything in the endless gauntlet except the first boss, I tried it on various shivan fighters/bombers and the first two bosses.

Re: Just Another Troubleshooting Thread

I found a couple arcade related bugs. The first is in the endless gauntlet if I take the Iapetus with a cloaking device in the third secondary slot I still get the lightning sword(spear?), and while the name of it doesn't change at max berserk tier I get a version that has the damage, charge up time, and visual effect of the max upgraded version with the lock on time and reload speed of the base version (all while having the cloaking device).

The other was that the HAXase virus secondary doesn't seem to work on anything in the endless gauntlet except the first boss, I tried it on various shivan fighters/bombers and the first two bosses.

I tried playing with these some more and it turns out the Haxase virus bug happens after I use it on something, then if I shoot the same enemy I used it on while they're friendly till they become hostile (which also plays the "whose side are you on dialog"), anything else I use it on will just stay hostile.

The cloaking device one happens when I have a cloaking device equipped then once I hit the first berserk level it swaps it to a lightning spear and stays even if I lose berserk.

Re: Just Another Troubleshooting Thread

Yeah, I think it's flagging you as a traitor. I'll be adding No Traitor mission flags to the XA missions where you can use the HAXase. (So just let them work for you! They'll self destruct after like 45 seconds)

Also I managed to fix most of the other bugs reported (just not m|m's messages related crash one, and the gatekeeper one is tricky so I'll look at it closer on the weekend), update will be going up shortly.

fonts.tbl(line 5): Error: Required token = [#End] or [$Font:], found [$TrueType: OpenSans-Regular.ttf].Try something more recent, like this nightly (and a newer version of wxLauncher that supports SDL2 builds).

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. <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.