John Dowson

That is correct. If you remove a macro file, it is still listed in the [MacroFiles] section. If you remove a macro file, you should remove any assignments to that macro and then delete the macro entry. I think you are mis-remembering here - macro files have always accepted multiple macros, hence the index number. If it was only one macro per file, you wouldn't need to index them. Ok, glad to hear it. I don't think the 127 limit is mentioned in the documentation - I will add this. Passing this limit should just result in new macros not being recognised though, and shouldn't affect existing macros or the entries in the drop down menus, so I am not sure why this happened. I have made a note to look into this at some point, but it will be low priority...I think this is the first time anyone has passed the 127 limit in 20+ years - or at least as far as I am aware! Cheers, John

Ok - this then has probably changed the location of your Community folder, but hasn't updated the location in the UserCfg.opt screen. This is why the FSUIPC WASM isn't being detected, as well as those other apps installed in the same location. Sorry but I have no idea how the MS Store and Xbox apps install or configure MSFS2024. Yes, I think that is probably a good idea. But before you do this, check in MSFS2024 where it thinks the Community folder is - you used to be able to do this from the Library settings, but there have been so many changes to MSFS2024 that I am not sure any more. If you can find this, try setting the InstalledPackagesPath (in your MSFS2024 UserCfg.opt file) to this location. You should uninstall FSUIPC7 before doing this. No, sorry - especially for MS Store installs as I use a Steam installation. However, I am sure there are many posts on how to do this if you google... I would have thought that uninstalling either using MS Store or the Windows Apps panel, and then removing the MSFS2024 folders from your AppData/Roaming folder should do the trick, but best to confirm this with other MS Store users/google. One think i would do before you uninstall MSFS2024 and re-install is to uninstall any Community add-ons first. For FSUIPC7, just run the uninstaller. However, as you are using the same installation for MSFS2020 and MSFS2024, this will also uninstall for MSFS2020, but you can then re-install for that version. After you have re-installed, move your Community folder to the location you want to use BEFORE installing anything. In Steam, I would just do this by setting the InstalledPackagesPath in the UserCfg.opt file, but it may be different for MS Store versions, I don't know. I also think that this was possible from within MSFS2024 (in Library settings), but not sure if this is still available. There have been so many updates to MSFS2024 that it is difficult to keep track.....! John

How many macro files do you actually have? There is a fixed limit of 127 macro files - do you have more than this? Try reducing the number of macro files to a maximum of 127. You can have up to 999 macros in a macro file. You should really only need 1 per aircraft, and maybe others for systems that are common between aircraft (e.g. avionics). Try combining your macros to reduce the number. If you have more than 127 macros, the rest should be ignored, and you should see an error message logged in your FSUIPC6.log file (can you please show me / attach this file). However, from what you say it looks like having more than 127 files is causing issues. I will look into this (when I get time), but for now can you please try reducing the number of macros to see if that solves your issues. John

To assign an axis to control an lvar, you need to use lua. You assign your axis to write its value to an offset (using 'Send to FSUIPC offset'). You then need a lua script, which should run automatically via a [Auto.xxx] section in your FSUIPC4.ini (where xxx is your profile name). The lua script monitors the offset to which you have assigned your axis, using event.offset, and in the event handling function you calibrate the axis value (given as a parameter to the handling function) to the lvar value range, and set the lvar using ipc.writeLvar. Try this and let me know if you have issues and I can help further. John

The FSUIPC WASM module is installed in your MSFS2024 Community folder, which is here: C:\Users\aegva\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\Packages\Community\ ...or at least FSUIPC thinks it is... This looks like a strange location to me, as it is under LocalCache. What else is installed under that folder? Is there an 'fcr-embedded' folder? If not, where is that installed? Where do you think your MSFS2024 community folder is? Could you show me / attach your UserCfg.opt: C:\Users\aegva\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\UserCfg.opt The Community folder is taken from the InstalledPackagesPath location specified in that file. Your MSFS2020 community folder is C:\MSFS2020\Community\, which is a lot better... John

Also, do you see the FSUIPC WASM installed under: C:\Users\aegva\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2020\fsuipc-lvar-module ?

So this would indicate that the FSUIPC WASM module is not running, which will be your issue. The FSUIPC_WASM.log file you attached is also very old - from 30th July. Could you please show me your InstallFSUIPC7.log file, and can you confirm that you are using an MS Store version of MSFS2024, and not Steam. John

Ok, but strange - I do not understand why that would fix your connection issue as it will be the exact same version as you were using.... John

Great - well done! Maybe you could attach your macro file for the Milviz Bell uh1 redux as it may be useful for other users (I will also update the title of this thread). John

By the way. have you tried using a mouse macro? Mouse macros depend on how the aircraft is implemented, but worth a try. John

