John Dowson

There are currently quite a few known ussues with the SimConnect_Text functions and its is currently not possible to have an updating text window. Due to this, I have added the lua wnd library to FSUIPC7 (previously only available in WideClient). I have attached two scripts which show the fps (and other things), one using the non-working simconnect text funcytons (via lua of course) and the other using the newly added wnd library, which should give you an idea how it works. Note also that anything using lvars won't work, as these don't exist in MSFS. Most probably. But if you find an offset or control that isn't working as expected, please let me know. Thanks, John FPS_Monitor.luaFPS_MonitorW.lua

Its in the Options menu, Exit with FS checkbox. It should be checked by default. John

You can try FSUIPC4 for P3Dv2. I don't think you need the registered version (if you don't already have a license) to use with the PFC drivers, so you can try without first. For FSUIPC4, you will need to use the 32-bit version of the PFC driver, not the 64-but version. John

Maybe. Have you tried the default hot key to show fsuipc7 - alt +f?

Btw, there is no 'installation' for FSUIPC7. You just download, unzip and run it. There is currently no installer.

No. They are completely distinct. However, you cannot run FSX and FSUIPC7 at the same time (due to the clash in windows class names), but why would you want to....!

Ok, thanks. I'll check that one tomorrow.

Yes, all offsets are maintained between versions and don't change, although maybe some new ones are added and others may not work. It means the status is unknown/untested. Many (most hopefully) will work, I just haven't gotten around to verifying them yet.

Ok. Could you keep it like this for a while, and send me the logs (the SimConnect ones + the FSUIPC7.log) once you get the disconnect. You may want to clear the SimConnect log files each time before you start, so you know which ones to send (or just leave them and send the latest if/when you get the issue again. Thanks!

Yes, seems that way, can't think of another explanation!

Ah, sorry, was getting confused - I was in MSFS/FSUIPC7 mode for some reason.....!

You can get it here: I would think that you have the 32-bit one, GFdev.dll, which is the one used with FSUIPC4. Cheers, John

Ok, but you really don't need the modules folder, but up to you. Its all automatic, you don't need to install (or "run"?!) any SimConnect. John

You issue sounds similar to this: What do you mean by this? If you try to run FSUIPC7 and its already running, it will show the existing running one. Is this what is happening? Note that it does not appear in the tray when open/shown, only in the task bar, but you say its not there which is strange. Maybe you can test by keeping the FSUIPC7 main window visible when you go back to the sim, and try and note when it disappears (if it does!).

@spokes2112Thanks Ramon! @jgoggi Could you test this please? Looks ok to me on first glance. Btw, what add-on aircraft are you using?

What aircraft are you using? I ask as this may be aircraft/model dependent. I just took a look with the Cessna 172 and it seems to update correctly (as does 0x30C8): John

I'll put a request in to see if I can get these added as simvars. For the time being, you could maybe use the aircraft title (offset 0x3D00). John

This is confusing me.... I've just taken another look, and now I am getting the full path name to the aircraft.cfg file in offset 0x3C00: @borgfan & @Dave March Could you see if you are now getting the full path or still getting the relative path please? Also, are you using a Steam install or an MS Store install? Thanks, John

The need for the 'Modules' folder was removed in FSUIPC6 (although you can still install there if you prefer). These days, its better to install add-ons outside of the sim folders if possible. And I would certainly do this with MSFS as not only does the folder structure/locations seem quite complex, locations are different between MS Store vs Steam installations. As Pete says, best just to create an FSUIPC7 folder somewhere outside of your sim folders. John

That's interesting, didn't notice that before, but that seems to be a later log entry logged when going back into the MSFS menus. The one that FSUIPC uses is the one logged when the aircraft is loaded: It looks like this is the one that's changed. I don't think I have enough information to determine the full path to the aircraft.cfg file at the moment. I'll raise this with Asobo. It also looks like there are no simvars for the "icao_type_designator", "icao_manufacturer" and "icao_model" at the moment either. I'll post about these as well.

Its still not 100% clear where the SimConnect.ini file should go on MS Store installations, but it looks like it should go in the same folder as the SimConnect.xml file (for MSFS) and the UserCfg.opt file. This is the folder reported in the FSUIPC log on line 3, so please check there. If that contains the SimConnect.xml, then place your SimConnect.ini there.

Try the FLT path, i.e. C:\Users\<username>\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\

Hi Charles, I have various GoFlight modules (GF-P8, GF-T8 and GF-RP48) and they are all recognized. Have you placed the GFDev64.dll driver into your FSUIPC7.exe folder?

Ah, then that must be for Steam installs - do you have an MS Store install? Try using the FLT UNC path, as reported in the FSUIPC7.log file (near the beginning). Can you let me know where that is for you and I'll update my comment. Thanks.

Ok, that's good to know, thanks. The modified version should do this automatically, but I would be interested in knowing how long this takes. As I have said though, this is only a work-around and I'll continue to investigate to find the cause.