Skip to main content

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

Hey, I'm the guy in charge of saves, was curious if you remember a few things about your third issue: if you reloaded your save, was it acting normal? Did you save while this was happening? If you did, did it persist after loading that save? Do you still have the same save where this happened? Also did it only happen in the immediate area or did it seem to work normally if you went somewhere else?

If this happened in the last or second to last time you've launched the game, the details might be in one of your log files. These are at "C:\Users\[your username]\AppData\LocalLow\Ninth Exodus\Peripeteia\". If you could send this to us (our discord would be a good place to get in contact), and possibly the save file (and anything in the error logs folder, since that might be relevant), we would greatly appreciate it, since this isn't something we've heard of with the recent builds. Glad to hear you liked the game, and we really appreciate the feedback and bug reports.

Deleted post

Thanks a lot, that's very useful info. I would appreciate the link.

Deleted post
(1 edit) (+2)

Thanks a lot. I ran your save on the current build, and it seems that it was an issue I unintentionally fixed the other day while cleaning up problems that would spam the log. The NullReferenceException in LightDetector.lightUpdate() was throwing errors every tick on the starting screen (that was also the PlayerMovement error you were seeing, which was only on start screen but also annoying me), so I added a check that also happens to catch the issue on your save (whatever is causing it I can now get a closer look at with your save since it's definitely a bug).

Basically what was happening is that LightController iterates through the entire list of LightDetectors, and at some point early on in that list one of them was broken in a way that threw that exception, causing most of the lights to stop working properly with our visibility system. Thanks again for your help figuring out the issue.