Pete Dowson

Just assign the button, in the Buttons and Switches tab in FSUIPC options, to "Elevator trim set", in the drop down for FS controls, and make sure the parameter field is 0. If you don't know how even to assign things in FSUIPC please start by looking in the User guide. Pete

I don't know. Do those settings exclude others? You'll need to try it. This is really an area I know very little about. I would ask over at the support site of the AI traffic program you are using if I were you. I know, for instance, Burkhard, author of FSTraffic X (support forum near here) is very helpful when asked questions. Pete Pete

You'll need to find out how those numbers relate to whatever FS can provide, then convert them appropriately. Pete

You need to refer to the FSUIPC4 offsets status document, included in your FSUIPC Documents folder. It describes each of the offsets I mentioned. Not some are control inputs, others outputs, some both. There's only one which actually gives the angle.)in radians in fact). Which you use depends on what you are trying to display. Also you'd need to consider how to convert the values in the offset (most of which are in 64-bit double floating point format) into whatever your display is supposed to show. Pete

You don't say what your previous version was, but unless it was very very old, there's been no change in any area anywhere close to joystick stuff. And all of that is identical between FSX and P3D in any case -- there's no need at all for any difference as it is Sim independent. So the disconnect problems must be very timing dependent. Obviously each version has very slight differences, milliseconds or less, in the way things happen. If the problem of joystick disconnection (especially with Saitek devices I note) is very time critical, i.e. this event before that or within so many milliseconds of something else, you can see if will vary from version to version and PC to PC, and even the same PC but with different other things going on. BTW there is a version 4.934f available now, which has a couple of changes -- some for the P3D 2.3 first Beta, not released of course, and one for Radar Contact on P3D. You are welcome to try it is case, again, the timings have shifted favourably for your FSX installation. Link FSUIPC4934f.zip. Pete

Ah, yes, there are FS controls for Rudder trim left and right. I'd forgotten those. As.long as the increment amount is okay for you they are fine. The only advantage of the FSUIPC offset control method is that you can choose the size of the increment. Pete

Is this the default FSX Airbus, or an add-on aircraft like that from Aerosoft? If it is default aircraft then the rudder trim offsets are 0488, 0498, 0C04 and 2EC0, which I just found by simply searching the offsets list (did you try this?) However, these are all designed to work as continuous axis controls/readouts, not using INC/DEC events. You can INC/DEC them, but you'd either need to program this in a Lua plug-in, or use FSUIPC's Offset sword inc and Offset sword dec controls. You can action these controls via offsets -- you write the parameter, a 4-byte value, to 3114 then the control value to 3110. But I doubt whether the software supplied with your control card can do 2 x 4byte writes, or one 8 byte write? Check. If not then you need to see if you can make it trigger a joystick button -- either a real one, seen by Windows, or more likely one of FSUIPC's "virtual buttons", done by toggling a bit in the offset range 3340 ff. You can do the latter with onw 4 byte write to offset 29F0. Once you have FSUIPC recognising your button presses you can program them to the offset controls in FSUIPC assignments, as suggested above. There's an exampler of how to do this in the FSUIPC4 user guide, in the box on page 31 or close. That's for elevator trim, but the same applies to all the trims. Just use offset 0C04 instead of 0BC0. For reading and displaying any of the values you'll need to consult your Opencockpits software, because whilst FSUIPC supplies the values you need something to convert them to displayable form and send them to the hardware. If you are using an add-on aircraft then I don't know whether this will apply, because many sophisticated add-on aircraft do their own thing. Regards Pete

In the axis assignments tab, assign the hat to the FS control "Pan view". That's the same as the default assignment for the hat in FS. Pete

Why programming a change on release? A value of 1 will be very slightly off-centre (by 1/16384th of max displacement! ;-) Pete

Construction of macros to write to L:Vars is covered in the Macro Controls section of the FSUIPC Advanced User's guide -- it is listed in the contents. Reading L:vars can only be done in a Lua plug-in. There's a button/keyboard assignable control in FSUIPC's drop-downs to List all current L:Vars and their state, and there's an example Lua plug-in provided which, when run, gives not only the list but changes in real time. Pete

Ah, I'll use this method to see my GPU temperature. Thank you. I am actually suspecting the fan on mine in any case -- it sounds decidedly odd. Pete

You are welcome. I'm pleased you got everything sorted out! Pete

There's a small chance it might be operating internally using a control. To check that, enable Event logging in FSUIPC logging options tab. If you also enable the Console Log there and (temporarily) run FS in Windowed mode, you'll be able to see if a control is used in real time, when you use the mouse to operate the switch. There are two other possibilities, both depending on how the gauge containing that switch is programmed: 1. Mouse macro. You'll need to refer to the documentation for this. Mouse macros only work with gauges and panels written using the Microsoft C/C++ panels SDK. 2. L:vars (local panel variables). You can have a macro which writes to a named L: var. This tends to be applicable to gauges and panels written in XML. To find out you'll need to list and monitor these variables. There is an assignable FSUIPC control which will list all current L:vars and their values at that moment, or you can assign a key to the Log liar lua plug-in provided in the examples -- that lists them and all subsequent changes. If none of these work, and, as I'm assuming, the originator has not provided an assignable key press, then there's really no answer. With a 2D fixed position switch (rather than VC) you could consider actually using the Mouse library functions in Lua to position the mouse pointer and clicking the. Button -- or using a dedicated program for such things, like Luciano Napolitano's Key2Mouse program. Pete

