Accessing "exported" monitors (Helios? Iris?) via Web Browser with touch functionality.

[RafaPolit]

Good afternoon friends.

I was wondering if there is a flow that would allow me to run everything I need in my main DCS machine and access some kind of profile / monitor / export / view from a remote browser preserving touch functionality.

This is the scenario: I would configure DCS with Helios? Iris? To export all the views I need... then I access the DCS machine via IP with a web browser that can see AND INTERACT (this is crucial) with, for example, the F-16 ICP screen.  So, I want to export the view of the ICP (and perhaps DED) and access it via a remote web browser.

Why haven't I found a solution to my needs?  Mainly because my remote PC is running Ubuntu on a RPi3.  I have found solutions for Android Tablets, it would also work for remote windows machines that could run Helios on them, but my machine needs to access a somewhat different flow.

Any ideas where to start looking?  Thanks a lot!  Best regards,

Rafa.

[gwheeler]

I am also exploring a browser-based client/server display and input system so I've thought about this scenario some.

One possibility I'm looking into involves using a dummy display dongle to create an extra virtual monitor on the simulation host machine that will receive the exported display renders. Then, use something like OBS to capture the virtual display contents and stream them over the network (I think people have made recent strides toward getting OBS to output an HLS stream that could be referenced directly in an HTML <video> tag.)

It may also be possible to use modern native browser APIs (as seen here: https://www.jitbit.com/screensharing) to share the contents of the virtual screen from the source PC to a browser running on the destination machine. In essence, the "client" PC browser connects to a web server running on the DCS host and uses websockets for comms between the client UI and the server app which bridges to DCS via DCS-BIOS or other direct Lua socket hooks. The client UI also accesses the video stream(s) from the server and using various bits of CSS trickery shows the bits and pieces of the source video in the correct areas.

I've not really had much of a chance to experiment with either method yet, but will keep an eye on this thread and update you if I do.

[RafaPolit]

I actually developed a Node.js server that connects to DCS-BIOS and sends requests back.  I can't "export" views, but I can replicate cockpit status for "known" states and I even have a working DED for the F-16.  Maybe you can take a look and see if you can improve on the concept?

Here's my attempt: