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
Run yarn create r3f-app next my-app which is the starter kit for react three fiber with NextJS.
Change the version of three from ^0.154.0 to ^0.155.0.
Before: 0.154.0 (Working)
After: 0.155.0 (Broken)
ThreeJS is currently on 0.156.1. I did some debugging to determine that 0.155.0 is the version that breaks the react three fiber demo with NextJS. I'm not even sure what is the bug here, it looks like some textures aren't loading or something?
I don't know if this is a bug with three or a bug with react-three-fiber, I'm honestly not very familiar with the libraries as this is my first time working with them. I just figured I would report it in case the team isn't already aware since the support for NextJS seems rather exceptional otherwise. Really awesome library!
Thanks,
Saavan
The text was updated successfully, but these errors were encountered:
SaavanNanavati
changed the title
NextJS 0.156.1 Broken
NextJS Versions Broken: 0.155.0 Onwards
Sep 11, 2023
R3F does not control how three.js behaves. This is a breaking change from r155 where it defaults to physical lighting since mrdoob/three.js#26392. You can opt out of this temporarily with <Canvas gl={{ useLegacyLights: true }} />.
yarn create r3f-app next my-app
which is the starter kit for react three fiber with NextJS.three
from^0.154.0
to^0.155.0
.Before: 0.154.0 (Working)
After: 0.155.0 (Broken)
ThreeJS is currently on 0.156.1. I did some debugging to determine that
0.155.0
is the version that breaks the react three fiber demo with NextJS. I'm not even sure what is the bug here, it looks like some textures aren't loading or something?I don't know if this is a bug with three or a bug with react-three-fiber, I'm honestly not very familiar with the libraries as this is my first time working with them. I just figured I would report it in case the team isn't already aware since the support for NextJS seems rather exceptional otherwise. Really awesome library!
Thanks,
Saavan
The text was updated successfully, but these errors were encountered: