192d328f16
Enable VK loader debug messages when running blender_debug_gpu_* scripts. Allows easier debugging for users not familiar with using terminal. It won't log anything when using OpenGL. Vulkan loading logging can be big (1000 lines) but gives a lot of insight how vulkan and related applications are configured on the user system Sadly it does contains actual paths but think it is OK as the user is still responsible for uploading it in the tracker. An example of a log has been attached. See #135327. Pull Request: https://projects.blender.org/blender/blender/pulls/135399
22 lines
923 B
Batchfile
22 lines
923 B
Batchfile
@echo off
|
|
echo Starting blender with GPU debugging options, log files will be created
|
|
echo in your temp folder, windows explorer will open after you close blender
|
|
echo to help you find them.
|
|
echo.
|
|
echo If you report a bug on https://projects.blender.org you can attach these files
|
|
echo by dragging them into the text area of your bug report, please include both
|
|
echo blender_debug_output.txt and blender_system_info.txt in your report.
|
|
echo.
|
|
pause
|
|
echo.
|
|
echo Starting blender and waiting for it to exit....
|
|
setlocal
|
|
|
|
set PYTHONPATH=
|
|
set DEBUGLOGS="%temp%\blender\debug_logs"
|
|
set VK_LOADER_DEBUG=all
|
|
mkdir "%DEBUGLOGS%" > NUL 2>&1
|
|
|
|
"%~dp0\blender" --debug --debug-gpu --debug-cycles --python-expr "import bpy; bpy.context.preferences.filepaths.temporary_directory=r'%DEBUGLOGS%'; bpy.ops.wm.sysinfo(filepath=r'%DEBUGLOGS%\blender_system_info.txt')" > "%DEBUGLOGS%\blender_debug_output.txt" 2>&1 < %0
|
|
explorer "%DEBUGLOGS%"
|