-
-
Notifications
You must be signed in to change notification settings - Fork 162
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
r138 #164
Comments
addressed the mrdoob/three.js#23414. |
gonna do mrdoob/three.js#22846 , which is going to be a moderate amount of diff. Update: #180 |
gonna do mrdoob/three.js#23498 Update: #183 |
gonna do mrdoob/three.js#23494 Update: #184 |
gonna do mrdoob/three.js#23386 Update: #185 |
gonna do mrdoob/three.js#23420 Update: #186 |
I have no knowledge about node material and have no idea what happened @ mrdoob/three.js#23418 ...... Update: mrdoob/three.js#23314 also has a lot of signature changes related to node materials |
have done the mrdoob/three.js#22772 : #187 |
gonna do mrdoob/three.js#23444 Update: #188 |
gonna do mrdoob/three.js#23455 Update: #190 |
gonna do mrdoob/three.js#23481 Update: #191 |
I think I've seen all the signature changes in r138. 50% confidence |
I've gone through and might have got more, but need to check the PRs in details. Lets aim 138 at master from now since it's the current release. |
will be resolved by #59045 |
Issue Tracker
This is used to track potential issues we need to investigate surrounding the
r138
release.Last checked: mrdoob/three.js@925fa24d6f (01 / 03 / 22).
The text was updated successfully, but these errors were encountered: