JeeHell FMGS forums

Hello all

We are suspecting that the startup sequence of JeeHell installed on different PCs is influencing the functionality of our setup.

In which order the different JeeHell instances and P3D should be started up to avoid Problems?

-all our PCs (4) start automatically when switched on (bios setup)
-on the master P3D, FMGS, Active Sky.... the apps are launched manually (in this order)
-on 3 pc clients widefs client is launched automatically via scheduled task when windows is launched
-nothing happens until the p3d is launched and it has not established a connection on the 3 widefs clients. This allows us to do navigraph updates and other intervention before launching the simulation.
-as soon as the clients connect to the p3d master, and therefore before the start of the master, a runready,close function launches the start of the client pc which executes all the respective JL applications
-when the clients have all executed their respective start and without rushing things , we execute the start of the master p3d, we check while waiting for "table found" to appear on the p3d visual and we launch active sky.

-To stop the simu, we stop the P3D by ctrl+C, the fact that the wideserver stops cuts the connections to the wideclient which closes their starts program and therefore all the JL applications stop on the clients, I turn off the PCs remotely. on the Master, I do it with the mouse to close the applications and widows...

This generally works well.
Problems can have so many origins that it would not make sense to rule things out....
I hope my explanations will be useful to you.
best regards
gilles

Hi Aron,

I also had these problems at the beginning. A good solution is to simply use the Windows task scheduler.
This way you can start the necessary software on each computer at the right time.
The order depends a little on your setup. For example, whether you use a separate Jeehell server or not.
And of course on the hardware you use. With Skalarki, the software has to be started when Jeehell is already fully loaded.

You can find a description of how I solved this in my Home Cockpit on my website: https://a320-simulator.de/homecockpit/h ... k-starten/
A translation function is integrated.