TBM 900 networked pc issues

[Yourmomm]

Hi. I posted this is a other forum, where I was told basically that this aeroplane hasn't been coded to ever work on a networked PC, and it was suggested I try to reach out to the developers, here, to check this?

My original post:

Ok hoping someone can help me out here. 

So I've just tried to network two pcs for x plane, one as master, (central screen) and one as slave (external visuals: left and right screens). No firewall.

Initially when I did it, x plane told me it only supported ipv6 protocol...so that took me ages to work that out, but I got it going in the end. It was working, but terrible..the TBM 900 was fine on the master, but it wasnt sending proper signals to the slave, so, (on the left and right slave screens only), flames were coming out of the engine, I was getting hypoxia and blacking out (which sort of defies the purpose of triple screen set up, when two of them go black); it was telling me I hadn't removed the pitot tube covers (I had, on the master, but this wasnt registering on the slave, even when I did so there, as well), the g1000's were completely black on the slave screens; it was telling me that the air conditioning wasnt on, when it was, I was dying in an engine fire (so the left and right screens turn red) etc etc (ALL on the slave machine only...the master was flying exactly as I controlled it, and its instruments were fine). Then, when i tried to reassign my router from dynamic to static, to see if that was the problem, it all went belly up pretty quickly and I had to start again, resetting the router, and taking hours to get back to where I started.

This time, x plane accepted ipv4 as a communication protocol no problems, but I STILL couldnt set up a static IP LAN, and EXACTLY the same problems flying the slave, as I describe above, still existed. 

I added screen photos of the settings I took, below; everything looks fine in them apart from potentially the udp settings:

Port we receive on 49010

Port we receive on (legacy) 49000

Port we send from (legacy) 49001

On BOTH master, and slave pcs?

And also the notification stating both "external visuals machine, being directed by this master simulator" (on the master) and "this machines master simulator" (on the slave/external visuals machine) stating "sending  but not replying". There's also a picture of my slave only hypoxia setting in, just before I black out....

Pretty sure when tinkering in the "output" folder that I got the g1000 screens working on the slave screens under ipv6, but I have no idea what I did, and I havent been able to replicate it again....not that I can get ipv6 working again, either.

Any advice here would be appreciated as I love this plane. It's the only plane i fly

[skiselkov]

I'm afraid we do not support multi-machine flying in this manner. The slave machines are quite simply running independent copies of the plane, so naturally all of the systems in them are completely out of sync. We only support multi-monitor operation from a single sim instance, not multiple networked ones.

[Yourmomm]

Shame. So you're sure it's not that I'm being an idiot with the networking setup?

Is there any way for me to turn off things like hypoxia on the slave?

[Yourmomm]

Ps my PC is not powerful enough to run a triple monitor setup on it's own, and that's with 4.5ghz clocked processor and overclocked gtx1080ti....until x plane does something a out its reliance on single core, it looks like this may only be a dream....