Simulation & model
The game or simulator name and version, the specific vehicle or model and any add-ons. Briefly describe what is missing and what you want to achieve.
ADAPTER GUIDE / COMMUNITY DEVELOPMENT
Your game or model is missing?
Bring it to the project.
Your game is not connected yet, or an existing adapter is missing your model? You can propose either. Aircraft, tank, truck or racing car: show us which simulation and model you use, which data you need and how you want to control your setup.
A shared foundation for different simulations.
A suitable adapter connects the usable data interface of a simulator or game and translates its values into the Live Hub data format. When your hardware follows this format, shared data can be processed across your own network for displays, controllers and your own developments.
YOUR INFORMATION PACKAGE
Show us what
your setup needs.
The more precisely you describe your model and its functions, the better we can assess its integration. Put together a clear package with the following information.
Annotated images
Detailed images from the simulation: cockpit, instruments, displays and control panels. Mark the relevant elements and explain the functions you want implemented.
Instruments & controls
What does each instrument show? Include values, units, ranges, states and warnings. For switches and controls, describe their positions, actions and feedback.
Interface & documentation
Link game manuals, API or SDK documentation and information about telemetry, inputs and outputs. If you do not know the data yourself, show us where the documentation is available.
Your hardware idea
Which switches, LEDs, displays or controllers do you want to connect? Include existing devices, your own electronics and sketches with dimensions, connections and the available space.
Your contribution
How can you help? For example with documentation, instrument knowledge, simulator testing, your own test setup or feedback on prototypes and development builds.
FROM PROPOSAL TO ADAPTER
Choose together.
Build together.
We review new proposals with the community. This directs development towards areas where demand, information and active participation come together.
- 01
Submit your package
Introduce your model and information package on our Discord. We discuss the idea there and gather open questions.
- 02
Review the interface & start a poll
We examine the usable interface, requested functions and development effort. We then present the proposal to the community for a vote.
- 03
More than 500 active supporters
When more than 500 users support the requested simulation or model and actively participate in implementation, we will develop an adapter or extend an existing one.
- 04
Develop, test & integrate
Together we clarify the functions, test the data and improve the integration. The finished adapter or model extension is then added to Live Hub.
HARDWARE IS SHAPED WITH YOU, TOO
You decide what you need.
And how you want to use it.
From sticks, rudder controls and pedals to panels, switches, compact desktop setups and complete cockpits: we want to develop suitable hardware from the needs of each simulator community.
Define functions together
Which controls are missing? Which feedback, layouts and dimensions make sense? Your experience should shape the solutions we take on.
Room for your own builds
Your own controllers and custom systems are part of the idea. The interface, shared data format and planned microcontroller workshop are intended to simplify the connection between simulator and your own hardware.
From test setup to product
Suggestions, practical experience and prototype tests feed into development. This should produce both ready-built 4SB solutions for beginners and expandable components for experienced cockpit builders.
Your needs set the direction.
So you can help decide what you use and how you use it. We want to give you suitable options instead of limiting your setup to a predefined solution.
Explore the community projectYOUR NEXT STEP
Bring your model.
We will take a look.
Join our public Discord community and introduce your proposal with its information package. Even if questions remain, share what you already know and tell us where you need help.
Introduce your proposal on Discorddiscord.gg/fbAj4n35JP
We use Discord for documentation, open questions and follow-up discussions. You do not need to share an email address with us. For confidential information, we first arrange a private conversation there.
Only share images and documents that you are allowed to distribute. You can link publicly available documentation directly.