John Dowson

All issues with registration are either due to: - not entering the correct details - not having the correct VC++ redistributables installed - anti-virus software blocking the validation - using unicode rather than ascII - trying to use a key for a different version of FSUIPC If you have checked all those (and make sure that you have downloaded and installed the latest VC++ redistributables) and still have issues, please let me know your order number and I will check it here. Do NOT post your key details. John

Please set Debug level logging in the WASM via the FSUIPC_WASM.ini file. Was the FSUIPC_WASM.log file attached when MSFS was still running? If not, the WASM has crashed, but I expect that MSFS was still running... Your log file shows a few presets were triggered and sent to the WASM: But I don't understand these log messages: Not sure why those are logged as that message is only logged when the button assignment panel is open. They are all buttons (3,5,32,34,36,38) on your throttle (1) that have no assignments. Was the assignments window open here? You need to set Debug level logging in the WASM. then test again - keep the logging console window open (Log->Open Console) and add the DontLogThese ini parameter to your [Profile.FENIX A320] section, i.e. and for your [Profile.B737 PMDG] profile: This will prevent excessive logging of those events that are continually seen and filling the log. Then test a few buttons that you have assigned to presets (with the logging console window open), check the button is triggered and the calc. code sent in the FSUIPC7.log file, and if the calc. code was received and applied in the FSUIPC_WASM.log file.

Please see the Installation and Registration guide, section Invalid Key Problems (or the README.txt).

There is an error on the first line of your FSUIPC7.ini fille: Remove those characters - in fact, remove the whole section as the [General] section has been added again further down. Ot correct that and remove the 2nd [General] section - your choice but there should only be one. And those log messages indicate that the button assignment panel was open when you tested, Button logging should look like the following: Button assignments are not triggered when the assignment panel is open, So please correct your ini, set logging for Buttons & Keys and WAPI->Debug and try again, and attach the files again if you still get issues. Also, try testing with the logging console window open (Log->Open Console) and you should see the lines logged in real-time. John

To diagnose issues with presets not working, I need to see 3 files from the same session: - your FSUIPC7.ini file. This shows me the assignments and profiles. Always attach after FSUIPC7 has exited. - your FSUIPC7.log file, with logging for Buttons & Switches, Events and WAPI->Debug level logging activated. This shows me the buttons/keys pressed, any assignments triggered and any calc. code sent to the WASM., Always attach after FSUIPC7 has exited. - your FSUIPC_WASM.log file, with Debug level logging activated. This shows me if the calc. cide has been received by the WASM and applied to the aircraft. Always attach after MSFS has exited. You only attached a log file. This just shows several button presses triggering the PMDG_B737-7_LIGHTS_RUNWAY_BOTH_ON and PMDG_B737-7_LIGHTS_RUNWAY_BOTH_OFF presets: You need to check the FSUIPC_WASM.log to see if they are being applied. If they are being applied, and those presets are working, then the runway lights should have flashed on then off 3 times. Not sure why you are getting a button release before a press. I presume that his is either a switch or sticky button, and it was already in the on/pressed state when FSUIPC7 was started.

No - why would you want to do that? I am pretty sure that is not in the correct format. As I said, there are already offsets allocated to PM. Forget about the myOffsets.txt file. What is your actual issue? If the problem is with your CPFlight device, check this support forum for similar issues. John

Do you know what the myOffsets.txt file is used for? This is NOT installed by the FSUIPC, and is only present when created or installed by the user. If its not there, you are not using one. This file is for a user to add simvars to free/spare FSUIPC offsets. Not sure what you mean by this. The Project Magenta offset areas are: 0x04E0 - 0x0537 0x5400 - 0x5FFF What offsets hold is defined in the Offset Status document. John

Can you try setting DirectAxesToCalibs=Yes to see if that helps. Otherwise please try the attached version, where I have switched to using the KEY_AXIS_ELEV_TRIM_SET control when writing to offset 0x0BC0 instead of KEY_ELEVATOR_TRIM_SET, as well as also allowing the KEY_ELEVATOR_TRIM_SET control to be calibrated. If neither of those works then I'm afraid it won't be possible to calibrate the elevator trim for your device. FSUIPC7.exe

Sorry but there is nothing I can do about this. You are using an unregistered copy and so FSUIPC isn't doing much except populate its offsets for use by other programs. Your logs show no issues. If you don't use AI data, you could set the following in the [General] section of your FSUIPC7.ini file: ProvideAIdata=No Otherwise I don't know what to advise, or why you are seeing such a drop in FPS.

You have no issues with any of your devices, and you don't have controllers listed multiple times, You have them listed with an id and with a letter - this is perfectly normal. No, You will get more issues if you install under C. I don't know why you are having such issues and why they are taking so long to resolve. From what I have seen so far, all your issues are due to the fact that you re-installed without installing the WASM. Don't bother with attaching screenshots - it is the files I need to see. And get into the habit of changing/shortening the aircraft names when you add them to a profile. This: should be Try setting the required logging and looking at the files yourself. Is the assignment being triggered on FSUIPC? Setting logging for Buttons & Switches will show any assignment being triggered, and for presets setting WAPI Debug level logging will show the preset code being sent to the WASM. Then WASM Debug level logging will show the code being received and applied in the WASM. So try that, and if a preset isn't working, check to see if 1. the button is triggering the assignment 2. The assignment is sending the correct calc. code 3. The calc. code is being received and applied in the WASM

I don't understand the question - button and axes assignments are completely independent. Assigning an axis with "Direct to FSUIPC calibration" will have no effect in any button assignments. Yes. The standard way to do this, but depends on the controller used, is to assign to throttle_dec (on repeat) on the throttle button that indicates past idle (if you have such a button), then assign to throttle_cut in the release to kill the reverse thrust. Then when you are in idle and push the throttle down, the button is triggered and throttle_dec commands are sent which will move the aircraft into reverse, and when you move the throttle back it cuts back to idle.

