Pete Dowson

What was the previous version of FSUIPC4 you were using? What do you expect to see when pressing the 0 button 4 times? I don't have enough information to understand what you think is wrong. Pete

Yes -- and please do ask them to contact me if they believe there is something amiss with later versions. I can only fix things if i have information. They can reach me on petedowson@btconnect.com if they are averse to using the Forum. I don't mind working with developers off-forum. Pete

Assuming you mean 4.994a, the current version, the previous one was 4.944, released less than a week before. The last one released in August was 4.943, on the 15th August. The only changes between them are these 44. Support for a range of read-only offsets for the PMDG 777X data is added, sharing the same offset areas as the PMDG 737NGX data. A document is installed in FSUIPC Documents which lists all these. Note that, at the date of release, this facility has not been fully tested so feedback is very welcome. 45. A recent error in the Lua display facilities, including the ipc.ask function, could result in unwarranted window re-draws and/or early closures. This is now fixed. Of those the first isn't working yet. I'm dealing with than now ready for the next release. Not really. There's never any point in going backwards in any case. You need to work out what has changed. Can you not use any of FSUIPC's logging facilities to detect the problem? I can help interpret the results of logging for you. I know OF "SPAD", but i do not know anything about what it does. There are hundreds of utilities and add-ons using FSUIPC. I don't have time to look into every one, and I don't use any Saitek devices. After all, lighting switches are rather basic and simple, there are easy FS controls ("events") to handle them. Are they not being sent? It is really up to each add-on provider to test his own add-on. If they need assistance from me I can of course provide it, but I cannot fix other folks programs nor help with FSUIPC changes without knowing what I'm supposed to change or fix. Pete

You "upgraded" from what version of FSUIPC? I'm afraid i know nothing at all about SPAD so cannot help. Can you ask their support? What part of FSUIPC does SPAD use in any case? Pete

I'm not a maths teacher either ... this is not really the Forum in which to learn any.thing you forgot from 1st grade. But: If 2*PI radians = 360 degrees, as I said, then obviously 1 radian = 360 / (2 * PI) degrees, or 180/PI. So multiply radians by 180/PI to get degrees. Surely, if you intend to fly at all you need some idea of simple arithmetic like this? :-( Pete

You are taking this out of context. You asked if it should be in a function. That was my answer. And no, nothing will call your plug-in again and again after a certain time UNLESS you use an event which will do this. THEN you need your code to be in a function. If you want a function to be called every 5 seconds, for instance, you would use event.timer(5000, "name of your function") [Auto] run plug-ins suit simple scripts needed only once OR scripts which stay resident and activate on events. Otherwise plug-ins are assigned to do actions in response to button presses, switches or axis movements. Pete

2EA0 is in radians. Looks like your gauge has it in degrees. There are 2*PI radians in a circle (360 degrees), so it is simple arithmetic, no? This is not an FS or FSUIPC question, but one of simple maths. Or have you never hear of radians? Sorry, I don't really understand the question. Are you trying to change the actual trim being used by the aircraft, or just make the value look different to some external program of which you have no control over? If the latter, what FSUIPC Clients are you using which you wish to fool? Pete

Toggling off/on only works withing one session. It doesn't remember the settings from session to session. When there are no previous known settings, and in your restart case, the toggle from 0 simply sets the airline traffic value, to 100% (or optionally to the value you give as a parameter). It won't touch the others as it doesn't know what they should be. If you want specifty particular values separate there are controls for that -- Airline traffic density set GA traffic density set Shipping traffic density set Pete

Are you assigning in FSUIPC or FS? If in FSUIPC, do you see the Input values increase steadily, or jump? If you calibrate in FSUIPC, what are the IN and OUT values shown on the left hand side at that 25% point? It most certainly sounds like bad calibration. Pete

There are 8 offsets, 30F0-30FE. Did you not try searching the Offsets List? That's what I have to do -- I couldn't possibly remember them all! ;-) I think all PDF viewers have search options. Pete

