JSBSim Compatible UAV Visualization Environment

Objective & Overview: The object of this engagement is to design a simulation environment in unity/unreal engine to perform SIL of UAVs. The Environment shall: Take UAV’s position, velocity and state related data over JSBSim property tree. Have provision to add and define 3D UAV models. Have provision to add sensors like Visible Light and Infrared Cameras and Rangefinders Simulate one or multiple vehicles (up to 7) simultaneously. Must be executable on windows & ubuntu. Must be compatible with Nvidia Graphic Cards. Detailed Technical Requirements: Scene Requirements: The simulation must support multiple weather conditions, such as rain, storms, fog, and haze, across a full 24-hour day–night cycle. The scene shall include premodeled landscapes such as mountains, plains, coastlines, airports, and cityscapes, with support for dynamic vegetation, water bodies, and seasonal variations. The system must provide terrain Level of Detail (LOD) optimization for smooth rendering from low-altitude to high-altitude flight. Provision shall be available to import custom landscapes and scenery assets using FlightGear-native formats (.ac, .xml, TerraSync tiles) as well as .STEP, .OBJ and .STL files. Scene Entities Requirements: The primary scene entity shall be an Unmanned Aerial Vehicle (UAV/drone). The simulator shall support the addition of custom scene entities, with up to seven active entities simultaneously. Each entity must follow a standardized definition format containing hierarchical sub-entity naming, kinematic state variables, unique ID, and payload sensor configurations. Each scene entity shall support dynamic state parameters including latitude, longitude, altitude, roll, pitch, yaw, velocity, and acceleration. The standard entity definition format shall support configurable payloads including cameras, LiDAR, GPS, IMU, and communication sensors. Communication Requirements: The simulator shall support bidirectional communication with JSBSim property tree. The interface must support entity initialization, real-time state synchronization, and lifecycle updates for multiple scene entities. Visualization & User Requirements: The simulator shall provide multiple visualization modes including chase view, FPV view, top-down map view, and free camera mode. The user shall be able to pause, resume, fast reset(~1 Sec), and adjust simulation playback speed in real time. The frontend shall maintain a minimum rendering performance of 60 FPS for up to seven active entities. The simulator shall have a HUD similar to the flightgear. The simulator shall support recording and replaying simulation sessions with timeline controls. The simulator shall provide configurable scene, camera, and rendering presets through external configuration files. The simulator shall provide debugging tools for packet inspection, entity state visualization, and performance monitoring. Sensor Data Requirements: The simulator must support the following sensors: Multiple Cameras ( Visible Light and Infrared ) LiDARs Gimbal The data of these sensors should be transferred realtime. The sensors should be able to be configured over configuration files. Deliverables: Simulation Executable: Windows 11 Ubuntu 22.04 and Ubuntu 24.04 Simulation & Environment Source Code Documentation: Explaining Configuration Files Explaining Entity Definition & Process Explaining Landscape Definition & Process Explaining Sensor Definition & Process Explaining Communication Explaining the Source Code Default Landscape & Entity: Default Landscape: City Landscape Default UAV: Quadrotor Milestones: Basic Simulation Environment with a simple scene and entity to test communication. Testing of entity motion with the communicated property tree Testing of multiple entity motion with the communicated property tree Testing of different sensor payload Simulator Performance analysis with Multiple payloads and entities. Final Delivery Acceptance Criteria: The Simulator must work smoothly with multiple sensors and entities The Simulator must work at 60Hz with all the sensors and entities at use. No Bugs and Exceptions Must Fulfil all the Requirements Final Acceptance Require Validation for the Client, failure in any of the given technical requirements would result in non acceptance. Roles & Responsibilities: Client Provide requirements and reference inputs Provide feedback within 24–48 hours Conduct validation testing Vendor Execute design and development Ensure manufacturability Support bring-up and debugging Testing & Validation: Testing at every milestone. IP Ownership & Licensing: Full ownership transferred to client: Executable Source Code Source Environment Documentation Vendors shall not reuse or distribute source code without written consent. Support Period: 60-90 Days post-delivery support for: Bug Fixes Minor Corrections Excludes major redesigns or scope changes Termination Clause Either party may terminate with written notice Payment due for completed milestones Vendor must transfer all completed work upon termination References: Flightgear Microsoft flight Simulator AirSim Physics Engine: https://jsbsim.sourceforge.net