Using Shader Debugging and Profiling Tools See Remote Shader Compiler for detailed instructions. It is highly recommended to use a locally running Remote Shader Compiler, so that shader debug symbols will be generated. r_ShadersEditing 1 ensures that shader code can be recompiled at run-time. Sys_PakPriority 0 makes sure that the shader files get loaded directly from the file system in the first place instead of just from pak files. In order for shader hot-reloading to work properly, the following options have to be added to the system.cfg: It is easy to write a batch file which copies the updated shaders automatically to the required folders. Before reloading, the shaders have to be copied to the console.įor the X360, they need to be copied directly to the Engine/Shaders directory on the devkit HDD while for the PS3, the local files in the app_home directory need to be updated. Hot reloading is supported on consoles as well by typing r_reloadshaders 1 in the in-game console. Sandbox supports hot reloading of shaders, so whenever you modify and save a shader file in a text editor, it will get reloaded automatically and the results can be viewed directly in a test level. The easiest way to write shaders is by using a text editor and Sandbox.
0 kommentar(er)
