Yes! That is exactly what I meant. That UI in your screenshot is the Inspector, which is present in both Playground and Sandbox. When you use the Inspector for picking, it puts the SelectionOutlineLayer in the gizmo utility layer:
function getOrCreateOutlineLayer(scene: Scene): SelectionOutlineLayer {
if (!outlineLayer || currentScene !== scene) {
disposeOutlineLayer();
utilityLayer = gizmoService.getUtilityLayer(scene);
outlineLayer = new SelectionOutlineLayer("InspectorSelectionOutline", utilityLayer.value.utilityLayerScene);
updateColor(outlineLayer);
currentScene = scene;
}
return outlineLayer;
}
This is the same thing that happens for transform gizmos (e.g. translate, rotate, scale) or visualization gizmos (e.g. for lights or cameras). That causes those tool features to be rendered, but not to show up in the main scene (which is what scene explore shows) because they are in a utility layer that is specifically for tooling, outside of the main scene created by the app.
Yep, the new Inspector CLI was being enabled by default, but it has since been fixed. And on that note, folks keeping tabs on this thread may also be interested in the new Inspector CLI (experimental). Check out the announcement post here! Inspector CLI (for AI agents) - Announcements - Babylon.js
if I click on that âTry Againâ button, everything is restored and working
this error is on Firefox (any version including the latest 150)
in Chrome it seems to work ok
the error has nothing to do with the popup blocker
A tip for the dev team:
Mozilla defines the web standards.
So any web app has to work properly on the Firefox browser.
If an app works fine in Firefox, you can be sure it works fine in Google Chrome or any other browser.
But you cannot say the same thing for Chrome.
Well, no explicit plans or timeline right now, but the intention is to support all Babylon features in Inspector. We have had some discussions around audio v2 in Inspector v2 in the past. Some thoughts that came up in those discussions:
Should audio v2 engines (and their sound hierarchy) show up in scene explorer, or should there be a whole new audio v2 pane on the left for audio engines (since they are not really connected to the babylon engine or scene)?
What should we show in properties? What kind of diagnostic activities do people want to do with audio?
Are there any more complex but useful audio visualizations that would be genuinely helpful for diagnostics?
Are there specific things youâd like to see for audio v2? Weâre also open to contributions of course.
was figuring just ways to play them and mess with play playback settings but mainly widgets to visualize the spatial part. Its not major but one of my coworkers was asking about it.
Oh I see. And when you say âparameterâ do you mean a query param you could use in the Playground/Sandbox url, or do you mean parameter in the ShowInspector API in your use of Inspector in your own app?
