Pete Dowson

There's really no such thing as a "poor FSUIPC configuration" provided you don't mess with WideFS paramters. The main thing should be to keep the FS frame rates down to something which works smoothly for everything -- like 30 fps. 40fps is fine for a network of relatively unloaded PCs and Laprtops. Also try to avoid WiFi which is never so good for the sort of continuous exchanges in use here. I'm not understanding what this "activesky snapshot" is. Are you changing the actual cloud graphics and so on on every load? I've only ever selected ones I like and leave them be. If you have programs messing with graphics I'd probably say run them on the same PC as FS. Also ActiveSky might be better on the FS PC in any case, especially if you keep FS off CPU Code 0 but using the AffinityMask. It isn't doing a lot all the time but when it does update the weather there's a lot of traffic. Pete

Nothing's changed recently to affect that, and it works fine here. But I always need VERSION NUMBERS. "Latest" isn't really helpful I'm afraid. It usually means "the last ones i saw" and that's sometimes turned out to be years or more older! Pete

All these are standard controls for default aircraft, but maybe you are using add-ons? One which does confuse folks is the jet idle/cutoff lever, which may be what you mean by "start and cut engines"? Those are fuel mixture levers, effectively, and operated by the Mixture Lean and Mixture Rich controls. The others are all listed fairly evidently, whether in FS's own assignments or FSUIPCs. you could also refer to the list of controls provided in your FSUIPC Documents folder. Pete

Maybe AirSimTech has a short timeout on responses from FSUIPC and the 3D reforming takes longer than that whilst preventing other FS or Simconnect processing. Pete

This is really completely unrelated to FSUIPC. I don't know of a program "imbedded" like that, but then I don't use FSInn. The FSUIPC installer most certainly touches nothing outside its own few files in the Modules folder and the FSUIPC Documents folder. Maybe FSInn support can help? Pete

I notice you are only using 1 byte for each. Is that enough? That range of an unsigned byte is only 0-255. How are you running it? Just puting it in the folder won't run it. Pete

No, never changed, always in same places -- one corner on the Key assignments, the other corner on the Button assignments. Pete

Oh dear! You are inventing your own syntax for the Lua functions? Please read the documentation more carefully. Also look in the FSUIPC log file when a Lua program does not work and you will see the Errors reported! This is all wrong: event.offset("9410", "6", "FaultLight") "6" is not a data type. Read the data types list permissable. "UB" is okay for "Unsigned Byte", but "6" means nothing whatoever and will be a reported error. Is 9410 a decimal offset value? It's unusual to see offsets exressed in decimal. Are you sure it isn't 0x9410? (No "" needed). To test bit 6 in a byte you have to use the logic.And function to get the bit out of all the others. Like so: if logic.And(value, 64) ~= 0 then -- Checks to see if bit 6 is set You And with 64 because bit 6 is 2^6 = 2 x 2 x 2 x 2 x 2 x 2 = 64. See the FAQ thread on bits and bytes. Pete

WideClient doesn't care about the filename, it automatically starts any .lua plug-in it finds in its own folder as soon as FS connects. Pete

Sorry, I don't understand the question. Pete

There's a Lua plug-in server and client example provided in the Lua examples installed in your FSUIPC Documents subfolder. It isn't so hard to extend that as you wish. I think you misunderstand. The WideClient interface is identical to the FSUIPC one. That's the whole point of WideFS, to allow applications written for FSUIPC in any language to run over a Network too. Pete

There's no way anything in FSUIPC has any relation ot sceneries. And I have every single UK2000 scenery installed n any case. I don't think your assignments are being lost, only that your inputs are not being seen. Are you using Windows 8 by any chance? That seems to be a problem many folks have with that. Pete

What do you mean by the "FSUIPC text window"? The multiline one has positions which get saved by FS in Flights, so you simply need to save the flights. If you mean the single line window at the top then I don't think that's saved by anything, not repositionable except manually. But it might be. Save a flight with it displayed and see if there's a section for it. All the Window things are saved in sections like [XXX Window] Undocked=False ScreenUniCoords=500, 400, 7192, 441 UndocCoords=0, 0, 0, 0 so can have dfferent sizes and positions according to docking state. Pete

The PFC driver which drives the serial-linked PFC Throttle console Unit is one which has a full set of menu entries/tabs and extensive documentation (PFC.DLL for FS9 and PFCFSX.DLL for FSX/P3D). I've never heard of a HID version, and it sounds like you installed PFCHID.DLL which is for the newer USB/HID based consoles. If that's what you have then everything is done in FSUIPC. BTW, all my FS software is available in Download Links subforum above, and most of it also on the Dowson page over at Schirattic.com. Pete

