You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the updateKinematics function in PawnSimApi (line 485 - 500), the linear twist is being transformed using the toLocalNed function from NedTransform.cpp (line 29 - 34). This function subtracts a ned_offset from the position, but in the updateKinematics function, the velocity is the input to toLocalNed(position). Since I have an Ned offset of {X=5690.00000 Y=-350.000000 Z=18.9090881 }, my linear velocity is having this offset (scaled with 1/100) when playing the game.
Question: I'm trying to fix this by having the originGeoPoint and PlayerStart in the settings such that there is no ned offset in the code now. Is there any other way that I can get a correct linear velocity? Maybe making a toLocalNed function for transforming velocity (only scaling and not translating?).
The text was updated successfully, but these errors were encountered:
Lotjeotje
changed the title
Question/bug: NED offset in linear velocity (wrong use of toLocalNed() in updateKinematics())
Bug: NED offset in linear velocity (wrong use of toLocalNed() in updateKinematics())
Nov 28, 2018
In the updateKinematics function in PawnSimApi (line 485 - 500), the linear twist is being transformed using the toLocalNed function from NedTransform.cpp (line 29 - 34). This function subtracts a ned_offset from the position, but in the updateKinematics function, the velocity is the input to toLocalNed(position). Since I have an Ned offset of {X=5690.00000 Y=-350.000000 Z=18.9090881 }, my linear velocity is having this offset (scaled with 1/100) when playing the game.
Question: I'm trying to fix this by having the originGeoPoint and PlayerStart in the settings such that there is no ned offset in the code now. Is there any other way that I can get a correct linear velocity? Maybe making a toLocalNed function for transforming velocity (only scaling and not translating?).
The text was updated successfully, but these errors were encountered: