A plugin for GTAV that transforms it into a vision-based self-driving car research environment. This repo outputs HD images, LiDAR, depth, stencil, and labels in KITTI and augmented formats. Please cite our work, the PreSIL dataset for autonomous vehicle perception (https://arxiv.org/abs/1905.00160) if using this repo.
To download pre-generated data see: https://uwaterloo.ca/waterloo-intelligent-systems-engineering-lab/presil-dataset-downloader
Visualization and tools to work with the data can be found here: https://github.com/bradenhurl/PreSIL-tools
Visualizations from the PreSIL Dataset:
Image with 2D Boxes
Pointcloud with 3D Boxes
Linearized Depth Buffer
Linearized Depth Buffer shown in color
Instance Level Object Segmentation
Stencil Buffer
If installation was successful, GTAV will automatically load the DeepGTAV plugin. Once the game starts DeepGTAV will wait for TCP clients to connect on port 8000.
Clients connected to DeepGTAV are allowed to send messages to GTAV to start and configure the research environment (Start and Config messages), send driving commands to control the vehicle (Commands message) and to stop the environment to fallback to normal gameplay (Stop message).
When the environment has been started with the Start message, DeepGTAV will start sending the data gathered from the game back to the client in JSON format, so the client can use it to store a dataset, run it through a self-driving agent...
The data sent back to the client and intitial conditions will depend on the parameters sent by the client with the Start or Config messages. Things that can be controlled for instance are: rate of transmission, frame width and height, weather, time, type of vehicle, driving style, wether to get surrounding vehicles or peds, type of reward function and a large etc...
VPilot provides a nice interface and examples written in Python to use DeepGTAV for your self-driving car research.
The following chapters describe the purpose and contents of each message.
Messages must be always be sent in two steps: First send the JSON message length in bytes and then send the message itself, this is done so DeepGTAV knows when to stop reading a message.
This is the message that needs to be sent to start DeepGTAV, any other message sent prior to this won't make any effect. Along with this message, several fields can be set to start DeepGTAV with the desired initial conditions and requested Data transmission.
When this message is sent the environment starts, the game camera is set to the front center of the vehicle and Data starts being sent back to the client until the client is disconnected or an Stop message is received
Here follows an example of the Start message:
{"start": {
"scenario": {
"location": [1015.6, 736.8],
"time": [22, null],
"weather": "RAIN",
"vehicle": null,
"drivingMode": [1074528293, 15.0]
},
"dataset": {
"rate": 20,
"frame": [227, 227],
"vehicles": true,
"peds": false,
"trafficSigns": null,
"direction": [1234.8, 354.3, 0],
"reward": [15.0, 0.5],
"throttle": true,
"brake": true,
"steering": true,
"speed": null,
"yawRate": false,
"drivingMode": null,
"location": null,
"time": false
}
}}
The scenario field specifies the desired intitial conditions for the environment. If any of its fields or itself is null or invalid the relevant configuration will be randomly set.
The dataset field specifies the data we want back from the game. If any of its fields or itself is null or invalid, the relevant Data field will be deactivated, except for the frame rate and dimensions, which will be set to 10 Hz and 320x160 by default.
This message allows to change at any moment during DeepGTAV's execution, the initial configuration set by the Start message.
Here follows an example of the Config message (identical to the Start message):
{"start": {
"scenario": {
"location": [1015.6, 736.8],
"time": null,
"weather": "SUNNY",
"vehicle": "voltic",
"drivingMode": -1
},
"dataset": {
"rate": null,
"frame": null,
"vehicles": false,
"peds": true,
"trafficSigns": null,
"direction": null,
"reward": null,
"throttle": null,
"brake": false,
"steering": false,
"speed": true,
"yawRate": null,
"drivingMode": null,
"location": null,
"time": true
}
}}
In this case, if any field is null or invalid, the previous configuration is kept. Otherwise the configuration is overrided.
As simple as it seems, this message can be sent at any moment during DeepGTAV's execution to control the vehicle. Note that you will only be able to control the vehicle if drivingMode is set to manual.
Here follows an example of the Commands message:
{"commands": {
"throttle": 1.0,
"brake": 0.0,
"steering": -0.5
}}
Stops the environment and allows the user to go back to the normal gameplay. Simply disconnecting the client produces the same effect.
Here follows an example of the Stop message:
{"stop": {}}
DeepGTAV will always send the messages in two steps: First it will send the message length in bytes and then it will send the message itself, so the client can know when to stop reading it.
The messages rate and content will depend on the configuration set by the Start or Config messages, and are always sent consecutively (Frame, Data).
This is a byte array containing the RGB values of the current GTAV screen (resized to the specified width and length). Make sure the window is not minimized, otherwise the values will be all zeroes (black).
DeepGTAV generates a useful log file named deepgtav.log in GTAV's installation directory. Please attach it in your issue when reporting any bug.
TODO:
Repo was originally cloned from: https://github.com/aitorzip/DeepGTAV