John Dowson

For your FSUIPC4 issue, try running the FSUIPC4 installer again (no need to uninstall first). That may repair any problems and won't do any harm - worth a shot. No problem. Take it easy, John

Yes - the same issue occurs with avionics 1/2. For avionics, the Avionics Master Set control works, but the toggle control not. I have updated the relevant offset to use the set control (but not yet released). There is a separate post on this issue. This sounds strange. I will take a look. Shouldn't be necessary really. I'll take a look and see whats happening... Thanks for the report. John

This sounds like an issue with LINDA then - maybe try the LINDA support forum.

Then maybe you should try smartCARS support.

This is a support forum for FSUIPC7 only. The main support forum is for all other products, apart from the .net dll client by Paul Henty which also has its own sub-forum. There is no specific support forum for FSUIPC4, use the main support forum. Sorry, but if it was working and is now no longer working, something must have changed. You need to determine what. As I have said, FSUIPC7 in no way affects other versions of FSUIPC. Anyway, as I said, if you have a problem with FSUIPC4 then please use the main support forum. And I don't know why you "reported" my post with the complaint "Does not contribute to finding a solution, or help give insight in any manner to my post.". I am only trying to help and determine what your problem actually is. Please not also that FSUIPC4 is NOT my product, its still with Pete, although I try to help with it where I can. John

This seems to be an issue with VRI devices. Did you try that ini parameter I mentioned previously? There are other posts on this as well with possible solutions. please search. I find this very strange. Can you please double check the background tasks please. I could update to manually remove the mutex (which is what is preventing FSUIPC7 from running) earlier in the shutdown process, but this would mean whatever background task you have running would still be running, and most probably would affect performance or functionality. You log shows that FSUIPC has not terminated and closed the log file, so there MUST be something still running - you just need to find it in the background processes and terminate. John

Sorry, but can you clarify what your issue is. I thought that you you were talking about FSUIPC4 (v4?), but if so why are you posting in the FSUIPC7/MSFS forum? FSUIPC7 should in no way affect FSUIPC4 - as long as it's not running. In fact, I doubt you can run FSUIPC7 if FSX is running (or vica versa), due to the clash in windows class names. So, in summary, I am perplexed and do not understand your issue. Could you clarify please?

All the information you need is in the provided FSUIPC documents. If you haven't used lua before, check the provided examples. @spokes2112 is very good with such plugins, he may have or know of a similar plugin that you could adapt.

Ok, thats interesting. Do you see the TransmitClientEvent failures in the log before you do this, and none afterwards?

FSUIPC7 is ONLY for MSFS. You need FSUIPC4 with FSX, as always. However, make sure FSUIPC7 is closed (and not in your system tray) when you use FSX/FSUIPC4. This should no longer be applicable with the latest MSFS update.

Then maybe report this as a bug to MSFS via their forums.

Sure, should be possible via a lua plugin.

Ok, that's good to know. But I think I'll update 3C00 to contain the full path to the aircraft.cfg file, as it was previously. And maybe find some new offsets for those 3 new entries ("icao_type_designator", "icao_manufacturer" and "icao_model"). I'll post here again when this is done (next week sometime). Yes, I believe something has changed - and different from the alpha/beta releases. I'll update for this (as I just said above). I'm not sure about this one yet. As I said, this is the "installation path", the one you choose during the installation, and is taken from the UserCfg.opt file. I'm still not sure ho useful this is at the moment. Under a steam install, this contains a lot of data under .../'Official/Steam', and I guess the 'Community' folder would/may contain add-on info, but its difficult to know at the moment with the lack of info provided by MS/Asobo on how these folders are used. Currently, I am open to suggestions on what paths/folders would be useful to FSUIPC users for these offsets. John

Oh, and please give your posts a relevant title, not your user name.

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.