Hi, we are using AODT v1.3. During the configuration of simulations through the graphical interface of the AODT Launcher, we have experienced problems related to the positioning and mobility behaviour of UEs.
First, when a UE is positioned manually in the map and no mobility profile is assigned (fully static), the UE unexpectedly changes to random positions across the map when the mobility generation stage is started. This behaviour suggests that either the static configuration is being overridden internally, or that the mobility engine assigns random trajectories by default when no explicit profile is provided.
Inversely, when mobility is explicitly defined through waypoints to trace a specific route, the UE becomes completely static when the simulation starts, ignoring the predefined trajectory. This contradicts the expected behaviour, where the UE should follow the assigned path.
Any guess on what could happen? Thank you!