John Dowson

How have you assigned your axes? In FSUIPC or in FSX? If the former, please show your FSUIPC4.ini file. Have you changed your "default assignments? Are you not using "profiles"? Strange. That screenshot (pretty useless as it is) just says that your axis aren't being processed by FSUIPC. I'm sure you haven't. Don't worry, it's probably something simple that you've missed. But, before we can help, you need to provide further information: - your FSUIPC4.ini and FSUIPC4.log files - more information on what you actually did. I'm sure that you didn't just install the aircraft and then try and calibrate. Did you assign? Are you using profiles (again) [and if not, why not?]? And if you uninstall, and your FSUIPC.ini file hasn't change, it can't possibly affect other aircraft. Have you changed the "default" (i.e. valid for ALL aircraft) assignment profile? John

Please see the link in the post previous to yours. I am locking this topic. John

I don't know. Really, everything should just work when using OneDrive. I have used OneDrive for FSUIPC before without issues. I started to get issues as I use FSUIPC on multiple PCs, sharing the OneDrive account, and I did not want these different installations to share the same add-on.xml. They don't. They select your Documents folder. The location for this is determined by the registry. I'm not sure how OneDrive works, whether it updates this location. or if it acts 'under-the-covers' and silently keeps your docs in sync to OneDrive. Either way, I think there are some issues with your OneDrive set-up, as it really shouldn't interfere with the installation process. No problem. Glad its now sorted. Happy flying! John

If you continue to have problems using the Documents folder, it may be better to install using the old DLL.xml method. To do this, just uncheck the 'add-on.xml' box during the installation process. You can still install in C:\FSUIPC using this method.

I don't think this is enough. The problem is that your Documents folder is still being managed by OneDrive, even if its not running. You need to remove management of Documents from OneDrive (temporarily). Or it could (maybe) be a permissions problem. Can you manually create a folder (using Explorer, for example) under your Documents folder and under your Documents\Prepar3d v5 Add-ons folder? What do you see under your OneDrive Documents\Prepar3d v4 Add-ons folder?

Ok, so FSUIPC6 is not installing correctly as it cannot write the \FSUIPC6\add-on.xml file to your ...\Documents\Prepar3D v4 Add-ons folder. It seems like an issue with OneDrive. Can you either (temporarily) disable OneDrive completely, or remove your Documents folder from OneDrive before you install? You can also try removing the FSUIPC6 folder under ...\Documents\Prepar3D v4 Add-ons to see if it gets re-created.

What actually happens when you run the installer? The Modules folder is no longer used/needed with FSUIPC6, unless you select that directory as the installation directory. I'd rather avoid this.

No, the add-on.xml file will go into your Documents\Prepar3d v4 Add-ons\FSUIPC6 folder. Is FSUIPC6 installed correctly? i.e. can you see FSUIPC in the P3D add-ons menu? Is it the correct version? If not, could you re-run the installer - don't uninstall manually first, the installer will automatically uninstall if a previous version was detected. Install into the same location (C:\FSUIPC), then show me both your install and uninstall logs, both from C:\FSUIPC. Well, lets check that you have FSUIPC6 installed and running first. I don't know or use the Aivlasoft EFB, but if it requires FSUIPC then you will need to make sure that it is installed and running first. Once thats done, you can check again. John

Sorry, forget this! Just checked the history and that problem was fixed in the v6.0.6 release, not v6.0.8. I think your issues are related to OneDrive. Uninstall FSUIPC6 and try re-installing outside of Documents and OneDrive. This can only happen by running the uninstaller created by v6.0.8. After you uninstall (and before you re-install), make sure there is no uninstaller left. John

Btw, when installing FSUIPC6, it is better to choose a location outside of your Documents/Prepar3D c4 Add-ons folder. That should really be just for the add-ons.xml file, and can cause issues if you use OneDrive. Try uninstalling again, then re-install to a different location.

Hi, No, this won't be necessary.There was a problem in the installer for v6.0.8 in that the uninstaller it created did not correctly remove some registry entries for certain install types. This has been corrected but it means that some v6.0.8 uninstallers will not work as expected. Could you post your install and uninstall log files please (the latest will do) and I'll take a quick look. I think you will need to uninstall FSUIPC6, then manually remove the registry entries (I can help with this) and then re-install FSUIPC6. John Later...actually I don't think it was registry entries, but related to the DLL.xml install method. Did you originally install using this method by any chance? If so, can you check your DLL.xml to see if there are any FSUIPC6 entries?

Ok. No need for your log (at the moment!), now that I understand what is causing your issue. It's a good idea to try LVARS and the custom controls first. You should maybe ask on the FSLabs forums about controls for the FCU/Autopilot, as I expect there would be some form of control/lvars if the standard FS controls don't work. You can always use mouse macros for control of the ones that aren't supported.

The problem is that switches (and "sticky" buttons) will send a button down event in one direction, and then a button up event when switched back. With repeat on, you will continually be getting the down event while the button/switch is on, and as this is assigned to a mouse macro, it will continually be sending a mouse click, which is what is preventing you creating further mouse macros. If you change those buttons to the 'off' position (rather than deleting the entries), this should allow you to continue with your mouse macro creation.

