It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Community
OrphanGames crashes on opening scene(6 posts)(6 posts)
(6 posts)
Pages:
1
This is my favourite topic
Posted November 05, 2018
Watching the scanner check out the children tubes, screen fades to black, "Wake up!" "Wake up!" Game crashes to desktop with the following error message.


___________________________________________
############################################################################################
FATAL ERROR in
action number 1
of Step Event0
for object obj_gui:

REAL argument is unset
############################################################################################
--------------------------------------------------------------------------------------------
called from - gml_Object_obj_gui_Step_0 (line 89)


Can anyone make any sense out of that? Game version is 1.0.0.6
Posted November 05, 2018
avatar
MadnerKami: Watching the scanner check out the children tubes, screen fades to black, "Wake up!" "Wake up!" Game crashes to desktop with the following error message.

___________________________________________
############################################################################################
FATAL ERROR in
action number 1
of Step Event0
for object obj_gui:

REAL argument is unset
############################################################################################
--------------------------------------------------------------------------------------------
called from - gml_Object_obj_gui_Step_0 (line 89)

Can anyone make any sense out of that? Game version is 1.0.0.6
Yep, this is a Game Maker studio error; apparently, the developer released a quick fix, but in the process, introduced this new fatal bug for any new games. Will need to fix it again.
Posted November 05, 2018
avatar
Alcator.504: Yep, this is a Game Maker studio error; apparently, the developer released a quick fix, but in the process, introduced this new fatal bug for any new games. Will need to fix it again.
Ah, alright, couldn't find anyone else having this specific problem in a quick search. Thanks! Gonna have to wait a few days then.
Post edited November 05, 2018 by MadnerKami
Posted November 05, 2018
Working on it now. I was playing this build last night. For a while. Can't believe this...
Posted November 05, 2018
Found it. Patch coming within the hour. Simple oversight but infuriating. Long-story short, I added a new gamepad hotkey system to the UI. Worked smoothly for me last night, but I never checked what would happen if a gamepad wasn't plugged in. In hindsight, terrible idea. It just never occurred to me. The error is caused because the UI is looking for a value for global.Select, which is defined by the gamepad select button. However, way back whenever I initially wrote gamepad controls for the game (years) I wasn't using Select and so I never gave global.Select a default value. This would have been immediately obvious to me had I tested last night without a gamepad.

I'm going to sit down, breathe and write a "patch checklist" that I will go through from now on every time I do an update so I don't miss these things again.

Very, very sorry. Patch compiling now... will just skip to 1.0.0.7.
Posted November 05, 2018
avatar
BrandonGoins: Found it. Patch coming within the hour. Simple oversight but infuriating. Long-story short, I added a new gamepad hotkey system to the UI. Worked smoothly for me last night, but I never checked what would happen if a gamepad wasn't plugged in. In hindsight, terrible idea. It just never occurred to me. The error is caused because the UI is looking for a value for global.Select, which is defined by the gamepad select button. However, way back whenever I initially wrote gamepad controls for the game (years) I wasn't using Select and so I never gave global.Select a default value. This would have been immediately obvious to me had I tested last night without a gamepad.

I'm going to sit down, breathe and write a "patch checklist" that I will go through from now on every time I do an update so I don't miss these things again.

Very, very sorry. Patch compiling now... will just skip to 1.0.0.7.
Hehehe, no worries mate. You're doing this on your own, as far as I am aware and it's a learning experience. As long as stuff gets fixed, things are fine. Btw. I actually do have a gamepad plugged in, except that I switched off it's usage in the game's configuration menu as, way back when, this once caused a game to only function with a wierd mishmash of keyboard-, mouse- and pad-controls, despite mouse and keyboard being selected. Out of habit I switch it off in any menu I encounter that offers this option.
Pages:
1
This is my favourite topic
Community
OrphanGames crashes on opening scene(6 posts)(6 posts)
(6 posts)