OPENRNDR uses kotlin-logging, which is a Kotlin flavoured wrapper around slf4j, to log its internal workings. Log messages are displayed in the IDE’s console and saved to the
build.gradle.kts we can modify the
Logging.NONEto disable logging.
Logging.SIMPLEto display monochrome log messages in the console.
Logging.FULLto display coloured log messages in the console to distinguish their types.
It is possible to change how exception errors are presented by adding
-Dorg.openrndr.exceptions=JVM to the VM options under
Run > Edit Configurations. This can sometimes help figure out why a program is crashing.
If a ShadeStyle crashes, a
ShaderError.glsl file is created at the root of the project. The content of the file is the actual shader program OPENRNDR tried to use. Studying this program can help figure out why shaders fail. A common reason is using incorrect names for methods, uniforms or variables.
When a video file is produced, a
ffmpegOutput.txt is created at the root of the project. Studying this file can help diagnose problems with video exporting.
If your graphics hardware and drivers support OpenGL debug contexts you can use
-Dorg.openrndr.gl3.debug=TRUE to enable the debug messages.
Run > Edit Configurations... menu in IntelliJ and make sure the
VM Options text field contains
RenderDoc is a graphics debugger currently available for Vulkan, D3D11, D3D12, OpenGL, and OpenGL ES development on Windows, Linux, Android, Stadia, and Nintendo Switch™.
This post explains how to use RenderDoc with OPENRNDR.