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
Destroyed texture [Texture (unlabeled 2430x1488 px, TextureFormat::RGBA8Unorm)] used in a submit.
- While calling [Queue].Submit([[CommandBuffer from CommandEncoder "renderContext_0"]])
Understand this warningAI
three.webgpu.js:26767 Bindings._update: binding should be available: NodeSampledTexture false Texture Texture true
_update @ three.webgpu.js:26767
Here the setup :
Scene A : a particles mesh ( using compute shader ) is render to a renderTarget (rt1)
Scene B : a quad using as colorNode texture(rt1.texture) is render via Postprocessing with afterImage pass to a renderTarget rt2
Scene C : use rt2 in another quad + other effects for final composition..
All works as expected until I resize rt1 & rt2 then i run into this unexpected error and the resize is not effective.
pipelines :
particles compute -> render particles scene to rt1 -> scene2 using node with texture(rt1.texture) render via postprocessing afterImage to rt2-> final render compositing
Reproduction steps
see above
Code
X
Live example
I'll do it when i have time. but i suspect it's using the texture(rt1.texture) which crash everything.
Description
I run into :
Here the setup :
texture(rt1.texture)
is render viaPostprocessing with afterImage pass
to a renderTargetrt2
rt2
in another quad + other effects for final composition..All works as expected until I resize rt1 & rt2 then i run into this unexpected error and the resize is not effective.
pipelines :
particles compute -> render particles scene to
rt1
-> scene2 using node withtexture(rt1.texture)
render via postprocessing afterImage tort2
-> final render compositingReproduction steps
see above
Code
X
Live example
I'll do it when i have time. but i suspect it's using the
texture(rt1.texture)
which crash everything.Screenshots
Version
r175dev
Device
No response
Browser
No response
OS
No response
The text was updated successfully, but these errors were encountered: