-
Notifications
You must be signed in to change notification settings - Fork 4.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
msgpackrpc.error.RPCError While Running AirSimNH and hello_drone.py #3917
Comments
You're using the latest master Python package which doesn't work with the 1.5 release binaries for the Camera APIs due to #3320. Try with the 1.5.0 Python package |
@rajat2004 , thank you for the quick reply. which Python package are you referring to? the AirSim python package? could you give some quick instructions on how to fix it? thank you! |
Install the |
this worked! thank you very much! |
Bug report
What's the issue you encountered?
I am getting the following error when running hello_drone.py while using the AirSimNH environment:
I run the AirSimNH executable, and then launch the hello_drone.py script and this is what occurs once it gets to the image calls.
Settings
I am using the following settings in my setttings.json file:
How can the issue be reproduced?
Include full error message in text form
Traceback (most recent call last):
File "hello_drone.py", line 57, in
airsim.ImageRequest("1", airsim.ImageType.Scene, False, False)]) #scene vision image in uncompressed RGBA array
File "/home/AirSim/PythonClient/airsim/client.py", line 266, in simGetImages
responses_raw = self.client.call('simGetImages', requests, vehicle_name, external)
File "/home/.local/lib/python3.6/site-packages/msgpackrpc/session.py", line 41, in call
return self.send_request(method, args).get()
File "/home/.local/lib/python3.6/site-packages/msgpackrpc/future.py", line 45, in get
raise error.RPCError(self._error)
msgpackrpc.error.RPCError: rpclib: function 'simGetImages' (called with 3 arg(s)) threw an exception. The exception is not derived from std::exception. No further information available.
The text was updated successfully, but these errors were encountered: