Pete Dowson

I don't think it's a default for FSX. Sometims the gauge code uses L:Vars (local variables) as a record of switch or other setting for other parts of the add-on to refer to, NOT as an actuator for them. Pete

Sounds like bad calibration. FSUIPC calibration spreads ANY input range from -16380 to +16380. Please just follow the numbered steps in the User Guide for good calibration. The maximum position calibrated is guaranteed to give 16380, which is max thrust. Pete

Are there other USB joystick or game type devices attached? Please download and run my HidScanner program, available in the Additional Useful Programs part of the Download Links subforum, and let me see its log file. More logging of the scanning part might be useful. Try this: In the [General] part of the FSUIPC5.INI file, add these lines: Debug=Please LogExtras=x200000 (make sure you get the right number of 0's there -- 5 of them!) Then run P3D again and show me just the Log. Also, please check the Windows Event Viewer. If the crash is recorded there, in "Windows Logs -> Application" please copy and paste the details here. It'll be in some format simialr to this: Faulting application name: ... Faulting module name: ... Exception code: ... Fault offset: ... etc Pete

-16380 to +16380 is what you get AFTER proper calibration. The raw figures beforehand don't matter so much as long as they are consistent and smooth. I've often seen an input range of -7040 to 7040. Make sure that if there is a Windows game controller calibration available that this is done first, though it isn't really necessary. you can access that by asking FSX for calibration. BTW I would doubt that reinstalling FSX completely would ever help problems with one device, like your switch panel. And there's rarely a need to destroy your FSUIPC settings in reinstalling FSx. When you uninstall it to reinstall it, FSUIPC's settings are lleft intact unless you actually deleted the Modules folder! Pete

Okay. I've fixed it. It was a bit complicated. It'll be fixed in the next update. Please look out for it, quite soon I think. I really do need to verify what is happening in FSUIPC4 with rather similar code, because it looks like that should have the same problem. But I only have a default install of FSX-SE, and I cannot find any mouse-macro usable cockpit switches in any of the default aircraft. Do know of any? Can you remember, or did you only use Mouse Macros with add-on aircraft? Pete

Really? Drat. I was sure I changed the internal text as well as Properties! Pete

It sounds like you have the switch already set in the position which control 69749 with parameter 0 is intended to set, so it can't do anything. Offset 66C0 will be 0 to start with so toggling it first sets it to 1. You can change that in any of three ways: 4=P1,0,Cx0D0066C0,x01 -{offset byte togglebits, offset 66C0}-5=B66C0=1 P1,0,C69749,1  -{Custom control: <69749>}-6=B66C0=0 P1,0,C69749,0 -{Custom control: <69749>}- or 4=P1,0,Cx0D0066C0,x01 -{offset byte togglebits, offset 66C0}-5=B66C0=0 P1,0,C69749,0  -{Custom control: <69749>}-6=B66C0=1 P1,0,C69749,1 -{Custom control: <69749>}- or 6=P1,0,Cx0D0066C0,x01 -{offset byte togglebits, offset 66C0}- 4=B66C0=0 P1,0,C69749,1  -{Custom control: <69749>}-5=B66C0=1 P1,0,C69749,0 -{Custom control: <69749>}- The first two should be obvious, the last makes use of the fact that the actions are executed in the line number (value before the = ) order. Do you see the logic in these?. Pete

If the macrofile is faulty like the one you showed, it won't load. Sorry, i wasn't clear. A good macrofile will load automatically without having to press reload, as soon as you press End Macro aking. I have proven that here. I have reproduced similar problems here and i am in the process of fixing them. Yes, and it should work fine, as documented. All this is one bug in fact, in multi-action macros. I'm working on it. Odd, because the code in this area in the same, so it should have the exact same bugs with multi-action macros. I'll test that when I've fixed FSUIPC5, because i think I'll need to put the same fixes in FSUIPC4. Once you have a good multi-action macro definition it works okay. It is only a problem with the automatic creation. I think users must have made them manually, editing the Macro files (which is a relatively easy job -- easier than button programming for sure). I won't be through here till tomorrow. It is more complicated than I expected. Either that or my brain is failing with old age. Pete

Good. So it was a registry error somehow. I think the Saitek software messes it up somehow. Else I don't know why it occurs. Pete

The reason it doesn't work is that this line 4=P1,0,Cx0D000042,x01 -{offset byte togglebits, offset 0042}- is, as it clearly says, toggling bit 1 in offset 0042 (which is NOT a user offset, and in actually a character in the start-up flight name). You should have programmed it for offset 66C0, which is the offset you are testing in the next two lines and which is a user offset! Change P1,0,Cx0D000042,x01 to P1,0,Cx0D0066C0,x01 Pete

Ah, I didn't understand that from your last message. There's a rescan missing. I'll test it, and if I can reproduce it I'll insert a rescan -- i.e. the same as pressing the "reload" button on the FSUIPC screen you are using to "end macro making". (That should be your workaround for now, whilst i check). Er ... so it is recording just ONE macro with no name and performing the same action twice. Which is very wird, because I assigned several actions to several buttons or switches on the cockpit, giving each one a different name, and they came out file in the file. Aha! I see you used the same name for each action, which explains why there are two entries for the same macro, but the name being missing is a puzzle, as is the reason for the two entries being the same. I'll try to reproduce this here and see what is going on. Thanks for the clarification. BTW did you make these sorts of macros for FSUIPC4 (FSX or P3D3) at all? Pete

Like FSUIPC4 compared to FSUIPC3, FSUIPC5 is a different product from FSUIPC4, with its own registration you need to purchase. Both those changes were massive re-writes costing lots of man-hours, and FSUIPC5 was the first really major revision in 11 years (Sept 2005 - June 2016). I think it justified a new purchase. Well, it will install, but as Unregistered, so it can be used by FSUIPC applications, and WideFS too. (Incidentally, WideFS is not changed -- the same registration will work for P3D4 as P3D3 and FSX). Pete

Sorry, but I cannot reproduce this. Here it is working fine -- I just tried it. You can "Start macro making", give the same name as a previous MCRO file, and OK out, create the macros (with new names, of course), and go back and "end macro making", and the ones you just made are added the the earlier ones. The code for this mechanism hasn't been changed since it was first implemented in FSUIPC4. The only changes for P3D4, apart from the 64-bit from 32-bit conversion, were: 1) re-code to use SimConnect windows for the text display when creating (previously they were via hooks direct into the display module), and 2) detect the mouse usage via the P3D4 PDK and encode the returns that provides. Neither area really impinges onto the file creation and updating itself, which is why I just tested that again myself. Maybe if you have a reproducible sequence of keypresses which do this, you could ennumerate them please -- using a default aircraft please? i don't have add-on ircraft. Pete

The numbers 0 and 1 are the IDs used in Windows' DirectInput. Do NOT delete theme. The whole point of JoyLetters is that no matter what numbers Windows assigns, your assignments stay intact, in your case as assignments to J and Y. Can you tell me WHERE they "come up" as 0 and 1? BTW PLEASE always post support questions to the main support forum, where I've now moved it. The FAQ subforum is a reference section, not a support area. Pete

Well, three things wrong. I don't see that you followed my instructions which were: 1. one line which uses an FSUIPC Offset byte togglebits control to change the byte from/to zero 2. a line with an offset condition testing for zero, and doing one action 3. a line with an offset condition testing for non-zero, and doing the other action There's no sign of the line 1 I suggested. That's best done first in the GUI. Instead of assigning to the PMDG control there, assign to Offset byte togglebits, set the Offset field to 66C0, and the Parameter to 1. You have a line testing something for zero, but not 66C0 -- you have 66CO (with a letter O). [The letters in the values here only go from A to F, representing 10 to 15]. Then you have the same condition again (B66CO=0) instead of B66C0=1. NOTE, though, that there is another way to implement a toggle action as in this case -- the offset way is more general and can cope with any number of different actions, not just two -- but the Flag method is probably best for such simple toggles. So i'll describe that a bit too (it is covered in more detail, with examples, in the Advanced User's guide -- with very advanced applications in a Appendix). Every possible button on every possible joystick ID (so 16 x 32 or 512 buttons) has a "flag" -- an internal marker which is either "on" (1) or "off" (0). These can be explicitly set or cleared or toggled (changed) by FSUIPC controls. However, the Flag associated with each button is also toggled (changed) whenever that button, assuming it exists, is pressed. Therefore it changes with each press. In your case we can simply add two (instead of three) lines, as follows: 4=CP(F-1,1)1,1,C69749,1 5=CP(F+1,1)1,1,C69749,0 Please, by all means just blindly put this into the INI file and test it, but also see if you can understand it, and the earlier elucidations on offset conditions, because then you can apply these techniques in all sorts of ways to expand your use of buttons and FSUIPC's facilities. Pete

Hi, Benny, Well, it's taken a while for this to get to the top of my "to do" list (over two months! sorry), but it is now done -- version 4.85 of MakeRunways is now released. Please see the read me document. The Jetway indication is a command line option. Also, of course, it only handles jetways defined in the Airport Facilities Data (AFD) scenery files being examined. I don't think this will include SODE jetways. Pete

So it will be okay to uninstall the device + driver. RAW and DIRECT are two different modes you can set in P3D4 for joystick access. Check its Assignment menus , last item I think. From the files you appeanded: Y, x1E, x06A3, x0C2D, Flight Throttle Quadrant, 0, 0, 0, ... Y, x1E, x068E, x00F2, CH PRO PEDALS USB, 0, 0, 0, ... Both those device have the same ID (0) in the Registry, so the second is taking precedence. This is a Registry problem so I think uninstalling and reinstalling the quadrant should help. The other thing to try if that fails is booting with the Pedals disconnected. If that works okay, then try reconnecting the Pedals. It is also a good idea to use JoyLetters (please see chapter in user Guide about this). Pete

No. All CONTROLS (not "buttons" which are the physical things you are assigning) have parameters, but not many of them use them. Where they do (as in controls with "SET" at the end) it is usually, but not always, obvious what the parameter would be. For many controls i really have no idea about parameters. The controls list is generated automatically from within your simulator -- and in the case of P3D4 it is still expanding. There's know way I can even know what they all do. Well, in the above case just do wht I suggeted. Please just do it as I said. And NOT a "free offset" -- the Parking Brake is ONLY controlled by the offset I showed in my instructions. "Free offsets" are for your use, for whatever you like. FSUIPC doesn't act upon them. Pete

Why two Parking Brake buttons? What are you assigning it to? What Simulator, what aircraft, what version of FSUIPC? That makes absolutely no difference, ever. Why? Nothing in any of those relates to FSUIPC, except in the DLL.XML file to tell Simconnect to load FSUIPC, among any other add-on DLLs. Pete

Which Sim? If P3D is that in RAW or DIRECT mode? It still sounds like the Registry is in a mess. If you uninstall as I said, and re-boot, does FSUIPC see it there? Did you uninstall as I said and try FSUIPC without the driver? You say "without the driver it doesn't work", which makes no sense at all. It is a standard USB joystick device and Windows handles it prerfectly with no Saitek software! There's nothing in the device needing anything different. Anyway, you'll need to show me three files from the Sim Modules folder. they'll be named with FSUIPC3, FSUIPC4 or FSUIPC5 depending on what version & what Sim you are using (you never said). The files are the Log, the INI and the Joyscan.csv file. Pete

You don't need or want any Saitek driver -- it seems to often make a mess of the Registry entries for the device, and doesn't give you anything useful. Best to go to the Windows Device Manager, uninstall the device completely, including driver, then re-boot and let Windows take care of it. I have a Saitek quadrant here (the only Saitek device I have, and then only for testing), and it has always worked fine. Pete

Don't change any letters already used and assigned, or you'll lose the assignments. The numbers only should be changed, after closing P3D. Pete

Unfortunately the simulator-supplied control for Parking Brake is a toggle (i.e. one control for both on and off). However you can do it by using FSUIPC's "offsets" instead. Offsets are locations in memory where FSUIPC stores data for programs to read, but when the same locations are written it acts upon them. Offsets and their values are listed in a document in your FSUIPC Documents folder (inside the FS Modules folder), but I can show you here exactly what to do: In Buttons & Switches tab, assign the Press (= On for a latch) to "Offset Word Set" with the Parameter entry set to 32767 and the Offset entry set to xBC8. Then, on the same entry, program the Release (= Off for a latch) to "Offset Word Set" with the Parameter entry set to 0 and the Offset entry set to xBC8. That's what I do for my Parking Brake lever. Pete

You make the macros in exactly the same way as in FSUIPC4, as described in the documentation! The format in the Macro files is the same, but the values are different. You have to discard all of your old mouse macros and make new ones -- just as you would have to in any case should your FSUIPC4 aircraft have been updated. Pete

And I helped as much as I could! I said that FSUIPC does not support infdciators, and that I do not know SPAD at all. I am sorry but I really do not know everything 😞 I did suggest what you could do to find more help. I really don't know what more I can do, and I think it is quite mean of you trying to play on folks' sympathies in such matters by giving your terrible life history. many of us have problems. i could not fly for real because of an hereditary eye disease, the biggest disappointment of my life, and that is why I got into Flight Simulation. I sympathise, but I cannot help more that i have done!!! I see Thomas confirms that SPAD will help with your need, but I myself do not know the program at all (as I've now said several times). Pete