John Dowson

So you populated them, and clicked Register and it validated? Can you open your FSUIPC7.key file and check that it contains the correct information (details are in the Installation and Registration Guide, under Invalid Key Problems). Can you also please attach your FSUIPC7.log file here - you will need to run FSUIPC7 to generate this again as there is none in that image you showed. Also, please attach your InstallFSUIPC7.log file.

Then it should work when you set them via FSUIPC....as I said, it worked for your dome lights, didn't it?

I don't know - I don't have this aircraft. Have you tried it? Use the Add-ons->WASM->Execute Calculator Code menu option, and try sending each of the following: 30 (>L:VC_Miscellaneous_trigger_VAL, number) 31 (>L:VC_Miscellaneous_trigger_VAL, number) to see if those move the switch. They should work, as that lvar controls the dome switch (with parameters 38 and 39). Also try the following: 10 (>L:VC_POSITION_LIGHT_SW, number) 0 (>L:VC_POSITION_LIGHT_SW, number) 20 (>L:VC_POSITION_LIGHT_SW, number) to see if those move the switch. If they work, we can simplify the assignments. If you still have issues, please activate WAPI Debug level logging (Log -> WAPI -> Debug) and logging for Buttons & Keys, and show me / attach your FSUIPC7.ini file and FSUIPC7.log file, the latter showing you using the assigned buttons. And always exit FSUIPC before attaching files please. John

Yes - sorry, I forgot to add the conditional letter 'C and the conditional comes after the press 'P' letter'. Should be 7=BA002=10 CP(+M, 29)M,27,CPNav_Strobe_Switch_Down,0 -{Preset Control}- 8=BA002=10 CP(+M, 28)M,27,CPNav_Strobe_Switch_Up,0 -{Preset Control}-

As you can see, the presets weren't recognised and changed to custom control 0. This is because I mistakenly used a colon for a divide between the preset name and the calculator code instead of a hash symbol - sorry about that... I don't have a hash symbol on my keyboard and I forget sometimes!. The preset should be: //iFly/737-Max8/Lights Nav_Strobe_Switch_Up#30 (>L:VC_Miscellaneous_trigger_VAL,number) Nav_Strobe_Switch_Down#31 (>L:VC_Miscellaneous_trigger_VAL,number) Nav_Strobe_Switch_Up_Two#30 (>L:VC_Miscellaneous_trigger_VAL,number) 30 (>L:VC_Miscellaneous_trigger_VAL,number) Nav_Strobe_Switch_Down_Two#31 (>L:VC_Miscellaneous_trigger_VAL,number) 31 (>L:VC_Miscellaneous_trigger_VAL,number) So change those. You also didn't change the conditional button to you M device. So, change to: [Buttons.iFly B737 MAX8] 0=BA000=0 PH,5,CPiFly737MAX8_Dome_Light_Up,0 -{Preset Control}- 1=BA000=1 PH,5,CPiFly737MAX8_Dome_Light_Up,0 -{Preset Control}- 2=BA000=2 PH,5,CPiFly737MAX8_Dome_Light_Down,0 -{Preset Control}- 3=BA000=2 PH,5,C1152,50 -{pause (ms)}- 4=BA000=2 PH,5,CPiFly737MAX8_Dome_Light_Down,0 -{Preset Control}- 5=BA002=20 PM,26,CPNav_Strobe_Switch_Up,0 -{Preset Control} 6=BA002=0 PM,26,CPNav_Strobe_Switch_Down,0 -{Preset Control}- 7=BA002=10 (+M, 29)PM,27,CPNav_Strobe_Switch_Down,0 -{Preset Control}- 8=BA002=10 (+M, 28)PM,27,CPNav_Strobe_Switch_Up,0 -{Preset Control}- 9=BA002=20 PM,28,CPNav_Strobe_Switch_Up,0 -{Preset Control} 10=BA002=20 PM,28,C1152,50 -{pause (ms)}- 11=BA002=20 PM,28,CPNav_Strobe_Switch_Up,0 -{Preset Control} 12=BA002=0 PM,29,CPNav_Strobe_Switch_Down,0 -{Preset Control}- 13=BA002=0 PM,29,C1152,50 -{pause (ms)}- 14=BA002=0 PM,29,CPNav_Strobe_Switch_Down,0 -{Preset Control}- John

