All Activity

Hello, thanks a lot, that helps ! Matthias

I haven't got time now to do a proper beta release, will do this tomorrow. but for now can you try the attached version, which is 7.5.0a. This is for both MSFS2020 and MSFS2024. I wo; release this in the Announcements sub-forum tomorrow. John FSUIPC7.exe

Hi Umberto, Yes - this will be updated and the version number for MSFS2024 will be 14. However, it will now only be populated once connected to the FS. Note you can also use offset 0x3124 which holds 110 for MSFS2020 and 120 for MSFS2024. I will be releasing a beta version of FSUIPC7 for MSFS2024 compatibility shortly. John

Hello DevTeam, would be possible to have a new FS Version number at offset 3308 for FS2024? Thanks Umberto

For the POV buttons. you have to assign to the relevant keypresses or assign in MSFS as the POV controls don't work in MSFS - as it says in the README.txt: Not sure about the "other" buttons, but note that many standard controls do not work for many aircraft (especially add-on aircraft), and you need to use presets (or lvars/hvars/Input Events). I will be very bust for the next few days (or weeks!) updating FSUIPC7 for MSFS2024 compatibility. So please: - ALWAYS check the documentation and support forum before asking questions - do not ask about anything for MSFS2024 at the moment, until I have updated and released a beta version that is compatible. And then, please post in the beta release topic (once available) until this is officially released.

John, I'd be interested in working with the beta for MSFS 2024. I haven't use FSUICP since my P3D days sp this will be a big learning curve for me. Please be patient if I have a lot of Questions. I manage to get the primary surfaces programmed in. but my POV and other buttons won't bind. I'm still using my Logitech G-940 flight system I've had for many years, and it still functions well. Probably one of the best things to come from Logitech. my last purchase was FSUICP 6

No - works ok here. But I am using a slightly modified version of FSUIPC7. For any issues with FSUIPC7 and MSFS2024, can you please wait until I have released an updated beta version, hopefully in a few hours. I will post/release this in the Announcements sub-forum. There is no point in posting any issues with MSFS2024 prior to this beta release of v7.5.0 John.

I've copied the fsuipc-lvar-module folder across to the new community folder and whilst I'm able to list the available LVARS (v7.4.18), I can't update or set any of them via Add-Ons > WASM > Execute Calculator Code. Any thoughts?

Thank you!

Thanks for the feedback! You had a better experience than me... Managed to install and ran it for the first time to download the remaining files. I then quit to install the FSUIPC WASM module, but after that I couldn't use it due, I think, to server issues. On the first restart it got stuck at 97% loading, the 2nd time at 0% loading, and then i was permanently in a log-in queue...I gave up after several hours... Seems to load ok today though. To use lvars/hvars/presets/etc, you can copy the FSUIPC WASM module (folder fsuipc-lvar-module) from your MSFS2020 Community folder to your MSFS2024 Community folder. I will be releasing a beta version of FSUIPC7 later today (hopefully!) with better compatibility with MSFS2024, and will also update and release the installer in the coming days. John

You can use the current 7.4.18 release of FSUIPC7 with MSFS2024. However, there will be a few issues, such as: - MSFS2020 folders will be used for various things, such as - saved flights (including auto-save) - flight plans - detection of WASM I will correct these and hopefully release a beta version of FSUIPC7 later today. I guess you could, but probably better to just use the current / latest version. For the time being, just copy/duplicate your current installation folder. I will be updating the installer to allow either one installation for both MSFS2020 and MSFS2024, or to have separate installations for each FS (as I do with FSUIPC6 which supports P3D versions 4, 5 and 6). This will tale me a couple of days. I will post details later, but if you want FSUIPC7 auto-started, you can create an EXE.xml (or add an entry to it if already created) file for MSFS2024, and for access to lvars/hvars/presets/calc. code, you can copy the FSUIPC WASM module (folder fsuipc-lvar-module) from your MSFS2020 Community folder to the MSFS2024 Community folder.

Hi John, can we use the 7.4.18 kit, that you accidently built with the 2024 SDK on 1st Nov.? Sandro

