John Dowson

But it is MSFS that launches FSUIPC7, not the other way around. Unless you are using a very old version, in which case you should update. The MSFS icon that the FSUIPC7 installer creates in your desktop just displays a splash screen while MSFS is starting. MSFS then starts FSUIP7 via the EXE.xml file.

I cannot access that link - it says 'You Need Access', with a button to request access. However, any information you have there you should be able to attach here. If its large, just zip it up. And please show me your FSUIPC7.log and FSUIPC7.ini files.

That is using a MobiFlight event. But here you are trying to write a Hvar as an lvar... Yes, you need to use ipc.activateHvar for hvars. Not that hvars to not have an associated value - you just trigger or activate them.

Sorry, but where is your name displayed exactly? It should only be visible from your registration details, i.e. in the Help -> Registration Details... window, and also logged in your FSUIPC log file when your registration details are verified.

Can you please show me your FSUIPC7.log file. I suspect that it is MSFS that is crashing. which causes a 'fault' in FSUIPC (not a crash). However, FSUIPC7 will exit when MSFS crashes as you have the option 'Exit with FS' set. Your log file will probably show FSUIPC7 closing normally.

Please show me your FSUIPC7.log and FSUIPC7.ini files.

I cannot access that link. Please describe your issue. But please, if this is the same issue you thought you had before (i.e. FSUIPC crashing MSFS), then please check your FSUIPC7.log and make sue that it is not MSFS crashing and FSUIPC7 exiting normally. When MSFS crashes, this will generate faults in FSUIPC7 reported in the event viewer, but this is due to MSFS crashing, not FSUIPC7. and to verify this, turn of the option 'Exit with FS'. With that turned iff, FSUIPC7 will keep running when MSFS crashes.

I never understood the original problem, and it seems it was not related to using FSUIPC. You can zip log files before attaching - they are text files and so zip up pretty small. Anyway, the log file doesn't tell me anything. How are you trying to start your aircraft? Of using FSUIPC, then I need to see your assignments, i.e. your FSUIPC7.ini file. And what happens if FUIPC7 isn't running? Can you start your aircraft then? As with the OP's problem, I don't think this is related to FSUIPC7.

Sure. Open your FSUIPC ini file in an editor and completely remove the following sections: [JoystickCalibration] [Axes] [Buttons] [Keys] [Auto] Then, take the profile name out of the specific profile that you want to make global for those sections, e,g, change [Axes.<yourProfileName>] --> [Axes] etc. You can then remove the [Profile.<profileName>] sections, and any other profiles you don't need. Probably a good idea to make a back-up first, just in case,

