-
Notifications
You must be signed in to change notification settings - Fork 39
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
Cannot use WASD controls in scenario_runner #24
Comments
Also, when I run this code, I typically only complete 1-10% of the scenarios. I tend to freeze at traffic lights/ intersections. Is this normal? |
Hi @aureliuszi thanks for the details, some more questions come to mind:
My first thoughts are that there is some input conflict happening, such as between the AI driver and your WASD inputs, but I'm not convinced. |
Hi @GustavoSilvera !
|
Okay, since this sounds like a scenario-runner only problem, have you tried rebuilding the DReyeVR PythonAPI ( We will try to reproduce this bug and gather more information. Also, is this on DReyeVR [main] or DReyeVR [dev] branch? Just so we can tune our testing accordingly. |
Also, we think there might by some backend autopilot stuff happening with scenario_runner itself (like, turning on the EgoVehicle's Autopilot without explicitly running |
|
Just tested again.
Carla pulls up and I am able to WASD
I am automatically advancing forward (without launching DReyeVR_AI.py or pressing any keys). To be honest, I am unsure about whether or not I am able to press 3 to enable autopilot because I start in what appears to be autopilot, and even when I try to activate manual control the response is minimal |
Gotcha, sounds like the autopilot is automatically being activated here (bug). When you are in this "ghost autopilot" mode can you press 1 to return EgoVehicle possession to the player? |
Pressing 1, 2, 3 should change who gets control of the EgoVehicle by toggling who is in possession of the EgoVehicle. Pressing 1 (should) return the control to the player, pressing 2 should allow the player to fly around as a spectator, and pressing 3 should provide control to the AI |
So scenario 2 is the only one that the car somewhat completes (about 40%) because there are no intersections or traffic lights during the first part. In scenario 2, which I activated by running the code below, I was unable to press 1, 2, or 3. The car had no response and proceeded to drive itself.
|
Gotcha, okay this is not expected behaviour and we will be investigating further. Are you testing the |
I have yet to rebuild, will probably do that tomorrow. |
Hi @GustavoSilvera ! We have rebuilt everything using The autopilot starts first. We are able to enter manual control by pressing 1 as long as we are not at an intersection. When we reach an intersection, we stop moving. Trying to use 1 to enter into manual mode (and start moving again) doesn't work and results in the unstable motion as shown in the video I sent you. There seems to be a problem with the intersection traffic logic. Note in the images below that the traffic lights that are perpendicular to each other appear to be the same color at the intersection at which we are unable to move. This happens across all intersections in all scenarios. |
Thanks for all the detailed info @aureliuszi ! Development is a bit slow at the moment since I am traveling but I will investigate this problem more this week. It looks like the routes have some kind of specific intersection logic to override all vehicle inputs and play some specific scenario (hence the multiple adjacent green lights). |
Hi @aureliuszi just wanted to let you know that I have been able to reproduce the bug and will have a patch out on |
Okay, @aureliuszi this is a mini-patch for now (upstream incoming) I think this will work for you: Go to if spawn_point: with if spawn_point and "dreyevr" not in blueprint.id: |
(Also, |
@GustavoSilvera Just followed your instructions above and it works! Thank you so much for all of your help :D |
Hey, @aureliuszi please check out the upgrading-DReyeVR section of the documentation to pull from |
Hello again friends!
I am having trouble using WASD (manual) controls in scenario_runner. I use the following commands below:
And when I try to manually control the vehicle, I am moving at speeds of 1-2.
A few things of note:
CarlaUE4.exe
I am able to WASD the vehicle without any issues.Thanks!
The text was updated successfully, but these errors were encountered: