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

Update to ThreeJS 133 #4788

Merged
merged 7 commits into from
Nov 2, 2021
Merged

Update to ThreeJS 133 #4788

merged 7 commits into from
Nov 2, 2021

Conversation

netpro2k
Copy link
Contributor

@netpro2k netpro2k commented Oct 27, 2021

Using our new update process to update to ThreeJS 133 (from 128)

See https://github.com/mrdoob/three.js/wiki/Migration-Guide#128--129 and up.

I have gone through the migration guide and list of changes in the Hubs repo, still need to check in our dependency repos, though things appear to be working correctly so far in my tests.

flines.unshift("uniform vec3 hubs_InteractorTwoPos;");
flines.unshift("uniform float hubs_Time;");
shader.fragmentShader = flines.join("\n");
shader.vertexShader =
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We might consider moving these changes into a patch in three to avoid breaking like this in the future

@@ -327,7 +283,9 @@ THREE.Water = function(geometry, options) {
renderer.xr.enabled = false; // Avoid camera modification and recursion
renderer.shadowMap.autoUpdate = false; // Avoid re-computing shadows

renderer.render(scene, mirrorCamera, renderTarget, true);
renderer.setRenderTarget(renderTarget);
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the only actual change in this file. The rest are formatting changes which appear to have not been applied in the past... Are we even still using this?

@arpu
Copy link

arpu commented Oct 27, 2021

do you know mozilla is working on a fix for this? mrdoob/three.js#22631

@netpro2k netpro2k changed the title Update to ThreeJS 133 (WIP) Update to ThreeJS 133 Nov 1, 2021
@netpro2k
Copy link
Contributor Author

netpro2k commented Nov 1, 2021

do you know mozilla is working on a fix for this? mrdoob/three.js#22631

Good callout, hadn't noticed this issue in my testing but seems like we should maybe include mrdoob/three.js#22759 for now...

@netpro2k netpro2k merged commit 710f7e0 into master Nov 2, 2021
@netpro2k netpro2k deleted the update-three-133 branch November 2, 2021 00:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants