Cody Bennett

Is this still an issue? IIRC R3F uses a different container for event tracking now.

cc @krispya this will need to be a documented pattern.

We specify `^6.32.1` which should upgrade to the latest in 6.x.x, so it should automatically work on your end when a version of `postprocessing` is available for three.

This is misinformed; none of those points are inherently true. Again, see my prior comment. I'm trying to release #268 which is pertinent to the quoted stack trace as previous...

Noticed this from a question. Effect passes usually require a camera as the first constructor argument, then a list of parameters: - https://github.com/pmndrs/postprocessing/blob/main/src/effects/ShockWaveEffect.js#L18 ```jsx import { forwardRef } from 'react'...

Geometry is not optional for `InstancedUniformsMesh`, you have to pass a non-null reference to its constructor. The surrounding design in three.js is notably awful since it has two optional arguments...

Something we did in pmndrs was check whether `colorSpace` existed and hardcoded enums: ```js if ('colorSpace' in texture) texture.colorSpace = 'srgb' else texture.encoding = 3001 // sRGBEncoding // if ('colorSpace'...

That React warning is a real bug, so I'm elevating this issue.

iOS does not support JIT under the browser ban (WebKit has special permissions), but pending March 2024 EU legislation this can change. In the meantime, no such implementation exists for...

This is probably caused by exactly https://github.com/pmndrs/react-three-fiber/releases/tag/v8.16.1. Maybe try 8.16.0.