Did you assign your rudder and brake axis to the required offsets? This issue is now covered by this User Contribution entry: Can you please post there if you have issues setting this up. And for any problems, don't attach the lua file unless you have modified it as that is available, and if you have modified it than please explain what the modifications were. You should also enable logging in the lua script, by setting enableLog to true at the top of the lua script, and look at the log file as that shouldthen give you a clue as to what is happening. If you can't figure it out, show me / attach your FSUIPC7.log with the lua logging enabled in that script, and also your FSUIPC7.ini so that I can check your assignments. I am closing / locking this thread now - please use that one referenced above. John

Yes - that option prevents the FSUIPC main window opening, even when there is a new version, but you will still see the pop-up if a new version is available. Or how else will you know that one is available? I am very reluctant to disable this...eventually you will give in and update to the new version, hopefully... John

I have moved this post to the FSUIPC7 sub-forum. Please use this sub-forum for all issues & questions on FSUIPC7. John

If you updated, you don't need to re-register. Were the registration keys fields pre-populated from your existing key file? Did you click the 'Register' button? Is there an FSUIPC7.key file in your installation folder? And are you sure you are running FSUIPC7 from the installation folder that you used for installation and registration (sometimes people have multiple copies installed and run from a different folder)? Check using the File -> Open installation folder menu item, and see if your key file is there.... Otherwise, re-install and re-register, or search for your FSUIPC7.key file and make sure that it is in your FSUIPC7 installation folder. John

