John Dowson

The log you attached shows the slope adjustment working as expected, so I don't understand your issue.. Is it working correctly for you now or are you experiencing the same issue?

The icon displays a splash screen and loads MSFS. MSFS should start FSUIPC7. Of it doesn't, there was possibly an issue updating your EXE.xml file during the installation process. Please check or post you install log. The usual solution is to delete/rename you current EXE.xml and re-install FSUIPC.

Check the file has the correct extension (.mcro). It will appear, near the top of the menu, listed as 'A320: L:A320_Neo_MFD_NAV_MODE Set'. If its not, the files in the wrong place ir has the wrong extension (or content). But does FSUIPC see your arduino board switches? If not, this wont work. If FSUIPC doesn't recognise your device as a HID joystick type device, you cannot assign directly using the UI. If its recognised as another HID type device, you could try the lua com library, but that is quite advanced. If thats the case, you maybe better off trying MobiFlight.

Thats enough for it to be recognised by FSUIPC. If you enabled lua plugin logging and didn't see anything, then it didn't run. Have you tried to assign in fsuipc, to a button or key press? If not, try that. I'm sure it will work. And as I said before, try logging the offset. Of course, you need a registered version of fsuipc to run lua scripts.

I think you are confusing things a bit. As I said, the FBW events just activate hvars or set lvar values. You can do the same with the lvar/hvar facilities provided by the WAPI .lib and .dll, and in c# using Paul's MSFSVariableServices class. If you really want to use the FBW events, you have to add them to FSUIPC using event files, as I indicated earlier. And to then use them, you need to use the control numbers assigned, which I also explained earlier. To start with, rather than using the FBW events, why don't you just look at the available lvars/hvars and see if you achieve the same via lvars/hvars. Looking at the FCU, the following hvars should be available for you to try: and the following lvars are related: Note that hvars are only available if you add them to your A320.hvar file, located in the FSUIPC WASM modules folder. From what I can see, only the first two (H:A320_Neo_FCU_MODE_MANAGED_SPEED & H:A320_Neo_EXPEDITE_MODE) are currently included in the provided A320.hvar file. To use the others, you will need to add them to that file . Once added to the file, you need to reload (function available from Add-ons->WASM-Reload menu option) or restart MSFS (or reload the aircraft).

I don't delete topics, unless raised by mistake. This may help others who have the same issue. Glad its now working for you. John

Did you try clicking Yes/ Oui to allow FSUIPC to run? If not, try that. It should then be ok. If you still have difficulties, please see If you have re-installed, make sure you have installed both service packs, SP1 and SP2.

If the executable is gone, then that sounds like some sort of anti-virus software that's doing this. Try disabling ort adding an exception to the anti-virus software you are using. Also, for installation issues, please consult the provided README.txt and Installation and Registration guide. If the installer is crashing/not working, if not anti-virus software, it is usually caused by missing or invalid VC++ redistributables. This is explained in the README.txt.

Yes, maybe he has a better way of doing this... I'm not sure about that...he wants to reduce support and spend more time on his cockpit and actually flying. It would be interesting to look into, but there's no chance I'll have time for this in the next 6 months or so at least - to much to do on FSUIPC7 (and FSUIPC6) for the time being, sorry... Maybe @spokes2112will take a look - he likes a lua challenge and has helped out many users before with useful lua scripts... You could try to look into why this doesn't work any more....

Ah, you are using MobiFlight....! You didn't mention this. I cannot support MobiFlight, you need their support (or Discord channel). However, that log extract is an IPC write log, which is showing the MF is writing to that offset area, which is the offset area for macro (and lua) requests. So that seems correct. Try logging offset 0x66C0 using the FSUIPC offset logging facility. You will probably see that that offset is also changing. IPC write log will only log the changes to offsets via IPC calls, not from macro or lua scripts, which are internal. You need to use FSUIPC's offset logging facility to see those.

Well, I thought that was what I was doing...giving you basic instructions. To create a file, right-click in the folder where you want the file created (in Windows Explorer), and select New-> Text Document. Then right click the file and select Rename, and give it the name A320.mcro. Then open that file in an editor (e.g. Notepad++), and add the text I specified and save it. It really isn't that difficult. Once you have done that, if you restart FSUIPC7, you will see the macro/lvar name in the assignments drop-down menu.

For MSFS (2020, not FSX), you need FSUIPC7. Please do not use 'FSX' when talking about MSFS, it is confusing (FSUIPC4 supports FSX). If you need/use WideFS, WideFS7 is compatible with FSUIPC7 (as with FSUIPC4-6), so if you already have that no need to purchase again. Note that you don't need WideFS7 unless you are using a 2nd PC to run FSUIPC clients (or additional devices). I will also update the title of your post to clarify it is for MSFS.

Well, using either 0x66C0 or "66C0" should work. This is a free user offset used by many folks (including me) for years without issue, so something else must be happening... Please activate logging for lua plugins, as well as offset logging for 0x66C0, and generate a log file running the lua, and show me that as well as your lua script.

No. Currently no access to weather information in MSFS using FSUIPC7.

