4,400
edits
Canvas properties: Difference between revisions
Jump to navigation
Jump to search
m
Link to special directory articles
m (Link to special directory articles) |
|||
| Line 167: | Line 167: | ||
At some point, the canvas system itself could probably benefit from being also able to use the Effects/Shader framework, so that canvas textures can also be processed via effects and shaders optionally, before they get drawn. That should make all sorts of fancy effects possible, such as night vision cameras or thermal view, rendered to canvas textures/groups. | At some point, the canvas system itself could probably benefit from being also able to use the Effects/Shader framework, so that canvas textures can also be processed via effects and shaders optionally, before they get drawn. That should make all sorts of fancy effects possible, such as night vision cameras or thermal view, rendered to canvas textures/groups. | ||
It is currently not yet clear how to address this best, the easiest option might be to specify if effects or vertex/fragment shaders shall be invoked via properties (boolean), including their file names referring to $FG_ROOT? | It is currently not yet clear how to address this best, the easiest option might be to specify if effects or vertex/fragment shaders shall be invoked via properties (boolean), including their file names referring to [[$FG_ROOT]]? | ||
That would then disable the default rendering pipeline for those canvas textures and use shaders. | That would then disable the default rendering pipeline for those canvas textures and use shaders. | ||