I've moved your post from the FAQ subforum, which is the repository and reference for answers to frequently asked questions, to the Support Forum, where it can be answered. Please only ever post support questions to the Support Forum! You seem to misunderstand something quite fundamental. Programming a button to do something can never stop things happening, or even do anything at all, when the button isn't actually pressed, because whatever you set isn't even referred to until and unless you press the button! Isn't that reasonably obvious? So it seems your Aerosoft Beaver trim doesn't work in any case. You'll need their support to sort that out. Incidentally, FSUIPC only interfaces to built-in FS functions. if an add-on aircraft does its own thing you'll need to find out how to drive it in whatever way its designers provided. Pete

Well, there was certainly a lot later on, where folks were talking about the error occurring when saving a flight. The flight is saved okay as <name>.fxml. That would be a valid flight file which WILL most certainly load okay when RC requests it. Why on Earth RC is complaining that the FLT file is missing, when it does not need it, does not read it, and does not refer to it, I have no idea. Even "Ronzie", when asking JD, was assured that RC does not need or use the FLT file. I'm afraid you are completely dependent on a more accurate answer from JD. BTW, why, later on, did you ask if my DLL change also fixed Mr. George's problem when the only problem he seems to have reported was the "same os the OP", i.e. you? Pete

Interesting. How did you identify it as the GPU? I have an older PC which does something similar sometimes. I always assumed it was down to all the other processes and services I have running on it -- it's my general use "dogsbody" PC! ;-) Pete

Well, to be exact, it checks for devices in the Registry, and uses the number assigned there by Windows. It must use those numbers in the calls it makes to the Windows joyposex API. If Windows assigns different numbers it's because you use different sockets, or other devices take the number last assigned. If you are changing connections, simply use FSUIPC's joystick lettering facilities which is designed explicitly for this. There's a section on this in the User Guide -- see the contents list, easy to find, near the beginning. Well, unplugging things isn't generally a good idea, certainly. And maybe not referring to documentation? Pete

You are using an unsupported version of P3D -- you need to update it! Please read the release notes which come with every FSUIPC update, and the pinned warnings at the top of this forum! Pete

FSUIPC always numbers buttons from zero, same as FS and Windows do internally. Many user interfaces, including FS's add 1 to show them as 1-32. It doesn't really matter, just assign to whatever it says. Pete

First time WHAT has happened? I don' t see anything wrong and you don't state any problem. [LATER] Okay, my friend Thomas has just pointed out that the folder, pointed to by the Registry entry for FS9, actually points to: "G:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\" and of course Microsoft, in its wisdom, also installs an FS9.exe in the FSX folder, so it passes the test that the FSUIPC3 installer makes. You have two choices: 1. Delete the FS9.EXE from the FSX folder and run the FSUIPC installer again. It should ask you to find the correct folder or, better (because the Registry problem will affect other installers, not just FSUIPC's), 2. Fix the Registry entry for the FS9 EXE path so it points to the actual FS9 folder. I don't know how your registry got into such a mess. Maybe you were using some program designed to fool some other installer that FSX was in fact FS9? I know there's one which does this sort of thing for P3D and FSX. I think there's a program around t help fix this sort of thing, but if not then you'll need to run RegEdit and change the EXE Path parameter entry in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\9.0 to point to the full path of your FS9 installation. And, please, next time you report a problem, please actually state what the problem is. Pete

That must be a very old version of FSUIPC as there has not been a code signature check in FSUIPC for a long time! I cannot support old versions! Pete

I'm certain FSCommander has nothing whatsoever to do with axis inputs. You are just seeing random effects I'm sure. Pete

If the key file caused FSUIPC to not respond properly to applications, it was an illegal pirate key in any case. And version 3.82 is very old and not supported in any case. Pete

Well, although many folks seem to be reporting that assignment in FSUIPC rather than in FS does stop drop-outs, I am really at a loss to understand why that should be so as FSUIPC uses pretty much exactly the same facilities in Windows as FS. There's actually starting to be almost as many folks saying FSUIPC doesn't help as those saying it does. At least this seems to be the case for Saitek devices. My opinion is that it cannot make up for what appears to be a fundamental flaw in Windows, or possibly flaws or Win8 incompatibilities in Saitek drivers.. Regards Pete

Sorry, the SimKit supplier is the only place you are likely to get help. I can't believe you get no information with them! Seems you chose the wrong parts if you can't use them. Maybe you can find someone else who uses them, but there's really no way I can help. You always need a driver, even if you have to write one yourself -- and in the latter case you need information on how to handle the gauges! Pete