Ok, then we have: Nav switch Down, Strobe Switch Down: VC_POSITION_LIGHT_SW = 20 (NAV lights steady, strobes OFF) Move nav switch up: VC_POSITION_LIGHT_SW = 10 (NAV and strobe lights OFF) Move strobe switch up: VC_POSITION_LIGHT_SW = 0 (NAV and strobe lights ON) Nav switch Down, Strobe Switch Up: VC_POSITION_LIGHT_SW = 0 (NAV and strobe lights ON) Move Nav switch up: VC_POSITION_LIGHT_SW = 10 (NAV and strobe lights OFF) Move strobe switch down: VC_POSITION_LIGHT_SW = 20 (NAV lights steady, strobes OFF) Nav switch Up, Strobe switch down: VC_POSITION_LIGHT_SW = 10 (NAV and strobe lights OFF) Move Nav switch down: VC_POSITION_LIGHT_SW = 20 (NAV lights steady, strobes OFF) Move strobe switch up: VC_POSITION_LIGHT_SW = 10 (NAV and strobe lights OFF) Nav switch up, strobe switch up: VC_POSITION_LIGHT_SW = 10 (NAV and strobe lights OFF) Move nav switch down: VC_POSITION_LIGHT_SW = 0 (NAV and strobe lights ON) Move strobe switch down: VC_POSITION_LIGHT_SW = 10 (NAV and strobe lights OFF) Re-arrange these by switch movement: Button 26 (nav switch up): set VC_POSITION_LIGHT_SW = 10 when VC_POSITION_LIGHT_SW = 20 set VC_POSITION_LIGHT_SW = 10 when VC_POSITION_LIGHT_SW = 0 Button 27 (nav switch down) set VC_POSITION_LIGHT_SW = 20 when VC_POSITION_LIGHT_SW = 10 & strobe switch down set VC_POSITION_LIGHT_SW = 0 when VC_POSITION_LIGHT_SW = 10 & & strobe switch up Button 28 (strobe switch up) set VC_POSITION_LIGHT_SW = 0 when VC_POSITION_LIGHT_SW = 20 set VC_POSITION_LIGHT_SW = 10 when VC_POSITION_LIGHT_SW = 10 (i.e. no change) Button 29 (strobe switch down): set VC_POSITION_LIGHT_SW = 20 when VC_POSITION_LIGHT_SW = 0 set VC_POSITION_LIGHT_SW = 10 when VC_POSITION_LIGHT_SW = 10 (i.e. no change) Note that button 27 is the only state change that needs a dependency on the state of another button as the VC_POSITION_LIGHT_SW value condition is the same. The next thing to determine if you can write to the lvar VC_POSITION_LIGHT_SW ti change the position? If so, this makes things easier, as you can then just write to the offset holding the lvar to change the position. But, as you said you need to use VC_Miscellaneous_trigger_VAL (with 30 for up and 31 for down) we will use that, So, define 4 presets (in your myEvents.txt file): //iFly/737-Max8/Lights Nav_Strobe_Switch_Up#30 (>L:VC_Miscellaneous_trigger_VAL,number) Nav_Strobe_Switch_Down#31 (>L:VC_Miscellaneous_trigger_VAL,number) Nav_Strobe_Switch_Up_Two#30 (>L:VC_Miscellaneous_trigger_VAL,number) 30 (>L:VC_Miscellaneous_trigger_VAL,number) Nav_Strobe_Switch_Down_Two#31 (>L:VC_Miscellaneous_trigger_VAL,number) 31 (>L:VC_Miscellaneous_trigger_VAL,number) I am not 100% sure about the _Up_Two and _Down_Two presets: we need to move the switch two positions for some assignments, but setting the same value to an lvar twice in the same calculator code string may not allow this. If not there are a few other things to try (see below). Now we can define our assignments: For Button 26, send switch-up when when VC_POSITION_LIGHT_SW = 20, and switch down when VC_POSITION_LIGHT_SW = 0 to send a switch up, using B as your Bravo device letter and starting the indices from 1 will give the following assignment entry: 1=PB,26,CPNav_Strobe_Switch_Up,0 -{Preset Control}- then add the offset condition on the value of VC_POSITION_LIGHT_SW held in offset 0xA002 1=BA002=20 PB,26,CPNav_Strobe_Switch_Up,0 -{Preset Control}- Next, we can duplicate that, change the index number, the preset and the offset condition for the switch down when VC_POSITION_LIGHT_SW = 0: 2=BA002=0 PB,26,CPNav_Strobe_Switch_Down,0 -{Preset Control}- Doing this for each button 27, we get: 3=BA002=10 PB,27,CPNav_Strobe_Switch_Down,0 -{Preset Control}- 4=BA002=10 PB,27,CPNav_Strobe_Switch_Up,0 -{Preset Control}- and then we need to add the additional condition on the strobe switch position (buttons 28 and 29): 3=BA002=10 CP(+B, 29)B,27,CPNav_Strobe_Switch_Down,0 -{Preset Control}- 4=BA002=10 CP(+B, 28)B,27,CPNav_Strobe_Switch_Up,0 -{Preset Control}- Doing this for all buttons, we end up with: 1=BA002=20 PB,26,CPNav_Strobe_Switch_Up,0 -{Preset Control} 2=BA002=0 PB,26,CPNav_Strobe_Switch_Down,0 -{Preset Control}- 3=BA002=10 CP(+B, 29)B,27,CPNav_Strobe_Switch_Down,0 -{Preset Control}- 4=BA002=10 CP(+B, 28)B,27,CPNav_Strobe_Switch_Up,0 -{Preset Control}- 5=BA002=20 PB,28,CPNav_Strobe_Switch_Up_Two,0 -{Preset Control} 6=BA002=0 PB,29,CPNav_Strobe_Switch_Down_Two,0 -{Preset Control}- So try that - just paste those entries into your profile buttons section, and change the joystick letter to the one you are using (also in the compound condition) and also make sure the index numbers are unique in your section. If the presets to move two positions don't work, you could try the following instead: 1=BA002=20 PB,26,CPNav_Strobe_Switch_Up,0 -{Preset Control} 2=BA002=0 PB,26,CPNav_Strobe_Switch_Down,0 -{Preset Control}- 3=BA002=10 CP(+B, 29)B,27,CPNav_Strobe_Switch_Down,0 -{Preset Control}- 4=BA002=10 CP(+B, 28)B,27,CPNav_Strobe_Switch_Up,0 -{Preset Control}- 5=BA002=20 PB,28,CPNav_Strobe_Switch_Up,0 -{Preset Control} 6=BA002=20 PB,28,C1152,5 -{pause (ms)}- 7=BA002=20 PB,28,CPNav_Strobe_Switch_Up,0 -{Preset Control} 8=BA002=0 PB,29,CPNav_Strobe_Switch_Down,0 -{Preset Control}- 9=BA002=0 PB,29,C1152,5 -{pause (ms)}- 10=BA002=0 PB,29,CPNav_Strobe_Switch_Down,0 -{Preset Control}- Here we are sending he preset twice, with a short pause between each one. The trick here is to get the pause large enough so that both presets are executed, but small enough so that the update of the lvar has not been received yet to update the value in the offset condition on 0xA002. I have used 5ms - you can use logging to determine if this needs to be increased or decreased (probably increased if anything - try 10ms next and so on). Give those a try and let me know if either works as expected. John

