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
Not sure if regression or missing migration hints, but MeshPhysicalNodeMaterial (or specific nodes?) doesn't work for me anymore from the npm version of three.js. It works fine with a local three.js dependency.
On r160 this exception is thrown:
On r159 it works fine:
Reproduction steps
Open repro case
Run npm i && npm run dev if it hasn't happened automatically
Note exceptions in console
In package.json, change to r159, run npm i && npm run dev again
Description
Not sure if regression or missing migration hints, but MeshPhysicalNodeMaterial (or specific nodes?) doesn't work for me anymore from the npm version of three.js. It works fine with a local three.js dependency.
On r160 this exception is thrown:
On r159 it works fine:
Reproduction steps
npm i && npm run dev
if it hasn't happened automaticallynpm i && npm run dev again
Code
See live example below
Live example
https://stackblitz.com/edit/vitejs-vite-awfcfn?
Screenshots
No response
Version
r160
Device
No response
Browser
No response
OS
No response
The text was updated successfully, but these errors were encountered: