Cody Bennett

Seems that loaders internally are not creating the correct response type. The following is what #3086 should do: ```jsx function Box() { const buffer = useLoader(THREE.FileLoader, require('./assets/tableau.obj')); const obj =...

I have a workaround you can try in https://github.com/pmndrs/react-three-fiber/issues/3085#issuecomment-1793472249. ```jsx function Box() { const buffer = useLoader(THREE.FileLoader, require('./assets/tableau.obj')); const obj = useMemo(() => new OBJLoader().parse(THREE.LoaderUtils.decodeText(buffer)), [buffer]) return } ``` I...

What is the issue exactly? Do neither of these work also? I'll look into getting #3086 out, but it may not be enough on its own. ```jsx // https://github.com/pmndrs/react-three-fiber/issues/3085#issuecomment-1837583297 function...

That example should work until #3086 is merged which lets the normal `useLoader` path for `OBJLoader` work again. Currently, loader internals return an `ArrayBuffer` due to how they are polyfilled...

Sorry, I missed this. Working on bugs surrounding arrays and us swapping elements in-place. We have a few flags already like `autoRemovedBeforeAppend` which workaround a more fundamental issue I need...

We'll be addressing this in #3248. Thanks for the help.

Does #3131 satisfy this?

I'll be implementing your suggestion in our v9 branch. Need to wrangle with types for v8, but should be possible to backport.

You can append a query url with a cache key currently, although cache behavior in general could be bettered with React 19. cc @drcmda

Needs integration testing with `GLTFLoader`. I recall it failing here which was a previous blocker.