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
I am attempting to simulate a camera on the default drone with airsim that is as close as possible to a camera I want to use in real-life. However, I'm finding that the FOV functionality in airsim isn't suitable for fisheye lenses. I want to use a 185 degrees FOV on my camera, however, when I configure the simulation to use these settings the results are bizarre, and highly unrealistic. Everything becomes warped and the camera perspective is completely wrong.
I have captured screen shots of what the ue4 shows vs what the simulated camera shows (this is for a custom 3d environment). The simulated camera is face down on the drone.
You can probably guess which one is which.
I used the following settings.json for the simulation:
This issue has been automatically marked as stale because it has not had activity from the community in the last year. It will be closed if no further activity occurs within 20 days.
Hello
I am attempting to simulate a camera on the default drone with airsim that is as close as possible to a camera I want to use in real-life. However, I'm finding that the FOV functionality in airsim isn't suitable for fisheye lenses. I want to use a 185 degrees FOV on my camera, however, when I configure the simulation to use these settings the results are bizarre, and highly unrealistic. Everything becomes warped and the camera perspective is completely wrong.
I have captured screen shots of what the ue4 shows vs what the simulated camera shows (this is for a custom 3d environment). The simulated camera is face down on the drone.
You can probably guess which one is which.
I used the following
settings.json
for the simulation:Is there any way the FOV calculations could be re-written so that they are more realistic?
Let me know if you require any more information.
The text was updated successfully, but these errors were encountered: