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
In this example the mips are created as expected and if you uncomment the pass that displays the mip it does display.
In my app, it actually results in ERROR_OUT_OF_POOL_MEMORY if I try to sample the mip in another pass. But seems to otherwise create the mips as expected (viewed in render doc) if I don't try to sample them.
Edit: In my app I made a simpler pass to just render a debug output of the textures and it this doesn't cause the ERROR_OUT_OF_POOL_MEMORY but does still show the WRITE-AFTER-WRITE
The text was updated successfully, but these errors were encountered:
I have a compute shader that writes to multiple mips of the same texture in one dispatch. When I run it I get
SYNC-HAZARD-WRITE-AFTER-WRITE
Minimal code example (based on screen-13 triangle example, with current main 0.38 ash support, bdc4a81)
https://gist.github.com/DGriffin91/d792f15c1d0ae0c323f3b64e50968abf
In this example the mips are created as expected and if you uncomment the pass that displays the mip it does display.
In my app, it actually results in ERROR_OUT_OF_POOL_MEMORY if I try to sample the mip in another pass. But seems to otherwise create the mips as expected (viewed in render doc) if I don't try to sample them.
Edit: In my app I made a simpler pass to just render a debug output of the textures and it this doesn't cause the
ERROR_OUT_OF_POOL_MEMORY
but does still show the WRITE-AFTER-WRITEThe text was updated successfully, but these errors were encountered: