Strange error with Wideclient and Prosim738

[frazer84]

Hi! 

I've been struggling with a problem for months, and now I've finally boiled down the problem to the combination of Wideclient and Prosim. 

I will try to summarise the problem as short as possible, since it's indeed a strange problem. 

I own an CPFlight MCP Pro version 1 (USB-Serial version) that has been working fine with Wideclient and Prosim version 2.

Upgrading to Prosim v3, it stopped working. After a lot of testing around, I found out that if I don't start Wideclient before Prosim, it works like a charm. But the other way around, then it won't work at all. Since the MCP is using a Com-port, I started to experiment with the GPSout function since it's the only thing in FSUIPC and Wideclient that uses serial data, by setting the com port in Wideclient.ini to a non-existing one just to make sure. This helped a bit, but it still feels a bit random. 

Any idea why Wideclient is interfering with my CPFlight MCP and blocking Prosim from accessing it? 

My temporary solution is to always shut down Wideclient before starting Prosim, but since the computer is normally without keyboard and mouse, I would prefer for this to work without manual interference. 

Some notes:

I'm using the latest version of Wideclient. I've deleted the ini file to start fresh. 

[John Dowson]

Sorry but I have no idea. Is there maybe a difference in the privileges when you start ProSim before or after WideClient?
Why does ProSim stop working - can it see the FS and/or FSUIPC?

You could try changing the ports used by WideServer/WideClient, but from what you say I don't think this will help.
Are there any changes from Prosim 2 to 3 that could cause this? Have you asked on ProSim support?