John Dowson

The second image shows that you have 'Gear Down' assigned - is this not working? If L,9 is showing , FSUIPC is receiving a press event for it. Could it be a problem with a sticky/faulty button? Try logging 'Buttons & Keys', to see if FSUIPC is receiving these when not pressed. Or maybe locate which button/switch that is on your device and see if you can turn it off.

Please see John P.S. Note that all questions on FSUIPC7 for MSFS should be posted in the dedicated sub-forum: https://forum.simflight.com/forum/183-fsuipc7-beta-for-msfs/

Hi Gerard, adding to what Andrew has said, there are no .air files in MSFS. And I don't see the full path name to the aircraft.cfg file in the log, only a relative path, e.g. 8500 SimObjects\Airplanes\Asobo_FlightDesignCT\aircraft.CFG But 0x3D00 is the name of the current aircraft.... 0x3E00 currently contains the "installation path" or (FS UNC path), as determined from the UsrCfg.opt file. I'm not sure how useful this is. Note also that locations are different in a MS Store vs Steam install. I have a steam install (strings truncated to 32 chars unfortunately): 90500 Monitor IPC:3C00 (AsciiZ) = [54]"SimObjects\Airplanes\Asobo_Fligh" 996078 Monitor IPC:3D00 (AsciiZ) = [20]"FlightDesignCT Asobo" 1336735 Monitor IPC:3E00 (AsciiZ) = [12]"D:\MSFS2020\" 1575703 Monitor IPC:3F04 (AsciiZ) = [103]"C:\Users\jldow\AppData\Roaming\M" 2649172 Monitor IPC:1000 (AsciiZ) = [58]"C:\Users\jldow\AppData\Roaming\M" Yes, they don't look very useful: 1801953 Monitor IPC:3500 (AsciiZ) = [23]"TT:ATCCOM.AC_MODEL_FDCT" - "TT:ATCCOM.AC_MODEL_FDCT.0.text" in aircraft.cfg 1883547 Monitor IPC:3160 (AsciiZ) = [23]"TT:ATCCOM.ATC_NAME_FLIG" - "TT:ATCCOM.ATC_NAME_FLIGHTDESIGN.0.text" in aircraft.cfg I can look into adding these. However, FSUIPC doesn't read the aircraft.cfg file, it gets the values via SimConnect, but these should be available I guess. I'll look into this in more detail (but probably next week sometime). John

But does windows see them as 'game controllers'? If not, FSUIPC will not see them.

I presume that you have updated to the latest MSFS patch - the SimConnect problem causing the frame drop was an MSFS issue, not FSUIPC7. I don't know - you should ask on 'A Pilots Life' support forum really. If you use FSUIPC7 without this, do you still see a frame rate drop?

Could you try this version please. It should close the simconnect connection after 5 errors and attempt to reconnect. You can also add an ini parameter TransmitErrorsReconnect=n to the [General] section of the ini to change the maximum number of errors received before reconnecting to n (must be > 0). Of course, it won't help much if you get this a lot, and you will lose control for a few seconds while it re-connects, so its not a solution but a temporary work-around for some folks. I'll look into generating a simconnect log to track this down further, but as Thomas suggests it would be useful to know if this applies to just specific aircraft, and what is being transmitted/received before this occurs (by activating non-axis event logging).. FSUIPC7.exe

A simconnect log file would be useful as well, although not sure how to generate one at the moment (i.e. where the SimConnect.ini goes). I'll look into this.

Thanks Thomas - I had missed the fuel weight offset!

Ok, thanks for reporting. I'll look into it.

Yes - the PFCcom driver sends the axis directly to the sim. You calibrate in the driver UI. You can't see the axes in the FSUIPC calibration tab unless you also assign in the FSUIPC assignments tab, but if you do this the sim will receive both values and so you may get jittering. The PFChid driver behaves differently and doesn't send the values directly to the sim but to FSUIPC, where you assign and calibrate. I'll report this.

Sorry, I don't understand. And what is '$'? Offset 0x126C has the total fuel weight (but in pounds), which you can use to cross-check your calculations from capacity and I'm pretty busy at the moment (on FSUIPC7/MSFS), but I'll take a look at this in more detail over the weekend if you are still having problems.

But you cannot write to the 'capacity' offsets - they are read-only. You need to calculate this. Google tells me that aviation fuel weighs 6lb per gallon (https://www.flight-mechanic.com/standard-weights-used-for-aircraft-weight-and-balance/) which is approx 2.72Kg per Gallon. So given you have the capacity and %age full, you should easily be able to calculate the weight, ie. 2.72 *capacity = capacity in kg, then (2.72*capacity) * %age full would be the fuel weight. Try that and see if it makes sense with your numbers.

Please see Yes, Instructions on how to activate your WideFS license are included in the link above (as well as in the README.txt included in the downloadable zip file). John

The option Exit with FS (under FSUIPC7 Options menu entry) is set by default, so FSUIPC7 closes when you close MSFS. If you do not want this behaviour, uncheck that option. As for your mouse problem, I don't think this is anything to do with FSUIPC7 as FSUIPC7 no longer handles any mouse actions. Do you get the same behaviour when FSUIPC is not running?

This is a known issue - please see I will close this topic. John

It doesn't as it does not show me that you have actually assigned anything to the brake axes. As I said, you cannot calibrate if you have not yet assigned. Please post your ini and I'll take a look there to see if it is assigned. No idea what that is. Nothing to do with FSUIPC. Sorry, I do not know what this means.... John

I see the alt key is still recognised in the key assignments panel. I'll remove this to avoid confusion

Hi Chris, sorry, but the ALT key modifier is no longer supported in FSUIPC7. Note also that keyboard input is no longer masked, so any key assigned in FSUIPC will also be seen by the sim. John

Have you actually made any assignments to the left/right brake axis (LeftBrake, RightBrake, and assign 'Send direct to FSUIPC Calibration')? Your video shows no assignments. You need to assign before you can calibrate.

Sorry, yes PFC.....! As I said, I don't have any PFC devices Well, that makes sense (to me at least!), as you have to have it assigned before you can calibrate. But you also said: Which seems to contradict this. Anyway, Thomas id the PFC expert, I've never used the PFC driver with FSUIPC so best wait for his response on this. John

Hi Simone, I don't think there has been any changes in FSUIPC for those offsets either....

I'll post a question on this. Sorry, I don't understand this. If you don't select any axis, whats controlling it? Sounds like you have your axes assigned in the sim, which would certainly cause jerkiness, as it would be getting two inputs, one from FSUIPC and one from the sim. If you assign axes in FSUIPC, you neeed to check that they are also not assigned in MSFS. I think this may be related to your PFC configuration (.ini). I'll see if Thomas can help with this. John

This offset was using the toggle control - I'll switch to using the set control in the next release. I've tested here and it works ok, although there are some complications if using individual on/off controls (e.g. via the UI or an MSFS assignment). When doing this, the Avionics 1 will drive the offset and Avionics 2 will have no affect. John

There is currently no documentation for FSUIPC7, but you can download the FSUIPC6 documentation. The UI has been re-organised (as its now an exe not a dll), but the main panels are pretty much the same. You can get the documentation here: FSUIPC6_Documentation Let me know how it goes. John P.S. I see you have also posted over in the MSFS forums - but no response so far...

😂 You're certainly not a chip off the old block are you 👍 Yeah, sorry I was a bit abrupt! Just seemed a strange question.Just discussing what this involves would not only be time consuming but also a waste of time. Its not something I would even consider - maybe if I had nothing else to do and someone paid me for this....! But at the moment, with continual P3D releases and MSFS just released, there is no point even starting a discussion.