Lewy Blue

> Is the expectation for state.viewport to be reactive? I'm not sure about that. However, I do think that a method such as `.getCurrentViewport` should report the live state and...

> when you want to set the viewport that is possible as well but it would be your responsibility to inform the state model. there is > a setSize function...

> I think it's confusing to reduce viewport to OpenGL semantics (R3F shouldn't be coupled to a back-end, and WebGPU/D3D12 semantics will only make this more confusing) That's fair, but...

> My concern is that they all define it differently, especially with coordinates, and R3F can't make any assumptions about the environment it's running in I'm not sure if that's...

> I trust you don't mean to come across as contrarian or pedantic. Not in the slightlest. Apologies if I came across that way, it was unintended. > I don't...

Thanks for the clarification! > Also note that Effect instances can be reused in multiple EffectPass instances to keep memory usage low. If you use two separate BloomEffect instances, you'll...

Hitting this issue as well - or at least, I'm getting the same error message intermittently on mobile. @duncan-vrify is this your post on Discourse? https://discourse.threejs.org/t/wasm-memory-access-out-of-bounds-using-dracoloader-on-mobile-browsers/22930

> We ended up having to alter the model itself because a particular node had like thousands of geometries associated with it so I'd say maybe double check the model?...

Thanks. In this case I was just using the CLI but if I come across this again I'll try that out.

I'm having the same problem and adding `autoClear={false}` on the `` works for me. EDIT: now nearly a month later and I have yet to see any negative side effects...