482
edits
Howto:Shader programming in FlightGear: Difference between revisions
Jump to navigation
Jump to search
Howto:Shader programming in FlightGear (view source)
Revision as of 04:46, 19 March 2017
, 19 March 2017→Error Reports, Debugging, Troubleshooting
(→Language features: Error log, troubleshooting section) |
|||
| Line 69: | Line 69: | ||
== Error Reports, Debugging, Troubleshooting == | == Error Reports, Debugging, Troubleshooting == | ||
Shaders are compiled at FG startup. | |||
Shader compilation errors can be found in the fgfs.log file. More about the [[Commonly_used_debugging_tools#fgfs.log|fgfs.log here]]. | Shader compilation errors can be found in the fgfs.log file. More about the [[Commonly_used_debugging_tools#fgfs.log|fgfs.log here]]. | ||
As of FG 2016.4.4, shaders do not seem to recompile upon Debug/Reload Aircraft Model or File/Reset. So the only option to re-compile/test a shader is to quit a re-start FG altogether. | |||
== Shader types == | == Shader types == | ||