There has not been any changes in FSUIPC weather setting for FS9 for years, and certainly it is not in control of runway selection. In fact nothing can control FS's own inbuilt runway selection. If ASE is setting the winds and they are setting correctly, that's as much as anything or anyone can do. The rest is entirely up to FS's internals. If I were you I'd look at getting a better ATC program, like Radar Contact perhaps. Pete

Er .... you have both a joystick and a yoke simultaneously controlling aileron and elevator positions? Not good, unless you can park them in a position completely absent from jitter. With a registered install of FSUIPC you could have the joystick assigned for some aircraft and the yoke for others. They won't interfere then. It'll be a matter of creating two profiles and assigning appropriately. You wouldn't assign in FS then. Pete

Nothing in FSUIPC has changed, and FSUIPC is totally unaware of clickspots, so you'll need to see what change you've made. A new add-on aircraft, perhaps? Pete

Assuming the data set on your computer is correct (check that first), you are most certainly making an error. All three parts must be exactly correct -- name, email, key. Cut and paste if you aren't sure. Pete

The first is not really as much an error as a safeguard against replacing a newer version with an older one. It's nothing to do with registration in any case. The second proves that you are trying to use an old unsupported version of FSUIPC and Installer, because there has been no signatures on any version of FSUIPC since earlier this year. The current supported versions are 4.92 (for FSX/P3D) and 3.999z8 (for FS9). Pete

It is only possible to run WideClient next to FSX (or, indeed, another copy of WideClient) if a different ClassInstance is used -- it's a parameter in the WideClient.INI file. However, changing the ClassInstance changes the windows class name used by most FSUIPC applications to find the right place to send their requests to. Some such applications also allow this ClassInstance to be specified, but not many. The problem is the same one which prevents two copies of FSX (or even FSX+FS9, etc) running at the same time on the same PC -- they don't allow more than one instance of the main Window class. Try it anyway. Maybe PlanG will still find WideClient with a different Instance. Otherwise your best bet would be to ask the PlanG author if he'd add an equivalent ClassInstance facility in his program. Pete

I am not sure wat the question is here, but if you are after the coordinates and names of all the gates at an airport, then that is a database matter. The free program "MakeRunways" will generate a Gates data file from your installed scenery. Maybe you need to look at that? Pete

I think you must mean "anywhere in an [Auto] section which gets the Lua plug-in still operating when you load the 777". When the Lua file is merely listed in the LuaFiles list, or referred to in an assignment, it will not run unless the assigned action is used. Your best best is to simply kill the plug-in when the 777 is loaded. You could do that with a LuaKill call in a profile-specific [Auto] section for the 777. Pete

No. Whether you are on the ground or flying does not affect weather setting. When you say you are using the METAR description, do you mean the SimConnect METAR format for FSX, or are you decoding a METAR and using the binary data methods, perhaps in FS9? you don't even say which Flight Sim you are using. How are you detecting that nothing is changing? Are you at the Destination when you set this destination weather? Whether you want to continually change weather for all near airports is surely up to you. You could simply set all the weather at the start or modify it as you fly. Different weather add-ons work differently. It may be smoother to set them the once at the start, but remember the FS weather is dynamic -- it will change in any case (there is a rate of change slider in FS's weather options, but even at minimum it still changes). In FSX it is not possible to specify cloud depth. FSX decides that for itself depending on cloud type. It's a major deficiciency which they were supposed to correct but didn't get around to it. This doesn't stop you having multiple layers though. Pete

I'm afraid I don't know this "FSUIPC Exporter", but I do know that FSUIPC has to direct access to the Wilco aircraft. I think there's an add-on program which you need to use to extract data from the Wilco and write to FSUIPC offsets, but I don't have details of this. Perhaps this is what you call "FSUIPC Exporter"? You ask for help, but exactly is the help you need? Are you writing a program in C, C++, Basic, C# or what? Have you downloaded the FSUIPC SDK to see the examples there? Do you know how to program? Pete

The crash information is useful, but not conclusive. On the face of it the crash is occurring when FSUIPC tries to process some message from SimConnect which appears to be an AI Traffic Add/Remove notification. but the data SimConnect provides is the wrong length. However, this makes no sense to me. I suppose it could happen with a corrupted Traffic file, but it seems unlikely. Another explanation which is possible, I suppose, is that somehow the wrong part of my code is getting executed for a different SimConnect notification. I can't see how at present. Whatever it may be, it is certainly related to SimConnect data in FSUIPC's hands. I made one very very small change to test for the latter idea. Please download FSUIPC 4.920a and see if that's any different. Just place the DLL in the FSX Modules folder and run the test again. If it doesn't help I need more information. As a first step, please add these lines to the [General] section of the FSUIPC4.INI file: Debug=Please LogExtras=16384 This will produce a large log file, but I just need the last few lines before it crashes. Pete