For the complete documentation index, see llms.txt. This page is also available as Markdown.

Supported screens

Supported screens

  • Vocore

    usb screen, supports "leds pass through"*

  • USBD480 : Usb screen, does not supports "leds pass through"*

  • USBD480NX Usb screen, supports "leds pass through"*

  • HDMI Monitor Simple monitor display , does not supports "leds pass through"*

  • Remote web display Provides a dedicated html "page" for each device, does not supports "leds pass through"*

  • MMF Rendering In memory rendering which can be read by an external application, supports "leds pass through"*

  • Simucube API Renders through the API exposed by Simucube Tuner, supports "leds pass through"*. Devices are matched using their Simucube API Manufacturer ID and Product ID. See Simucube integration.

* leds pass through : Leds data can be sent through the screen instead of using a separate hardware interface.

Simucube API

The Simucube API screen type supports compatible displays exposed by Simucube Tuner. Tuner must remain running while the display is in use.

Enter the Manufacturer ID and Product ID shown by the Simucube device scan. These are stable API model identifiers, not USB identifiers. When the same device also provides LEDs, enable the LED feature and select Screen passthrough as the hardware communication mode.

Simucube displays support fine software brightness control. Touch input is not currently supported.

MMF Rendering

MMF rendering is producing a dashboard rendering in memory. In this particular case a "consumer" application (typically making the interface with the real hardware) will expose all the available devices. Then Simhub can connect and render through shared memory the dashboards like any classic hardware displays.

This rendering can be used to bridge to unsupported screens/displays handled by an external application as well as virtual displays (IE : In sim dashboards textures ...) A demo "consumer" application can be found here: MMFVisualizerV4

V4 update : Support for multitouch

To get it running make sure to make the device type id match the one shown in the device authoring tools :

Last updated