FlyPT Mover + XPlane 12 autoconnect problem

FlyPT mover is working really well so far with our 3DOF rig. But we still have a problem when starting up the system. If we select auto-connect in the source window (checkmark in the "connect" box) it immediately connects (or pretends to do so, light turns green) even if XPlane is not running yet. If we then start XPlane which takes quite some time to boot all values (lateral speed...) stay at zero and nothing happens. We have to manually disconnect and re-connect. Then we have live data (values dither a bit around their average value) and the rig starts to move.
I guess that XPlane 12 somehow expects some sort of trigger before it starts to send data over the UDP connection.
This is kind of annoying because XPlane agressively occupies all 3 monitors with stay-on-top full size windows. So we have to press windows-tab to get access to the FlyPT window. No big deal for now but it would be nice if we could remove the PC keyboard and mouse from the cockpit, later.

Is this a bug? Is anybody here who has this working correctly or can provide a workaround?

Sorry for the problem.
Please keep an eye on the new release coming 20 September with new from scratch code for all the sources.

In Mover you can force the window to be the topmost. Doesn't work for all games, but you can try.
From what I remember (to many sims/games), XPlane needs to receive a request to start sending data.
What happens is that Mover sends when it connects, and stops sending the request... If XPlane is closed the result is what you see.

Just tested in the new release to be sure...

Ah thanks for the info. That looks really promising. I'm looking forward to the new release. I also plan to build a new rig. I'll make another donation as soon as it runs for the first time.

BTW, what do you prefer? Creating a new thread for a problem report or posting everything in the big FlyPT Mover thread? I thought a seperate thread makes it easier to find for other forum members, especially for newcomers who have not already browsed through the full 189 pages.

A possible solution would be to re-send the request when no values are received for a certain timeout period. But you surely already figured that out.

Well, the ultimate goal is to make the startup procedure fully automatical. So the pilot can enter the cockpit, flip the main switch, the PC boots up and within 1-2 minutes he can startup the motor and go flying without any further Windows/PC interaction.

In the new relese, I'm sending the request periodically while not connected.

If you look at the video that setup I made is now a default setup for that game/plane. If auto load is enabled and you open XPlane12 with that plane it loads that setup.
The left column with game images in the main Mover window are the default setups that can be auto loaded.
You can also make the setup general by saying it's not a specific vehicle (in some games we can't know the vehicle).

There's a command line to start Mover in the tray. That way if you have default setups you don't even need to see Mover to use it.
Also, you can assign any control to the buttons/numerics in Mover to adjust parameters from the cockpit.
You can even use MIDI controllers for that in the new release.

You can ask questions anywhere, but need to mention me or I will not notice the question.