I often use the sandbox to debug glb files.
If i load a large city scene into it and want to be able to zoom in and view details, the default camera lower radius limit makes it impossible to zoom in enough.
the same goes for the near plane.
So I was wondering if we could either change the defaults, or introduce setting these from the querystring, or persist them to localstorage?
Love the idea, I did this a lot as well.
cc @PatrickRyan to see how we could introcduced smthg for this
The min radius is calculated based on the bounding volume of the loaded asset. The reason it’s larger like this is due to the original intention of the sandbox which was to be an example of a product renderer for e-commerce. You wanted to make sure your customer didn’t get lost when viewing the 3d render of the product so the minimum radius was set conservatively never to collide the camera with the model. But that assumed human scale products that you would go to a store to see in person. When we start dealing with larger scales like cities, that minimum radius math doesn’t make sense anymore.
I assume that we could make it easier without changing the default for everyone which would have the opposite effect for human scale assets. Perhaps a user defined camera preset selectable from the bottom bar which saves to local storage. We could give the ability to create multiple presets so that if you have an asset that you need the camera in a particular angle for, you have that preset available. This gives flexibility to set up a preferred workflow for your scale of asset while the casual user who comes once in a while gets a consistent experience from before.
I’ll look at this, great idea!
We could check the bounding spheres radius and if it’s bigger than some value (~100m) we could apply some other defaults that are more in line with environments.
it would be nice with presets, but it would be nice that it would just work.
either way it’s important to me to be able to apply the fix using the url.
I’m currently launching the sandbox from our admin with a debug button that opens the sandbox with ?assetUrl=...
and being able to have it work directly without having to pick a preset or enable some feature would be great.
What if we could use a free/universal camera? Zooming with the mouse wheel isn’t very convenient when the scene gets too big.
Hey @Leon I haven’t forgotten about this, still working on it. I have a question for you if you could try. Do you mind opening your model here:
Babylon.js Viewer Configurator
And telling me if the camera behavior in the Viewer Configurator is better for your scenario? (or worse or the same? :D). That will help me figure out the right fix for this. Thanks!
in the viewer configuration i can zoom in a lot further so that is better.
the near clip is still a problem though.
another feature that would be nice it WSAD (RF) to move around the scene. It might be out of scope, but i’m guessing a lot of us are using the sandbox as a debugging app it would be great.
Just an idea like this :
Maybe a way to do this (in the future) would be a “snippet-ready” version of the Sandbox.
The same way we can create a playground and save it under a unique URL, it would be nice to be able to save a “Custom Sandbox URL” which would be about Default Sandbox + Code Snippet (for whatever camera / scene / custom stuff)
At the end, I was so much in the need of this, I now have my own (private) Sandbox which is basically exactly default Sandbox + custom code…
This is super useful. Would you be able to share with me a model that reproduces your issue so I can use it to debug?
