Cody Bennett

Looks like the issue we encountered in https://github.com/mrdoob/three.js/pull/24001#issuecomment-1119203172. Also, from https://discord.gg/poimandres: > This is basically a shot in the dark, but can you try adding a large transparent cube to...

Clearing the canvas before every frame is a good workaround for the moment. You can do that by adding a lambda pass before your other effects: ```js import { LambdaPass...

Three.js had the usual PR chain die from inactivity (https://github.com/mrdoob/three.js/pull/18846), but they were concerned about the performance of their implementation since EffectComposer (forward) renders passes in series without MRT and...

Centralizing the rendering logic in the effect composer sounds like a good first step. As for code, I have a sandbox here https://codesandbox.io/s/7x7p3q. IIRC the postprocessing version on this box...

Yes, that would be great!

R3F should be optional here alongside react. https://github.com/FarazzShaikh/THREE-CustomShaderMaterial/blob/2696b65c381e0113ea3ad4f8091004d7280d1b0f/package.json#L75-L84

Yikes, prob best to let Sveltekit know of that issue with package resolution with SSR -- that can load multiple versions of libraries and cause deeper breakage. Another issue with...

I think these are clearly pnpm and svelte issues, if you could forward these to their respective repositories.

That is also an issue with three (they go halfway with three.cjs and three.module.js), but I don't think it's reasonable to expect everyone to follow Node's conventions for ESM in...

I see, you mean in regards to Node resolution -- three has resolved this already (via type="module" and .cjs), and we still need to do the same here in Lamina....