Coordinate system move performance depends on rover traverse size

[gpaar]

When a large traverse is loaded (e.g. Mars 2020, in particular MSL), moving the coordinate frame results in several seconds of waiting time. It looks as if the change of geographic vertical results in re-calculation of all virtual rover positions / individual coordinate frames gaining huge additional workload for the system, which should be avoided.
It shall be checked if the same applies to scale bars that have been defined as vertical / horizontal and other such entities.