You can do this as you would for any multiple assignment to a button. First assign your button for the first control and click 'Ok' to save this assignment. Then open your FSUIPC7.ini file in an editor and located the line for that assignment just added - it will be the last entry in either your [Buttons] section or [Buttons.<profileName>] section, depending upon whether or not you are using profiles. Now comment that line out by inserting a semi-colon ';' character after the index number of the entry and save that change. You can then open the Button & Switches assignment panel again and click 'Reload all buttons'. You can then assign your second action to that button. Repeat if you want to add further actions. Once all have been added, you can remove the semi-colons previously added to uncomment those entries, save the file and agaiin 'Reload all buttons'. You will then have multiple actions assigned to that button - the Button assignment panel will only show one entry and it will be grayed-out, indicating it cannot be changed via the UI (you have to edit the ini to adjust/remove when you have multiple assignments to a single button or key.

I'm sorry, but as Pete indicates, we can't support software that is using FSUIPC - you need to contact the software developer. If the developer of the package you are using is no longer supporting the software, then maybe you should switch to something else. The most advanced and often used API is the c# one provide by Paul Henty, but there are many others - check out the available SDKs that are provided, which will be under the SDK folder in your FSUIPC installation folder (if you opted to install). However, please note that we only support the interfaces that WE provide, we cannot support 3rd party add-ons or APIs, but we can point you in the right direction if using those... Many of the interfaces provided are still supported by the developers of those interfaces. John

Please realize that this is invalid. The first number is the index number, which must be unique. And why are you adding the same lvar to different offsets. I think you are misunderstanding how lvars to offsets work.... Try with this: i.e. each lvar in its own offset. Then assign your buttons to those offsets as previously described.

you could try that attached in where I've done those updates for you: FSUIPC6.ini

Hi Jim, before anything else, could you please update to the latest version, v6.1.1. Only the latest version is supported. Not sure why you have started again - you have lost so much of your assignments, If I were you, I would go back to your initial profile and we can sort out the problems there. Copy all the [Profile.PMDG 777 United] sections from your new ini to your old ini. Also, delete all parameters from under the [General] section. This will be rebuilt when you next run FSUIPC. Note also, that you should use the substring function for your profiles to catch all variants, so this, for example: Can be changed to this: The profile would then be used for all aircraft which contained the substring "PMDG 737", and so catch all variants. You can do something similar with all your Profile sections that link the profile to the aircraft. Once all that is done, test again, and report back if you still have issues.

There are 3 ways to do this: 1. create a macro file to to either set or toggle the lvar, and assign a button or switch to this lvar macro. Ecactly how you do this depends on how your buttin/switch works. 2. write a short lua script to activate the lvar, and assign your button to the lua script. Or you could use event.button in your lua script, and skip the assignment completely. 3. Add the lvar ro an offset, and then assign your button/switch to toggle or set the lvar via the offset 3 may be the easiest. However, adding lvars to offsets is only available in the latest 7.2.0 beta, so please download and install this, from Then, you need to create add an [LvarOffsets] section, or an [LvarOffsets.<profileName>] section, specifying the lvar you want to use, together with the offset to hold the value together with the size of the offset, e.g as the following (although better to use a profile]: [LvarOffsets] 1=L:ASCRJ_OVHD_LDG_NOSE=UB0xA000 This will add the lvar ASCRJ_OVHD_LDG_NOSE to offset A000 as an unsigned byte, for both reading and writing, i.e. you can read that offset to read the lvar value, and setting that offset will update the lvar value. Then, to assign to a button or switch, go into the FSUIPC7 Buttons & Switched assignments panel, press/switch your button, and then assign to the control Offset Byte Togglebits, giving A000 as the offset, and x1. as the parameter. That button will then toggle the lvar value. Depending on if using a button or switch, you could assign to Offset Byte Set with a parameter of 1 for press and 0 for release (for example, if using a switch, maybe also with an offset condition to keep the switch in-sync.). The actual way you assign depends on what you are assigning to and how the button/switch works.

Do you mean the file itself, or that the icon is not in your system tray? If the file has gone, you must have deleted it. Just re-install. if the icon is not in your system tray ot task bar, FSUIPC7 isn't running. I make the FSUIPC7.exe available on its own only for beta releases. I don't understand why you would want to download just the exe. All releases come built into the installer as, as a minimum, the documentation always changes between releases. However, to use FSUIPC7 you don't actually need to have it installed by the installer - you can just run the FSUIPC7.exe.

But that makes no sense. An uninstaller ALWAYS uninstalls from the location you selected when you install. This obviously (if you think about it) presents issues when you have installed once for two versions of the app, then want to uninstall for one. Its just not possible. And, this IS a problem in the installer that allows you to do this. I am going to update the installer so that it detects if you have installed a single copy for use by both versions then it will not allow you to deselect a version to re-install - it must be for both. And I will update the Installation and Registration guide to explain this, and what you must do if you want to revert to separate installations, i.e. you have to manually run the uninstaller first. Sorry, but this is just a scenario I hadn't considered when I decided to allow a single installation for both P3D versions. You may, more than likely, get problems next time you choose to update one of your installations. I think it would be better to sort this out now when its fresh, rather than having further issues when there is an update you need to install. But thats up to you. Cheers, John

Ok. The log shows that the axis is assigned and sending the correct axis value. If thats the case, then it doesn't look like this us a real axis control. What happens if you assign to a button with parameter 5 - does that work at all? You could try to see if there are any available lvars that you could use - try listing them using the Add-ons->WASM->List Lvars menu entry, and see if any look applicable, Then change in the UI, and list again to see the new values. If you find something that looks like it controls the lighting. Then, you can test this by changing the value of the lvar using the WASM0>Set Lvar... menu option. if you find an lvar that works, I can then show you how to use this. Otherwise, you may want to ask how this works and how to control on the Carenado forums. I dont have this add-on so its difficult to advise.

@Nenad Bogojevic Could you try the attached version please. v7.2.0c. There is a corresponding update to the WASM to ignore the additional calc code sent to reset the CDA, but this isn't strictly necessary as its harmless.FSUIPC7.exe

Then try their Discord channel: https://discord.com/invite/NcnwDKx

You logs show the control is being sent with the correct axis parameter, although the axis isn't moving that much: And you also have the same control set to a button with a fixed parameter of 5 for some reason: On fact, you have multiple assignments to LIGHT_POTENTIOMETER_SET in the profile you use for the Carenado Mooney: Why assigned in so many places? Anyway, can you generate one more log. This time, please don't start a new log file - its far easier for me if you give me one full log file, not continuation log files (I think I'm going to remove this facility). For this log, just load your aircraft, and move a single axis to, which you have assigned LIGHT_POTENTIOMETER_SET , through its full range forwards then backwards. We can then see the parameters being sent with that control when you operate it through its full range.

Sorry, but I have no idea what SLC is.

What has this got to do with FSUIPC7?

Ok, good. Not that we have helped you at all. I don't even know which aircraft you are trying to control, but I presume its the A320 (as this is the one that causes most issues and is far more difficult to set-up than most of the others). I am locking this topic now. If you require any further assistance in the future, PLEASE attach your FSUIPC7.ini and FSUIPC7.log files. Without these, I cannot help you.

That is the uninstaller. You cannot change that - it uninstalls from the locations where you installed. If you select P3Dv4, it will uninstall from the P3Dv4 location. If you select P3Dv5, it will uninstall from the P3Dv5 location. If you select both, it will uninstall from both. As I have said, a problem arises if you previously installed a single installation for both P3Dv4 and P3Dv5, but then just uninstall (or re-install) for one location, and change the installation folder. If you do this, it will uninstall the shared copy, then re-install a copy just for the version selected. So, if you previously installed a single copy for both versions, it is best to manually run the installer and uninstall for both versions. Then run the installer twice, and install for each version in a different location. It is the installation location you should choose, not the uninstall location.