I've noticed that my app's performance drops dramatically (<30fps) when the user navigates the Camera close to the ground/surface. This is much more apparent on 4K monitors which both of my dev machines use. I am measuring the FPS of the entire ApplicationWindow. This can be replicated with the Display a scene sample (doesn't matter if CPP or QML). Having the camera close to the surface is important for my use case (e.g. camera represents aircraft position & orientation).
Notes:
- Surface::setNavigationConstraint(NavigationConstraint::None)
- I notice this does improve the performance a little but then I start seeing tile edge artifacts
- Using a TransformationMatrixCameraController and using setClippingDistance()
- No effect at various clipping distances
- Don't add a Surface to the Scene
- Resolves issue, buttery smooth 60fps...but I need the elevation Surface...
- Playing with the atmosphere effects, lighting, etc.
My system specs:
- CPU: AMD Ryzen 9 5950X
- GPU: Nvidia GTX 1080Ti, other dev machine has a GTX 3090
- 64GB RAM
- 4K monitor
- ArcGIS Qt 200.2.0
- Qt 6.5.2
- Manjaro Linux
- Nvidia driver 535.113.01