Hi Ray, FSUIPC only holds the details of the nearest 96 AI aircraft. For ground traffic, you could monitor the additional AI ground aircraft data at offset D040, matching on the departure ICAO to your landing ICAO, and then check/match the runway (and/or maybe the runway designator?). For the state, you would need to read from E080. Any matches, you could then kill (via offset 2900). You could do this in lua. Interesting project.... There is also the 'Detecting runways in use' facility, at offset D000, but I don't think that provides AI details for you to kill. Pete may have other suggestions... Cheers, John

I have already told you: i.e. the folder in which you installed FSUIPC7, where the FSUIPC7.exe is located...

Ok, then try creating the A320.mcro file, as advised. Then go into your button assignments and click 'Reload all buttons'. That should pick up the .mceo file (if created while FSUIPC7 was running - if you started FSUIPC7 AFTER creating this file, it should already be recognised). Then if you turn you rotary, you should see each rotary position recognised as a button press. If you don't see your rotary buttons, I think you will need to use MobiFlight (or the lua com library....), If you do, you can assign to that lua script, and give the parameter for each button press that indicates the mode you would like to set with that button.

That is because you have lots of logging options enabled. Disable those for now. That log file also shows that FSUIPC7 closed down successfully as MSFS exited - FSUIPC7 didn't crash: Are you sure that is the log from your "crash"?

If you want to assign in MobiFlight, then you need to go to MobiFlight support. I do not use MobiFlight (excpet the WASM, occasionally) and cannot adivise on how to assign using MobiFlight. To assign in FSUIPC, you can do this in two ways. 1. Using a macro file To use this method, create a macro file (e.g. A320.mcro) in your FSUIPC7 installation folder and add the following content: You can then assign your button/rotary to this, with the parameter indicating the mode, so assign to that for each "button" on your rotary with the appropriate parameter. 2. Using lua There are various ways to do this in lua. You could have an event.button call whose event function writes the value to the lvar. However, it may be easier (for a novice) to just have a simple script (e.g. mfdNavMode.lua that simply uses ipc.writeLvar to update the lvar with the provided (global) parameter. I can explain further if you assign in FSUIPC, but if you are assigning in MF, probably better to talk to MF support directly, either via their forums or Discord server (e.g. https://discord.com/channels/608690978081210392/749561530672087091)

To be clear, first try using those lvars directly (with the latest FSUIPC7.1.0 beta, soon to be released). If you want to use events, create a file in your FSUIPC7 installation folder, called (say) FBW.evt, and add the following: You can then see those events in FSUIPC's drop-down menus for assignment. If you want to use them externally, you will need to know which control numbers are assigned to the events. The control numbers for events in event files are determined as follows: control number = 32768 + (event file index)*256 + event index number where event file index is the index number of the event file (in your FSUIPC7.ini, under [EventFiles]) and event index number is the index number if the event in the event file. So, the first event in the first event file will have a control number of 32768, the second event 32769, first event in the second file as 33024. etc

The FBW events just control hvars/lvars. If you are writing a FSUIPC client program and wish to use lvars, you are better off using the FSUIPC WASM module _ the WAPI (the WASM API) which will give you an API to access and control hvars and lvars. This is a C++ API, but there is also a c# wrapper dll. See I'll let @Paul Henty comment if using this with his .net client dll. If you want to use custom events with FSUIPC, you can add these to FSUIPC by using event files (*.evt). There is a thread (or two) in the FSUIPC7 support forum on how to use the MobiFlight events/WASM with FSUIPC7 (but, as I said, you don't really need this for most things, as you can use the hvars/lvars directly). P.S. No idea what that image you attached is, and its too small to read,

Can you please supply more information. I need to at least see your FSUIPC7.log file, and a description of what you were doing when FSUIPC7 crashed would be helpful.... By thee way, have you installed FSUIPC7 into the MSFS folder: ? If so, please re-install into another folder, e.g. C:\FSUIPC7 or C:\MSFS-Add-ons\FSUIPC7. You should not install it into the MSFS folders or any windows protected folders (such as Program Files, etc.

Go to the Add-ons -> WASM->Set lvar... menu option. Then select that lvar from the drop down, and try changing its value to one of the following: Then try the same with A320_Neo_MFD_Range (again, using the values I posted earlier). What we are trying to achieve at the moment is to determine which lvars you need. So test them, to see if those are the ones you require. But it won't appear in the log if controlled by and lvar - that is events being logged. As I said, when you select 'rose arc', you should list the lvars again and see which lvar has changed, it won't be logged as an event if not controlled by an event.

I thought you wanted to control the mode and the nd range, which are, as I said earlier: otherwise please explain in more detail what you are trying to do. What do you mean by 'arc knob', and what does it do? I though that ARC was a nav mode, not a knob... I am not that familiar with the A320, or airliners in general, so you have to give more detail and explain what you are trying to achieve. What does the 'arc knob' actually do/change in the FS?

And the WASM menu now has Disable instead of Enable? Try restarting FSUIPC7, and if its still the same show me your FSUIPC7.ini file.