You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OS/device including version:
Windows 11
Lenovo laptop with a NVIDIA GeForce RTX 2060
Issue description:
On some rare occasions, trying to preview a random node output on preview2d will cause it to "jitter" for a few seconds, appearing to rapidly change seeds, before stabilizing in a single state
When the bug occurs in a material, the jitter will occur even on nodes that are not connected to the shader.
Steps to reproduce:
Bug can be reproduced with the following node chain:
Previewing the "blend" node, or any node that takes it as an input will cause the seed on preview to jitter for a few seconds, the issue also occurs when replacing the preview of the glitched node chain by any other node, even if unconnected.
Jittering also sometimes happens when a node in the glitched chain is updated.
Example:
Screen.Recording.2024-11-30.193550.mp4
The text was updated successfully, but these errors were encountered:
Material Maker version:
1.4a
OS/device including version:
Windows 11
Lenovo laptop with a NVIDIA GeForce RTX 2060
Issue description:
On some rare occasions, trying to preview a random node output on preview2d will cause it to "jitter" for a few seconds, appearing to rapidly change seeds, before stabilizing in a single state
When the bug occurs in a material, the jitter will occur even on nodes that are not connected to the shader.
Steps to reproduce:
Bug can be reproduced with the following node chain:
Previewing the "blend" node, or any node that takes it as an input will cause the seed on preview to jitter for a few seconds, the issue also occurs when replacing the preview of the glitched node chain by any other node, even if unconnected.
Jittering also sometimes happens when a node in the glitched chain is updated.
Example:
Screen.Recording.2024-11-30.193550.mp4
The text was updated successfully, but these errors were encountered: