John Dowson

Please note that there are known issues with flight loading at the moment, so use this feature at your own risk. I'll take a look at your logs later and get back to you, but could you check your MSFS settings in relation to this, as reported in similar post (FSUIPC7 Control problem): John

Did you not read the announcement or the README.txt file provided in the xip: John

@zkiwi, @jaxx& @Fremmed Thanks for the logs. I;ll take a look, but no need to provide any more at this stage. Uoi can stop the logging now (SimConnect + FSUIPC). I also released a new build yesterday. This has the automatic re-connect in and also (hopefully) fixes the crash that this introduced - please download and try this version. Report back if it re-connects and continues working please (or if it doesn't!), bit no more logs needed at the moment for this. @N987PL Your issue is not related to the SimConnect error. I see you are using both the PFCcom and PFChid drivers - do you need both? Your PFC throttle is also recognised as a standard USB device, so that shouldn't need either driver. This is also very strange: 2408781 Attempt to set external joystick assigns refused Not sure what this means at the moment, I'll check, bit maybe you can determine which driver you actually need,, if any.

It looks like there is a new simvar for this - TRANSPONDER_STATE: Its also documented as read/write, but looks to be only readable at the moment. I'll find a free offset and add this, but it won't be writeable until this has been corrected in the SDK/ SimConnect. John

You do not have any keys assigned in FSUIPC7. You don't have any buttons or switches assigned in FSUIPC7 either. Your log file doesn't show much. Could you activate logging for Axes Controls in FSUIPC7. Once activated, exit FSUIPC7 and restart . Load an aircraft and then move your throttle through its full range, from 0 to full and then back to 0. Then open and close the axes assignments dialog and repeat. Send me the logs. There is currently another support request from a user with a similar problem, although his throttle (also mixture/prop) starts working after he has opened and closed the axes assignment dialog, which is why I would like you to also try this. See Probably also worth trying with a different aircraft as well, although it works fine here with the TBM 930. John

Your log file doesn't show anything as FSUIPC7 was not connected to MSFS. Was MSFS running? What do you see in the title bar of FSUIPC7? When you start FSUIPC7, it should initially have the title 'FSUIPC7: Simulator not detected'. When it detects MSFS, this should change to 'FSUIPC7: Simulator is available: Trying to connect....', with a log entry of 'Simulator detected'. And when FSUIPC7 connects, this changes to 'FSUIPC7: Simulator is available: Connected'. So, I am surprised that anything works!

Is there a new update? What is the version? I am still on 1.7.14.0, released on the 28th August. Even if you assign in MSFS? Seems like a problem for MSFS then. Could you attach your FSUIPC7.log and FSUIPC7.ini files please and I'll take a look. John

@borgfan & @IanAbel I have now added the ICAO designator, manufacturer and model (read directly from the aircraft.cfg file) to the following offsets: icao_type_designator: 0x0618, 16 bytes (including string terminator) icao_manufacturer: 0x09D2, 16 bytes (including string terminator) icao_model: 0x0B26, 32 bytes (including string terminator) However, not that these will only be available if the full path name of the aircraft.cfg file is received AND if it exists! I say this as, during testing this, I noticed that when loading the C172 classic (without G1000), I receive the aircraft.cfg file as D:\MSFS2020\Official\Steam\asobo-aircraft-c172sp-classic\SimObjects\Airplanes\Asobo_C172sp_classic\aircraft.CFG However, this file does not exist....! There does not seem to be an aircraft.cfg file for this aircraft model. Also, it seems that the path to this file is relative if/when you start FSUIPC7 AFTER the plane has been loaded in MSFS, but the full path is given if you load or change the plane when FSUIPC7 is already running. I will post to Asobo about these various issues. I will release the build containing this update later this evening (or perhaps tomorrow morning). John

The Saitek switch panel is not recognized by FSUIPC/windows as a hid device. To use this, you are better off using the SPAD driver (free) or SPAD.next (payware).You can also use via lua, but have not tried this - see John

Sorry, but you log doesn't tell me much as its a 'continuation' log - I can't even tell what aircraft you were using. Anyway, it doesn't matter, I think I know what the issue is, but need to look into this a bit further. I'll get back to you, but I suspect that the airbus is not updating the AUTOPILOT ALTITUDE LOCK VAR simulator variable correctly.

Btw, how are you sending the alt/dec controls? Is this using FSUIPC, or are you operating it in the UI? If the latter, can you activate event logging in FSUIPC, and see what events are being sent when you do this. I suspect that FSUIPC may not be seeing the alt/dec events in the Airbus,, but are in the Boeing.

Ok, I'll take a look. Thanks.

I don't think this is necessary. Are you saying that the AP Alt inc/dec controls are reflected in offset 0x07D4 for the Boeing directly when sent, but not in the Airbus until you confirm with the AP Alt (set) button/control?

But this is correct, no? The offset only changes when the AP Alt is set.... I'm a bit confused now.... let me check this....

It is 0x07D4. I'm not sure I understand the log snippets you posted. How did you generate them? The A320 log (which you say isn't working) is using the AP_ALT_VAR_SET_ENGLISH event - is this via offset 0x07D4? The Boeing log only shows inc and dec controls,.

If it works on the Boeing but not on the Airbus, it sounds like an issue with the Airbus model. I'll take a look and see if this needs reporting to Asobo, but I don't think this is an issue with FSUIPC7. I'll report back once I've investigated. Thanks for the report.

That is strange. Could you activate logging for Axes Controls in FSUIPC7. Once activated, exit FSUIPC7 and restart (with MSFS running and an aircraft loaded). Then move your throttle. Then open and close the axes assignments dialog and then move the throttle again. Post the log file together with your .ini. Thanks.

No, as this would mean that it is not possible to send the full axis range, which seems a strange thing to do... joystickcurves looks interesting though.Shame its an application rather than an API! Improving the response curves to something like that used by jjpystickcurves could be added at some point in the future. However, this would be a lot of work for only a small benefit. It is something I can look into in quieter times... Thanks for the suggestion. John

I'm not sure if uses Simconnect, but probably not as I can see no other 'Open' calls in your SimConnect.log. Maybe check for that in the full log to be sure.

Btw, are you using any other SimConnect clients, or any 3rd party add-ons that use FSUIPC?

I doubt it, it shouldn't matter where FSUIPC7 is installed. I recommend you follow the advice in that link, and uninstall and re-install the VC runtime.

Sorry, but I need some more logging activated in FSUIPC. Could you go to the Log -> Custom menu entry, and enter x400, then repeat your tests. The FSUIPC7.log file produced will also be very big and may need culling. Thanks.

Sorry, I didn't realise your issue was that the buttons are outside the usual 0-31 (32 buttons) limit. You will have to use virtual buttons to get these recognised, as given in the solution posted by @jaxx (thanks!). John

Activating this control locally, I can see it being logged when you click the ADF frequency swap button in the UI, but sending this event via SimConnect/from FSUIPC has no affect. I'll also report this. Thanks for the report.

Hmm. This has been reported twice before on other versions of FSUIPC, and in both cases we could not determine why this happens, as the slope display is using standard windows API calls. Its maybe be related to a driver issue, but can't be sure. I'm afraid I don't think there's much I can do about this. See .