John Dowson

Yes. You need to copy the GUIDs from the newly assigned letter entries (as well as the names, but only if they have changed) to the old letter entries, and delete then delete the new entries. If you have any issues or difficulties, show me / attach your FSUIPC7.ini and an FSUIPC7.log file and I can help. John.

For COM frequencies, you can use FenixQuartz (https://github.com/Fragtality/FenixQuartz) which provides the lvars "FNX2PLD_com1Active", "FNX2PLD_com1Standby", "FNX2PLD_com2Active" and "FNX2PLD_com2Standby" - although these may be read-only. This post indicates that these hold the correct values in MSFS2020, but not in MSFS2024: The OP of that topic also indicated that he has found a way without using FenixQuartz - I have asked if he can provide any further information on this. John

@Mark van Wissen How do you read the COM/NAV frequencies without using FenixQuartz? What do you use to set/change these, in MSFS2020 and/or MSFS2024? I am asking as another Fenix user is having difficulties with this - see

Then we need to determine why - it should run ok. Are you running P3D as admin? If so, you would need to run any connecting problem as admin. Here is a VS project for the UIPCHello - try building and running from this: https://fsuipc.com/download/UIPCHello.zip I am asking if you have tried the lua com library (the HidDemo.lua program) to see if that can recognise your buttons/switches/axes. If it can, then you can use that to assign directly in FSUIPC - no need to write your own program to interface to the hardware, John

Please read the Installation and Registration guide, section Invalid Key Problems. All reports on this issue are due to one of three things: - not entering your key details correctly. All 3 parts must match (Name, Address/email & /key). It is recommended to copy and paste these from your purchase email or from your key details in your SimMarket account. - not having the correct VC++ redistributables installed. Download and install the latest combined VC++ redistributable package for both x64 and x86. - anti-virus software blocking the registration check. check your ant-virus software for details. John

👍😎

What is FSUIPCuser64.h and why are you including this? As I keep saying, first get the sample program compiled and working. Once you have that working, then adapt that to your needs. John

This is not correct - it is working correctly. The issue is that you do not have a license to use WideFS: You need to purchase and/or register your WideFS license. If you do not have one, you can try the trial license. John

It looks like WideServer is not being enabled in unlicensed versions of FSUIPC7. I will look into this. For now, can you download the trial license (available in the first post in this sub-forum) and use a licensed version of FSUIPC. I will look into why WideServer isn't being started with an unlicensed version and get back to you. You shouldn't need an FSUIPC7 license to use WideServer. John

Then WideServer isn't running. Please attach a full FSUIPC7.log file.

Can you please exit FSUIPC7 / WideClient before attaching log files. Your FSUIPC7.log file ends after 5 seconds and shows that WideServer was not even yet started. Also, please attach your WideServer.log file. Also try with ServerName instead of ServerIPAddr, and also set Protocol=TCP. Do you see the WideFS menu in FSUIPC7?

First, I presume this is with using MSFS2020 / MSFS2024, so I have moved it to the appropriate forum. I don't have the fenix, but looking at the avionics presets in HubHop (https://hubhop.mobiflight.com/presets/?vendor=FenixSim&system=Avionics) it looks like lvars are used for most of the buttons. I don't know if the standard FS controls (Simconnect events) to set the frequencies will work, but I suspect they would (they work in most aircraft to set the frequencies). If you don't want to use the SimConnect SDK, you can use one of the FSUIPC SDKs to do this (and the WASM with the WAPI for lvar/hvar access). The C# library is the most advanced and also integrates with the WASM / WAPI- see Paul' Henty's .Net dll client sub-forum: https://forum.simflight.com/forum/167-fsuipc-client-dll-for-net/ A Python wrapper is also available - see the FSUIPC SDK folder (i.e. install FSUIPC7 and look in the SDK folder). John

So you cannot build the UIPCHello sample in VS2022? What errors do you get? No - but have you tried the lua com library as I have already advised?

That lib is 2022. It was updated for this thread: But looks like I only included this update in FSUIPC7. I will also update in FSUIPC6 for the next release. John

Did you try linking to the kibrary I provided? That may be 2022, or possibly 2019. It is generally better to use the class name (when possible) rather than the window title. The class is more portable, as its the same for all versions of P3D, and same in personal, professional and professional plus editions. The window name will vary. FSUIPC always uses the clase name FS98MAIN for this. John

Yes - its just a name (string) attached to the calculator code - you can use whatever is appropriate. You can also give a fixed value rather than using a parameter ($Param) if you prefer, and have several presets each setting a different fixed value. John

First, to update the scoped lvar, you need to create a preset in the myevents.txt file (create this if you don't yet have one): //ProSim/A320 ProSim737_MIP_AUTOBRAKE_MAX#$Param (>L:1:I_MIP_AUTOBRAKE_MAX_L) then assign to that with an appropriate parameter value. To add this to an offset (for reading only - writing/updating won't work), create a lua script to copy the value of the scoped lvar to a standard lvar, and add the standard lvar to an offset. The lua script to keep the lvar in sync with the scoped lvar is as follows: -- function to copy the value of the scoped lvar to the standard lvar function updateLvar(time) ipc.execCalcCode("(L:1:I_MIP_AUTOBRAKE_MAX_L) (>L:I_MIP_AUTOBRAKE_MAX_L") end -- Create an lvar to hold the value of the scoped lvar -- Note that if you want to do this for multiple scoped lvars, better to create the lvars using calculator code, e.g. -- ipc.execCalcCode("(L:1:I_MIP_AUTOBRAKE_MAX_L) (>L:I_MIP_AUTOBRAKE_MAX_L") -- for each lvar, and then call -- ipc.reloadWASM() -- This is because using ipc.createLvar will also force a reload, and you don't want to do this after creating -- each lvar - best just to do it once after all the lvars have been created. -- But as we are only currently doing this for one scoped lvar, we will use the ipc.createLvar function. ipc.createLvar("I_MIP_AUTOBRAKE_MAX_L") -- wait until the new lvar has been received ipc.sleep(250) -- Start a timer function to keep the lvar in sync with the scoped lvar event.timer(150, "updateLvar") The script should be auto-started in your profile [Auto.xxx] section (where xxx is the profile name).You can then add the lvar to an offset in the usual way, e.g. John

Then that will be the issue. As far as I am aware, ADE has not been updated to be compatible with v6. As I said, you need to ask about this on any ADE forums, but as far as I am aware, this product is no longer supported. You could possibly trick ADE into thinking that you are running Prepar3D v4 or v5, but I do not know the consequences of doing this. I allow this in FSUIPC7 for fooling some add-ons that MSFS2020 is running rather than MSFS2024, but I don't think this is possible in the current version of FSUIPC6. I could allow this and provide you with a test version if you would like to try this, but I have no idea if ADE would still work as expected. I suggest you first look at the ADE forums on using this with P3Dv6. If you can't find much useful, I can provide an updated version of FSUIPC6 that will allow the P3D version to be updated, and so maybe fooling ADE - but, beware of the possible consequences of doing this! John

Why not just include the FSUIPC_User64.h and link to the FSUIPCuser64.lib? Yes - can you not use the provided lib? I did update this to a later version of VS/VC, but only added this in FSUIPC7. I have attached this updated lib and header. I am a bit busy at the moment and cannot look into this in detail at the moment. When I have more time, I will look into which VS versions should be used, and update to VS2022 if needed. John FSUIPCuser64.lib FSUIPC_User64.h

For the next release of FSUIPC7, I have added: INTERACTIVE POINT GOAL at offset 0x341B INTERACTIVE POINT OPEN at offset 0x3424 both are 1 byte, with each bit indicating the index number (e.g. 0x341B bit 4 is INTERACTIVE POINT GOAL:4). This won't help your problem at the moment, but if you could log these offsets, as well as offset 0x3367 (EXIT OPEN), all as U8 in hex, this may shed a light on what is being used. It is possible to spoof the reading of the existing door offset (0x3367 for EXIT OPEN) to these new offsets, but most probably the bits referenced will be for different doors. I don't have the FSL A321neo, or GSX/SLC, so cannot test with these. I looked at the FSL A321, but that just seems to use the EXIT OPEN offset. Anyway, maybe try the attached and add the offset logging for those 3 offsets (all as U8 in hex), and we can see what this tells us. John FSUIPC7.exe

@stefangr Is this clear for you? I can provide a sample lua script for the I_MIP_AUTOBRAKE_MAX_L variable, if it is a scoped lvar, if you need this. Let me know. John

What version of P3D are you using? That message indicates that the version of ADE you are running is not compatible with the version of P3D you are using. I believe that ADE was updated for P3Dv5, but am not sure if it has been updated for P3Dv6. But I cannot help with this - this is an issue with ADE, not FSUIPC. Ask on the ADE support forums. John

But what type of variables are they? Are they scoped lvars? Then they are probably scoped lvars. MobiFlight will read these by executing a calculator code script and getting the value in the response. In FSUIPC, I do not provide/allow for a response from executing calculator code. Again, this depends on the variable type. If they are scoped lvars, you can only get the value, and add this to an offset, by writing/copying the value of the scoped lvar to a standard lvar, and then read or add this to an offset. You would need to update the value of the lvar (from the scoped lvar) at regular intervals (e.g. at 6Hz) as well, so that the lvar holds the current value of the scoped lvar. You can do this using a lua script.

It all depends on what variable types they are. They won't be simvars, or A-type variables, as these are only defined by MSFS/Asobo. They could be lvars, hvars or input events (also known as b-vars). First, with the aircraft loaded, try listing the available lvars (Add-ons->WASM->List Lvars). Do you see them listed? You can also try listing the available Input Events (Log->List Input Events) - do you see them there? Note that MSFS2024 also has a new type of lvar (local variable), called 'scoped lvars'. There is currently no way to discover such vriables, but you can update them using calculator code. To read them, you would need to use calculator code to write the value to a standard lvar, and then read that. See If it is a scoped lvar, it may also be available as an Input Event, so please make sure you check there.

Yes.