Also, this post should be in the FSUIPC7 sub-forum - I will move it. Note that all your posts seem to be for FSUIPC7 / MSFS, but you keep posting in the main support forum. Please use the specific sub-forum for FSUIPC7 for all questions / issues with FSUIPC7 / MSFS2020 & MSFS2024.

It should work via assignments whenever it works in the VC. Can you show me your assignments (i.e attach your FSUIPC7.ini file), and a log (or log extract) showing you first doing this in the VC, then trying the same via your assignments. Also set logging for Buttons & Keys (as well as Events) for this log. This should show if the same events are being sent via assignments as using the VC.

Just use logging - set logging for events, open the console window and use the VC to trigger the action that you want to assign. You will probably see lots of other events logged that will make the ones you are interested in seeing difficult to find. You can ignore such always-triggered events by setting the DontLogThese ini parameter, best used in the [Profile.xxx] section as such events are always different for each aircraft. John

Yes, I understood. Just trying to point out that when using two switches, one for each light, its never going to work in the same way as one 3-position switch to control the lights. The honeycomb light switches are designed for on/off of each of the lights, so however you implement this is going to be a fudge, but maybe ne that you can live with. And no need for the pictures either... Yes, that's fine. No, but you can assign to a preset and then make that assignment conditional on an offset value. Or just also add the lvar VC_Miscellaneous_trigger_VAL to an offset, and just use assignments with offset conditions, as I advised. If you can just tell me what you want the switch position to be in the UP/UP state I can show you how to do this - its easier to do it this way than in lua.

@frankj76021 & @Rafa P: I would like to understand why you could not validate your license details on your own without me having to provide a key file for you. I generate this key file by entering your details and then validating, which is why I do not understand why you could not validate. I ask as I would like to improve the documentation to prevent so many support requests on validation.

CP will work, as you get a press on 26 moving up, and a press on 27 moving down. Can't remember if you get a release, but this is not important or needed when you get a press in each position. So you just assign to the press events. John

Here is the table with the state changes: Nav switch Down, Strobe Switch Down: VC_POSITION_LIGHT_SW = 20 (NAV lights steady, strobes OFF) Move nav switch up: VC_POSITION_LIGHT_SW = 10 (NAV and strobe lights OFF) Move strobe switch up: VC_POSITION_LIGHT_SW = 0 (NAV and strobe lights ON) Nav switch Down, Strobe Switch Up: VC_POSITION_LIGHT_SW = 0 (NAV and strobe lights ON) Move Nav switch up: new state? Move strobe switch down: VC_POSITION_LIGHT_SW = 20 (NAV lights steady, strobes OFF) Nav switch Up, Strobe switch down: VC_POSITION_LIGHT_SW = 10 (NAV and strobe lights OFF) Move Nav switch down: VC_POSITION_LIGHT_SW = 20 (NAV lights steady, strobes OFF) Move strobe switch up: new state? Nav switch up, strobe switch up: current state? Move nav switch down: VC_POSITION_LIGHT_SW = 0 (NAV and strobe lights ON) Move strobe switch down: VC_POSITION_LIGHT_SW = 10 (NAV and strobe lights OFF) What do you expect when both switches are up? Makes sense to have this as nav off, strobes on - but that is not possible..... But you need to define what happens in this position, even if you don't intend to use those actual positions. If you can define what you would like in that position, the assignments should be relatively straightforward....