You can use one of the many free file transfer services, such as https://filetransfer.io/ John

...and if the IPS are unique and you have specified them correctly, the ONLY reasons that it fails to connect would be either the Workgroup name or firewalls blocking the connection. Please double check that your laptop is in the same workgroup as the PC, and temporarily disable all firewalls (laptop, PC, router). If IP addresses change, you would almost certainly need to update your firewall rules to allow the connection. This is why you should disable all firewalls and see if you can connect, then once you have a connection start each one at a time to see which one is blocking the connection.

I need to see all your files: WideClient.log, WideClient.ini, FSUIPC7.log, WideServer.log. I need to see all these files from the same session if you have connection issues. Did you try when using ServerName instead of ServerIPAddr as I keep asking? i.e. ServerName=YB-17936 Protocol=TCP ? Sorry, you said you tried this - but please show me the files. Are you now sure your PC and laptop have unique IP addresses? What are they?

Just to be clear, the public/external IP addresses will/should be the same, but the private/internal ones (starting 192.) must be different. If they are the same, you need to correct this - try google, e.g. https://learn.microsoft.com/en-us/answers/questions/2752121/two-computers-on-network-with-same-ip-address John

Maybe also try calibrating your throttle first using Windows Game Controllers...

Not that I know of, as I said...

Your logs show that FSUIPC7 is waiting for the WASM. Can you: 1. Check to see if the WASM is running. You need to enable the developer tools in MSFS to do this. Once you have enabled the MSFS developer tools, go to Debug -> Display WASM Debug menu, and then select the FSUIPC WASM module from the menu, and go to the Module Section tab. What do you see? Can you take a screenshot. It should look like this: Maybe also a screenshot of the Wasm Section tab. 2. Show me / attach your FSUIPC_WASM.log file. If you don't know where this is, take a look at the WASM section in the Advanced User guide. It may also be a good idea to set Debug level logging in the WASM (via the FSUIPC_WASM.ini file LogLevel entry), also explained in that section. John

This is not possible....or shouldn't be! Every device on a network needs its own unique IP address - if the IP addresses are not unique, how can anything connect?!!! And as I said, there was an error in your ini - did you correct this? Did you try with ServerName instead of ServerIPAddr?

They will be in your FSUIPC7 installation folder, on your client PC. They must be there - check also that you have not set Explorer to hide the extensions of known file types. Your ini file has a mistake: That should be ServerIPAddr. Also usually better to use ServerName unless you have allocated static IP addresses. As it says in the WideClient.log: John John

Do you know where I can download the FSX version? Found a version here: https://milviz.sharepoint.com/sites/GeneralProductSupport/Shared Documents/Forms/AllItems.aspx?id=%2Fsites%2FGeneralProductSupport%2FShared Documents%2FGeneral%2Finstallers%2Fv5%2FMV_UH1H_v2.210719.zip&parent=%2Fsites%2FGeneralProductSupport%2FShared Documents%2FGeneral%2Finstallers%2Fv5&p=true&ga=1 but that seems to only be for P3Dv4 and P3Dv5. This question was also recently asked here: https://www.avsim.com/forums/topic/682013-uh1-huey-redux-for-fsx/ John

Listing the lvars does just that - it lists all the local panel variables available. You then have to determine if any are relevant to the switch you are trying to control. You list the lvars two or three times, with the switch in different positions and see if any of the values change. Ok - and what switch are you looking at? As its freeware, I can install it and take a look, but it will take me a couple of days before I will have time to do this. I am just back after a couple of days away and need to catch-up on a few things first. John

There don't seem to be any issues with the latest update as far as I can see here. Can you please show me / attach your FSUIPC7.log file. John

So it doesn't work with only the MSFS assignment? That is very strange. The Nose Wheel Steering control is not available for external assignments - there is no such event in the SDK. Did you try Steering Set? Also try this without calibration first (i.e. remove any steering calibration). As I don't have this aircraft, I don't know. Try the Steering Set control. If that doesn't work, list/log input events to see if there are any that control the steering tiller. Also list the lvars and show me a log file.

Did you try either the Steering Set or Axis Steering Set axes (using 'Send to FS as normal axis')? FSUIPCs SteeringTiller axis is a special axis that should only be used in conjunction with the rudder and provides blending between the rudder and tiller (see the User guide). If you are using a separate Steering Tiller axis, you should try assigning to one of the MSFS-provided steering controls. If those don't work in the fenix, then you will need to look to see if any input events or lvars are available to control this axis. I don't have the fenix so cannot look into his for you, but if you log/list the available lvars and input events and anything looks applicable I can show you how to use theses. John

Glad you solved it. I think you got confused with the joyletter being 'C' and also with a C being used to indicate a Compound assignment, so you initial assignment 'PC...' needed to be changed to 'CP(-j2,b2)C...'... John