Description:
Describe the bug When dragging the 3D globe (GlobalMap3D) with the left mouse button, if the view is dragged beyond a certain range (likely crossing the date line or extreme latitude/pitch angles), the map rendering becomes unstable. This results in severe screen flickering or Z-fighting artifacts.
To Reproduce Steps to reproduce the behavior:
Open the 3D Map view.
Use the Left Mouse Button to drag and rotate the globe continuously.
Drag rapidly or extensively towards the poles or across the 180° meridian.
Observe the flickering artifacts on the map layers (Land, Ocean, or Routes).
Expected behavior：
The 3D globe should rotate smoothly without visual artifacts, regardless of how far or in which direction it is dragged. The camera should handle wrapping or clamping correctly to prevent rendering glitches.
Environment：
OS: Windows
Browser: [e.g. Chrome, Edge]
Library: deck.gl (suspected issue with GlobalMap3D.tsx view state or controller settings)
Possible Cause：
The GlobeView or OrbitView controller might not be clamping coordinates correctly.
Potential floating-point precision issues at extreme coordinates.
Z-fighting between SolidPolygonLayer (Sea) and H3HexagonLayer (Land) when the camera projection matrix becomes distorted.
Description:
Describe the bug When dragging the 3D globe (GlobalMap3D) with the left mouse button, if the view is dragged beyond a certain range (likely crossing the date line or extreme latitude/pitch angles), the map rendering becomes unstable. This results in severe screen flickering or Z-fighting artifacts.
To Reproduce Steps to reproduce the behavior:
Open the 3D Map view.
Use the Left Mouse Button to drag and rotate the globe continuously.
Drag rapidly or extensively towards the poles or across the 180° meridian.
Observe the flickering artifacts on the map layers (Land, Ocean, or Routes).
Expected behavior：
The 3D globe should rotate smoothly without visual artifacts, regardless of how far or in which direction it is dragged. The camera should handle wrapping or clamping correctly to prevent rendering glitches.
Environment：
OS: Windows
Browser: [e.g. Chrome, Edge]
Library: deck.gl (suspected issue with GlobalMap3D.tsx view state or controller settings)
Possible Cause：
The GlobeView or OrbitView controller might not be clamping coordinates correctly.
Potential floating-point precision issues at extreme coordinates.
Z-fighting between SolidPolygonLayer (Sea) and H3HexagonLayer (Land) when the camera projection matrix becomes distorted.