-
Notifications
You must be signed in to change notification settings - Fork 30
Debugging instructions
187J3X1-114514 edited this page Feb 19, 2026
·
3 revisions
- The configuration file is located at
<game directory>/config/super_resolution/config.toml - The library files are located in the
<game directory>/config/super_resolution/libraries - The shader code will be stored in
<game directory>/config/super_resolution/debug - Shader compilation error reports are located at
<game directory>/config/super_resolution/error_logs - Shader caches are stored in
<game directory>/config/super_resolution/shader_caches
You can enable it directly in the module's configuration interface, or you can enable it in the configuration file by modifying the value of enable_debug.
- Some GPU resources within the mod (such as textures, FBOs, and shaders) will have a label (you can see it in graphics debugging tools such as Nsight Graphics and Renderdoc).
- Some GPU operations within the mod will have markers before and after (i.e., debug groups).
You can enable it directly in the module's configuration interface, or you can enable it in the configuration file by modifying the value of debug_dump_shader.
Dump the shader code inside the module into a file with the filename format <shader name>.<shader type>.<graphics API>.<code type>.glsl. Here, <code type> will be either source or preprocessed. source is the raw shader code input during shader compilation, without any insert macros. preprocessed is the shader code processed by Glslang and can be compiled directly; it has undergone macro expansion, preprocessing, etc.