You only have 4 assignments on 2 buttons (to the press and release of each button). Are those switches, sticky-buttons or momentary buttons? If the latter, then what is happening is that the taxi lights are being switched off when you press the button, and then back on on the release, That is how you have assigned, If that is not happening, then you need to set logging for Buttons & Switches and WAPI Debug level logging in FSUIPC, and also Debug level logging in the WASM. You have nothing assigned to the pitch and elevator axes in FSUIPC.

Those errors can safely be ignored - they are reported when the WASM is trying to clean-up after MSFS has quit, and the simconnect calls are failing as the connection is dead.

I have added the LIVERY NAME simvar to offset 0x2480 (128 bytes) in the attached version if you would like to try it. This offset will only b populated in MSFS2024 and not in MSFS2020. John FSUIPC7.exe

I am just saying that you need to follow my advise and change your profile names to use substrings, otherwise your profiles won't work when you use aircraft with different liveries. For example, in the log file you attached, you used the aircraft 'PMDG 737-800 vRYR Ryanair EI-DCJ' which doesn't match any aircraft in your B737 PMDG profile and so the profile won't have been loaded and you will not have any of your PMDG assignments available. They are empty in the one you attached. If you have one where they are not empty then use that, otherwise you should delete them and re-assign. If you selected to install and it didn't, check the InstallFSUIPC7.log file for errors, and see the installation and registration guide on how to resolve any issues. Once the WASM is installed, your presets should work, but you will have lost your general assignments unless you can install them from backup.

But you did not run FSUIPC afterwards. The version of the ini is 7.4.18, but the log reports 7.5.1. So this ini was not used by that log file. O need to see files from the same session. No, those changes could not affect MobiFlight in any way. You should make those changes as advised, and if you have issues report them and we can investigate. But if you don't follow my advise, I can't help you. Nothing was working in the aircraft you tried as all the assignments are empty: Not sure why that is, but you should remove those and re-assign. And for your PMDG / FBW / Fenix profiles, they all use presets and won't work as you have not installed the FSUIPC WASM module: If you selected to install the WASM and it wasn't installed, then check your installation log for errors. You cn try re-installing and install the WASM, and if any issues check the documentation or previously reported issues. There are various known issues that can prevent the WASM being installed. You may also have issues if you have installed FSUIPC under the Windows Program Files folder: ? If that is one you created then thats ok (it is not under c:\), but otherwise it could create issues.

Null zones are calibrated in FSUIPC's axis calibration pages. See the User guide. John

What do you mean by this? If you previously reported the same issue, you should use the same support topic. Is this the same issue reported here: If so, please continue there rather than starting a new topic for the same issue.... I will close/lock this shorty, unless this is a new issue... John

That is interesting - I hadn't noticed that. That will at least make the profile matching easier/more reliable for most people! It is not possible to add MSFS2024-only simvars to FSUIPC offsets at the moment, as this would create issues when using MSFS2020. I could look into only requesting certain simvars in specific MSFS versions at some point if needed, but I don't think this one is useful enough for enough people to add this to a fixed offset at the moment.

Your upload limit is rather restricted as you are a new forum user - it will increase the more you post. You can try compressing/zipping it, but if still too large you can use one of the free file exchange services, e.g. https://filetransfer.io/ You only need to update the one, but it doesn't matter. Ok, so the buttons on your controllers/devices are not recognised? If thats the case, please also attach your FSUIPC7.ini and FSUIPC7.JoyScan.csv files. And that would explain why nothing is working, but is not exactly the issue of this topic...

That can have absolutely no affect whatsoever, as only additional software and files are installed with this, and nothing is actually started or used unless you manually do something with what is installed. The log file you attached was attached when FSUIPC was still running - please exit FSUIPC before attaching files. Did you check the MSFS logging console for messages? Did you try setting the ThreadAffinityMask?

Thats not strictly true - it could be that the WASM couldn't acquire a simconnect connection, which may be your issue. This is usyally caused by another third party app taking too many connections. FSUIPC can sometimes cause this, if nadly tuned, but the auto-tuning facility should detect this and set auto-tuning to run, and after FSUIPC7 has been ran a few times (2 or 3) it should have tuned itself. Anyway, if thats the case, the FSUIPC7.log file may help. but I may also need to see a SimConnect.log file to see what is taking all the connections. But let me see the FSUIPC7.log file first, and follow my other suggestions. John

I am afraid that 16 is the maximum number of devices allowed. Not sure why you are only seeing 15 though... John

This is possible but not via offset area 0x3340 as that is for FSUIPC-internal virtual buttons and such buttons are only seen by FSUIPC and its clients. What you need to do is download and install the vJoyOffsets program. Use this to configure a separate/distinct offset area for your virtual buttons. then use that area. Changes to such an area are then forwarded to windows (using vJoyFeeder) and can be seen by any other windows application. Make sure you read the vJoyOffsets documentation. John

The WASM log file shows that it was attached when MSFS was still running and that you hadn't even started a flight yet. Please always exit MSFS before attaching a WASM log file, and also please set Debug level logging.in the WASM (via the FSUIPC_WASM.ini file). And I also need to see your FSUIPC7.log file generated showing your issue, preferably with WAPI debug logging set (Log->WAPI->Debug) as well as for Events and Buttons & Switches, so please attach that, but only once you have exited FSUIPC7. You should switch to using substrings for your aircraft profile names in all your profiles. For example, for your B737 PMDG profile, change to and to This will prevent issues with the profile not being loaded when using a new livery. Updated from which version? There were hardly any changes between 7.5.0 and 7.5.1, and nothing that would effect presets. John