Please never say that. All versions have numbers. The 'newest' is 4.944a. Check. Folks have been known to say "latest" or "newest" and really meant "the last one I noticed" and have been a year or more out of date. Nevertheless, whatever version: Assuming FSX sees the buttons (does it? You don't say), the most likely problem is an installation error by the Saitek driver. The registry entry assigning an ID is omitted. FSUIPC relies on the Windows Joystick ID (a number from 0 to 15) in order to read it. There's a utility you can use to assign your own ID number, to correct this. Please see this (new) FAQ subforum topic: Fixing joystick connections not seen by fsuipc Pete

Sometimes the installation program for a joystick does not fill in all of the Registry entries, with one entry important for the way FSUIPC works omitted. This is the Windows joystick ID number, a value from 0 to 15. This seems to be more prevalent on Windows 8 and 10, but wherever it occurs the following might help: Download JoyIDs here http://airgroup51.ne...hp?topic=2435.0 Install the program then run it. You should see your connected joystick(s). Double click on the problem one (should highlight green) and click on a different Id# to move it there. This will fix the entry in the Registry. You can move it back again if you wish. It won't affect anything else. Pete

Well FSUIPC will be doing exsactly the same thing and it will most certainly not have any built-in delays. It sounds very similar to the sorts of delays folks are getting on Win10 with Autosaves -- maybe revolving around process or thread switching. Hopefully Win10 will be fixed by its automatic updates in time, but like all new things it seems rather buggy at present. I will be staying with Win7 for the foreseeable future. Easily the best O/S Microsoft have ever done! Pete

Well, there's an error already, in the first line already! Offset 0x330 is most certainly NOT a 65-bit signed number. 64 = 8 x 8 = 8 bytes. Why not actually check the offset details in the list. You'll see 0x330 is 2 bytes = 16 bits = a word. And because the pressure cannot be negative it is unsigned, so "UW". Second error. "BaroSTD_cur = 0" will set that variable to zero. Comparison is ==. Please do be more careful. Programming is a precise practice -- garbage in, garbage out. I'm not sure what you want to do with this: but it will simply display the text "QNH_our". Did you want the value instead? "" denote text strings. The same errors are repeated later. Not sure what you want 8888 to represent. Pete

FSUIPC does this automatically for all the files it knows, just set the number you want to retain to 4. For files it doesn't know you have to add details into the INI file. There's a section in the Advanced user guide explaining all this -- it is listed in the Contents, "AUTOSAVE: INI-file only options". Pete

FSUIPC's autosave is optional and is defaulted off in any case. You must have turned it on. The PMDG cockpit state saving is automatically done when it detects a flight being saved. It isn't independent. Pete

Sorry, an oversight. 49430004 means "4.943d" which was the version of 4.944 under test and was identical to 4.944. It'll be fixed on the next update. Thanks for reporting it. Pete

And in your searches did you not notice that version 4.937 is well out of date and cannot support the current FSX-SE release? The only currently supported version of FSUIPC4 is 4.944. Please always check you are up to date before asking for support. Please remove that from the Modules folder before installing 4.944. It is not needed with FSX-SE. Next time, if you still have problems, please find the Log files which are produced in the Modules folder. There will be an Install log and, if FSUIPC4 does get to run, an FSUIPC4 Log. Paste the contents of these text files into your message here. Pete

No, nothing has changed. The installer will do that if YOU copied the Loader into the FS Modules folder. If you do that it naturally assumes you want to use it! If you don't need it just delete it from the Modules folder and re-run the Installer. Pete

I used to have something like that, and at that time it worked fine with my PFDHid driver. Did PFC supply no documentation? Pete

But the Installation document lists the documents and other goodies you get, and does actually tell you where they are!! Why not look at that? No idea, I'm afraid, but most sophisticated add-on aircraft do their own thing and need some special attention, whether mouse macros, Local Variable (LVar) assignments or, yes, possibly Lua plug-ins. Pete

Using INC and DEC controls, whether a value increases or descreases by 1 or 10 or 100 or 1000 depends entirely on how it is programmed in the aircraft gauge itself. To increment or decrement by a defined amount you'd need a little program to read the current value, change it and write it back. That can be done with a Lua plug-in to FSUIPC, but this sort of thing is seldom needed. If you merely want the INC or DEC to repeat whilst the switch or button is held on, just select the option to repeat in the button assignments tab. There's no need to "trawl through Google" when FSUIPC comes with full documentation for you, installed in the FSUIPC Documents subfolder. Did you not even look? Pete

I don't know either the Aerosoft aircraft nor your quadrant, but you should be able to calibrate it in FSUIPC to match what you need. Have you tried? Maybe one of the slopes supported for throttle calibration will help, otherwise it ma be more a case of having more of a dead area at one end or the other. FSUIPC offers detente calibration for flaps and for speedbrake/spoilers, but for throttles the only normal detente which is set is for idle. Pete

Isn't Madcatz the same as Saitek? You say you have enabled iti n FSX "but it still won't work". FSUIPC cannot fix things that don't work. If it doesn't work in FSX at all, it won't work through FSUIPC either. Pete

None of those errors are anything to do with FSUIPC. In any case the FSUIPC installation documentation only covers the installation of FSUIPC, and your Install log shows that was perfectly successful. You have some other add-ons screwing with your FS -- FSCOPILOT perhaps? FSUIPC cannot stop FS responding to joysticks and keyboard. You evidently have a seriously corrupt installation of FSX. Pete