wideserver FSX

[Pete Dowson]

As a SB user of many years I noticed this with interest so ran a check myself. Both the AI  & Transponder modules are producing the same multiple errors.

 

I would add that these errors are logged after the FSUIPC connection at > 3.26100 [74, 1]Open: Version=0x00000004  Name="FSUIPC4". The first error 25 at < 10.46126 [190] >>>>>  EXCEPTION=25

 

Yes, but Andrew's log, with FSUIPC4's entry delayed by 30 seconds using "InitDelay=30", shows the same errors occurring in SB before FSUIPC4 starts. So I don't think it's a contributory factor at all.

 

Regards

Pete

[Andrew Kewley]

Hi Pete,

 

Just noticed something. If I start by loading the "previous flight" as saved by FSUIPC, wideserver starts no problem If, however, I change an aircraft/location and then start the flight, wideserver doesn't load. This occurs irrespective of default aircraft or 3rd party addon. The problem with wideserver seems to generate at the point of changing the settings on the flight selection screen in FSX. Any thoughts?

[Pete Dowson]

Just noticed something. If I start by loading the "previous flight" as saved by FSUIPC, wideserver starts no problem If, however, I change an aircraft/location and then start the flight, wideserver doesn't load. This occurs irrespective of default aircraft or 3rd party addon. The problem with wideserver seems to generate at the point of changing the settings on the flight selection screen in FSX. Any thoughts?

 

Is this a new problem? Are you now saying that the "InitDelay=30" change doesn't work after all?

 

Note that there is no "problem with WideServer". The problem is MUCH worse -- FSUIPC is not actually starting its services to anything, not only WideServer. It can't do this because SimConnect is rejecting all of its requests with "too many requests".

 

FSUIPC knows nothing whatsoever about anything you do in loading flights or changing aircraft or airports. All it is dependent upon is receiving information from SimConnect. I suspect that what is happening in the situation where you are changing things is that the 30 seconds has by then elapsed and your changes are causing Squawkbox to do its thing again. Howeer, I can't really tell what is going on without information. I explained what I thought with the earlier logs and so on. I'm sure you can look at them now yourself and work it out.

 

Pete

[Andrew Kewley]

Just re-read all of your replies and a rather obvious thought occurred re the simconnect constantly trying to work. Prior to moving PC's around, I installed the win8.1 update on the non FS machine. Although I had opened all the ports previously, it seems that the update changed the custom rules. Having opened the simconnect ports (and changing the delay to 120), everything works!

 

As for your last comment.. you clearly have more faith in my computer skills than I do!!

 

:)

[Pete Dowson]

Just re-read all of your replies and a rather obvious thought occurred re the simconnect constantly trying to work. Prior to moving PC's around, I installed the win8.1 update on the non FS machine. Although I had opened all the ports previously, it seems that the update changed the custom rules. Having opened the simconnect ports (and changing the delay to 120), everything works!

 

Okay ... so that last report wasn't really about WideServer not starting, but about WideClient not connecting.

 

Glad you sorted it.

 

Pete