WideFS Connected, but maybe not?

[rwebb616]

I am trying to use a registered version of FSUIPC and WIDEFS with VASFmc 2.0a9. The wide client on the secondary computer says connected and the FS9 title bar shows connected. VASFmc shows NO FLTSIM CONNECT. I can't seem to get it to communicate no matter what I do. I saw a forum posting in another forum where a guy had the same exact problem and he said it was a problem with WideFS (a configuration thing) and that he had fixed it but he didn't say what it was. Any help would be appreciated. It would also help to know where I can find a manual for WideFS since it seems to be practically non-existent.

Thanks,

Rich

[Pete Dowson]

I am trying to use a registered version of FSUIPC and WIDEFS with VASFmc 2.0a9. The wide client on the secondary computer says connected and the FS9 title bar shows connected. VASFmc shows NO FLTSIM CONNECT.

If both Server and Client say they are connected, then they are connected. Are there any problems reported in the WideServer.log or WideClient.log files? Those are the places to look if you suspect anything wrong.

If this VasFMC program says "NO FLTSIM CONNECT" you really need to find out from their support exactly what that program is checking before it gives such an error. Maybe it is not related so much to the connection but to things like version numbers.

I can't seem to get it to communicate no matter what I do. I saw a forum posting in another forum where a guy had the same exact problem and he said it was a problem with WideFS (a configuration thing) and that he had fixed it but he didn't say what it was.

There's no configuring to do in WideFS normally, and most certainly not if your are getting a connection.

It would also help to know where I can find a manual for WideFS since it seems to be practically non-existent.

Well, that's the opposite of what most folks complain of, that I write too much documentation so they can't be bothered to read it all! Did you actually look inside the WideFS ZIP file for the WideFS User Guide, the WideFS Technical, and the WideFS History documents? If you've not actually bothered to look in the downloadable ZIP for WideFS then naturally you won't find the documentation!

Pete

[rwebb616]

Well, that's the opposite of what most folks complain of, that I write too much documentation so they can't be bothered to read it all! Did you actually look inside the WideFS ZIP file for the WideFS User Guide, the WideFS Technical, and the WideFS History documents? If you've not actually bothered to look in the downloadable ZIP for WideFS then naturally you won't find the documentation!

Pete

That was my bad! Sorry - yes, I found it in the zip file after I posted. Actually I had already read it, but had confused that documentation with project magenta because they have their own "quick setup" guide that I had followed. I also had read your documentation but apparently I had just opened it up from the zip file and not extracted it. Seems like when you're troubleshooting something you read so many different things that you forget what you've read!

I had also tried a demo of Project Magenta's general aviation glass cockpit (the g1000) and it also seemed as though it wasn't connected. It came up on the screen and said "please run this demo in the Los Angeles area" - so I reset my sim to start at LAX and restarted fsuipc/widefs as well and it gave me the same message. Don't know why it wasn't picking up the information from the simulator.

It doesn't seem like there is really all that much to FSUIPC and WideFS for configuring .. once you get it seeing the other computer it seems pretty straight-forward, that's why I can't understand why these programs aren't working. I'll try posting on VASFmc's site as well and see if they can offer any suggestions.

Thanks

Rich

[Pete Dowson]

... I reset my sim to start at LAX and restarted fsuipc/widefs as well and it gave me the same message.

It doesn't seem like there is really all that much to FSUIPC and WideFS for configuring .. once you get it seeing the other computer it seems pretty straight-forward, that's why I can't understand why these programs aren't working. I'll try posting on VASFmc's site as well and see if they can offer any suggestions.

But why not look at the WideServer and WideClient log files, as I already suggested? Or let me see them -- they won't be long, you can paste them into a message here. Whilst you are at it post your FSUIPC log file too.

I can help, but not without information. I did ask you to look in these files before. Both FSUIPC and WideFS always post details of what they are doing, including whether there's anything wrong, in the Log files. That is why I suggested looking there rather than going around in these circles.

Regards

Pete

[rwebb616]

But why not look at the WideServer and WideClient log files, as I already suggested? Or let me see them -- they won't be long, you can paste them into a message here. Whilst you are at it post your FSUIPC log file too.

