Thanks Kevin. Indeed there has been much confusion about the Cesium Georeference system.
Takeaways:
- Your recommendation would be to use v2.0 with sublevels instead of GlobeAnchorComponents
- I tried v2.0, but I documented some issues with the Atmosphere in my post. Reverting until that works:
- v2.0 issues
- There is usually ONE master Georeference, and that is the ‘Georeference Actor’ in the outliner
Could you please confirm?:
- ‘Fly To Location’ function DOES NOT actually rebase the Unreal world’s coordinates to the Georeference of the location that has been flown to? If I’m not using Sublevels, I DO need to call ‘Set Georeference Origin’ at the same time as ‘Fly To Location’ in order to make sure that the Unreal scene at that point is oriented correctly and has the correct accuracy?
- ‘Set Georeference Origin’ is the function to call to actually rebase the Origin. The other ‘Set Georeference’ functions are just storing a location which can be resolved later?
- Resolve Georeference and Set Georeference on CesiumGlobeAnchor Component do what exactly?
Thanks!