While people in the MSFS forum are complaining about having to spend all that time setting up their controllers, once I got MSFS2024 running, I fired up CLS2Sim (for the Brunner yoke) and FSUIPC, acknowledged the "CrashIO" dialog (haven't seen that for a while), disabled the default layouts MSFS had picked for the devices it recognized, and went flying. I'm sure I'll find problems in time, but having working controls within a minute, that was, for me, the highlight of this launch day. ❤️ FSUIPC ❤️

I need different lua scripts and most likely different bindings for 2024. How can I do a 2nd FSUIPC installation for MSFS 2024? I don't want to change my 2020 setup. Karl

There's an example project that explains how to use it. It also explains where to get a required file called FSUIPC_WAPID.dll that you need, and how to include it in your project. http://fsuipc.paulhenty.com/#downloads The example project is a few years old now. If it includes a FSUIPC_WAPID.dll file it could be too old to work so you should get the latest. On the MSFS side you need to install the WASM module which is installed by the FSUIPC installer. So make sure you're also up-to-date with the latest FSUIPC7. MSFSVariableServices is a completely separate system from the normal connection used for offsets. It's the preferred way to work with LVars (and HVars) in MSFS as it's hundreds of times faster than FSUIPCConnection.ReadLVar(). Paul

Hello, i am using MSFS, but i did not know about MSFSVariableServices . Can you pls give me a little tip how to use it in a C# project ? Or is it in the FSUIPC description ? ( i am not home right now ) Matthias

If you're using FSUIPC7 (MSFS) and the new MSFSVariableServices class then yes, you can: MSFSVariableServices.CreateLVar("L:NewLVar", 0); // (Name, Initial Value) If you're using FSUIPC6 (i.e. the legacy FSUIPCConnection.ReadLVar() method) it's possible (FSUIPC6 supports creates) but I haven't included it in the DLL. Let me know and I can a add it. For FSUIPC5 and earlier versions it's not possible to create LVars. Paul

Hello, very short question, is it possible to create a LVar using C# ? I think to remember i saw this anywhere, but could not remember... Thanks Matthias

The new ATIasHold program with a Image Gallery is here: https://www.intrasystem.it/ATIas/ATIasHold.html Raimund .

The new ATIasHold program with a Image Gallery is here: https://www.intrasystem.it/ATIas/ATIasHold.html Raimund .

Oh, that's the reason !!! 👍

This is because you are using a preset name already defined in the events.txt file: Please give your presets a unique name. As most presets are aircraft dependent, its a good idea to prefix the preset name with the aircraft name, e.g. TFDi_MD11_Master_Caution_Press#86110 (>L:CEVENT) TFDi_MD11_Master_Caution_Depress#86111 (>L:CEVENT) I should maybe add a check to make sure the name is unique when loading the presets... John

One more question. The “Master Cautuon” from my “myevents.txt” is assigned to button A25 Master_Caution_Press#86110 (>L:CEVENT) Master_Caution_Depress#86111 (>L:CEVENT) When assigned, everything works fine. But after a while it stops working! In the log instead of the code: 86110 (>L:CEVENT) I see this code: 2 (>L:var_masterCautionLatching). So that's why it stops working. I assign it again - it works and then “86110 (>L:CEVENT)” is replaced automatically to “2 (>L:var_masterCautionLatching)” I see this in FSUIPC7.log 2017265 Button changed: bRef=0, Joy=1 (A), Btn=25, Pressed 2017265 [Buttons.TFDi Design MD-11F GE CF6-80c] 157=PA,25,CPMaster_Caution_Press,0 2017265 [DEBUG]: Calculator code sent: 2 (>L:var_masterCautionLatching) 2017468 Button changed: bRef=0, Joy=1 (A), Btn=25, Released 2017468 [Buttons.TFDi Design MD-11F GE CF6-80c] 158=UA,25,CPMaster_Caution_Depress,0 2017468 [DEBUG]: Calculator code sent: 86111 (>L:CEVENT)

Ok, thanks for the update. I could not understand your issue as each button repeat should be independent, i.e. repeats on one button should not affect repeats (or not) on other buttons.

I figured it out, I was the one with the problem. The function "Repeat while held" works fine!