-
Notifications
You must be signed in to change notification settings - Fork 35
Description
I'm currently trying to use react-three-map with the latest version of three.js, however, updating to any version of three.js above r165 breaks the "overlay" transformations of the overlaid r3f objects,
I've made a live example here to demonstrate the issue, it's currently setup to reproduce the error using r166 but the difference can be seen by reverting three.js to r165 or removing the overlay flag from the Canvas eg...
<Canvas latitude={51} longitude={0} /*overlay={true}*/>
I'm wondering what could have possibly changed from three.js r165 and r166 to cause this break and where I'd need to look in the react-three-map repo to try to find and propose a fix for this? three's migration changelog from 165-166 has no obvious clues as to what changed under the hood...
@RodrigoHamuy let me know if you have any ideas why this might be happening or if you happen to realize what'd need to be updated this side to get this working with the latest versions of three it'd be great to hear from you!