When the scene is large, I can’t move the camera freely to see the detials

[engineerhe]

When the scene is small, I can move the camera freely. When the scene is large, I can’t move the camera to see some details in the scene view.And the 3dtiles url as follows:
http://61.146.36.148:8088/zhanjiang_gisdata/tileset.json

[j9liu]

Hi @engineerhe,

Unity is not configured to navigate large-scale applications by default, but you can configure the Editor camera's settings so that it moves faster in the scene.

Go to the toolbar under the Scene view, then click on the camera icon:

This will bring up a menu where you can change the clipping planes and speed of the camera. You can increase the camera speed as needed so that the camera isn't so slow.

Please let me know if this helps, or if I've misunderstood your issue.

[engineerhe]

@j9liu Firstly,thank you very much for your answer. Maybe i dont not have made my meaning clear. I know that you can set the scene camera near and far clipping planes, and then view the scene closely by shortcut keys W, A, S and D.But what I want to know is whether I can view the scene freely through the mouse wheel, because when the scene is large it's almost impossible to zoom in and out after a certain point.

[engineerhe]

@j9liu One more question,how to set the sensitivity of the mouse wheel in the scene view and how to avoid memory overflow caused by too large far clipping value in the scene.

[j9liu]

Hi @engineerhe,

Unfortunately, there is no way to adjust the scroll wheel sensitivity in the Editor. But you can try these options to better navigate the scene. (I'm using Windows, so you may have to look up what the controls are for MacOS if you use that.)

1. If you want to focus on a specific game object, you can bring it into view by double-clicking it in the Hierarchy window, or by selecting it and pressing F. You can also press Shift + F. This is used to lock onto a game object so that the camera follows it as it moves. Usually it zooms further in than just pressing F, because it zooms in on the position specified by the object's Transform.
2. Hold the Alt key on your keyboard as you press the right mouse button. This will allow you to zoom in and out with your mouse.
3. Increase the camera speed, then use the arrow keys to move forward towards your tileset. The longer you hold the arrow keys, the faster the camera will travel.

For your second question, you could always decrease the far clip value in the scene. But try setting the Maximum Cached Bytes to 0 for your tilesets in the Inspector window, that might help.

[engineerhe]

@j9liu Thank you very much for your patient answer. I will have a try

[engineerhe]

dear @j9liu ,
I want to ask you one last question, I promise.
Can you help me explain the reason for this, as shown below

[j9liu]

Hi @engineerhe ,

I'm not sure what the problem is from a glance. Does this happen with just any Cesium3DTileset, or is it because you have a lot of them in the scene?

[engineerhe]

Dear @j9liu ,
This fatal error usually happens when I set the camera while browsing the scene, not all Cesium3DTileset have this problom.No matter how I set up the camera, there's a high probability of this happening, right. This means that when I'm editing the scene, I can't set any parameters to the camera.So I feel strange and ask you the reason about it

[j9liu]

Hi @engineerhe,

Thank you for the additional detail. I'll have to look into this more. It sounds like a lot of tiles are being loaded at once and the system can't handle that much memory, so I'll check with my team to see where the problem might be.

Can you confirm something for me -- is this just with the Editor camera, or does this happen with the in-game cameras as well? In other words, does the crash happen with

1. only the editor camera?
2. only the in-game cameras? (You can test this in play mode.)
3. both the editor camera and the in-game cameras?

[engineerhe]

Dear @j9liu ,
Today I tested it in the scene view and the game view respectively. Maybe it has nothing to do with the camera Settings, but it crashes frequently. The following two screenshots are errors in the game view and the scene view respectively.And the Cesium3dtiles's address I tested was " http://223.243.132.41:5002/maspipemodel/phase1/model1/tileset.json"

[engineerhe]

By the way, I didn't do anything while I was testing, just navigating the scene.

[j9liu]

Hi @engineerhe ,

Yeah I imagine that the camera settings don't actually have much to do with the tile loading. In cesium-native (which Unity is built on), the clipping planes are treated as 0 and infinity, basically, so changing the Unity camera's clipping planes shouldn't actually have an effect on tile loading.

May I know what operating system and GPU you're working with? If the data is publicly available I will try to look into it when I get a chance

[engineerhe]

Dear @j9liu ,
My OS is win10 Professional and the GPU is NVIDIA RTX 3060.The data I give is publicly accessible.Finally, thank you very much for your guidance.