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
Hi, I'm Jeonggi Yang in Republic of Korea.
We developed some simulators by using AirSim. Thanks you.
Recently, we found some bugs of Lidar offset function.
As you mention,
X Y Z | Position of the lidar relative to the vehicle (in NED, in meters)
in settings.h file.
But the lidar position is not moved when I set the X:5 and rotated the drone in the yaw directions
And in the code, Ray starting point is not affected with Drone's attitude.
Please, fix this phenomenon.
Thank you.
The text was updated successfully, but these errors were encountered:
Hi,
We developed some projects on old version. We didn't know that It was solved lately.
I think It is okay to close the issue.
Thank you.
-----Original Message-----
From: "Rajat Singhal"<notifications@github.com>
To: "microsoft/AirSim"<AirSim@noreply.github.com>;
Cc: "didwjdrl12"<qaz10987@naver.com>; "Author"<author@noreply.github.com>;
Sent: 2020-01-17 (금) 00:40:20 (GMT+09:00)
Subject: Re: [microsoft/AirSim] Lidar offset in the 'Setting.h doesn't' mean the 'relative' position to the drone body frame (#2385)
Hi, is this the behaviour with the latest master? #2143 has been merged which I think fixed this problem
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Hi, I'm Jeonggi Yang in Republic of Korea.
We developed some simulators by using AirSim. Thanks you.
Recently, we found some bugs of Lidar offset function.
As you mention,
X Y Z | Position of the lidar relative to the vehicle (in NED, in meters)
in settings.h file.
But the lidar position is not moved when I set the X:5 and rotated the drone in the yaw directions
And in the code, Ray starting point is not affected with Drone's attitude.
Please, fix this phenomenon.
Thank you.
The text was updated successfully, but these errors were encountered: