mhilbrunner
commented
1 year ago Really cool demo! On Windows 10, it hangs a bit for me on load when starting the run in editor in Godot 4.0.2. It also outputs this:
ERROR: Viewport Texture must be set to use it.
at: (scene/main/viewport.cpp:116)
ERROR: Viewport Texture must be set to use it.
at: (scene/main/viewport.cpp:111)
ERROR: Node not found: "Testers/ShaderPlasma/SubViewport" (relative to "WorldEnvironment").
at: (scene/main/node.cpp:1364)
ERROR: ViewportTexture: Path to node is invalid.
at: (scene/main/viewport.cpp:76)
ERROR: Viewport Texture must be set to use it.
at: (scene/main/viewport.cpp:116)
ERROR: Viewport Texture must be set to use it.
at: (scene/main/viewport.cpp:111)Then it works correctly. On exit, it spams more errors, not sure these are important though?
Calinou
InfiniteProductions
jtnicholl
This demo includes procedurally generated materials with 3 different techniques:
NoiseTexture2D: Built-in class that generates images on the CPU based on noise patterns (such as Simplex or Cellular). This is suited for static textures only. Texture generation is done asynchronously and is faster than using scripting, since the noise algorithms are implemented in C++ in the engine.
Scripting: Uses the Image class to procedurally generate an ImageTexture on the CPU. This is suited for static textures only. This approach is more flexible than NoiseTexture2D, but is slower to generate textures. Once the texture is generated, rendering performance is identical to NoiseTexture2D.
Shaders: Uses a 2D shader on a ColorRect node that matches a Viewport's size with the resulting ViewportTexture applied to a material. This is updated on the GPU in real-time, and is most suited for animated textures. This approach can also be used for static textures, with a lower performance overhead since the texture doesn't need to be updated every frame.
Preview