John Dowson

As I have said, the reg file only removed entries for specific devices and can no way affect MSFS installation. Did you take a registry backup of your registry before you started to make any changes, as advised? You should ALWAYS back-up your registry before making any changes. If you have this back-up, try reverting back to that. But something very strange is going on in your system. The last registry change should just have removed the entries for your G13 joystick, but now your rudder and stick have also disappeared. I will look into providing you with additional logging flags to log the registry matching. Can you also please check (again) that you are not using any logitech or saitek drivers for any of your devices, and if so remove them. Also, please do not run/install any software for these devices - unless absolutely needed. Always best to try without any additional software running.

It will be in your purchase email and also show in your SimMarket account. If its not there, you need to ask SimMarket. I can see your order - I will PM you your registration details. John

Yes of course - you can also use the Axis Throttle Set control on a button press, with an appropriate parameter. Custom controls need something to understand them at the other end (i.e. in the FS) - you cannot just create your own custom control in FSUIPC. Also, you could try calibrating some "sync" points - see the section CALIBRATING MULTIPLE THROTTLE, PROP & MIXTURE AXES TO "LINE UP" on P45 of the User guide. John

Just use the latest lua, or create a lua file with the contents in my last post. This is basically what that script does, although the value is not written but 'spoofed', so any external program that reads the offset will read the spoofed value. Is the lua actually running? i.e. have you added it to the [Auto] (or profile [Auto.xxx]) section of your FSUIPC7.ini file? Have you installed the FSUIPC WASM module and enabled it? Otherwise, try enabling lua debug logging and generate a log file where you load the aircraft, apply and release the parking brake, and then exit. Do not start a new log - I need to see the full log file. Note also that lua is only available to registered/licensed copies of FSUIPC.

Where have you installed FSUIPC6? If you have installed in the add-ons folder (under Documents), or in any other windows protected folder (such as Program Files), then please try installing in a different location. Otherwise, please show me your Installation log (InstallFSUIPC6.log).

Still an issue with your G13 joystick. Can you disconnect, and run the following as a .reg file, then reboot and reconnect. Before starting FSUIPC, delete the contents of your [JoyNames] section in your FSUIPC7.ini file and let that get rebuilt. The log also reports an error reading the details of your joystick: Not sure if this is an issue, but try connecting it to a different USB port/hub - if its in a USB2 port try moving it to a 3.1 port (if you have any), and if its in a 3.0 or 3.1, try moving it to a USB 2.0 port. Once thats done, start FSUIPC7, exit and then show me the files again. If there are still registry issues after this, I will give you instructions for logging the registry matching FSUIPC performs - there may be some other registry entries that need removing. Hows it going with the MSFS re-install?

I did say I would look into this. I just have other things that are of higher priority at the moment. I have a backlog of requests pending, as well as planned improvements on how to access lvars, hvars and calculator code. The current profile mechanism has been around for 10+ years and so I'm sure it can wait another few months before I get around to looking into this. John

You are reading the values as a signed double, which us 4 bytes, but your offsets are only spaced by 1 byte, so they are overwriting each other. How are you writing them? If writing them as Dwords (32-bit, 4 bytes) then if the first is at offset 0x66C0, the next should go at 0x66C4 and not 0x66C1. John

Ok, but still very strange... Thanks for reporting back. John

You can try that, using offset 0x31F0. Try logging that offset first to check its holding the correct state for the aircraft you are using. You can start a timer to call a function to play the wav when the offset value changes from 0,1 or 2 to 3 (pushback off). Regards, John

It will be in the FSUIPC6 installation folder, where you selected to install FSUIPC6. The Documents\Prepar3D v5 Add-ons\FSUIPC6 folder is where the add-on.xml file resides. If you do not know where you installed FSUIPC6, use the Open Folder button in the FSUIPC6 Logging tab. John

By the way, does the Aerosoft A320 have a flypad/efb? If so, you may need to configure there before you assign in FSUIPC. But, as I said, the aerosoft forums may be your best resource for this issue.

Sorry Al, I was mistaken. They are the bit-oriented calibration flags: 2^3 (8) = Filter 2^4 (16) = Reverse 2^5 (32) = No Reverse Zone The delta values are in the axis assignments, as you rightly say. Yes, thanks, but far too short....! John

