rwebb616
-
Posts
17 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by rwebb616
-
-
I don't know VASfmc, but if it is simulating a proper FMC then the FPA value is set in the descent page of the CDU. I don't think any FMC implementation would provide controls for all of the CDU functions, there's too much and mostly it has to be done using the CDU keyboard and buttons.
I got a response back on their forum and there is no offset at present to adjust it, but it will be available in the next release. VasFMC mimics an Airbus A320 style FCU/Autopilot and the control panel has a knob for adjusting V/S but when in FPA mode it also works for adjusting the flight path angle. When in V/S mode it works via FSUIPC, but when in FPA mode it doesn't. Their implementation doesn't yet do VNAV.
And I don't know how VasFMC uses its offsets if it has any (I don't recall if it has an allotment offhand, sorry).Yes, they do have several to control many aspects of the system, just not FPA yet. It's still very usable without it, but like you, I'm trying to avoid using any keyboard or mouse input. I just wish there were a buttonscreen like in wideclient that would work for X-Plane because I'm thinking of gradually switching over to it.
-Rich
-
Does anyone know what the control name is or an offset that will allow adjustment to the flight path angle? I am using VASfmc which adds a bunch of their own controls to the FSUIPC controls dropdown, but non of them will adjust the FPA. I can switch between v/s mode and fpa mode, but I just can't adjust the angle once in that mode.
Any help would be appreciated.
Thanks
Rich
-
The timeout is 10-15 seconds initially (extending to 20 after first connection). For some reason you are starting Wideclient at just about the wrong time. Why are you starting it a good 13 seconds after FS is ready? Best to have all your clients running, ready and waiting, really, before you even start FS. I have my clients loaded as part of Windows "startup", so they automatically connect as soon as FS is ready, every time.
That particular time I started it, it was only done for the test. Previously when it was happening, I was stopping and restarting wideclient several times (after adjusting the .ini file).. sometimes it would immediately connect and other times it would wait for about 10 seconds and then connect, and yet others it would do the flash thing where it connects and then drops. It seems very inconsistent as to what it is doing.
It isn't critical, but the answer is to start WideClient earlierThis time (for which I have attached the logs) wideclient was up and running well before fsx and it was a good 10-12 seconds before my button screen appeared after seeing the virtual cockpit. I also should mention that these problems did not happen on the fs9 setup I was previously using. It only seems to be on the fsx version.
Here are the logs:
Wideclient:
Date (dmy): 20/10/09, Time 15:28:30.984: Client name is MAGENTA
406 Attempting to connect now
1406 Trying to locate server: Protocol not yet decided
1406 Failed to connect: waiting to try again
3406 Attempting to connect now
67406 Trying to locate server: Protocol not yet decided
232093 Server = FS
232093 Trying TCP/IP host "FS" port 8002 ...
232093Okay, IP Address = 192.168.5.10
232093 Connection made okay!
232234 Connection closed by server!
232734 Attempting to connect now
237093 Server = FS
237093 Trying TCP/IP host "FS" port 8002 ...
237093Okay, IP Address = 192.168.5.10
237093 Connection made okay!
291484 ****** End of session performance summary ******
291484 Total time connected = 55 seconds
291484 Reception maximum: 23 frames/sec, 669 bytes/sec
291484 Reception average whilst connected: 19 frames/sec, 509 bytes/sec
291484 Transmission maximum: 0 frames/sec, 31 bytes/sec
291484 Transmission average whilst connected: 0 frames/sec, 21 bytes/sec
291484 Max receive buffer = 397, Max send depth = 1, Send frames lost = 1
Wideserver:
Blocksize guide = 4096 (double allowed)
Date (dmy): 20/10/09, Time 15:32:01.328: Server name is FS
15547 Initialising TCP/IP server
15562 Initialising IPX/SPX server
15562 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family
15562 Failed to start IPX/SPX Server
15562 Initialising UDP/IP server
16015 Broadcasting service every 1000 mSecs
17531 Incoming connection Accepted ok (skt=9232) TCP
17656 Restarting service due to zero reception!
17672 Failed to start IPX/SPX Server
22547 Incoming connection Accepted ok (skt=9140) TCP
22719 Connected to computer "MAGENTA" running WideClient version 6.780 (skt=9140) TCP
77328 Error 10053: client socket disconnected at Client: removing (skt=9140) TCP
FSUIPC.log
Running inside FSX (using SimConnect Acc/SP2 Oct07)
Module base=61000000
Wind smoothing fix is fully installed
DebugStatus=255
203 System time = 20/10/2009 15:30:26
203 FLT UNC path = "C:\Documents and Settings\user\My Documents\Flight Simulator X Files\"
203 FS UNC path = "C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\"
1328 LogOptions=00000000 00000001
1328 SimConnect_Open succeeded: waiting to check version okay
10375 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)
10375 Initialising SimConnect data requests now
10390 FSUIPC Menu entry added
10453 C:\Documents and Settings\user\My Documents\Flight Simulator X Files\Cold and Dark.FLT
10453 C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\Sweeded_FSND_FSX_Citation X_750\citation.AIR
95422 System time = 20/10/2009 15:32:02, Simulator time = 16:30:38 (20:30Z)
95515 Aircraft="Citation X"
95953 Advanced Weather Interface Enabled
161000 Sim stopped: average frame rate for last 66 secs = 23.7 fps
163734 Weather Mode now = Theme
163734 C:\Documents and Settings\user\Application Data\Microsoft\FSX\Previous flight.FLT
Hope we can resolve it!
Thanks
Rich
-
WideClient, WideServer and FSUIPC4 logs are needed
Here they are:
Wideserver.log
15375 Initialising TCP/IP server
15375 Initialising IPX/SPX server
15375 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family
15375 Failed to start IPX/SPX Server
15375 Initialising UDP/IP server
16000 Broadcasting service every 1000 mSecs
29500 Incoming connection Accepted ok (skt=3580) TCP
29625 Restarting service due to zero reception!
29625 Failed to start IPX/SPX Server
34532 Incoming connection Accepted ok (skt=7668) TCP
34735 Failed to start IPX/SPX Server
37500 Incoming connection Accepted ok (skt=7672) TCP
37594 Connected to computer "MAGENTA" running WideClient version 6.780 (skt=7672) TCP
558438 Error 10053: client socket disconnected at Client: removing (skt=7672) TCP
WideClient.log
281 Attempting to connect now
812 Server = FS
828 Trying TCP/IP host "FS" port 8002 ...
828Okay, IP Address = 192.168.5.10
828 Connection made okay!
953 Connection closed by server!
953 Attempting to connect now
953 Trying to locate server: Protocol not yet decided
5812 Server = FS
5812 Trying TCP/IP host "FS" port 8002 ...
5812Okay, IP Address = 192.168.5.10
5828 Connection made okay!
6062 Connection closed by server!
6062 Attempting to connect now
8812 Server = FS
8812 Trying TCP/IP host "FS" port 8002 ...
8812Okay, IP Address = 192.168.5.10
8828 Connection made okay!
FSUIPC.log
529719 ****** End of session performance summary ******
529719 Total time connected = 521 seconds
529719 Reception maximum: 24 frames/sec, 671 bytes/sec
529719 Reception average whilst connected: 23 frames/sec, 615 bytes/sec
529719 Transmission maximum: 1 frames/sec, 41 bytes/sec
529719 Transmission average whilst connected: 0 frames/sec, 20 bytes/sec
529719 Max receive buffer = 387, Max send depth = 1, Send frames lost = 1
47 System time = 19/10/2009 13:07:55
47 FLT UNC path = "C:\Documents and Settings\user\My Documents\Flight Simulator X Files\"
47 FS UNC path = "C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\"
1265 LogOptions=00000000 00000001
1265 SimConnect_Open succeeded: waiting to check version okay
3734 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)
3734 Initialising SimConnect data requests now
3734 FSUIPC Menu entry added
3875 C:\Documents and Settings\user\My Documents\Flight Simulator X Files\Cold and Dark.FLT
3875 C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\Sweeded_FSND_FSX_Citation X_750\citation.AIR
26797 System time = 19/10/2009 13:08:22, Simulator time = 13:07:59 (18:07Z)
26890 Aircraft="Citation X"
31609 Advanced Weather Interface Enabled
590875 Sim stopped: average frame rate for last 560 secs = 23.8 fps
593765 Weather Mode now = Theme
593765 C:\Documents and Settings\user\Application Data\Microsoft\FSX\Previous flight.FLT
Thanks
-Rich
-
No. It sounds like something is wrong on your system. Is FSX struggling to start? Maybe FSX is taking so much processor time in the initial stages that WideServer or the network side isn't getting a look in? What have you changed recently?
Actually nothing, all I was doing was sitting at O'Hare on the ground and programming my buttonscreen. Each time I would make a change to the Wideclient.ini I would exit Wideclient and restart it to see my changes. It had been working all night, but then started doing what I described.
WideClient, WideServer and FSUIPC4 logs are needed.I'm not in front of the machine at the moment, but will as soon as I can. I just wanted to give more information as to what I was doing. Also, this is a clean install - nothing else is on the computer besides FSX, FSUIPC and the aircraft I'm using is a freeware Citation-X from Simviation.
-Rich
-
It has been working fine right along and now tonight, wideclient takes two or three times to connect. I use the buttonscreen on it and I see the buttons flash for a second then disappear about 3 times, and then it finally connects and stays. Is this any kind of known issue?
I'm using FSX and can provide the log files if you like.
Thanks,
Rich
-
So if I had both for FS9 and then wanted to upgrade to the FSX version then I would have to buy both items?
Thanks,
Rich
-
Hi,
Just wondering if this is compatible with both FS9 and FSX? I May have just bought a second copy of it for nothing! It appears on the site like you need both for either FS9 or FSX depending on what you're running. I purchased both for FS9 and then just purchased both for FSX. Looking at it now, I'm wondering if WideFS works for both versions?
Thanks
Rich
-
If that's the case, and it doesn't provide any keyboard shortcuts or other ways of operating its transponder mode, then you can't do it through FSUIPC. Sorry. I'd be glad if you took it up with the FSInn folks.
I figured it out - there is the ability to assign hotkeys in FSINN to anything. I now have a hotkey (shift-C / shift-S) for Charlie and Standby and have programmed a button on the wideclient to toggle it. It works great. So, now all you need to do is set your home cockpit up with FSINN and you can fly online without having to use the mouse to switch modes.
Now if I can figure out the com1 radio set command.. :)
-Rich
-
For 1200 you need to enter x1200 as the parameter. For 2000 it is x2000. FS uses hex numbers for the transponder.
Thanks - that worked great!
The vast majority aren't FSUIPC-added controls, which are documented in the Advanced User's guide. The FS controls are simply listed from FS's own "CONTROLS" module. What they may or may not do is decreed by Microsoft, not me. I've never been able to document them all as I've never tried them all, and the list varies from version to version. About the best documentation you might get is from when I actually tried to do it in FS2000 days -- the List of FS2000 controls on the Schiratti "Dowson" download page.Ah.. I didn't realize that.
One more question if I may... How are the values handled on the com1 radio set function? I would like to make a button that will immediately set com1 to 122.8 for vatsim unicom. Is that possible?
-
Hi,
I have a few questions relating to setting the xpdr using fsuipc and the wideclient button bar. I use FSINN and FS9 while flying on Vatsim, and I've search high and low for any reference as to how to control FSINN from fsuipc and can't find anything. I only had found one article talking about how FSINN doesn't use fsuipc and that it has it's own thing it uses.
I'm trying to figure out how to change from Normal/Standby/Ident modes on FSINN. That's the first question.
The second question is probably a little easier, but I can't figure it out. I'm trying to define a button to instantly set the xpdr to 1200 and another to 2200. I used the xpdr set option and put 1200 in the box but it displayed something like 430 or something when pressed. I'll be happy to read any documentation on this function, but I couldn't find anywhere where it talks about the individual command options in the drop down lists in FSUIPC.
I am very happy with FSUIPC and WideFS so far - I just purchased a 15" touch screen monitor for it's use. It works well. Thank you for great software!
-Rich
-
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
-
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
-
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
-
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
-
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
Looking for FPA adjustment control
in FSUIPC Support Pete Dowson Modules
Posted
I flew a bit more with it tonight and I'm with you! Went to Chicago O'hare and it didn't have a terminal or taxi / runway lights etc. FS is worlds ahead of them. I guess they have time to catch up at least. Hopefully the folks at X-Plane know what they're up against. I'll be sticking with FSX for a while to come.
-Rich