Demious

I'm working on a 'general assignment' profile, that is most functional for default aircraft, as well as as base for custom aircraft. For this I created a 4-step setup that is easy to adjust to my personal taste, for every aircraft that has to be adjusted. The idea is to use compound buttons to use modifiers to work with 4 settings on 1 switch. I did this in the following way: 61=PB,141,C65962,1 -{FUEL_SELECTOR_SET}- (Both tanks) 62=CP(-A,6)(-A,7)B,142,C65962,0 -{FUEL_SELECTOR_SET}- (Off) 63=CP(+A,6)B,142,C65962,2 -{FUEL_SELECTOR_SET}- (Left Tank) 64=CP(+A,7)B,142,C65962,3 -{FUEL_SELECTOR_SET}- (Right tank) But when I test with the default Cessna 172, the following is the result: Switch 141 (line 61) turns the virtual switch to on for both tanks (1), switch 142 with the modifier A,6 (line 63) turns the virtual switch to the left tank (2) and switch 142 with the modifier A,7 (line 64) turns the virtual switch to the right tank (3) and so far everything works as expected. When I use this in the default Cessna 208B Grand Caravan, switch 141 (line 61) turns the virtual switches to on (1) and switch 142 (line 62) turns the virtual switch to off (0), so again, this works as expected. However, when I'm in the default Cessna 172 and I use switch 142 (line 62), which should turn the virtual switch to off, as setting that is not present in this aircraft, I'd say the commands should be ignored, since there there is no position the virtual switch can go. But instead of not responding, the virtual switch turns to the left, which is a command that is reserved for the switch with the modifier A,6 (line 63). As you can see, I already made the Off-position (line 62) not respond to the modified commands, by adding the (-A,6)(-A,7), but this has no effect on the switch turning to the left tank when given the Off-command. What can I do to keep the Off-command exclusive for the Off-position of the virtual switch?

I change all 3, control number, parameter and comment, every time. I had a little trouble with control numbers at the start, but I got that figured out now. I'll keep an eye on when and what changes. I'm starting to get the hang of it, thanks for the help!

