Inquiry Regarding Potential Conflict Between Dotween Plugin and Dynamic Camera in Unity World Coordinates

Description: I am currently working on a project in Unity where I utilize the Dotween plugin to smoothly visualize a continuous trajectory on the Earth’s surface based on latitude and longitude data received at a 50ms interval. The challenge arises when enabling the Cesium dynamic camera, as the Unity world coordinate origin undergoes constant changes during camera movements. I am seeking clarification on whether there might be a conflict between the Dotween plugin, which relies on Unity world coordinates, and the dynamic camera in Cesium.


  1. Does the dynamic movement of the Cesium camera introduce conflicts with the Dotween plugin’s functionality, specifically in managing smooth trajectory visualization based on Unity world coordinates?
  2. Are there any recommended practices or considerations to address potential conflicts when using Dotween alongside the Cesium dynamic camera for continuous trajectory animation?

Note: I am looking for insights on how to effectively combine Dotween’s capabilities with the dynamic camera in Cesium, considering the dynamic changes in Unity world coordinates during camera movements. Any advice or alternative approaches would be highly appreciated.

Hi @jh007,

Our team isn’t familiar with the Dotween plugin, but I’ll attempt a response. :sweat_smile:

If the Dotween plugin visualizes a trajectory using Unity coordinates, then it unfortunately will be a problem when combined with CesiumOriginShift on the DynamicCamera. Since the origin will shift with the camera’s movement, the curve will appear to move with the camera.

You may have to use CesiumGlobeAnchor to translate the desired latitude / longitude data to its corresponding Unity position. The CesiumGlobeAnchor will update whenever the CesiumGeoreference changes, so it will automatically account for the origin shifting, and keep the objects at the same globe-relative coordinates.

1 Like