Note that only one profile is ever used/loaded for the current aircraft. Pete's comment shows how you can load a different profile for the same aircraft, by giving the aircraft a 2nd name. The profile loaded will be dependent on the name of the aircraft that you load. John

Could you both let me know: - what aircraft you have loaded - what other add-ons you are using - what windows version you are running - what video driver you are using This is to try and determine what is common between your systems that may be the culprit. Could you also try setting the following ini parameter in the [General] section of your FSUIPC6.ini file to see if this makes a difference: UseDialogMode=No If you already have that set, try removing it. John

Have you followed the instructions in the Installation and Registration guide, under Invalid Key Problems? If not, please do that. If you still have issues after that, try manually creating your key file - see If that doesn't work, please let me know your order number and I will check it here. Also, before posting, can you please: 1. First check the documentation 2. Search the forum for similar issues - most questions have been asked before John

I have other ideas planned to allow parameterized calculator code to be used. Unfortunately, at the moment all my time is being taken by support (and keeping up with MSFS and P3D releases) and I have very little, if any, spare time at the moment to look into this. Hopefully I will get a chance to investigate this later this year. For the time being, you can achieve what you propose relatively easily using lua. If you write the axis value to an FSUIPC offset ('Send to FSUIPC Offset' checkbox), you can have a lua script that monitors that offset (using the event.offset function) and then in the handling function construct the calculator code string and use ipc.execCalcCode function to execute. John

Please see the README.txt file (included in the zip file you downloaded). Instructions on this issue are provided there - you need to install (or re-install) the latest combined VC++ redistributable package. John

The OP was referring to event files which are loaded by extension .evt and not matched to the aircraft name. Macro files are also loaded on extension .mcro and also not matched to the aircraft name. John

What do you mean by this? If FSUIPC is closing as it cannot find MSFS, and you are on Windows 11, then please see the provided README.txt, Otherwise, please explain what your issue actually is and show me your FSUIPC7.log file. Connection to MSFS is the same in the unregistered and registered versions. If you purchased FSUIPC7, then you should register your details at the end of the installation process, If you have not purchased a license but would like to try the registered facilities, there is a time-limited key file available in a sticky post at the top of this forum. John

I don't see how this can be.... Loading the default FBW I see the following aircraft name: 134000 Aircraft="Airbus A320neo FlyByWire Xmas" This will load the A320NX profile, NOT the A320 profile. If you think the wrong profile is being loaded, can you show me the Aircraft title, as logged by FSUIPC. When you load an aircraft with a new livery that is not currently assigned to any profile, it is up to the user to select the profile for the new livery (or create a new one) - this is not done automatically. Therefore it must have been the user' choice to assign the 'British Airways OperatorLand468 FBW' to the A320 profile, and not the A320NX profile. For this, then you need: That is a possibility. However, I am concerned if this will be possible with all aircraft due to the encryption sometimes used with deluxe and add-on aircraft. I will have a think about this and maybe look into this. A main issue changing to this would also be that it would invalidate all current profile assignments. I guess I could handle this by determining the FSUIPC version and re-writing the profile sections, but would be a bit of a pain. Let me think about this. No, nothing has changed in this area. Yes - hvar file names must also match in the same way. However, If I do decide to change the way profiles are matched, this would not change the way hvar files are matched. The hvar files are loaded by the WASM which (currently) has no knowledge of the aircraft.cfg file, its location or access to FSUIPC offset information. I could also look into this but would be separate from the profile issue. I also have other changes planned which I think are far more useful to the general community, so I cannot give you any timescales when I will look into this at the moment. John

I have never heard of such behavior and have no idea what could cause this...FSUIPC is not actually doing anything when the UI is opened - it is just waiting for mouse input events from windows. Have you tried re-installing the P3D client? Can't think of anything else at the moment...

But did it detect anything when you press the buttons on the device?

As you have already ran the first one, just run the 2nd one, with your logitech jopystick and rudder pedals disconnected, then reboot and reconnect. then run FSUIPC7 and exit, and show me the 3 files again. Sorry about your issues with MSFS, but I can't help with that. Try the Asobo forums for installation issues.

I haven't tried this but the result depends in which level the MSFS applies the sensitivity curves. From what you say, it looks like the values send from FSUIPC go at a higher level and bypass the MSFS calibration. John