https://community.cadence.com/cadence_technology_forums/physical-system-simulation/virtual-test-drive/en-USTelligent Community 13https://community.cadence.com/cadence_technology_forums/physical-system-simulation/virtual-test-drive/f/virtual-test-drive-x/74708/understanding-the-vtd-rdb-documentation/1434940Mon, 05 Oct 2026 06:00:00 GMT75bcbcf9-38a3-4e2e-b84b-26c8c46a9500:e31c509a-49d9-4772-a77d-2e9c2531e2c1Mayuresh SuryawanshiRDB (Runtime Data Bus) documentation is one of the most important references when working with VTD integrations, ADAS validation, vehicle dynamics, sensors, HIL systems, or custom applications. The documentation explains every RDB package, structure, enum, bitmask, and protocol definition used by VTD. To know more about RDB refer: RDB in VTD Opening the RDB Documentation You can open the RDB documentation using either of the following methods: Option 1: From VTD GUI Open VTD GUI → Docs → Open Docu → RDB Option 2: Directly from the installation directory → Doc → RDB_HTML → index.html Understanding the RDB Documentation Layout The RDB documentation is divided into four major sections: RDB Change Log Modules Data Structures Files 1. RDB Change Log The Change Log contains the history of modifications made to the RDB across VTD releases. 2. Modules The Modules section acts as the dictionary of RDB, containing all package IDs, enums, constants, and bitmasks that help you understand what a package represents and how to interpret the values stored inside its fields. The Modules section is further divided into four major categories. A. General Definitions Contains the fundamental RDB protocol constants and settings, such as communication ports, protocol version, message validation values, and other definitions that govern how RDB communication operates. These values define the basic behavior of the RDB protocol. For example: RDB_DEFAULT_PORT = 48190 tells us that the default RDB communication port is: 48190 Similarly RDB_VERSION identifies the version of the RDB protocol. When to use it? Use this section when: Configuring TCP/UDP connections Verifying protocol versions Debugging communication issues B. Array Sizes Contains fixed-size buffer definitions. Examples: RDB_SIZE_OBJECT_NAME = 32 RDB_SIZE_FILENAME = 1024 Many RDB structures use these constants. Example: char name[RDB_SIZE_OBJECT_NAME]; which becomes: char name[32]; Example Suppose an object name is: Ego Internally VTD reserves 32 bytes for the field regardless of the actual string length. Understanding these constants is important when writing custom parsers. C. Enum Definitions This is one of the most frequently used sections. It contains all RDB enumerations (enums), such as RDB_PKG_ID , RDB_OBJECT_TYPE , RDB_SENSOR_TYPE , and RDB_COORD_TYPE , which define the possible values a field can take and help translate numeric values into meaningful RDB concepts. Enums represent a single valid value. Suppose an RDB package contains: pkgId = 9 Go to: Modules └── Enum Definitions └── RDB_PKG_ID You will find: RDB_PKG_ID_OBJECT_STATE = 9 Now we know package ID 9 represents Object State data. This is usually the starting point for understanding any package. D. Bitmask Definitions Bitmasks differ from enums because multiple values can exist simultaneously. This section contains RDB flag definitions where multiple states can be combined in a single field, helping decode status information such as vehicle lights, visibility flags, lane states, and wheel states using bitwise operations. In RDB, a bitmask packs multiple independent status flags into a single integer field, allowing multiple simultaneous states to be set and evaluated together using bitwise operations. Example A vehicle is braking while turning left. Instead of sending separate variables, RDB packs both states into one integer field using bitwise OR (|): Suppose we have Vehicle Light Field = 0x28 i.e. field: lightMask = (RDB_VEHICLE_LIGHT_INDICATOR_L | RDB_VEHICLE_LIGHT_REAR_BRAKE) = 0x20 | 0x08 = 0x28 (Binary: 0010 1000) From this, we can decode: Brake Light ON and Left Indicator ON at the same time. We can use it whenever a field contains multiple status flags packed into a single variable. 3. Data Structures The Data Structures section contains the actual RDB package definitions (C structures) that describe how simulation data such as vehicle states, road information, sensor data, and driver controls are organized and transmitted within an RDB message. This section answers: "How is the data organized?" It is divided into two sections: A. Data Structures Clicking a structure shows Structure Name, Data Fields, Detailed Description, Field Documentation Example: Reading RDB_OBJECT_STATE_BASE_t You may see fields such as: uint32_t id; uint8_t category; char name[32]; RDB_COORD_t pos; RDB_GEOMETRY_t geo; They describe: Field Meaning id Object ID category Vehicle, pedestrian, etc. name Object name pos Object position geo Length, width, height For example: ID = 1 Name = Ego Position = (100,20) Length = 4.8 m Width = 1.9 m This information is stored inside the Object State package. B. Data Fields Every structure page contains a Data Fields section. Data Fields is a reverse lookup section that helps you find which RDB structures contain a particular field name. Instead of asking "What fields are inside RDB_OBJECT_STATE_t?" it helps answer "Which structures contain the field playerId or pos?" Example 1: If you search for: playerId you'll see a list of structures such as: RDB_DRIVER_CTRL_t, RDB_ROAD_POS_t, RDB_WHEEL_BASE_t, RDB_ENGINE_BASE_t etc. Example 2: Using the Data Fields Section to Find Vehicle Velocity Suppose you want to find where vehicle velocity is stored in RDB . In Data Structures → Data Fields , search for: velocity or click on ‘v’ You may find only: velocity : RDB_DYN_2_STEER_t This indicates that velocity is used in a specific dynamics-to-steering interface package and is not the general vehicle speed field most users are looking for. Additionally, clicking on RDB_DYN_2_STEER_t navigates to the structure in which this velocity is stored. 4. Files The Files section contains the original source files used to generate the documentation. The most important file is: viRDBIcd.h Navigate to: Files → File List → viRDBIcd.h The Data Structure pages provide a readable format, but the source file provides the exact implementation. Example: typedef struct { uint32_t id; uint8_t category; uint8_t type; uint16_t visMask; char name[32]; RDB_GEOMETRY_t geo; RDB_COORD_t pos; } RDB_OBJECT_STATE_BASE_t; The source file shows: Exact field order Exact data types Reserved fields Array sizes Actual memory layout This is especially useful when developing: Python parsers TCP/UDP clients Shared memory applications Custom RDB tools Worked Example: How to Read an Unknown Package Suppose your RDB Viewer or parser reports: pkgId = 9 Step 1 Go to: Modules └── Enum Definitions └── RDB_PKG_ID Find: RDB_PKG_ID_OBJECT_STATE = 9 Now we know the package is: OBJECT_STATE Step 2 Go to: Data Structures └── RDB_OBJECT_STATE_t Step 3 Study the structure. You will find: RDB_OBJECT_STATE_BASE_t RDB_OBJECT_STATE_EXT_t Step 4 Open the referenced field definitions. For example: ‘category’ may refer to: RDB_OBJECT_CATEGORY Open the corresponding enum to decode the value. Step 5 If additional detail is needed, open ‘Files → viRDBIcd.h’ to view the exact implementation. Key Takeaway The easiest way to read RDB documentation is to start with the Package ID , identify the corresponding package from Modules → RDB_PKG_ID , open the associated structure under Data Structures , and then use the linked enums and bitmasks to decode individual field values. If you need exact implementation details, refer to Files → viRDBIcd.h , which serves as the source of truth for all RDB definitions. This workflow will help you efficiently understand and decode any RDB package available in VTD.https://community.cadence.com/cadence_technology_forums/physical-system-simulation/virtual-test-drive/f/virtual-test-drive-x/74708/understanding-the-vtd-rdb-documentationMon, 05 Oct 2026 05:17:00 GMT75bcbcf9-38a3-4e2e-b84b-26c8c46a9500:b4bb7544-ba72-4204-9ae6-2ab8712c550bMayuresh SuryawanshiHow to Read and Navigate the RDB Documentation in VTD? This Q&A has been posted by Cadence Technical Support for the benefit of our community members.VTDhttps://community.cadence.com/cadence_technology_forums/physical-system-simulation/virtual-test-drive/f/virtual-test-drive/74706/runtime-data-bus-rdb-in-vtd/1434934Thu, 01 Oct 2026 06:40:00 GMT75bcbcf9-38a3-4e2e-b84b-26c8c46a9500:4ebd6617-280e-4cc9-be25-36d392128507Mayuresh SuryawanshiRDB is VTD's real-time data communication channel . It continuously transfers information about everything happening in the simulation world during every simulation frame. Think of RDB as a live broadcast service running inside VTD. During each simulation step, VTD generates information such as, Vehicle positions, Vehicle speeds, Road geometry, Lane markings, Traffic signs and traffic lights, Sensor detections, Weather conditions, Camera images. Why Use RDB? RDB enables real-time communication between VTD and external applications for each frame. The data may be sent / received via TCP/IP, UDP or shared memory . RDB Transmits Data from VTD: VTD continuously generates simulation data and publishes it through RDB in the form of packages such as: Vehicle and object states (OBJECT_STATE) Road and lane information (ROAD_POS, LANE_INFO, ROADMARK) Traffic signs and traffic lights Sensor outputs Environment and weather conditions External tools such as model based development, ADAS algorithms, or XIL systems can read these packages to understand what is happening in the simulation. RDB Receives Data into VTD: RDB is not only for reading data. External applications can also send information back to VTD, such as: Driver commands (steering, throttle, brake) Vehicle dynamics outputs Engine and wheel data Object states from external simulators Custom control commands VTD then uses this information to update the simulation. How RDB Data is Organized? RDB data is organized into messages and packages . A message is like a container. Inside the container are one or more packages that carry specific information. For e xample: RDB Message: ├── OBJECT_STATE ├── ROADMARK ├── TRAFFIC_SIGN ├── SENSOR_OBJECT └── ROAD_STATE Each package has an identifier called pkgId that tells the receiver what type of information follows. Example: Understanding RDB_OBJECT_STATE_BASE_t One of the most important RDB packages is: RDB_OBJECT_STATE_BASE_t . This package contains the basic information describing an object in the simulation. Imagine an ego vehicle driving in a scenario: Vehicle Name Ego Vehicle ID 1 Position X=125.5, Y=20.3 Heading 90° Length 4.8 m Width 1.9 m Height 1.5 m Category Vehicle Type Car The same information is represented in RDB as: Message = RDB_OBJECT_STATE_BASE_t id = 1 name = "Ego" category = Vehicle type = Car pos = (125.5,20.3,0.0) geo = (4.8,1.9,1.5) parent = 0 visMask = Visible RDB contains a large number of package types and data. To explore more about RDB: Refer to the official Redmine Wiki: redmine.vtd.hexagon.com/.../Daten_aus_VTD You can also access the RDB documentation directly from VTD: Open VTD GUI → Docs → Docu RDB Or open VTD directory → Doc → RDB_HTML → index.htmlhttps://community.cadence.com/cadence_technology_forums/physical-system-simulation/virtual-test-drive/f/virtual-test-drive/74706/runtime-data-bus-rdb-in-vtdThu, 01 Oct 2026 05:59:00 GMT75bcbcf9-38a3-4e2e-b84b-26c8c46a9500:7b31d44d-3123-4233-aaa9-33dcb6237932Mayuresh SuryawanshiWhat is RDB in VTD? This Q&A has been posted by Cadence Technical Support for the benefit of our community members.VTDhttps://community.cadence.com/cadence_technology_forums/physical-system-simulation/virtual-test-drive/f/virtual-test-driveTue, 29 Sep 2026 14:43:00 GMT75bcbcf9-38a3-4e2e-b84b-26c8c46a9500:6afef15e-faa1-4f79-9c70-dc41fb42bc06https://community.cadence.com/cadence_technology_forums/physical-system-simulation/virtual-test-drive/f/virtual-test-drive-xTue, 29 Sep 2026 14:43:00 GMT75bcbcf9-38a3-4e2e-b84b-26c8c46a9500:ff9b462f-f516-490d-aa54-2ddbdbc2f872https://community.cadence.com/cadence_technology_forums/physical-system-simulation/virtual-test-drive/Tue, 29 Sep 2026 14:43:00 GMT75bcbcf9-38a3-4e2e-b84b-26c8c46a9500:29720601-7403-4bc6-804f-d98eb307bec6https://community.cadence.com/cadence_technology_forums/physical-system-simulation/virtual-test-drive/f/virtual-test-drive/74701/ackermann-steering-vtd/1434924Mon, 28 Sep 2026 01:27:00 GMT75bcbcf9-38a3-4e2e-b84b-26c8c46a9500:cd64b5c8-1b1f-45b3-990c-0978ceb476bbAjay GopidasIn Classic VTD, you can switch from the legacy steering algorithm to Ackermann steering, which uses an ideal 3-wheel model calculation to determine the steering angle toward the next waypoint. Depending on your VTD version and whether you want to enable it for a single vehicle or globally, you have two options: Option 1: Enable for a Single Vehicle (VTD 2024.2 and newer) You can enable Ackermann steering for an individual player at runtime via an SCP command: (Replace "Ego" with the specific player/vehicle name if different.) Option 2: Enable Globally for All Vehicles (VTD 2026.1 and newer) To apply the Ackermann steering calculation across all vehicles in your simulation, add the " -steeringAckermann " option to your simServer configuration file:https://community.cadence.com/cadence_technology_forums/physical-system-simulation/virtual-test-drive/f/virtual-test-drive/74701/ackermann-steering-vtdMon, 28 Sep 2026 01:17:00 GMT75bcbcf9-38a3-4e2e-b84b-26c8c46a9500:c0f714eb-3f0e-43ae-82f8-ee04330e6096Ajay GopidasHow to Enable Ackermann Steering in Classic VTD This Q&A has been posted by Cadence Technical Support for the benefit of our community membersVTDhttps://community.cadence.com/cadence_technology_forums/physical-system-simulation/virtual-test-drive/f/virtual-test-drive/74322/run-perceptionsensor-plugin/1432799Fri, 31 Jul 2026 09:45:00 GMT75bcbcf9-38a3-4e2e-b84b-26c8c46a9500:392a6836-7c78-4d1f-bf8f-ef7ecad03459Ajay GopidasThis article walks through the steps required to set up and run the PerceptionSensor plugin in VTD. Before proceeding, ensure that all system requirements and prerequisites have been met as outlined in the PerceptionSensor in VTD article. Step 1 — Extract the Add-on Package Place the add-on .tgz file alongside your VTD installation directory and extract it from the parent directory: cd /path/to/parent_directory_containing_VTD tar xfzv VTD_202x.x_addOns.PerceptionSensor.yyyyyyyy.tgz This will extract the PerceptionSensor files into the following location within your VTD directory structure: VTD.2024.3/Runtime/Addons/PerceptionSensor/ Step 2 — Install the LLVM C++ Standard Library PerceptionSensor requires libc++, the LLVM C++ Standard Library. Installation steps vary by operating system: Ubuntu: sudo apt install libc++-dev Rocky Linux (VTD 2026.1 and later): Navigate to the following directory and extract the provided archive: cd [VTD_ROOT]/Runtime/Addons/PerceptionSensor/ tar xvfz libc++.tgz Step 3 — Verify the NVIDIA Driver Version Run the following command to check the currently installed NVIDIA driver version: nvidia-smi PerceptionSensor requires proprietary NVIDIA driver version 535.x . If PerceptionSensor fails to run or encounters rendering issues, downgrade/upgrade the driver to version 535.x . Step 4 — Select the PerceptionSensor Setup and Launch VTD Navigate to the VTD binary directory and start VTD with the setup selection flag: cd ~/tools/VTD.2024.3/bin ./vtdStart.sh -select From the list of available setups, choose one of the following: Standard.PerceptionSensor — basic PerceptionSensor with classic VTD traffic Standard.ScenarioEngine_PerceptionSensor_SE — PerceptionSensor with ScenarioEngine (if available in your version) Once the GUI opens, select the SampleProject.PerceptionSensor project. The required TaskControl settings are applied automatically for this project. If you intend to run a different project, the TaskControl settings must be configured manually. The following parameters are required: composeSingleMessage: true sendTrafficObjectCfg: true sendTrafficObjectCfgExtOnly: falsehttps://community.cadence.com/cadence_technology_forums/physical-system-simulation/virtual-test-drive/f/virtual-test-drive/74322/run-perceptionsensor-pluginFri, 31 Jul 2026 09:33:00 GMT75bcbcf9-38a3-4e2e-b84b-26c8c46a9500:5f209e0b-6f4b-4490-a79f-47c3c65050a7Ajay GopidasHow to Set Up and Run the PerceptionSensor Plugin This Q&A has been posted by Hexagon Technical Support for the benefit of our community membersVTDxVTDhttps://community.cadence.com/cadence_technology_forums/physical-system-simulation/virtual-test-drive/f/virtual-test-drive/74321/perceptionsensor-in-vtd/1432798Fri, 31 Jul 2026 09:09:00 GMT75bcbcf9-38a3-4e2e-b84b-26c8c46a9500:862417d4-849e-446d-98c8-9cdb00ef912cAjay GopidasPerceptionSensor integrates the Unreal Engine 5 rendering pipeline into VTD — the same pipeline used by VTDx. Designed for full compatibility with VTD's communication architecture, it works seamlessly alongside other VTD components. This compatibility is achieved through a new component called the Bridge , which connects VTD's RDB/SCP communication protocol with VTDx's DDS protocol while supporting both data structures. System Requirements To run PerceptionSensor, the following software and hardware are required: VTD SIMULATE or FULLSTACK package A valid PerceptionSensor license The PerceptionSensor add-on package An up-to-date Intel Core i7 or i9 CPU (Recommended: with a clock speed greater than 4 GHz) Note: For complex environments, more than 20 dynamic objects, or smoother frame rates, 16 GB VRAM is recommended. Prerequisites Before running PerceptionSensor, ensure the following dependencies and configuration settings are in place. LLVM C++ Standard Library The LLVM C++ Standard Library must be installed on the target system. Installation steps vary by operating system: Ubuntu: Run: sudo apt install libc++-dev Rocky Linux (VTD 2026.1 and later): Navigate to [VTD]/Runtime/Addons/PerceptionSensor/ and execute: tar xvfz libc++.tgz NVIDIA Driver Proprietary NVIDIA driver version ( 535.x Recommended) is required. TaskControl Configuration The following TaskControl settings must be configured in VTD Setup. When using Standard.PerceptionSensor , these settings are applied automatically: composeSingleMessage: true sendTrafficObjectCfg: true sendTrafficObjectCfgExtOnly: falsehttps://community.cadence.com/cadence_technology_forums/physical-system-simulation/virtual-test-drive/f/virtual-test-drive/74321/perceptionsensor-in-vtdFri, 31 Jul 2026 08:37:00 GMT75bcbcf9-38a3-4e2e-b84b-26c8c46a9500:e9105a21-04c4-45c7-9c1d-6e4ba428efc9Ajay GopidasWhat Is PerceptionSensor in VTD, and What Are Its Requirements and Prerequisites? This Q&A has been posted by Hexagon Technical Support for the benefit of our community membersVTDxVTDhttps://community.cadence.com/cadence_technology_forums/physical-system-simulation/virtual-test-drive/f/virtual-test-drive/74305/how-to-create-opencrg-single-objects/1432759Tue, 07 Jul 2026 02:03:00 GMT75bcbcf9-38a3-4e2e-b84b-26c8c46a9500:16f4564b-df72-445b-ac99-05d28fe927f3Stefan FinkThis is a guide for creating single OpenCRG objects for VTD. Please follow the steps consecutively. Create 3D mesh file Create your 3D mesh data in a tool of your choice Move the origin: x = center of your object, y = 0.0, z = cut plane with the road Convert the 3D mesg data to a supported OpenSceneGraph supported file format (tested: flt , osg , osgb , ive ) Save file to VTD/Data/Distros/Distro/Databases/ObjectsCommon [Optional] Create 3D Mesh stencil object for cut in objects If the object will will cut in to the road surface (e.g. manhole or pothole) a stencil object needed to be created The stencil object should be the intersection plane of your object with the road surface (e.g. a circle for manhole) Move the origin to the same point as your 3D mesh object Save file to VTD/Data/Distros/Distro/Databases/ObjectsCommon Start SurfaceAnalyzer cd VTD/Runtime/Tools/SurfaceAnalyzer ./startSurfaceAnalyzer.sh Select 3D mesh file Select File -> Import -> Mesh in upper tool bar Browse to your 3D mesh file e.g.: VTD/Data/Distros/Distro/Databases/ObjectsCommon/MiscManhole02.ive Click on button Open Create OpenCRG data Move mouse with left button to preview object (right button zoom) Change your U and V resolution accordingly to your needs Click on button Send Height Data Wait Save OpenCRG data Move mouse with left button to preview object (right button zoom) Check resolution. Start from Select 3D mesh file for changing the resolution Select File -> Save -> CRG File in upper tool bar. Save file to the OpenCRG folder: VTD/Data/Distros/Distro/Databases/ObjectsCommon/CRG Create XML configuration file Create a file e.g. MyManhole.xml and copy above content and place in Data/Distros/Distro/Config/Players/Objects Set in tag Model the the attribute ID to a unique name Set in tag ObjectTemplate the the attribute name to the same name Set in tag Graphics the the attribute model to the same name Set in tag Model the filename to the filename of your 3D mesh file in VTD/Data/Distros/Distro/Databases/ObjectsCommon Set in tag Geometry the attributes length, width, height accordingly to your bounding box (see information in SurfaceAnalyzer) Set in tag Geometry the the attribute originOffsetX to -length*05 Make sure that traffic="false" in tag Visibility Set in tag OpenCRG the the attribute crgFile to your OpenCRG file in VTD/Data/Distros/Distro/Databases/ObjectsCommon/CRG (e.g. ObjectsCommon/CRG/MyManhole.crg) [Optional] Add to your Graphics tag for cut in objects Test OpenCRG files Start VTD with setup OpenCRG [Optional] If you want to use your own setup and want to test cut in objects, you need to add the attribute stencilBits="1" to the RenderSurface tag in *CfgDisplay.xml (make sure it is not overwritten by scripts or change it in the scripts directly) Start ScenarioEditor Create an object and change the object definition to your new file (e.g. MyManhole) Run the simulation and have funhttps://community.cadence.com/cadence_technology_forums/physical-system-simulation/virtual-test-drive/f/virtual-test-drive/74305/how-to-create-opencrg-single-objectsTue, 07 Jul 2026 01:41:00 GMT75bcbcf9-38a3-4e2e-b84b-26c8c46a9500:6d7c7d9e-6017-4e39-bf2b-ae961416f873Stefan FinkThis Q&A has been posted by VTD Technical Support for the benefit of our community membershttps://community.cadence.com/cadence_technology_forums/physical-system-simulation/virtual-test-drive/f/virtual-test-drive/74272/bugreport/1432687Wed, 06 May 2026 05:58:00 GMT75bcbcf9-38a3-4e2e-b84b-26c8c46a9500:9dd13786-e7f0-49a0-8d45-4add1e0e51aaAjay GopidasIf you are reporting an issue in VTD, please include all relevant information that may help us reproduce the issue (e.g., screenshots, configuration files). VTD also provides a built-in option to generate a bug report containing most of the necessary information. When raising a ticket, please attach the file generated by this tool. A script is available to assist in collecting the required data , execute the script, and follow the on-screen instructions. You can find it in: Runtime/Tools/Bugreport To create the report: Open a terminal Navigate to: ... VTD.20xx.x/Runtime/Tools/Bugreport Run: ./vtdBugreport.sh After execution, you will see a message similar to: *************** Please send the file "/tmp/vtdBugreport.xxxxxxxx_xxxx.tgz" to VIRES . The indicated file is generated in the tmp directory Please attach the generated file to your ticket or share it with VTD support.https://community.cadence.com/cadence_technology_forums/physical-system-simulation/virtual-test-drive/f/virtual-test-drive/74272/bugreportWed, 06 May 2026 05:41:00 GMT75bcbcf9-38a3-4e2e-b84b-26c8c46a9500:858cc06d-e5ca-4506-ae7f-cd95be4a79f1Ajay GopidasHow to use the Bugreport tool to generate a report which will include most of the relevant information that might be needed to resolve an issue. This Q&A has been posted by Hexagon Technical Support for the benefit of our community membersVTDhttps://community.cadence.com/cadence_technology_forums/physical-system-simulation/virtual-test-drive/f/virtual-test-drive/74219/error-during-database-generation/1432562Mon, 23 Feb 2026 02:59:00 GMT75bcbcf9-38a3-4e2e-b84b-26c8c46a9500:725ec695-bc02-441b-9dc6-bc68079d7195Ajay GopidasThe error during database generation typically occurs due to an incorrect Python version or if Python is not properly configured. Please note the following version requirements: ROD versions up to 2023.4 require Python 2.7.15 for track generation. Untill Ubantu 20.04 : s udo apt-get install python Ubuntu 22.04 and later : sudo apt-get install python2 ROD 2024.1 and later versions require Python 3.8 or later for track generation. sudo apt-get install python3 Once the appropriate Python version is installed and configured, you can verify the active version using: python --version If multiple Python versions are installed, you may need to configure Python alternatives to switch between Python 2 and Python 3. Please follow the steps below to configure the correct Python version: Install Python 3 (if not already installed): sudo apt-get install python3 Check all available Python versions on your system: ls /usr/bin/python* Ensure the required Python version is listed. Check whether Python alternatives are already configured: sudo update-alternatives --list python (If alternatives are listed, note the selection numbers for the next step.) Configure Python alternatives (one for Python 2 and one for Python 3): sudo update-alternatives --install /usr/bin/python python /usr/bin/python2 1 sudo update-alternatives --install /usr/bin/python python /usr/bin/python3 2 Select the required Python version: sudo update-alternatives --config python Enter the selection number corresponding to the required version (Python 2 for ROD ≤ 2023.4, Python 3 for ROD ≥ 2024.1). Verify the active Python version: python --version If the issue persists after configuring the correct Python version, please reach-out to our support, and we will be happy to assist further.https://community.cadence.com/cadence_technology_forums/physical-system-simulation/virtual-test-drive/f/virtual-test-drive/74219/error-during-database-generationMon, 23 Feb 2026 02:43:00 GMT75bcbcf9-38a3-4e2e-b84b-26c8c46a9500:32c0bd01-d46b-490f-a4ce-f6f07d3b0bc9Ajay GopidasHow to eliminate the error that occurs during Database generation in ROD This Q&A has been posted by VTD Technical Support for the benefit of our community membersrodVTDhttps://community.cadence.com/cadence_technology_forums/physical-system-simulation/virtual-test-drive/f/virtual-test-drive/74199/generating-opendrive-and-visual-database-files-in-rod/1432528Tue, 03 Feb 2026 02:56:00 GMT75bcbcf9-38a3-4e2e-b84b-26c8c46a9500:d69f0cfe-1ba1-438b-a038-ea00690de1e4Ajay Gopidas1. OpenDRIVE File Generation OpenDRIVE ( *. xodr ) files are a core component of VTD/ VTDx simulations. They provide a logical description of the road network (layout file), including road geometry, lanes, junctions, road markings, and more related features. 1.1 Steps to Generate an OpenDRIVE file Save the .tdo file From the top menu bar, select Generate . Click OpenDRIVE . 1.2 Steps to Export an OpenDRIVE file Open the File menu. Select Export . Choose the required OpenDRIVE version (for example, OpenDRIVE 1.8 ). 2. Visual Database ( Scenegraph ) Generation The Visual Database represents the graphical (3D) view of the environment . ROD currently supports the FLT , IVE , and OSGB formats. 2.1 Default Database Generation Click the Generate Database icon in the left toolbar. The complete 3D world is generated and stored in the project’s database directory as an FLT, IVE, or OSGB file. The generated database is automatically opened in the selected database viewer. ROD remains usable during the time this file is made or is opened . Only selected tracks are generated; if no track is selected, the entire database is generated. Generation behaviour can be configured in Project Settings (Section 3) . 2.1 Database Generation using Defined Area Select the Set Generation Area icon from the left toolbar. Draw a rectangle over the desired region in the main window. The database generation icon changes to indicate partial generation. Click the icon to generate only the marked area. 3. Project Settings 3.1 Database Generation Configuration Generation settings are available in Project Settings → DB Generation . The output file format may be changed either to FLT, IVE or OSGB. Note that some features are only available for OSGB files. The landscape configuration may be changed by the generation mode combo box to following modes: Landscape only Landscape with base signals Landscape with base and extra signals Base and extra signals Extra signals 3.2 Database Generation Modes Databases can be generated in two modes: HCS (High Contrast Sky) – Default mode. PBR (Physically Based Rendering) – Provides higher model detail and more realistic lighting. Model must support PBR. If no compatible PBR model is available, the model will not appear in the database. The default mode is HCS, PBR must be enabled in Project Settings before generation. When creating overlays, externals can be filtered using the HCS and PBR buttons and the following combinations are possible : Features: Additional visual features can be enabled via the GUI. Each enabled feature generates a separate database file. Available features depend on the installed ROD version. Options Copy FLT and/or intermediate files to the project directory for debugging. Optionally delete track or build directories after generation. Select the default database viewer ( OSGViewer or VIGViewer ) and enable or disable automatic opening. Define additional TRACK arguments (recommended for advanced users only). Select the Database Generation Tool : Default: Track Optional: TrackGenerator (generate required files for USD exports in VTDx ) Saved settings are applied to future database generation runs. HCS : Shows externals with HCS models only PBR : Show externals with PBR models only HCS + PBR : Shows only externals supporting both HSC and PBR modes 3.3 OpenDRIVE Export Configuration OpenDRIVE export settings are configured in Project Settings → Export . Logic Export Options Logics complete Logics with base signals Logics with extra signals Object outline type when importing OpenDRIVE files containing CornerLocals or CornerRoads . Export style definition: It is possible to export the pavement styles and fillets as OpenDRIVE user data. Export objects: As an Overlay may have many Externals, the OpenDRIVE file can become very large . If you do not need these objects you can switch them off.