Glitches won't work

[dirkk0]

Hi,

I came from this thread: https://github.com/donmccurdy/aframe-extras/issues/225#issuecomment-385849705

and tried the examples (like https://cherry-teacher.glitch.me/); they all gave me an Cannot read property 'groups' of undefinederror once I hit a WASD key.

Thanks, Dirk

[donmccurdy]

Mainly, you can't walk around with constrainToNavMesh: true before creating a navmesh. Typically you would create the navmesh, export it, and then import it directly to your scene. But yeah ideally the scene shouldn't crash here and should let you test the navmesh nicely... :)

[dirkk0]

Sorry - my bad, it seems I missed a lot. From your blog post it was 'create a NavMesh in Blender', import it and you are ready to go.

Now I see that you need to enter the inspector (which I don't use much, generally), hit build, and then you are ready to go. I guess I would prefer a (semi?-)automatic build when I load the file.

[donmccurdy]

The idea is that you can use the inspector plugin while authoring a scene — set up obstacles and models however you want — then build the navmesh and export it to a .gltf file. Once you've done that, you import the navmesh with <a-entity gltf-model="navmesh.gltf" nav-mesh/> as you'd do with a navmesh created in Blender.

For the finished scene, the plugin should not be included at all. You wouldn't want to build a navmesh every time a user visits the scene as that (1) takes a while and (2) requires uploading the entire scene to a server for processing.

This just lets the Inspector replace Blender for building the navigation mesh, as a one-time step.

[donmccurdy]

The issue about movement throwing errors until a navmesh is created should be fixed on latest aframe-extras. I'll document the rest of this when the plugin is further along.