If this is the case, then I can't see how you can control the strobe and nav lights independently with two switches. For example, if the nav lights were off and you wanted to switch only the strobe lights on, the value would go from 10 to 0 and so the nav lights would also be on, regardless of the position of your nav light switch. You are missing UP/UP....? But the logic should determine what happens when you move a switch, so you need: Nav switch Down, Strobe Switch Down: current state? Move nav switch up: new state? Move strobe switch up: new state? Nav switch Down, Strobe Switch Up: current state? Move Nav switch up: new state? Move strobe switch down: new state? Nav switch Up, Strobe switch down: current state? Move Nav switch down: new state? Move strobe switch up: new state? Nav switch up, strobe switch up: current state? Move nav switch down: new state? Move strobe switch down: new state? i.e. the logic needs to encompass all possible states and state changes. And it can be okay for no state change on a switch position change, as long as its consistent. If you can fill that in consistently, then you should be able to achieve what you want by overloading your assignments (i.e. having multiple assignments to the same switch/button) and using a combination of offset conditions (where the actual assignment triggered depends on the value held in an offset) and/or maybe compound conditions (where the assignment triggered on a button/switch press is determined by the state/position of another button/switch) - you don't have to use lua. You need to add VC_POSITION_LIGHT_SW to an offset (as unsigned byte or UB). If you can fill in those states above, I can help you further with this. John

As I said, you can add it to an offset via the ini file and read it from the offset., as you would an lvar or simvar. Basically yes - but not all b-vars may be available as input events. You can also do that. But I don't understand why you don't just add the input event to an offset and use that. You can then read the value from the offset, and also write to the offset to change/update the value of the input event. This works in the same way as adding lvars to offsets. See page 53 of the Advanced User guide. John

So that validates? If it validates, you must previously have entered your details incorrectly. Buy you said that you cut and pasted the details, so how can this be?

@frankj76021 I have pm'ed you your key file. Save this to your FSUIPC7 installation folder and try again - the key details will be populated from this file. Try and validate it. If it doesn't validate, I can't think of anything else it could be other than the redistibutables or antivirus (please check that as well). You should also be able to run FSUIPC7 with that key file without it being validated by the installer. So, even if validation fails, try running DSUIPC7 and see if its registered. Let me know how it goes. John

Sorry - Log -> List Input Events to see//list available Input Events and their current values. Log -> Input Events will log all changes in value for all Input Events. John

Use Log->Input Events. You can also assign buttons & keys to input events by checking the relevant check box. You cannot assign to an axus directly at the moment. To use on an axis, assign the axis to an offset and use a lua script. You can also add input events to an offset - see the advanced user guide. John

But what do you mean by this? Did it validate? If so, if it didn't validate when you entered the details, you entered them incorrectly. I don't want to point blame or anything, I just would like to understand why so many people seem to be having validation issues.... If I can understand this, I can update the documentation accordingly - would save me a lot of time....! John

I am not sure how you are using MobiFlight in conjunction with FSUIPC, but if you are using the presets you said: You could also maybe change these to update the simvar, e.g CANADAIR_HDG_BUG_DEC#1 (>B:INSTRUMENT_HEADING_BUG_LEFT_Dec) (L:1:EHSI_1_HDG) (>A:AUTOPILOT HEADING LOCK DIR,Degrees) CANADAIR_HDG_BUG_INC#1 (>B:INSTRUMENT_HEADING_BUG_LEFT_Inc) (L:1:EHSI_1_HDG) (>A:AUTOPILOT HEADING LOCK DIR,Degrees) But I think using the input event would still be the easier solution.... John