Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
aframe 1.2.0 and navmesh
See original GitHub issuewhen using a simple navigation mesh
-
Using aframe 1.0.4 with aframe-extras works
-
Using aframe 1.2.0 with aframe-extras does not, with the following
Uncaught TypeError: THREE.Geometry is not a constructor
When I then used a local non-min copy of aframe-extras the additional info indicates the error is
Uncaught TypeError: THREE.Geometry is not a constructor at i.loadNavMesh (aframe-extras.js:11127)
when I used a local, non-min copy of aframe-extras
I am not a programmer, but I THINK it’s the THREE.js issue mentioned in “Ocean extra nlot working on aframe 1.2.0”. That said, I have no idea what a work around might look. There are a few other features in aframe 1.2.0 that I am trying to hold on to (for very simple student VR projects)
Issue Analytics
- State:
- Created 2 years ago
- Reactions:5
- Comments:16 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Can you please help me reintroducing the applyMatrix. Can you please create a glitch example with your fixed models and add again scale and position, so I can remix it and work on a fix.
Thanks for the reproduction case @dirkk0 Your navmesh looks correct when I open it in blender. Indeed “WARNING: Multiple instances of Three.js being imported.” is not normal, that may be the issue.