I can help, but not without information. I did ask you to look in these files before. Both FSUIPC and WideFS always post details of what they are doing, including whether there's anything wrong, in the Log files. That is why I suggested looking there rather than going around in these circles.

Regards

Pete

Pete, I realize that you suggested to look in these files. I am currently at work and not in front of my simulator. I appreciate the offer of help and I will post the contents of these logs as soon as I have a chance to sit back down at the machine.

I did look at all of those files as a troubleshooting step but did not see anything that corresponded to VASfmc attempting to send data across the connection. Once I get a chance to post them, maybe you will see something that I didn't.

Thanks,

Rich

[Pete Dowson]

I did look at all of those files as a troubleshooting step but did not see anything that corresponded to VASfmc attempting to send data across the connection.

There won't be anything like that without adding logging parameters, but that is not the point. I would be able to confirm that WideFS and FSUIPC were all okay and that it was a problem with vasFMC -- or not, as the case may be. Include the FSUIPC log as well please.

Pete

[rwebb616]

Here are the logs:

********* WideClient Log [version 6.78] Class=FS98MAIN *********

Date (dmy): 27/09/09, Time 23:10:15.281: Client name is MAGENTA

172 Attempting to connect now

203 New Client Application: "vasfmc" (Id=1772)

1172 Trying to locate server: Protocol not yet decided

1172 Failed to connect: waiting to try again

3172 Attempting to connect now

12266 Server = FS

12281 Trying TCP/IP host "FS" port 8002 ...

12281Okay, IP Address = 192.168.5.10

12281 Connection made okay!

67656 ****** End of session performance summary ******

67656 Total time connected = 55 seconds

67656 Reception maximum: 18 frames/sec, 1111 bytes/sec

67656 Reception average whilst connected: 12 frames/sec, 566 bytes/sec

67656 Transmission maximum: 2 frames/sec, 83 bytes/sec

67656 Transmission average whilst connected: 2 frames/sec, 65 bytes/sec

67656 Max receive buffer = 896, Max send depth = 2, Send frames lost = 0

67656 **************** Individual client application activity ****************

67656 Client 1772 requests: 561 (Ave 10/sec), Data: 24022 bytes (436/sec), Average 42 bytes/Process

67656 ********* Log file closed (Buffers: MaxUsed 2, Alloc 1238 Freed 1238 Refused 0) *********

********* FSUIPC, Version 3.93 by Pete Dowson *********

Running on Windows Version 5.1 Build 2600 Service Pack 2

Verifying Certificate for "C:\Program Files\Microsoft Games\Flight Simulator 9\MODULES\FSUIPC.DLL" now ...

SUCCESS! Signature verifies okay!

Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL)

User Name="Rich Webb"

User Addr="rwebb@zylatech.com"

FSUIPC Key is provided

WideFS Key is provided

Module base=61000000

ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E

WeatherOptions(Orig)=40003605[40003605]

InitDelay: 0 seconds

WeatherReadInterval=4

LogOptions=0000000D

DebugStatus=255

750 System time = 27/09/2009 23:09:17

750 \\FS\FS9\

750 System time = 27/09/2009 23:09:17, FS2004 time = 12:00:00 (00:00Z)

11219 \\FS\FSPLANS\ColdAndDark.flt

11235 AIRCRAFT\Aeroworx Super King Air B200\awxb200.air

11406 Aircraft="Aeroworx Super King Air B200 - 2D EFIS Cockpit & VC"

28344 AIRCRAFT\Eaglesoft Premier1\ESPremier1.air

28422 Aircraft="Premier1"

32641 \\FS\FSPLANS\UI generated flight.flt

32875 Clear All Weather requested: external weather discarded

34406 Advanced Weather Interface Enabled

38735 READ0 3304, 4 bytes: 02 00 00 00

38735 READ0 3308, 4 bytes: 02 00 00 00

38735 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

47844 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

48438 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

49047 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

49578 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

50156 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

50985 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

51516 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

52094 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

52625 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

53219 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

53766 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

54360 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

54922 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

55469 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

56031 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

56563 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

57172 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

57735 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

58266 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

58813 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

59422 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

59953 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

60516 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

61125 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

61656 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

62203 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

62766 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

63328 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

63906 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

64438 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

65047 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

65610 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

66141 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

66672 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

67281 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

67844 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

68375 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

