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
While debugging my vulkan renderer, I noticed that under certain circumstances, most textures start being displayed as black (0, 0, 0, 0) color. "Certain circumstances" seem to be somehow related to me trying to access textures that persist from previous frames. These textures are used as storage images in compute shaders across multiple frames (fluid simulation) and sometimes I can see their contents if I entirely overwrite it within one frame, but if I'm using data that's already there from previous frames, then they are displayed as black.
Textures in question are for example in Compute Pass #1. All textured are displayed as black, but I know from behavior of the renderer that they are not.
Another clue: in that pass, all textures are actually derived from 3D Image 209 (that persists from previous frame) and if was black, then everything else would be as well. So probably that texture got screwed and everything else was a consequence of it.
I'm running GTX1060 laptop GPU.
The text was updated successfully, but these errors were encountered:
While debugging my vulkan renderer, I noticed that under certain circumstances, most textures start being displayed as black (0, 0, 0, 0) color. "Certain circumstances" seem to be somehow related to me trying to access textures that persist from previous frames. These textures are used as storage images in compute shaders across multiple frames (fluid simulation) and sometimes I can see their contents if I entirely overwrite it within one frame, but if I'm using data that's already there from previous frames, then they are displayed as black.
Here's one of those black captures: https://drive.google.com/file/d/1py7hx2EwDaTTDZQVRMCq4gctF0l9xroG/view?usp=sharing
Textures in question are for example in Compute Pass #1. All textured are displayed as black, but I know from behavior of the renderer that they are not.
Another clue: in that pass, all textures are actually derived from 3D Image 209 (that persists from previous frame) and if was black, then everything else would be as well. So probably that texture got screwed and everything else was a consequence of it.
I'm running GTX1060 laptop GPU.
The text was updated successfully, but these errors were encountered: