monoDrive Simulator

Linux

Simulator

Extract the archive to a common location like ~/monodrive.
If downloading for the first time, you will need to download the license.txt file through your account on monoDrive.io, unless one has been provided directly from monoDrive. Copy the attached license.txt file to the extracted location ~/monodrive/VehicleAI/license.txt.
Run the simulator by navigating the ~/monodrive/VehicleAI directory and running the shell script VehicleAI.sh -opengl.

Extract the archive to a common location like ~/monodrive.
If downloading for the first time, you will need to download the license.txt file through your account on monoDrive.io, unless one has been provided directly from monoDrive. Copy the attached license.txt file to the extracted location ~/monodrive/VehicleAI_Editor/license.txt.
Clone Unreal Engine: branch 4.25.4.
Extract the Plugins.zip archive into the 4.25.4 Engine's Plugins directory. e.g. if the UE4.25.4 branch is cloned at /usr/local/UE_4.25.4, then extract the archive into /usr/local/UE_4.25.4/Engine/Plugins. The resulting directory structure should look as follows:
```
  /usr/local/UE_4.25.4/Engine/Plugins/monoDrive
    +-- monoDriveRadarSensor
    +-- monoDriveLidarSensor
    +-- ... (other monoDrive plugins)
  
```
Setup & Generate Visual Studio project files. Open the terminal in the Unreal Engine Folder, /usr/local/UE_4.25.4/, and run these commands.
```
      $ ./Setup.sh
      $ ./GenerateProjectFiles.sh
      $ make
    
```
Afterwards to launch the Scenario Editor or Simulator:
```
    ${UE4_ROOT}/Engine/Binaries/Linux/UE4Editor ${SIMULATOR_ROOT}/Simulator/VehicleAI.uproject
  
```
Note that the editor may take a long time to compiling shaders, and may appear to get stuck at 95% or 99%. This is expected and you will need to wait for the compiling to finish. If no error is reported then the system is still compiling shaders, this only happens the first time opening.