All Activity

OH! Now I understand!!! Sorry, I missed this element. This is very useful and for sure is the most effective solution! I'll test ASAP!

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?

John, reading my previous post I had an idea... what if I could ciclically execute some calculator code in lua (not triggered by a var or offset change) eg: ipc.execCalcCode("(L:1:EHSI_1_HDG) (>A:AUTOPILOT HEADING LOCK DIR,Degrees) ") this will update constantly the A var... probably not the most efficient solution in this case, but could be useful in other situations. Maybe it's already possible, but I can't remember how in lua.

Hi John, I've seen the input event under the list, and I can assigne it to a control, but I have to set a parameter. I can also see this input event under msfs20204 sdk behaviors input events. That being said, I still can't understand how I can use it for reading the current heading value, that is what I find under the scoped Lvar. For me the solution I found (following your suggestion to transfer the scoped var to an A var) works perfectly, since Mobiflight reads this Lvar and allow me to write some code that transfer this value to the "standard" autopilot heading value, that I intercept easily with Fsuipc offset and then in SIOC. OMG now I understand 1 (>B:INSTRUMENT_HEADING_BUG_LEFT_Dec) (L:1:EHSI_1_HDG) (>A:AUTOPILOT HEADING LOCK DIR,Degrees) input events are the B: vars ??? Even so, I can write a custom event to be called by SIOC with the code above, but still I can read the heading value in A:AUTOPILOT HEADING LOCK DIR,Degrees ONLY after I change it. But I cannot display the value on the AP panel before at least one change of the value... I could write this line under LUA as calculator code, and probably works, but since I cannot read the scoped var I cannot trigger the transfer to the A:var when the scoped var changes. Anyway, since I solved the problem and all works, I don't want to bother you with this issue. Handling scoped vars will be useful but I understand it requires a lot of work. Thanks for your deep understanding of the matter and for your explanations that made the thing much clearer to me!

I am good to go John, that worked. Appreciate your time and support,,,,have a great weekend.

@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

Thanks John. Say Hi to Pete.

Sorry have been out of town, yes I downloaded both 86 and 84 without luck. I also copied and pasted the info from Simmarket.

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

Er... sorry but I couldn't figure out what is INSTRUMENT_HEADING_BUG_LEFT. It's not listed under variables, neither under events nor hvars... I simply cannot find it. If it is an input event how can I extract a value? I feel stupid, sorry...!

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

thanks John, the file worked it fine

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

Hi John, sorry for the delay in my answer but I had no access to my pc for some days. Before leaving I tried to read the 1: Lvar from lua but, as you wrote, the current wasm didn't get it. So I modified the command line in mobiflight reading the Lvar and assigning it to the standard autopilot heading value, that is then handled easily in SIOC using the offset : in Mobiflight I set an input code as (L:1:EHSI_1_HDG) (>A:AUTOPILOT HEADING LOCK DIR,Degrees) then I added to myoffsets.txt 0x66C8, 2, AUTOPILOT HEADING LOCK DIR, I32, Degrees, w I prefer this solution instead of 07CC that requires calculations (Autopilot heading value, as degrees*65536/360) I just wonder why making things so uselessly complicated instead of using the common A:AUTOPILOT HEADING LOCK DIR, Degrees !!! But since I saw these scoped lvars in other planes I think it will be useful to have a future wasm release handling also these vars. I haven't tested yet the INSTRUMENT_HEADING_BUG_LEFT, I'll do that asap!

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

I thought to have that available in the dropdown menu (at least the way I have been saving flights anyway the past few decades) is so I can assign a specific filename. I actually use numbers for my saves.

Hi John, same issue here too, SIMMarket order 3643233 bought today. I have the redistributables installed and I copy/paste the information but no luck, please advice

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

My bad ... just edited my post ... Problem solved by myself... sometimes creating a post helps to reflect the issue and the thing around it.... WHY and WHAT has caused the DetectToConnectDelayAuto Value to change to the default value of 30... have not edited the .ini for months nor deleted it .... this msfs2024 drives me crazy.

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

As i wanted to get the L-VARS to check something i just noticed, the WASM Menu is missing .... i have not changed anything, noithing updated so far ... its not there anymore... the last time i used it was 1 or 2 weeks ago .... Any suggestion ? The WASM Module is loaded