It seems like I've figured out all the commands and control numbers, I've seen them all work, but the biggest problem, at the moment, is that when I start MSFS (the start-up procedure of the sim program itself, not the loading of one aircraft/flight), the entries in the ini-file get changed into different commands. Like SET_STARTER2_HELD is often changed into MAGNETO_SET, or MAGNETO1_SET (and those commands don't even work for the starter function), but I think I've seen about every line of the magneto control change, on time or another. I already uninstalled and reinstalled FSUIPC and I've reset MSFS (removed cloud profile, which clears all adjusted settings and user data), but that doesn't make any difference. Any advise on how to prevent MSFS from making changes to the ini-file? I have two engines on a lot of aircraft, but I have only one magneto switch on my yoke, so I need to direct the switch to one engine first, and then to the other. FSUIPC7.ini FSUIPC7.log

That's the formula for assigning 2 control switches to 1 FS function, as it is written on page 21 of the manual you pointed out. See attachment. I just told and showed you: FSUIPC7.1.log FSUIPC7.ini

I think I need a little more help, here. This is all new for me. 😁 The formula (n=CP(+j2,b2)j,b, ...), that is for the lines underneath, am I right? [Buttons.C337 Skymaster] ..... 10=CP(+D,8)PD,30,C65927,0 -{MAGNETO1_SET}- 11=CP(+D,8)PD,31,C65928,1 -{MAGNETO1_SET}- 12=CP(+D,8)PD,132,C65929,2 -{MAGNETO1_SET}- 13=CP(+D,8)PD,133,C65930,3 -{MAGNETO1_SET}- 14=CP(+D,8)PD,134,C65931,0 -{SET_STARTER1_HELD}- 15=CP(+D,9)PD,30,C65927,0 -{MAGNETO2_SET}- 16=CP(+D,9)PD,31,C65928,1 -{MAGNETO2_SET}- 17=CP(+D,9)PD,132,C65929,2 -{MAGNETO2_SET}- 18=CP(+D,9)PD,133,C65930,3 -{MAGNETO2_SET}- 19=CP(+D,9)PD,134,C65931,0 -{SET_STARTER2_HELD}- The Joystick number is 0, or D and the modifier switches are 8 and 9. I added the formula in the manual to these lines, but I think I'm doing something wrong. I used the FSUIPC log to check which parameters are assigned to the switches in the aircraft, which are Magneto 1 and 2 Set (with parameters: 0, 1, 2, 3) and the Set Starter Held 1 and 2. I also tried the Magneto1_Both, Magneto1_Right, Magneto1_Left, etc... but the results of both attempts are not what I expected, or better, what I hoped for. When I turn the hardware switch (without the modifier switch), both switches in the cockpit are triggered and they make random jumps between positions. For example, when I turn the hardware knob to Both, the virtual knobs turn to Right, or when I turn the hardware knob to Off, both virtual knobs turn to Left. I checked if assignments in the default FS control section still are active, but this is not the case, all entries for this knob and these functions have been removed. Have you got any advise on how to proceed?

Yep, found it! Thank you!

Yesterday, my new Honeycomb yoke was delivered and I'm trying to figure out how to set up everything. From the default assignments in MSFS, I saw some of the functionality of this yoke works with double-switch assignments, like for trim, you push 2 switches at the same time. To make the magneto switch usable for dual engine aircraft, I need to do the same, combine the positions of the rotary knob with another button or switch, to specify for which engine it has to work. Is there a way to do this in FSUIPC7? I'm using a registered version.

I'll have a look. Thanks John!

I see its not the aircraft, when I only open MSFS, that is already happening, while no flight is loaded.

In another post I found an advise for using the logging console to find the used controls for the Aeroplane Heaven P-51, but when I open the logging console, I get a constant spam of Avionics_Maser_Set, making it impossible to use a switch and read the result. What can I do to read any input logging? Cheers, Maarten

Today I installed the payware version of FSUIPC7, everything went fine, installation, registration, all as expected, but in FS2020, for buttons as well as axes, some assignments work and some dont, while the settings are the same for each button. For example: I got to Assignments>Button&Switch, click a button on a controller, lets say, the 4-position switch on my Saitek Pro Flight Yoke, I push up and FSUIPC registers Joy# A - Btn# 32 (all controllers are properly recognised), I check the box for 'Select for FS control', and under 'Control sent when button pressed', I enter 'View Up'. When I go back to the cockpit and press the button, there's no response. Same goes for the other 3 positions with 'View Down', 'View Left' and 'View Right' and others. However, when I do the same (same button on the yoke used, as well as a button on the CH Throttle Quadrant) with the command 'Flaps Incr', it works fine, same as a lot of other commands. I've done this hundreds of times before, for FSX and P3D and I never seen this happen before. I uninstalled FSUIPC, removed leftover files, and reinstalled from a new download from this forum. Then I repaired FS2020 and tried again. Far as I can tell, the same functions as before work fine and the same functions as before dont work at all. I installed FS2020 yesterday, so everything should be up to date. Windows11 is updated, controller drivers and software, Geforce driver, motherboard drivers, etc... Everything driver related has been checked. There's not much other software on the computer besides P3Dv4 with no addons (yet), and World of Warcraft. I've looked for an ini-file (explorer search), but non is found. Log is attached. Some help getting this figured out is much appreciated. Cheers! Maarten InstallFSUIPC7.log

I've been using FSUIPC for quite a few years now and I cant imagine what I would do without. Thanks for all your efforts, for all those years, with FSUIPC4 and even more for continuing with FSUIPC5! You're the man, Pete! ;)

I think I already found the answer. Measuring 200MB of VAS and then OOM says it all, I think.

I notice that when I use FSUIPC to measure VAS use in Windows 10 Insider Preview, it is quite a bit lower than what I'm used to. I noticed that Process Explorer measures quite a bit higher than I'm used to and very unstable, it increases by as much as 200-300MB just from panning around, so I tried what FSUIPC would do and FSUIPC measures quite a bit lower than I'm used to. Can I trust the measurement of the curent FSUIPC in Windows 10, at this point, or does FSUIPC have to be updated first for this to work properly?

I saw your anouncement about your busy schedule and I cant imagine how you managed to fit it in to have a new FSUIPC ready, this fast. But non the less, an awesome and very welcome Christmass present. Thanks a whole bunch and have a wonderful Christmass, pete!