Author Topic: Crash Report - ST:R (HUD Issue?)  (Read 2545 times)

0 Members and 1 Guest are viewing this topic.

Crash Report - ST:R (HUD Issue?)
Played through a few missions of ST:R (amazing by the way, incredible work, loving it!!!), made some graphical changes to the HUD (changing colors on different objects) then got the following error when loading the next mission:

Error: Player file has invalid radar range -1

File: plr.cpp
Line: 143

Ran the debug build, fs_open.log attached.

Tried resetting the HUD, still getting the error; if I click "Debug", it lets me continue, popping up the same error over and over, until it crashes outright. Can reinstall if necessary, but I'd love to be able to fix it without.


[attachment stolen by Russian hackers]

Re: Crash Report - ST:R (HUD Issue?)

Tried resetting the HUD again, got further, but this time the error is

Error: Player file has invalid radar range -1

File: radarsetup.cpp
Line: 487

Further additional:

Went back one more time, actually used the Reset HUD button instead of choosing one of the optional HUD_1/2/3 files... all errors gone. So, seems as though changing from the absolute default HUD was the culprit. Problem solved for me; at least I can play!  :D


Offline Goober5000

  • HLP Loremaster
  • Moderator
  • 214
    • Goober5000 Productions
Re: Crash Report - ST:R (HUD Issue?)
A bit late, but glad it's working, and thanks for the kind words. :)

Re: Crash Report - ST:R (HUD Issue?)
Out of curiosity, is the inability to customize the HUD a known issue?


Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Re: Crash Report - ST:R (HUD Issue?)
Out of curiosity, is the inability to customize the HUD a known issue?
...No. Does this happen every time you try to change the HUD configuration in any way, or is there some specific action that sets it off?
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> 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.

Re: Crash Report - ST:R (HUD Issue?)
I didn't test extensively - that is, I broke it, fixed it, broke it again, fixed it again, learned my lesson and stopped ;) - but it just seemed to be any time I changed the HUD from default in any way.