I’m not sure I understand. I don’t use addons bundle.
No additional extension installation.
I don’t know what the Atmosphere element is. I this error when I select scene, node, material… or any other node in the list “Scene explorer” and I have this error show in the properties panel.
Scene Explorer Sorting
Hey all (cc @cx20, @labris, @coryboyle), just a heads up the latest version of Inspector v2 now has a Scene Explorer toggle to enable sorting entities (within their parent nodes) alphabetically:
4 Likes
Hi! Is there a way to add new lights and cameras still in the vs sandbox? I know it used to be done by right clicking nodes, thanks!
@Tumble-wd sorry it took a long time, but we finally made some adjustments so the contrast is not so intense. It is more similar to Inspector v1 now, and you won’t have bright white on black. Everything is toned down a bit.
Yes. Currently it is done through the Quick Create Tools extension. You can install it by clicking the extensions button in the upper right and then installing this extension. It will give you a whole new pane where you can create various different entities.
We are trying to make Inspector more focused on diagnostics by default and keep the interface simple by default, and so we decided to make this an “optional” feature. But we could enable it by default in Sandbox, or even enable it by default all the time. Curious to hear more feedback from the community on whether this makes sense and just requires some getting used to, or people really prefer having it available by default without needing to enable it as an optional feature.
@Dad72
here is the fix for UMD - thank you for reporting!
[InspectorV2] Fix UMD inspectorv2 failing when addons is not explicitly included by georginahalpern · Pull Request #17778 · BabylonJS/Babylon.js
3 Likes
Hey all! As per some community feedback that the “Copy Property” UX felt cluttered, I added a setting to ‘Disable Copy Button’ which will remove the button for all properties. I also added ctrl+click on label to copy property (works regardless of whether the disable copy button setting is on), plus a lightweight toast notif to confirm the copy succeeded.
4 Likes
2 Likes
Property Filtering / Pinning / Hiding now available!
Huge thanks to @aknshr for implementing these features, offering enhanced functionality that was not previously available in v1 and was explicitly asked for (@j-te )
To access the pin / hide feature, enter ‘edit’ mode via the pencil icon, or holding down the ctrl key while hovering on a property line. Note that we also previosuly implemented ctrl+click on property label to copy the property – this feature still exists, and we plan to consolidate the UX in future 
Note the pinning / hiding functionality use localstorage so they persist across sessions.
3 Likes
Thanks @georgie! My contribution here was just the concept and the POC.
I see the new features, just got around to testing - it’s looking really good! I’m currently getting minified React errors in Chrome just after turning the visibility off:
I’ve tried disabling cache/deleting local storage.
Thanks for letting us know @j-te! Is this in Sandbox, Playground, or your own project? I can’t repro it in Sandbox or Playground. Any more details you can share that might help with a local repro? 
Scene Explorer Drag & Drop Reparenting
In Scene Explorer, you can now drag & drop a node to reparent it, thanks to this contribution from @marns!
This is currently only supported for the Nodes section, but the feature design makes it simple for any section to allow drag & drop operations when it makes sense.
Big thanks again for this great community contribution!
2 Likes
Numeric Input Improvements
Numeric inputs now support the following:
- When the
shiftkey is pressed and the value is incremented/decremented (clicking the up/down buttons or pressing the up/down keys, the step is multiplied by 10 (making it easier to make big adjustments). When thealtkey is pressed, the step divided by 10 (making it easier to make small adjustments). - Math expressions can now be entered into the input, e.g.
10 * 4.
1 Like
I have just tried on a fresh laptop, sandbox.babylonjs.com encountering the same error (Minified React error #300 – React) it may be a CDN/build issue? I am now mobile, not yet had time to debug properly. Repo: I downloaded the boombox.glb from the BJS repo which is the second glb that throws the errors, may be linked to physical materials in the scene? Apologies for the lack luster repo but should be back at the tools on Monday. You need to just go into Edit mode, turn off some texture channel properties then hit the check button.
Anyone else getting performance drops?
E.g. here https://playground.babylonjs.com/#GCG2Z7#5
The moment I turn on v2, the playground goes from 60fps to 30fps. Here is a profile: Firefox Profiler