Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

This means a fatal error happened in the game, which is really bad. Please check your game's folder and look for an "Error Log (Date).txt". If you find one, please copy/paste the contents here for me to read.

I can't find it, I don't know if it's because I don't know how to search or because the problem originated on a different computer than the one I'm using now. I transferred the game from one computer to another with a pendrive, so it should be the exact same in both of them. I can't even find where the saves in general are saved.

Hmm. I'm going to talk nerd here.

Sadly, your save file will be left on the old computer, even when you transfer the game folder to the new computer. And I suspect it's the save data that's causing the fatal error. So, if the game is still making the fatal error on the new computer (without the save data), that's worrying for me.

But, then again, on the later versions of the game, it automatically imports a save data whenever it detects a "Backup (version).nbb" file in the game folder.

And "Backup (version).nbb" files are always created every time the game detects you're playing a new version.

Wherever the error is happening, that's where the "Error Log(Date).txt" should be created. (The same folder as where the .exe is located)


We have two options:

1. We try our best to salvage what we can get from the corrupted save data. (We will use the File Utility for this, which can be a bit complicated. That or you share with me your "Backup (version).nbb" and I'll do it for you.)

2. You delete the save data and make a fresh start. (Ouch, but it's easy. It's in the Settings of the Main Menu.)

First time playing, having the same issue, stuck in the same spot when first heading to Glitch City, no error Log made, just a player log in AppData. This is repeated over and over at the bottom of the current one:

NullReferenceException: Object reference not set to an instance of an object

  at HubMap.LateUpdate () [0x0069d] in <96a50ba62ec649f59895c2e0ad3b3a4e>:0

Thank you for sharing this! It's the first time I've heard of this problem. I'll investigate this problem when I get the chance.

I might have been wrong in my assumption above.

If it's not too much bother, I wish to ask for a favor in checking the player log again. (If it's still available)

You mentioned there are multiple "NullReferenceException" over and over. What I wish to have you check is if there's a different error/s before all the "NullReferenceException" started.

There's this:

NotSupportedException: The URI prefix is not recognized.

  at System.Net.WebRequest.Create (System.Uri requestUri, System.Boolean useUriBase) [0x000ae] in <fbf3bef999a04908bac2dd07829c8508>:0 

  at System.Net.WebRequest.Create (System.String requestUriString) [0x00014] in <fbf3bef999a04908bac2dd07829c8508>:0 

  at Data.AMLDHHJLEMH () [0x00000] in <96a50ba62ec649f59895c2e0ad3b3a4e>:0 

  at Hub.Awake () [0x0004c] in <96a50ba62ec649f59895c2e0ad3b3a4e>:0 

Unloading 24 unused Assets to reduce memory usage. Loaded Objects now: 24716.

Total: 9.366200 ms (FindLiveObjects: 0.858700 ms CreateObjectMapping: 0.555300 ms MarkObjects: 6.736200 ms  DeleteObjects: 1.215900 ms)

NullReferenceException: Object reference not set to an instance of an object

  at HubNewsSolo.DDNOGFBNMGH () [0x005a8] in <96a50ba62ec649f59895c2e0ad3b3a4e>:0 

  at HubNews.HIELOOHLKEE () [0x00068] in <96a50ba62ec649f59895c2e0ad3b3a4e>:0 

  at HubNews.Start () [0x0031a] in <96a50ba62ec649f59895c2e0ad3b3a4e>:0 

NullReferenceException: Object reference not set to an instance of an object

  at HubNewsSolo.DDNOGFBNMGH () [0x005a8] in <96a50ba62ec649f59895c2e0ad3b3a4e>:0 

  at HubNewsSolo.Update () [0x00025] in <96a50ba62ec649f59895c2e0ad3b3a4e>:0

And some stuff about the Fallback Handler not being able to load the OculusXRPlugin library

Thank you very much for your help!

6.5.13 is now available, which includes changes based on your reports. However, I'm not sure if I managed to fix the issue 100%, but if I didn't, I made several adjustments to the code so that if the same error occurs in this version, the game will give out a better report on the error. (Hopefully)