Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Regression: Nodes not working anymore in r160 #27426

Closed
hybridherbst opened this issue Dec 22, 2023 · 0 comments
Closed

Regression: Nodes not working anymore in r160 #27426

hybridherbst opened this issue Dec 22, 2023 · 0 comments
Assignees

Comments

@hybridherbst
Copy link
Contributor

hybridherbst commented Dec 22, 2023

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:
image

On r159 it works fine:
image

Reproduction steps

  1. Open repro case
  2. Run npm i && npm run dev if it hasn't happened automatically
  3. Note exceptions in console
  4. In package.json, change to r159, run npm 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants