https://github.com/rpaladin/debug-blender-crashes-guide
Guide to debugging Blender/BGE/UPBGE crashes
https://github.com/rpaladin/debug-blender-crashes-guide
bge blender crash guide logs upbge
Last synced: 3 months ago
JSON representation
Guide to debugging Blender/BGE/UPBGE crashes
- Host: GitHub
- URL: https://github.com/rpaladin/debug-blender-crashes-guide
- Owner: rpaladin
- Created: 2021-05-21T21:40:37.000Z (about 4 years ago)
- Default Branch: main
- Last Pushed: 2022-10-25T17:58:17.000Z (over 2 years ago)
- Last Synced: 2025-01-15T22:36:28.042Z (5 months ago)
- Topics: bge, blender, crash, guide, logs, upbge
- Language: Batchfile
- Homepage: https://blender.org
- Size: 21.5 KB
- Stars: 0
- Watchers: 1
- Forks: 3
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Guide to debugging Blender/BGE/UPBGE crashes
### Prerequisites
* `blender_debug_log.cmd`
* Windows OS (feel free to convert the script for your OS)
**NOTE:** Blender 2.8+ versions usually ships with the script, so no need to download it if you already have the script locally. You can double-check if you have it already by searching in your root _Blender_ folder. If your Blender/UPBGE folder doesn't have this script, you can download it from this repository.
### How to generate crashlogs - Blender/BGE/UPBGE
1. Place `blender_debug_log.cmd` in your root Blender (if it isn't already there).
2. Run `blender_debug_log.cmd` by clicking it.
3. A _terminal_ window should open - once so, hover your _cursor_ over the generated terminal window.
4. Once the _terminal_ window is active or in focus, push the _ENTER_ key to confirm the opening of Blender - Blender should open normally then.
5. Attempt to make Blender crash again; when it does, _File Explorer_ should automatically open a new _Explorer_ window containing a new _TEMP_ folder, which should contain the newly generated crashlogs.
6. In the crashlogs folder, make sure to view `blender_debug_output.txt` and not `blender_system_info.txt` to prevent wasting time.
**NOTE:** Please be aware that Blender may _NOT_ crash while the debug terminal is still open, as most exception alerts have been automatically disabled.
## How to generate crashlogs - Exported Runtime
1. If your exported runtime has a filename other than _Blender_ or _blender_, for example `Game.exe`, you'll need to tweak the script to recognize your runtime in order for the script to properly launch and debug your runtime.
2. To edit the script to fit your renamed runtime, open your script in a text editor and rename: `"%~dp0\blender"` to `"%~dp0\%PROJECT_NAME%"`.
**NOTE:** `%PROJECT_NAME%` should be the filename of your runtime such as `Game`. No need to add your runtime's extension type (exe, app, elf, etc.), that's automatically detected.