FR :: Directive to open modified shader in text editor #3
Description
Issue:
My code is relying a lot on Shady to improve the readability of everything. However when ever I run into an error on a multi area refactor it can be hard to track down what exactly the issue is when the compile error says "at line 297 : '='" but there is only 40 lines in that shader.
Solution:
Much like how one would show_debug_message to print something, I would like an entry point to view the source easier. I know the files are cached somewhere, but at the time of writing I dont know where they are, although having something like this could make debugging easier.
Alternative:
Maybe there is a way to track for failed builds? and if so then open the failed file(s)? That could be another solution if possible.