Check if the aircraft has some documentation or an SDK. Lvars and custom (or repurposed) controls should be described there. You can use the 'Clear' button in the assignments panel, or just delete the line from the ini file before you start the FS. You can just attach the log file to your post (either drag and drop or by using the 'choose files' link just below where you enter your comments.

No, thats an ini parameter for FSUIPC4 only. John

The UI rectangle (switch/button) given the problem is RX400001c6, to which you have two macros assigned: 31=LDG LT Toggle=RX400001c6,3 32=LDG LT TOGGLE UP=RX400001c6,1 These macros are assigned to your Alpha Flight Controls buttons 22 and 23: 30=R1,22,CM1:32,0 -{Macro A320 Test: LDG LT TOGGLE UP}- 31=R1,23,CM1:31,0 -{Macro A320 Test: LDG LT Toggle}- These are also assigned to 'repeat' (R) - surly you don't want a toggle button to be repeated, no? Anyway, I suspect that one of those buttons may be continually firing, but I need to see a log file with button logging activated (as previously requested) to confirm that. You could try removing those two assignments as well, to confirm that they are the cause of your problem. Remove one at a time, starting with the last one first. John

Mouse macros emulate a mouse operation on the UI, which then alters the model somehow, either by sending a control/event or changing the value of a variable. Its more efficient to just send the control/event or modify the variable directly, rather than via the mouse operation. Also, different models of the same plane may have different rectangle ids for the same button/switch, whereas the control/event or variables would be the same. So, controls/events are more general, and can apply to many aircraft, and variables can be aircraft specific, but generally work for that series of aircraft, whereas mouse macros tend to be specific to that model. You need to check the documentation for that aircraft. Some add-on aircraft re-purpose unused controls, whereas others use 'custom' controlnumbers (e.g. PMDG). The 'Rotor brake' control you mentioned looks like it has been re-purposed to control various actions depending upon the parameter. To get a list of the lvars available for your aircraft, you can assign a button or keypress to the List Local Panel Vars control, which will list the available lvars (and their current values) for you. There is also a lua script (included in the provided examples) that does a similar thing. John

No problem. If you are starting afresh, you should investigate lvars. Check the documentation on this (which will be in your Documents folder, under an FSUIPC6 folder). You can get the user (and advanced user) guides there as well (to put on your phone!). A good place to start with lvars (and lua) would be the LINDA module for the FSLabs A320. You don't have to use LINDA, but its worth checking out what they use (offsets & lvars) to control the aircraft. It will be quite advanced, but should should be able to get some good tips if you take a look. Try https://www.avsim.com/forums/topic/502679-fslabs-airbus-a3xx-x-15-3-jul-20/ for info + the download (also looks like it's been recently updated). I've a similar problem on my flight PC at the moment - it randomly reboots during a flight on occasion. Only when using one sim, but quite regularly, and with no crash or event reported anywhere that I can find...very frustrating!

No, your ini contains the assignments to the macro file. The macro file itself is the name you gave It - it's in your installation folder, called A320 Test.MCRO.

You can delete (or rename) the macro file. But you already have lots of assignments to it, so you would need to remove them as well. I would leave this for now, until you have done the further tests I have advised, and provided me with the macro file so I can see what is in there, and a log showing your issue (with button logging activated). This would really help in tracking down the issue. If that rectangle is already assigned to a button, and that button is sticky/faulty (i.e. continually sending a press and/or release), then this would explain your issue.

Ok. I would like to see your macro file though, to see if anything is already assigned to that id. If its already there, and you also have assigned a button/switch to this macro, then this may be activating it. Logging 'buttons and switches' would also help if this is the issue.

Once you have tried the above (and sent me the files), could you try the following dll please: FSUIPC6.dll Just drop that file into your installation directory to replace the current one. With this dll, you can add a new ini parameter to the [General] section of your ini, thus: IgnoreTheseRectangles=RX400001C6 This will instruct FSUIPC6 to ignore input from that button/switch (mouse rectangle) while you create the macro. Of course, this doesn't solve your original problem which I would still like to get to the bottom of, just a (temporary?) work around. John

Just rename the file (in windows Explorer) then test. Afterwards, change it back. Maybe you could post this file as well and I'll check that. Nothing obvious in there. The only peculiarity is that you still have controllers enabled - if assigning axis in FSUIPC it is better to disable controllers completely in P3D, otherwise they may get re-assigned in P3D causing conflicts. You also seem to be using mouse macros for everything... It is better to use standard controls/events if/when they work. If not, you should try to see if an lvar is available for that function. You should use mouse macros as a last resort, when standard P3D controls don't work and there is no lvars available. You should also change to AutoAssignLetters=Yes in the [JoyNames] section of your ini - this will prevent problems if your JoyIds change, and make it easier to recover if your GUIDs change - see the "JoyLetters" section of the user guide for more details. However, none of this is related to your issue. Let me know how it goes when removing that macro file and/or trying a new macro file name. P.S. Also try with logging for 'Buttons and key operations' active, as I think this also logs mouse buttons. Produce a log file generated when you have your problem please.

When you create the macro, are you giving the name of an existing macro file? If so, what happens if you give a new file name? Do you also get the issue if you remove (i.e. temporarily rename) the macro file (or files) that you have already created for the A320? Do you know what button//switch the rectangle id is referring to? If you have previously created mouse macros for this aircraft, something must have changed.

Could you post your FSUIPC6.log and FSUIPC6.ini files and I'll take a look to see if there is anything else there that could be interfering.