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
When I run Carla consecutively for a few hours (1hour - 3hour) I will got stuck when trying to spawning a collision sensor ('sensor.other.collision'). But right before spawning the collision sensor, I am able to spawn a vehicle. When getting stuck, the carla keep printing the message of "Task graph took xx ms for RT to receive broadcast", as shown in the yellow text above.
This issue randomly appears, in the sense that sometimes it will not get stuck at that position. When it does not get stuck, it will print out the following logging message:
The text was updated successfully, but these errors were encountered:
Hi @gy20073 , have you solved this problem. I got the same problem. The server will not get stuck after hundreds of episodes of training. The FPS of client drops to 0. I also create an issue here #1840. Thank you!!
Currently we have not detected that problem, but if the frame rate is low the Unreal can show those yellow warning meaning that by some reason some resource is taking more time than expected. Did you try using synchronous mode?
carla version: 0.9.5
os: 16.04
GPU: V100, driver, 396.26
When I run Carla consecutively for a few hours (1hour - 3hour) I will got stuck when trying to spawning a collision sensor ('sensor.other.collision'). But right before spawning the collision sensor, I am able to spawn a vehicle. When getting stuck, the carla keep printing the message of "Task graph took xx ms for RT to receive broadcast", as shown in the yellow text above.
This issue randomly appears, in the sense that sometimes it will not get stuck at that position. When it does not get stuck, it will print out the following logging message:
![image](https://cdn.statically.io/img/user-images.githubusercontent.com/6026892/56877234-63008200-6a01-11e9-8c89-5591189fc9ef.png)
The text was updated successfully, but these errors were encountered: