When making a virtual environment, it's those last 10% of changes that can take the most time to get right. Fortunately there's a little-known trick to iterate much faster.
In the past, it was tedious to check the results on Mozilla Hubs. Typically, the pipeline for updating a scene looks something like this.
The old way:
1. Make a change
2. Export .glb file
Then (if you're bypassing Spoke):
In Project manager
3. Import from Blender
4. Upload .glb file
6. Once finished, click on the project again
7. Open in Hubs
8. Create a new room
9. Join Room
10. Set Audio
11. Check the change you made.
Or if you're using Spoke:
3. Upload the asset
4. Change the URL on the asset you updated to the new upload
5. Publish scene
6. Confirm publish
7. Create a new room
8. Join room
9. Set audio
10. Check the change you made.
Both pathways can take a long time, especially for changes that can take many iterations to get just right.
The New way:
If you're not familiar with them, 'Query String Parameters' are words you can add to the end of the URL with a '?' to get some extra development and debugging options https://hubs.mozilla.com/docs/hubs-query-string-parameters.html.
The debugLocalScene Query String Parameter helps expedite the iterative process tremendously.
?debugLocalScene (case-sensitive) to the end of the URL here:
and reload the room.
Here is a video demonstration:
Once reloaded with this parameter, dropping a .glb file into the scene loads them as the scene. So all you have to do is:
- Make change
- Export from Blender
- Drag and drop .glb file into the hubs scene
- Voila! Check the change you made
You can see how this new way can greatly reduce the time it takes to try different looks or make rapid adjustments to your scenes. If you have more time-saving techniques, please share them on our Hubs Discord. Our community would love to see what you've been making.