68985 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

69516 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

70125 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

70688 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

71219 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

71766 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

72328 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

72906 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

73469 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

74047 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

74594 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

75141 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

75688 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

76281 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

76828 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

77375 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

77985 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

78531 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

79078 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

79625 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

80172 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

80766 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

81313 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

81922 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

82469 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

83016 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

83563 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

84110 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

84719 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

85250 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

85844 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

86391 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

87016 WeatherOptions set, now 40003605 (timer=0)

87016 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

87500 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

88094 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

88656 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

89188 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

89485 \\FS\FSPLANS\UI generated flight.flt

89797 Clear All Weather requested: external weather discarded

91516 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

91516 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

91516 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

91516 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

92125 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

92563 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

93110 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

93719 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

94266 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

94813 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

95360 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

95953 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

96500 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

97047 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

97641 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

98203 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

98750 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

99297 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

99891 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

100688 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

101235 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

101844 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

102391 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

102938 WRITE0 (failed, read-only!) 330A, 2 bytes: EC 03

1394453 \\FS\FSPLANS\UI generated flight.flt

1394703 Clear All Weather requested: external weather discarded

1401016 System time = 27/09/2009 23:32:37, FS2004 time = 23:09:33 (04:09Z)

1401016 *** FSUIPC log file being closed

Memory managed: 9 Allocs, 1731 Freed

********* FSUIPC Log file closed *** *******

********* WideServer.DLL Log [version 6.78] *********

Blocksize guide = 4096 (double allowed)

Date (dmy): 27/09/09, Time 23:09:17.750: Server name is FS

42531 Initialising TCP/IP server

42531 Initialising IPX/SPX server

42531 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family

42531 Failed to start IPX/SPX Server

42531 Initialising UDP/IP server

44031 Broadcasting service every 1000 mSecs

44031 Preferred protocol = TCP

46578 Incoming connection Accepted ok (skt=5088) TCP

46578 Connected to computer "MAGENTA" running WideClient version 6.780 (skt=5088) TCP

101984 Error 10054: client socket disconnected at Client: removing (skt=5088) TCP

1400015 Close signalled to clients

1401109 Closing down now ...

Memory managed: Offset records: 40 alloc, 40 free

Read buffer usage: 117 alloc, 117 free, max in session: 1

Write buffer usage: 732 alloc, 732 free, max in session: 1

Throughput maximum achieved: 18 frames/sec, 1325 bytes/sec

Throughput average achieved for complete session: 0 frames/sec, 10 bytes/sec

Average receive rate from "MAGENTA": 0 frames/sec, 2 bytes/sec

********* Log file closed *********

Let me know what you thinkthose write failed entries can't be good I'm thinking.

Thanks

Rich

[Pete Dowson]

Let me know what you thinkthose write failed entries can't be good I'm thinking.

No, they are irrelevant. The problem is that FSUIPC thinks you are using illegal keys. Looking at the date and time of the session, from the log:

System time = 27/09/2009 23:09:17

and the date and time of your registration -- 28 September 2009 01:32

it appears to FSUIPC that your keys weren't valid on the day you used them. I bet if you tried again now everything would work fine. In fact just an hour later would have been okay.

Regards

Pete

[rwebb616]

No, they are irrelevant. The problem is that FSUIPC thinks you are using illegal keys. Looking at the date and time of the session, from the log:

System time = 27/09/2009 23:09:17

and the date and time of your registration -- 28 September 2009 01:32

it appears to FSUIPC that your keys weren't valid on the day you used them. I bet if you tried again now everything would work fine. In fact just an hour later would have been okay.

Regards

Pete

That is correct - it works now. What's up with the date and time thing? Just because of different time zones? Thanks for your help.

-Rich

[Pete Dowson]

That is correct - it works now. What's up with the date and time thing? Just because of different time zones?

Seems so. This is only the second time it's been a problem in the 6 years of FSUIPC registration. You purchased the key when it was "tomorrow" in Germany but still "today" in America, and tried to use it before "tomorrow" arrived.

The date check is part of the essential anti-piracy checks on the registration keys. Now that the time zone thing has caused a problem more than once I might take a look to see if I can adjust the check for time zone differences, or possibly just allow one day's "grace". ;-)

Regards

Pete