With a long experience of 11+ years in application development with three.js, this is one of the topics I have focused on. I have collaborated with public agencies for the development of simulations and walkthroughs based on the “Matterport approach” in other areas, and I know the subject in depth.
You can see my collaborations to this topic in this forum in the following links
- How can i implement this in panorama? [May 2024]
- 360 Real Estate Properties Showcasing Project [Sep 2023]
- Matterport features for THREEjs? [Apr 2022]
- Mixing multiple “env” maps [Sep 2021]
- Moving between skyboxes / matterport [Feb 2020]
Having said that, let me comment:
- The pipeline you mention is well laid out. If you don’t need full views (i.e. Dollhouse view) you don’t even need a 3d model, with the depth maps you have all the data required to calculate the transition.
- Depending on how you set up the targetPoint,
THREE.OrbitControlsmight not be the best behavior for user interaction, since there are better ways to look around without moving the camera position. - The logic behind using
requestAnimationFramecould be made more efficient to avoid running when there is no user interaction, thus improving performance. - So far, what kind of problems do you still have? what kind of errors does the console throw ?
Feel free to DM
Best