Pete Dowson

Since when successful the FSUIPC_Read call returns "TRUE", the FSUIPC_Write function will only ever be called if the Read fails! surely that is the opposite of what you want. Remember, in C conditional combinations are only evaluated as far as is necessary to determine the result. Try && instead of ||. Pete

Cutting fuel is usually performed by reducing the Mixture control to zero. The fuel tank valve switches are used afterwards to ensure no leakage from the tanks -- you should always cut fuel by reducing mixture first so that there's no fuel left in the engine which could then cause accidentally starting if someone rotated the props. Check the assorted mixture controls -- Mixture Lean is what you are looking for. Pete

Yes, but is this for the PMDG 737NGX? If so you'd be better off using the control numbers, as documented in the ".h" file in the NGX SDK. If you are programming buttons to send keypresses, just do so on the left-hand side of the Buttons & Switches tab. The only use of the "press&release" control is when either programming keypresses via offsets, as from another program, or from the right-hand side (zones) part of the axis assignments facility. There is no parameter if you simply program the buttons to send keypresses. It's just a simple matter of entering the keypresses themselves! If you must use the "press and release" control, then the parameter is the numerical version of the key (e = 101), from the table given, and the "ctrl+shift" part is worked out by adding the values for those together (as in the list provided), multiplying by 256 and adding the result. Shift=1, Control = 2 so 3 x 256 = 768, 768 + 101 = 869. Alternatively and maybe more simply you can use the format "JsBk" where s = shift codes and k= keycode, so J3B101 would be the same as 869. Pete

Sorry, no idea. FSUIPC merely lists the controls catalogued in the FS module called "CONTROLS.DLL". I know there are several with do not work at all, several that are mis-named, and probably even more that may do something in the right circumstances. The "Bail out" one may merely be a leftover from the Combat Flight Simulator series. Pete

Assuming you mean "mouse macros", then it all depends on how the gauges were written. The technique involves finding and hooking into the actual code, and for many gauges there either isn't any such code 9only interpreted XML) or the gauge has been written with no regard to the standards laid out in the C/C++ gauge SDK. Most Microsoft gauges aren't compliant at all in most areas. However, mostly they do obey the FS controls, so it is less important for default aircraft. Pete

Yes. It's an FS bug. They got the names the wrong way round! (FSUIPC merely gets the list from the FS "CONTROLS.DLL"). Pete

Thanks! Pete

I think removing airports and sceneries you never go near would only improve loading times, not really help with performance and OOMs -- excepting that one side effect of less airports is less AI traffic arriving from those airports. Pete

Do you mean "does" or "doesn't"? The main control axes should be enabled on the "Flight Controls" page, and the quadrant is just assigned as instructed once enabled. All is explained, with pictures, in the PFC DLL documentation. I've never had to explain it before so I think it is all covered there. No. Pete

The parameter is supplied in the variable named ipcPARAM, as documented. Not sure how you managed to miss that? The value is also set for a running Lua plug-in by the LuaValue control. The other answers seem to be answering a different question altogether, one far more complex Is it me that's missing something? Pete

I don't really know. FSUIPC simply interfaces to the FS mouse look option. Does the FS implementation do the same thing? Maybe it is related to "Opus as Camera view software"? Pete

You'd need to write a small (one-line) Lua plug-in to do this, and have it executed by a profile or aircraft-specific [Auto ...] section in the FSUIPC INI. Pete

Sounds like you are using a registered install of FSUIPC with either a pirated key, or on a PC with a date set before your purchase date. Pete

Sounds like the button you are using is a toggling button -- one which a press-release action switches it on and off, alternately. Buttons on bedside lights (for example) operate like that. Keyboard commands? Are you holding the key pressed when the button is pressed and releasing it when released? Where is the keypress defined -- in FSUIPC or in WideClient? It is not a good idea to use keypresses in any case. Why not assign direct ot the relevant FS controls? I think you need to be more explicit on what you are actually doing! Pete

Are you using a registered install of FSUIPC? If so, it sounds like you are either using a pirated key or you have the date in your PC set to one before your purchase date. Pete

Sorry, no. The option screens appear to be confusing enough (judging by the support I need to provide) without adding things just for errors in add-ons which should have been corrected there. If I started doing that there's be a load more I'd need to add too! Pete

I've no idea about SIOC scripts, but, as documented, the doors each have one bit -- bits 0, 1, 2 and 3. If SIOC cannot handle bits you'd need to write a Lua plug-in to act as an interface. Pete

All my modules for FSX work fine with P3D. They simply interface to FSUIPC4 in any case, and it is FSUIPC4 which has to be changed for each update. Pete

With FSX, FSUIPC can only intercept messages written via FSUIPC, not those written directly through SimConnect. Pete

The FSUIPC offsets for READING the values are in the document I provide when you install FSUIPC4. Switches and dials are not controlled by the mapped offsets in any case -- the offsets are only for reading data. All of the switches and dials can be controlled by sending controls -- the appropriate control numbers can be derived from the list in the .h file and can either be sent via FSUIPC 3110 or can be assigned directly to buttons or keypresses. Pete

You can use the "Deny" facilities, parameters in the INI file, to prevent all or specific (WideClient-loaded) applications from writing to specific offset. But this does not really suit your problem, and it may result in that program getting stuck in a loop if it sees its updates are not working. Surely, for displays of gauges only there are alternative applications you can use? WideClient will transmit buttons actions to FSUIPC, but not axes. Really you are much better off connecting aces directly to the FS PC otherwise the latency can become a problem. If you must send axes from a client you can do it easily enough with a Lua plug-in on the Client. If both sets of control axes are assign "direct to FSUIPC calibration, then FSUIPC will automatically arbitrate between them, only taking the one with the maximum deflection from 'normal'. This is okay for dual control, assuming your copilot does not go crazy and try to outdo your control. In real aircraft of course both controls operate all the time (and actually move together). Pete

Please install 4.858 or later and try again (see Download Links subforum). Also, when you ran the Installer, did you run it "as administrator", as documented? Else it may not have access to the correct paths. Pete

I cannot possibly support such an old version! Please update. Pete

Please see the FAQ subforum thread entitled FSX fails to run after FSUIPC4 first installed Pete

Without spending more time than I have trying to analyse what you are doing here, I cannot advise. Perhaps you could point out what you think is wrong more explicitly? Before that, please note that Lua plug-ins run independently of everything else. Your entries merely load and start them. They are running in their own threads in their own time. Pete