Luke Kolin

Pete asked you for the log. I'm sure he understands that others may not have the same results, but unless you give him more information how is he ever going to find out what isn't working?? Cheers! Luke

Neither situation is caused by excessive load. Both are caused by poor programming and (in the former) malformed data. Cheers! Luke

There's at least part of the problem. Upgrade to 4.945a. Cheers! Luke

As you point out, when you don't use SmartCars the problem doesn't occur. The problem is really a PMDG problem - with the 777 the sim pauses for an excessive amount of time when saving the flight, and I suspect SmartCars is saving the flight on a scheduled basis. Cheers! Luke

These are all FSINN/FSCopilot errors. Go to the VATSIM forums to get help for that, or just use VPilot instead. Cheers! Luke

Pete, would it make sense now to default to TCP as the protocol? Cheers! Luke

Just the FSUIPC.INI file. Cheers! Luke

I suspect c) is what did the trick. Cheers! Luke

Pete, I'm not sure. If you look at the WideClient log, the first connection is blocked because (assuming the clocks are sync'd) the server hasn't come up yet. But the second connection looks good, both client and server report that they've made a connection. During that 1 minute connection, the client reports it was receiving around 480 bytes per second, which looks OK. It looks connected to me. Cheers! Luke

The 127.0.53.53 addresses are the result of misconfigured name resolution. In those situations it's best to use the IP address rather than the host name. Cheers! Luke

127.0.0.0/8 is a localhost block. http://serverfault.com/questions/626612/dns-just-started-resolving-my-server-prod-addresses-to-127-0-53-53 Cheers! Luke

That's not the error details. Before you go farther, you will want to update to the latest version. Pete won't be able to help you with any error details until you do. If you still get the message, I'd be curious to see the FSUIPC.LOG file. Cheers! Luke

Iain, as I told you - you have a name resolution problem. Putting in the computer name will NOT work. What is the log when you specified an IP address? Is port 8002 open on the server? Are you certain? Cheers! Luke

You have name resolution problems, not address issues. You could probably tell WideClient to connect to the IP address instead of the name, or use a fully qualified host name in DNS. (If you don't know how to do the latter, do the former.) Cheers! Luke

Why is host "ALPHA" using a 127.x.x.x address? Cheers! Luke

I don't understand. Windows 7 still works. if you had a problem with your setup you could just reinstall. Cheers! Luke

No, you were right, Pete - I am battling the flu and didn't see that I was decrementing the value by one to map to a zero-offset array. Even after 28 years, I still make these kinds of mistakes. :( Thanks for looking into it. I'll make some more debug builds to give to my users to see what is going on. Cheers! Luke

Would anyone be able to validate what value is returned by Acceleration? I have SP2 that returns 2 (not 3 as the documentation suggests), so I assume Accel returned 3. It doesn't appear to be, but I don't have a copy to test against. Cheers! Luke

"Problem Exists between Chair and Keyboard" :) Cheers! Luke

I've never know a language where they were identical.... except basic. Cheers! Luke

Is the DLL in the same folder as the EXE? Cheers! Luke

Thanks - I really appreciate it. Cheers! Luke

If you have the time, an offset to provide this data (whether the user is running FSX SE) would be really helpful, as well as minor version number of available like what you did with P3D. Cheers! Luke

Microsoft Windows [Version 6.1.7601] Copyright © 2009 Microsoft Corporation. All rights reserved. C:\Users\luke.POLARIS>c: C:\Users\luke.POLARIS>dir C:\Users\luke.POLARIS>cd \ C:\>dir /s fsx.cfg Volume in drive C is Windows Volume Serial Number is 1C6F-CFAA Directory of C:\Users\luke.POLARIS\AppData\Roaming\Microsoft\FSX 01/12/2015 11:10 PM 12,026 fsx.cfg 1 File(s) 12,026 bytes Total Files Listed: 1 File(s) 12,026 bytes 0 Dir(s) 37,131,309,056 bytes free C:\> Cheers! Luke

Worst case, play with the AffinityMask setting in FSX.CFG to prevent it from using all the cores. Cheers! Luke