Thylacine Studios - Forum

Fatal error that force closed the game  (Read 653 times)

Offline Zack

  • Administrator
  • *****
  • Posts: 3388
    • View Profile
Re: Fatal error that force closed the game
Reply #2 May 27, 2016, 01:49:54 PM
Thanks, found it!
Designer and Programmer of Siralim and The Negative. Follow us on: Facebook | Twitter | YouTube

Offline Zagaran

  • *
  • Posts: 25
    • View Profile
Fatal error that force closed the game
Reply #1 May 27, 2016, 01:44:21 PM
1) Is your issue a bug, or is it a crash?

I would say a crash

2) If it's a crash, please copy and paste the full error message below, or post a screenshot of it. Otherwise, leave this field blank.
___________________________________________
############################################################################################
FATAL ERROR in
action number 1
of Key Press Event for S-key Key
for object obj_critsheet:

Unable to find any instance for object index '6' name 'obj_material'
at gml_Object_obj_critsheet_KeyPress_83
############################################################################################


3) Please describe in as much detail as possible how to reproduce the bug or crash.

This one is thankfully simple- although I do not know if it applies to the one instance in the one specific area- but that is why I am posting this here, for testing.
It happened in the tutorial of the game. I just defeated the monster laid out before me, and got the artifact. I equipped it to my creature, then decided to have a look at the creature in my creature menu. After getting a look at the stats, I accidently pressed the DOWN arrow key, and the fatal error popped up, crashing the game when the only option is to press abort.

4) What operating system are you playing the game on? Windows, Mac OS, Android, iOS, or Playstation? If it's Playstation, please also state your region (NA or EU).

I'm playing on Windows 7.
My region is CA

5) What game version are you playing? You can find the version number on the title screen in the lower left corner.

It is on version 0.0.2

6) Any other details to help us solve the problem, such as what you were doing when the bug/crash occurred, or any hints on how we can reproduce it.

Not really. I gave all that is needed. I just followed the tutorial to the letter, then did what I mentioned above, the trigger point being on accident.