John Dowson

Those messages are usually due to a corrupt installation. Do you get the same result when running without FSUIPC (just temporarily rename the dll)? If so, try uninstalling and re-installing. Make sure you also delete generated files, and also your Prepare3d.cfg file - it will be re-generated and you then have to re-apply your settings.

Hi Adrem, could you try the following dll please (v6.0.9c): FSUIPC6.dll I will (most probably) release this publicly at the weekend, as version 6.0.9. Cheers, John

No problem. I checked it here and seems to work fine, but I always like to get the user to check requested additions. I'll probably release this officially within the next few days or so, together with a few other updates. Cheers, John

@pluckasHi Paul, I have added an optional parameter to the DELAY option, so you can use DELAY=<n> where <n> is an integer between 1 and 60. When the parameter is not present, the default will be used. Could you try the following dll please: FSUIPC6.dll Thanks, John P.S. If you are using FSUIPC5, let me know and I'll update and post that. Not possible now for earlier versions.

It is peculiar as he says that his add-on.xml references the dll in the same folder: Is the actual folder shown when you click the "Open Folder" button the same or different? If its the same, its very peculiar! If different, maybe you re-installed using the dll method instead of the add-on.xml one, in which case the add-on.xml file was not removed correctly when it was uninstalled (there was a problem in earlier installers that did not remove this correctly). Or are you using OneDrive and have your Documents folder in the cloud? I have seen some strange issues with this, and if you are using OneDrive its best not to have FSUIPC installed under Documents. John

You can zip up test files - they compress well. First though, try remapping your joystick ids using the JoyIds program. See: Not sure if the download link in that post is still valid though, but you can download from here: https://theairtacticalassaultgroup.com/forum/showthread.php?t=13009 You need to remap your throttle to use the id of 0.

Hi Stuart, looks like your registry entries are a bit of a mess as you have multiple entries for the throttle with an id of 0 and also with an id of 2, which is the same as your rudder pedals. First, try setting the joystick id of your throttle to 0 in your ini, i.e. [JoyNames] AutoAssignLetters=No 0=Saitek Pro Flight X-55 Rhino Throttle 0.GUID={CAECA370-AA6B-11EA-8005-444553540000} 1=Saitek Pro Flight X-55 Rhino Stick 1.GUID={CAEC0730-AA6B-11EA-8002-444553540000} Then start P3D and see if FSUIPC can correct this for you. If you still have issues, then repost your .log, .ini and .JoyScan.csv files and we'll see what needs removing from the registry. John

What problem - your buttons are no longer recognised? Again, we need to see your ini and log file (preferably with the additional logging specified above activated). What else have you tried? Did you try with "NoWeatherAtAll=Yes"?

@Jason Fayre I have added an additional ini parameter LuaTrapKeyEvent which you can add to the [General] section of your ini to prevent lua key events being passed on to P3D: LuaTrapKeyEvent=Yes If possible, could you try the following dll please (v6.0.9a): FSUIPC6.dll Thanks, John

Ok, glad it's now working. If you are not using the "JoyLetters" facility, it's a good idea to activate it as this will prevent possible problems later (e.g. when unplugging and replugging your devices into a different USB socket/hub). Just change the AutoAssignLetters ini parameter (in the [JoyNames] section) from No to Yes. See the User guide section on this if you need further details.

Did You check the advanced user guide section Compound Button Conditions? The format is n=CR(+j2,b2)j,b, ... So, first program your button without the mode switch. Then, add a 'C' after the '=', then add your condition after the "repeat" code 'R' (with no comma!), so something like 27=CR(+P,9)P,15,CM14:2,0 -{Macro QW788: DecreaseApAlt}- (assuming P is the letter assigned to your joystick device) Again, check the Advanced 'user guide, section Macro Control References: The last number is the parameter to the macro. John

I don't know, sorry. I've not noticed that here for my macros. Usually a flashing taskbar icon indicates a pending message or event in the application that requires attention, but not sure why it would flash just once.

Hi Diego, first, try activating lua debug logging (from the FSUIPC logging options) which should help you debug any lua script. On a first glance, your ipc.macro calls are obviously wrong - the parameter is a string and needs to be in quotes, e.g. ipc.macro("<macro file name>: <macro entry name>"), as described in the documentation. John

As Reinhard recommends, using lvars is a better and more reliable method than using mouse macros.

Yes - if by remap you mean re-create, then yes. The problem is that different models may use different ids to identify the screen area (rectangle). Try re-creating the macros for those that don't currently work, your A320IAE. You could have one macro file with different names for the entries, but it's far cleaner to have a macro file per aircraft. You can then use that macro file in your profile for that aircraft, assuming you have different profiles for each of the models. If you don't currently have different profiles set-up for the different models, you can create a new profile for the A320IAE based upon the one for the A320CFM and then change the macro file used for that aircraft (see the User Guide for details on how to achieve this). Also, make sure that you are using appropriate "strings" (or "sub-strings") to differentiate the two aircraft models so that the appropriate profile is loaded. John

I see you are using OneDrive. This may be causing issues Could you try re-installing to a folder outside of your Documents folder. The Documents\Prepar3D v5 Add-ons\ folder should really only be used to hold the FSUIPC6/add-on.xml file anyway. Just re-run the installer and select a different folder (e.g. C:\Prepare3D Add-ons\FSUIPC6). This will also uninstall FSUIPC6 from its current location. You will need to move your files (.key, .ini, .lua, .mcro, etc) and folders across to the new installation location afterwards.

What sort of macros? If its mouse macros, these would normally have to be remade for each aircraft as the mouse rectangles can have different ids. If you are using macros with standard controls/events, then these may not work with some complex add-on aircraft as they tend to implement there own controls/sub-systems rather than rely on the P3D ones. If they are using lvars, the lvars may be different for the different models. So it depends. Maybe post your macros and more information on the airbus models that work and don't work, and someone with a similar model may be able to help. John

Did you also copy your FSUIPC5.ini to your new installation folder and rename it to FSUIPC6.ini? Could you attach your .log and .ini files and I'll take a look.

Lua files go in the FSUIPC6 installation folder, i.e. the folder which you selected to install FSUIPC6 into during the installation process. If you don't know where this is, you can use the 'Open Folder' button from the Logging tab. John

No, there is no such function. You are probably better off using a user offset to drive your gear light indicator (e.g. starting offset 66C0). You could have a lua script that simply copies the gear offsets (0BEC, OBF0, 0BF4) to this area if gear is retractable (offset 060C), or otherwise writes 0. John

It seems that that offset area is documented as for general use by mistake! That area is actually reserved for the "SoundViaIPC" interface documented in the FSUIPC for Programmers guide. This is very little used so I could make this optional, but for now I'll just update the documentation in the next release. I suggest you use one of the other offset areas for general use instead, maybe starting at 66C0. John

Verified. I'll look into it. John

You can do that to start your scripts. However, you won't be able to stop them from there when the aircraft changes. To do this, you would also have to monitor the aircraft name in each script so that it can stop itself when the aircraft name changes, as I said.

You can also use the [Auto.<xxx>] section of your ini (where <xxx> is the profile name) to automatically start/kill luas on aircraft load/change. See the Advanced User guide, section entitled Automatic running of Macros and Lua plugins. John

Do you have the rudder pedals off in the MCDU options menu? See this post over on the FSL forum: https://forums.flightsimlabs.com/index.php?/topic/7942-setting-up-the-tiller-using-fsuipc-registered/