You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the app uses the floorplan navigator, it doesn’t work like it should be. I saw in the documentation that the elevation it’s defined by the SceneHeigth parameter, but when the fragments are generated in the model, this value is always the same. Even throw I change the elevation calculation by using the Elevation.value parameter, it takes me to a wrong level. What can be happening? Thanks!
Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
Make sure this is a IFC.js components issue and not a framework-specific issue. For example, if it's a THREE.js related bug, it should likely be reported to mrdoob/threejs instead.
Hey @RASRC can you please let me know where that is stated in the docs? Does this still happen? If so, is there any chance you could provide an IFC privately so that we can fix it? Thanks in advance!
Describe the bug 📝
When the app uses the floorplan navigator, it doesn’t work like it should be. I saw in the documentation that the elevation it’s defined by the SceneHeigth parameter, but when the fragments are generated in the model, this value is always the same. Even throw I change the elevation calculation by using the Elevation.value parameter, it takes me to a wrong level. What can be happening? Thanks!
Reproduction▶️
https://github.com/RASRC/Pruebas_Varias
Steps to reproduce 🔢
No response
System Info 💻
Used Package Manager 📦
npm
Error Trace/Logs 📃
No response
Validations ✅
The text was updated successfully, but these errors were encountered: