trisager

There are plenty of those in flightsimming, as you will discover :D The G1000 in the default planes in FSX is rubbish. There is a much better one in the Flight1 Mustang (http://www.flight1.com/products.asp?product=f1mustang) - it does not include all features of the real-world unit, but what is implemented seems pretty solid to my untrained eyes (my real-world flying experience is as a passenger only). I have no idea if you can use it in the way you describe, but the product support forum is visited by the developers on a daily basis - you can find it here: http://mustang.flight1.net/forums/ Good luck, Tom

I think this issue may be related specifically to FSX and PMDG aircraft. Maybe that is why this is coming up now - more and more users flying airline sims in FSX, particularly the MD-11? Re the rate of smoothing that I'm using: With the Level-D 767 and other compex addon aircraft smooting at the rate of a few knots per second works fine, but with the 747x and the MD-11 it has to be fractional knots per second to avoid altitude and speed excursions. The general advice in the PMDG forum seems to be to smooth at 8-10 seconds per knot change. (Currently I'm using 3 seconds per knot, but it doesn't make much difference from before when I was using a slower rate - the AP still goes bonkers when coming back from the menus). A typical reason for me to go into the menus in-flight would be to reset a failure, or to allow another failure to happen after the first one has triggered. I try to avoid it, obviously - partly for immersion, but also because it mostly means spending time recovering from an overspeed or low-speed condition. And like Andy I sometimes change display settings en route, e.g. to add some AI if flying online in an empty region. Cheers, Tom

I'm using FSUIPC wind smoothing only, not ASA's. Here is a typical scenario (just tried it again): I'm in cruise with winds apparently stable (i.e. wind vectors on display not changing). I open FSUIPC and immediately exit to FSX. Slam, a huge wind shift causing a 50kt drop in indicated airspeed. I was thinking that somehow, maybe because of the slow rate of change that I allow, wind changes got buffered somewhere by FSUIPC and then instantly released to the sim when I exited the menu. Anyway, as I said, not much of a problem, I was just wondering. Tom

I'm using ASA with FSUIPC wind smoothing enabled in FSX with very good results. I have the smoothing set to 4 seconds per knot change which completely eliminates wind shift problems. However, I've noticed that if open an addon (e.g. open FSUIPC or edit PMDG failure options) while in flight, when I return to FSX I always get a big wind shift, resulting in an altitude and/or speed excursion. This is not much of a problem, but I'm wondering why it occurs. Is FSUIPC somehow buffering up changes that get released instantly when coming back from the addon? Tom

Marty, did you try this: http://www.mcdu.com/forum/viewtopic.php?p=22204 Tom

Hi again, The latest version in this thread worked quite well on a test flight - about the same as the first one you modified I would say. Thanks, Tom

Very puzzling, and I do understand your reluctance to change things. I just tried again with the first version you adjusted, and there very definitely is a difference. Both in response time when I try to do something with RC4 on the laptop (e.g. show the list of ATC frequencies, or just bring the window to the foreground) and the length of pauses in the dialogue. The flights today were all done with another Wideclient application running (FSAcars). Perhaps it is not that common for RC4 users to use Wideclient? After all it does require either using speakers (something I cannot do since I share the room) or wearing two sets of headphones (which makes you look a bit odd). I'll try with the latest version later this evening. Tom

Hi Pete, I've tried a couple of flights with the version in the post above - RC seems to be slower to respond with this version than with the previous, but I did manage to complete the flights. Is this particular timing value something that could be set via the ini file, or as a command-line option? Tom

... in the beta FSUIPC is brilliant! Easy to use and works flawlessly. Thanks, your work is very much appreciated :D :D :D Tom

Thanks, Pete. The new version of WideClient solved the problem - Radar Contact performed quite well on a test flight. Tom

I must be tired :oops: I tried with FS Commander instead, WideClient sits at about 10-20% CPU on my laptop with that application (1.7 GHz Pentium M, 1 GB Ram). I've sent you the logs via email. The high CPU usage kicks in about 2-3 seconds after the Radar Contact window appears on the FSX screen. Tom

I'm having exactly the same problem as the OP. The laptop running Wideclient has never had any gamecontrollers installed, and I checked in the hardware device tab just to be sure. Laptop is running Windows XP sp2, latest beta of Wideclient, latest beta of FSUIPC, and I did try ButtonScanInterval=0 with no improvement. I should mention that the same laptop is running Active Sky X without Wideclient misbehaving. Logfiles below. Tom Wideclient.ini: [Config] ButtonScanInterval=0 Window=75,81,593,489 ClassInstance=0 NetworkTiming=5,1 MailslotTiming=2000,1000 PollInterval=2000 Port=8002 Port2=9002 ResponseTime=18 ApplicationDelay=0 TCPcoalesce=No WaitForNewData=500 MaxSendQ=100 OnMaxSendQ=Log NewSendScanTime=50 Priority=3,1,2 Wideclient.log ********* WideClient Log [version 6.759] Class=FS98MAIN ********* Date (dmy): 25/04/08, Time 21:19:25.578: Client name is TOM-LAPTOP 691 Attempting to connect now 751 Server = TOM-DESKTOP 761 Trying TCP/IP host "TOM-DESKTOP" port 8002 ... 761Okay, IP Address = 192.168.1.35 761 Connection made okay! 71212 New Client Application: "rcv4" (Id=3132) 111039 ****** End of session performance summary ****** 111039 Total time connected = 110 seconds 111039 Reception maximum: 15 frames/sec, 667 bytes/sec 111039 Reception average whilst connected: 14 frames/sec, 458 bytes/sec 111039 Transmission maximum: 6 frames/sec, 335 bytes/sec 111039 Transmission average whilst connected: 0 frames/sec, 31 bytes/sec 111039 Max receive buffer = 612, Max send depth = 2, Send frames lost = 0 111039 **************** Individual client application activity **************** 111039 Client 3132 requests: 3393 (Ave 30/sec), Data: 346148 bytes (3146/sec), Average 102 bytes/Process 111039 ********* Log file closed (Buffers: MaxUsed 3, Alloc 5053 Freed 5053 Refused 0) ********* wideserver.log ********* WideServer.DLL Log [version 7.272] ********* Blocksize guide = 4096 (double allowed) Date (dmy): 25/04/08, Time 21:11:04.678: Server name is TOM-DESKTOP 17222 Initialising TCP/IP server 17222 Initialising IPX/SPX server 17222 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family 17222 Failed to start IPX/SPX Server 17222 Initialising UDP/IP server 18127 Broadcasting service every 1000 mSecs 19624 Incoming connection Accepted ok (skt=8952) TCP 19780 Connected to computer "TOM-LAPTOP" running WideClient version 6.759 (skt=8952) TCP 332921 Error 10054: client socket disconnected at Client: removing (skt=8952) TCP 503774 Incoming connection Accepted ok (skt=7308) TCP 503914 Connected to computer "TOM-LAPTOP" running WideClient version 6.759 (skt=7308) TCP 614144 Error 10053: client socket disconnected at Client: removing (skt=7308) TCP 636905 Close signalled to clients 638028 Closing down now ... Memory managed: Offset records: 351 alloc, 350 free Read buffer usage: 252 alloc, 252 free, max in session: 1 Write buffer usage: 5851 alloc, 5851 free, max in session: 1 Throughput maximum achieved: 19 frames/sec, 607 bytes/sec Throughput average achieved for complete session: 4 frames/sec, 140 bytes/sec Average receive rate from "TOM-LAPTOP": 0 frames/sec, 24 bytes/sec ********* Log file closed *********

Hi Pete, Since this is a relatively rare occurence I for one will definitely not stop using the wind smoothing features in FSUIPC - I much prefer the overall smoothness that you have achieved, with the occasional issue on approach a drawback but not a showstopper. Keeps me on my toes, after all, so I don't forget the possibility of a missed approach :) Much worse before, with aircraft overspeeding and crashing due to overstress. I don't think I can reproduce it to order, but the next time it occurs I'll grab the files that you requested. The METAR data that I was looking at was what ASX showed me for location I was at, not any other stations. I'll take a look at ways of obtaining that information. Tom

Hi Pete, The METARs at the time did not indicate any wind variance. In the first case the wind speeds were at 20-25 kts, the one time it happened on the ground had winds around 5 kts. I don't know how you simulate wind variance, but I would expect an element of randomness. In these cases there was no random shifts in direction or strength - the wind direction moved through an arc at the rate allowed by wind smoothing, then instantaneously jumped back to the starting direction and the pattern repeated, exactly the same on each iteration. No changes in the wind velocity. As previously mentioned this is an infrequent occurence, and this far it has only happened during approach or on the ground. Tom

Once in a while I get a problem with the FSX winds, usually on final approach to a landing. What will happen is that the wind will change direction over an arc of about 120-180 degrees within a few seconds. The wind direction will then jump back to the starting position and go through the arc again, etc. This goes on for a while while I climb and go around, until it stops as suddenly as it began. It happened again today, this time while I was still parked at the terminal (I had wind smoothing at the surface level enabled in FSUIPC). This time I tried disabling FSUIPC surface level wind smoothing, and the problem was gone. Of cause this is only a single data point, but in case this problem does have something to do with FSUIPC wind smoothing, what kind of data can I collect the next time that can help find the cause of this? I have all sorts of stuff installed with FSX, but things I think are relevant are: FSX SP2, FSUIPC 4.26 (and 4.261 since yesterday, problem seen with both) configured to smooth wind and pressure, and Active Sky X (wind smoothing in ASX disabled) on a different computer. OS is Vista32. I've seen the problem both with and without surface wind smoothing enabled, and it has happened with two different airplanes from different vendors. Tom