New update makes the game chrash on start up

[SirZkully]

I tried doing a fresh install and deleting everything, including what was in the AppData, anyone else has this problem? and knw of a fix?

[AnItalianGuy]

For me, only on laptop sometimes it crashes on start up, but most of the times if i dont tuch anything it starts and goes well form then on.

[Mangledwit]

I just bought the game and am also experiencing this. Did you find a fix for it?

[lori vornoy]

Hey! Do you guys have any logs in your equivalent of this folder: C:\Users\User\AppData\Roaming\Godot\app_userdata\Dungeons of Blood and Dream\logs

The latest log file is the one that doesn't have a date on it. You can just paste it here or on Discord.

[Mangledwit]

Originally posted by lori vornoy:

Hey! Do you guys have any logs in your equivalent of this folder: C:\Users\User\AppData\Roaming\Godot\app_userdata\Dungeons of Blood and Dream\logs

The latest log file is the one that doesn't have a date on it. You can just paste it here or on Discord.

Funnily enough I tried to open the game again after posting my reply and it started working but I'll paste one of the logs from when it crashed here anyway.

Godot Engine v3.5.1.stable.official.6fed1ffa3 - https://godotengine.org
OpenGL ES 3.0 Renderer: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2
Async. shader compilation: OFF

GodotSteam initialized.
ERROR: File must be opened before use.
at: get_line (core/bind/core_bind.cpp:2113) - Condition "!f" is true. Returned: String()
ERROR: Error parsing JSON at line 0:
at: call (modules/gdscript/gdscript_functions.cpp:1215) - Error parsing JSON at line 0:
ERROR: File must be opened before use.
at: get_line (core/bind/core_bind.cpp:2113) - Condition "!f" is true. Returned: String()
ERROR: Error parsing JSON at line 0:
at: call (modules/gdscript/gdscript_functions.cpp:1215) - Error parsing JSON at line 0:
ERROR: Skeleton parenthood graph is cyclic
at: _update_process_order (scene/3d/skeleton.cpp:219) - Skeleton parenthood graph is cyclic

Loving the game so far by the way! Where can I find the link to the discord?

[lori vornoy]

Originally posted by Mangledwit:

Originally posted by lori vornoy:

Hey! Do you guys have any logs in your equivalent of this folder: C:\Users\User\AppData\Roaming\Godot\app_userdata\Dungeons of Blood and Dream\logs

The latest log file is the one that doesn't have a date on it. You can just paste it here or on Discord.

Funnily enough I tried to open the game again after posting my reply and it started working but I'll paste one of the logs from when it crashed here anyway.

Godot Engine v3.5.1.stable.official.6fed1ffa3 - https://godotengine.org
OpenGL ES 3.0 Renderer: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2
Async. shader compilation: OFF

GodotSteam initialized.
ERROR: File must be opened before use.
at: get_line (core/bind/core_bind.cpp:2113) - Condition "!f" is true. Returned: String()
ERROR: Error parsing JSON at line 0:
at: call (modules/gdscript/gdscript_functions.cpp:1215) - Error parsing JSON at line 0:
ERROR: File must be opened before use.
at: get_line (core/bind/core_bind.cpp:2113) - Condition "!f" is true. Returned: String()
ERROR: Error parsing JSON at line 0:
at: call (modules/gdscript/gdscript_functions.cpp:1215) - Error parsing JSON at line 0:
ERROR: Skeleton parenthood graph is cyclic
at: _update_process_order (scene/3d/skeleton.cpp:219) - Skeleton parenthood graph is cyclic

Loving the game so far by the way! Where can I find the link to the discord?

Thanks! I just updated the game. I think it might be fixed now. You might need to restart the Steam app to grab the latest update.
The Discord link should be on the Steam library page for the game. And here it is: https://discord.com/invite/GJD3rK7q82

[sp00ky]

It does the same for me, and the game is amazing I love the vibe; instant favorite for me.

[lori vornoy]

Hi, so here are a couple of solutions for these crashes that a couple of players have mentioned:
- click on the game window immediately as the game starts to focus on its window
- reinstall the game (only worked for some)

It looks like my attempted fix didn't work. I will try something different for the next update.