Open Leviathan321 opened 5 months ago
Hi, 0.2s seems very slow indeed, are you creating multiple large-resolution camera sensors? If not, maybe you have some software installed that filters/slows the connection? If you share your script (here or to tech@beamng.gmbh), we can try to run it and test its performance at our machine.
Actually, I am directly using the code from the competition here: https://github.com/sbft-cps-tool-competition/cps-tool-competition. I have tried the code on different machines. I was running it on
There was a similar problem...
I am doing research with beamng and I am using basically a driving controller which has to retrieve the camera images to process and to calculate driving commands (similiar to here: https://github.com/sbft-cps-tool-competition/cps-tool-competition).
However, I am facing the problem that retreiving the sensor data and as well other state information takes roughly 0.20 s (BeamNG 0.26.2).
It looks to me that the socket communication is very slow. Did anyone had similar issues before?