Skip to main content

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

Strive for Power

Fantasy Slave Management/RPG Erotic Game · By Strive4Power

Crashing while loading

A topic by BlindJack created Jan 13, 2021 Views: 790 Replies: 1
Viewing posts 1 to 2

So recently I downloaded the most recent version of the game (version 69 for windows 32 bits). The game crashes constantly on old saves after a certain amount of time goes on (which is usually at the start). Even tho recently it just gets stuck on a loading loop (possibly a memory leak) where the only possible way out is force closing (yes, I've tried leaving it loading. 20 minutes and still stuck there). I also tried to make a new game in case it was related to the old save but it just instantly crashes, and this is the message windows gives:

  Nombre del evento de problema: APPCRASH
  Nombre de la aplicación: Strive.exe
  Versión de la aplicación: 3.2.4.0
  Marca de tiempo de la aplicación: 00000000
  Nombre del módulo con errores: ig4icd32.dll
  Versión del módulo con errores: 8.15.10.2869
  Marca de tiempo del módulo con errores: 506df81f
  Código de excepción: c0000005
  Desplazamiento de excepción: 0005d091
  Versión del sistema operativo: 6.1.7601.2.1.0.256.1
  Id. de configuración regional: 2058
  Información adicional 1: 0a9e
  Información adicional 2: 0a9e372d3b4ad19135b953a78882e789
  Información adicional 3: 0a9e
  Información adicional 4: 0a9e372d3b4ad19135b953a78882e789


 I got a different crash message different than the windows one, but I didn't write it down. It happened while loading an old save (I can't reproduce it again, for some reason). On the bright side, the game didn't crash while managing inventory like it used to. If there is any way I could get a crash log or something more I'd be willing to try.

First, the Windows error report is pretty much useless, even if it was in English. Strive creates log files in %appdata%/Strive/logs (this path can be used by Windows Explorer or  the Run app, windows key + R ). The DEBUG_TRACE file is created by the code and will report problems in a couple parts of the game like the mod system or file paths. The godot file is created by the engine and will provide the error messages pointing to exact lines of code when the game closes, so long as the game does not suddenly crash before it can finish the file. If the game closes normally, then the last 8 lines of that file will be errors related to closing the game.

Second, I have posted a mod which starts the game in debug mode, which does not crash upon the first error and has a second window that reports the same things as the godot log in real-time. https://itch.io/t/1137280/debugmod-v1 Please note that simply because the game does not crash when errors occur does not mean that the game will be fine; some errors  result in corrupt data which can disrupt gameplay or result in invalid save files.