John Dowson

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

Yes, please do that - I think that is the easy solution for this... It seems that in MSFS (2020 & 2024) aircraft developers are implementing things in their own way and don't consider at least using or updating the standard simvars available. It is a bit of a pain - means that you have to figure out how everything works for each aircraft. And, as FSUIPC is aircaft agnostic, you have to determine these things for yourself and assign/use the offsets in aircraft-specific ways. These type of values are stored in that wat as they are then integer values, and you then make the appropriate adjustment to get the floating point value. When you do things as you are, you will only get the integer component. Thats fine, if you are not interested in the decimal part, but means that a heading of 135.95 will be read as 135, which can cause issues if this is not taken into account. John

Ok. I will look into this when I have time.

I have also checked the license in that order here and it validates just fine. Are you sure that you installed the combined (2015, 2017, 2018 and 2022) redistibutables for both x64 and x86? Pleae double check that. I have also 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. John

Please don't do this...this makes this post now difficult to understand. If you have found out what the issue was, just add another comment saying what the issue was and how you corrected it. This is then useful for anyone else who has the same issue and comes across this post. I have removed your edit. This parameter can be auto-tuned - if it is, then this is logged. If you don't want to use the auto-tuning of this parameter, you can set StartUpTuningDoneVersion=-1 This is all explained in the Advanced User guide, section Auto-tuning of initial start-up ini parameters on [ag 11. Please read that section. John

If the WASM menu isn't there, then this implies that FSUIPC could not find it under your InstalledPackagesPath (from your UserCfg.opt file). Could you please show me / attach your FSUIPC7.log file, and tell me what the value of the InstalledPackagesPath is - or, better still, attach your UserCfg.opt file as well. The location of that file should be logged in the log file, like this: John

@Daveo There is already a control available to save a flight: Trigger Auto-save. Given this, is there really a need to add an option to the file menu for this?

@frankj76021 Did you manage to register your license? What was the issue?

First, if you re-installed windows, make sure you download and install the combined VC++ Redistibutable packages from Microsoft. You can download them from the following site: https://learn.microsoft.com/en-US/cpp/windows/latest-supported-vc-redist. Download and install both the x64 and x86 packages. Did you run MSFS2020 before installing FSUIPC? You need to run MSFS at least once before installing, otherwise the installer won't find the necessary files under your AppData folder. So first try re-installing FSUIPC after running MSFS. If you get the same issue, please see the following FAQ entry: John P.S. Please give your posts an appropriate title for your issue. Just saying 'fsuipc' means nothing - every single post in this forum is about FSUIPC!. I have updated it for you this time.

That is nothing to do with FSUIPC - that will be a false-positive and due to a update to Secutity intelligence (anti-virus definitions). What version of Security intelligence are you using? I am on 1.433.192, updated this morning, and I don't get that here. You can restore the file from Windows Security, under Protection History. This keeps happening recently - when it happens here, I report to Microsoft and they are pretty quick to update the definitions to allow it, but for now you will need to restore it. John

These are the FSUIPC support forums and are not really the place for such questions - uoi should try the MSFS / Asobo forums. They should. See the following: https://steamcommunity.com/app/2537590/discussions/0/4839770694276165539/ https://forums.flightsimulator.com/t/msfs-2020-premium-deluxe-content-not-shown-in-2024/666813/8 https://www.avsim.com/forums/topic/649281-is-premium-deluxe-for-2024-worth-it-if-i-own-it-for-2020/ if you google you will find plenty of threads on this, e.g. https://www.avsim.com/forums/topic/663902-cant-decide-whether-i-should-upgrade-to-msfs-2024-or-not/. Personally, if not using the new features or aircraft, then I would stick with MSFS2020. You may get better performance from MSFS2024 though, if that is an issue, as long as you have a fast and stable internet connection. I don't want to promote discussions on this topic in these forums, so I am closing this thread. John

There are many ways to send multiple commands on a single button 1. Use macros - see the Macro Controls section in the Advanced User guide. 2. Overload your assignments. You do this by making the first assignment, commenting this out in the ini file, reload the updated ini file, then make the second assignment, then uncomment the first assignment and reload the ini. 3. Define your own preset to send multiple commands (FSUIPC7 only). I have explained how to do this in detail many times before. See one of the following:

Ah, sorry - forgot to check the poster...!