John Dowson

Are you using the latest beta of FSUIPC7 which has added support for MSFS2024? If not, please update to that version. See If using that version, please post any issues in that topic until I release this version officially, and make sure to at least include/attach your FSUIPC7.log file. John

Yes, as these devices are not assigned in FSUPC, in fact you have no assignments at all, it cannot be anything to do with FSUIPC. Your MCP and Efis are not even detected by FSUIPC. The log file you attached when FSUIPC7 was running and ends after 3-4 seconds and shows nothing. Please ALWAYS exit FSUIPC before attaching any files. John

¿Puedes decirme cuál es el error? Además, adjunta tu archivo FSUIPC7.log. ¿Estás usando un add-on para el StreamDeck? Si es así, comprueba que se haya actualizado para MSFS2024. Consulta:

No need for a screenshot. This sounds like your device has gone to sleep (as the button press is not recognised) - check the USB hub properties in device manager. Otherwise, please show me those files with the logging activated.

Both log files look ok and show that FSUIPC7 was running and had not crashed. When this occurs, can you operate in the FSUIPC7 main window? i.e. does Alt+F open the main window, and can you then open the assignments windows and use those? If so, can you see the assignments you have bound to the switch? Is the switch/button recognised? The WASM log looks ok, and shows that that didn't crash. You do have a few reconnection attempts at start-up, although this is nothing to do with the issue you are having, To prevent these, can you please set/update to the following in your FSUIPC7.ini (in the [General] section): DetectToConnectDelayAuto=90 InitialStallTime=45 StartUpTuningDoneVersion=-1 For your issue, can you please activate logging for Buttons & Keys, Events, Extras and WAPI Debug level logging, and the next time this occurs first open FSUIPC7 and the assignments window and press the button (presumably not recognised?), then exit FSUIPC7 and send me/attach your FSUIPC7.log and FSUIPC7.ini files. Then restart FSUIPC7 and try again. Does it now work? Presume so (from what you said), but if not, please then exit MSFS and show me / attach your FSUIPC_WASM.log file. Also please check the power settings on your USB devices and hubs, and make sure Allow the computer to turn off this device to save power (under Power Management) is disabled. Windows has a habit of resetting this setting for some reason... - John

Yes, you will need to purchase a license for FSUIPC6 for P3Dv5 (and it is also valid for P3Dv4 and P3Db6). Your WideFS7 key is still valid and this can be used with FSUIPC6. John

If you have previously purchased a license for FSUIPC6, then the details of your purchase (including the license key) will be available from your SimMarket account. If you don't have a license, you can purchase one from SimMarket. John

The trial license has been updated, now valid until 01/01/2025, John

First, there is no point in monitoring such offsets, Monitoring logs the value of the read offset, whereas you write to the write offset (there are separate areas for read and writing), Well, no point in monitoring, and even if you did you should monitor as a FLT64. The parameter/value for all input events is a 64-bit floating point value (double), as it is for lvars, So make sure you write it as such, and not as an S32 (int). Please re-read the documentation.... John

No. Please see the FSUIPC7 Offset Status document on how to use the facility at offset 0x7C50: John

I am not sure why this would be - I will take a look sometime next week.

There are no id numbers associated to Input Events. Each one is identified internally (and by MSFS) by a hash number, but I don't make these available. But to send an Input Event via an offset, you should use offset 0x7C50/0x7C90 not 0x3110/0x3114, and use the input event name, preceded by 'I:'. John

Which would confirm that it is not related to FSUIPC, but more of a coincidence that it also happens when FSUIPC is loaded. I think this issue has been reported before, but I can't remember what the issue was caused by, sorry.

Your log shows you didn't install the WASM for MSFS2024, which could be an issue, Anyway, 7.5.0c has been released now with a full installer, so please download and re-install from John

So your MCP and EFIS don't work? In MSFS2020 or MSFS2024, or both? How are the devices assigned? In FSUIPC or elsewhere (e.g. cpflight plugin)? Does FSUIPC even recognise your devices? Was this working in MSFS2020 with 7.4.18? Please clarify what your issue is and why you think this is related to FSUIPC. And please also show me / attach your FSUIPC7.log file as this will at least give me some basic information.

This normally happens when the DirectAxesToCalibs ini option is set to Yes. Remove that it set it to No. If you need that option set, then you can set it to All (see Advanced User guide for details). If that is not the issue, show me / attach your FSUIPC7.log and FSUIPC7.ini files and I will take a look. However, it may take me a few days to get back to you. John

Sorry, but I do not understand what your question is. 7.5.0-beta is now available with an installer from the following page: John

That is very strange, and I don't see how FSUIPC can be doing this. When this happens, can you open FSUIPC7 (Alt + F) and does it work (i.e. can you operate the menus)? Can you exit FSUIPC7? If so, please do that and show me / attach your FSUIPC7.log file. Once exited, foes MSFS then display the ready-to-fly button? When you start MSFS and FSUIPC7 is auto-started (presuming you are using auto-start), can you then exit FSUIPC7 and let MSFS load to the main menu. Then select your aircraft and get to the ready-to-fly stage before starting FSUIPC7. Does it then work? Maybe also worth checking the MSFS console for any messages logged there. You need to turn on Developer mode (in the General options) to see the developer menu bar. This is the support forum for FSUIPC7 and I am the developer.... John

What do you mean? You use PMDG aircraft in MSFS2024 as you would in MSFS2020....

I see no reason why not...please just try it! Cheers, John

Note that you probably need the latest FSUIPC7 beta version (7.5.0-beta) for full compatibility with MSFS2024. currently available from the Announcements sub-forum.

Ok. If you are using Paul's .Net dll, he has already updated this for MSFS2024 and FSUIPC 7.5+ so update to that if not already. The only other thing to consider is if you are checking/reading offset 0x3308 for the FS version (new version number for MSFS2024, and now only populated when connected to the FS). Otherwise you should be ok. Cheers, John

The current 7.5.0-beta (available from Announcements sub-forum) is pretty much what I will be releasing as 7.5.0 (currently no outstanding issues). Working on the installer at the moment, finished but testing. I then need to update the documentation and will release the full installer + documentation as a beta when this is done, hopefully at the weekend. I will then leave in beta for a week or so, to fix any reported issues, then I will make this the next official release. I recommend trying the v7.5.0-beta now and report any issues found. Or maybe wait for the installer release when it comes in a few days. The official release will be around the 7th December. John

I have just checked this here, assigning both with send direct and to fs and don't see any issues, either with or without calibration and a slope. Do you see the same issue when assigned in MSFS? If not, can you show me your FSUIPC7.ini and an FSUIPC7.log file, generated with logging for Axes Controls activated, Just load the aircraft, move your rudder fully in both directions then back to center and then exit. Axes are also calibrated when assigned externally (i.e. not in FSUIPC). If the aircraft does not match a profile, the general calibration section will be used, otherwise the profile specific. This has always been the case. If you want to calibrate for a specific aircraft (rather than general calibration) then you should do this in a profile. You can also disable post-calibration (i.e. calibration of axis events seen by FSUIPC, not necessarily assigned) completely by setting AllowSendToFSCalibration=No John