John Dowson

I can look at adding this at some point (maybe in a few weeks...), but first a few questions: 1. Not sure what GNSS Quality or IMU Alignment Status are - would a value of 0 be ok for these fields? 2. For the heading accuracy I would just use 0.001 and for the roll and pitch a value of 0.010 - would that be ok? 3. Could you test this for me once implemented - I cannot test GPS out functionality here. John

No - I am referring to FSUIPC profiles. You have two FSUIPC profiles, one for the Mooney Bravo and one for the FSLabs A320. I was saying that as you do not have an FSUIPC profile for the PMDG, the general calibration section will be being applied. You have corrected your issue now by deleting the general throttle calibration, but this could re-appear if you calibrate for any other aircraft not in a profile. The better way to stop this happening is to create a calibration profile for the PMDG and reset the throttle calibration there. John

I have no idea what the GoFlight Interface tool is, and cannot help with issues with that - you need support for whoever provides that tool. And you do not need this, or the GoFlight driver, for using most GoFlight equipment with FSUIPC. You don't say what GoFlight modules you are using, but see www.fsuipc.com for the GoFlight driver for FSUIPC6, together with a list of the modules that it supports. You should uninstall the GoFlight driver as well if using these, and let windows install the default driver. John

So you only get a drop in FPS after landing? This sounds very strange as nothing special is done on landing... What happens if you restart FSUIPC7 after the stutters have gone - do they return? Is it ok after landing without using FSUIPC7? Only with the PMDG 738 or also with other aircraft? Can you please try with 7.3.19, just released.

@Markus Hermans Now SU12 has been released I have re-tested with a version of FSUIPC7 (and WASM) that has been rebuilt against the latest SDK (0.21.0.0) and still see no drop in FPS. I will release this updated version, 7.3.19, tomorrow - can you please test with thus and let me know if you still see a frame rate drop. John

Can you please attach your files rather than pasting their contents. I find them a lot easier to read this way, and it also drastically reduces the sizes of the posts. What did you do last time you had this issue? Maybe try that again... What are you using FSUIPC4 for? Your ini looks pretty empty - no assignments for buttons or axes, and no keys section which is strange....

Ok, thanks for the update. Glad this has been resolved, John

What is PASHER and how is it used? Can you provide a reference and an example? It doesn't seam to be a NMEA sentence - they are also all 3 letters as far as I am aware... John Later: Ok - I have found PASHR (not PASHER): http://receiverhelp.trimble.com/oem-gnss/NMEA-0183messages_PASHR.html

👍🙂 You can remove those additional logging directives now that it is working. John

Yes. You can skip registration, and after installation copy across your FSUIPC6.key and FSUIPC6.ini files (as well as any *.lua or *.dll files that you may use) from your old installation folder to the new one. Add those additional logging flags I mentioned to the FSUIPC6.ini. Then, run P3D/FSUIPC6 and check/activate and set your GPS Out settings and try again. Any issues, show me/attach your FSUIPC6.ini and FSUIPC6.log files. John

As you have no profile for the PMDG aircraft, the default calibration section will be applied. Create a calibration profile for the PMDG and clear/reset the throttle axis calibration in that profile. You should also change this: to this to catch different liveries (using substring matching). And also change the aircraft name in your new PMDG profile to a substring match rather than using the full aircraft-with-livery name. John

This is a windows issue, not an issue with WideClient, and I cannot really help with this. Google gives me this: https://www.addictivetips.com/windows-tips/run-app-as-admin-at-startup-on-windows-10/ and also: So maybe try one of those methods... John

No. No limitation there, and I do not currently know why the rate you set is not being saved, which is why I want yo see yout files. It is in the same folder as your FSUIPC6.ini. If you cannot see it, it is probably because you have windows explorer set to hide the extension of known file types. I wan to see this as this will tell me where you have installed FSUIPC6. If you have installed it into a windows-protected folder, such as under Documents or Program Files, then this can cause issues. Well, that would certainly prevent the GPS out data beinf sent! Your ini file also show that you are using an old an unsupported version of FSUIPC6, 6.1.0 - can you please update to the latest and inly supported version, 6.1.9. When you re-install, make sure that you do not install in a windows protected folder. And I also need to see your updated FSUIPC6.ini now that you have actually enabled GPSOut. In your FSUIPC6.ini, can you also please add the following to the [General] section: Debug=Please LogExtras=4 This will then log the GPS out data sent. On the client PCs, you can look for an application that can monitor the data received - maybe your applications are just not understanding what is being output. Also check that you are using the correct COMx number for your adapter. Please attach your updated FSUIPC6.ini and your FSUIPC6.log file generated with that logging specified. John

I suggest you change this to: to catch more variants/liveries. Check that the buttons are not also assigned in P3D. For the buttons not working, could that be because the loaded aircraft did not match the profile (i.e. different livery)? Can you activate logging in FSUIPC's logging tab for Buttons and key operations and Events (non-axis controls) and generate a short log file showing your issue, and then attach your FSUIPC6.log and FSUIPC6.ini files with a description of what you did and what went wrong. I will need to see another log file for this issue but this time with Axis controls logging activated. Once you have experienced the taxiing issue, exit P3D/FSUIPC so that the log file doesn't get too large, although you may still need to compress/zip it. John

Can you please attach your FSUIPC6.ini and an FSUIPC6.log file. The minimum time interval is 100 msec. What map application? The user manual does say "GPSout may not support all other moving map and atlas programs, but ..." John

No - I don't think the times are available. All AI traffic information is stored in the TCAS data and data2 offsets at 0xE080 & 0xD040 (for AI ground aircraft) and 0xF000 & 0XD840 (for AI airborne aircraft). John

Can you try the attached dll to see if this helps - add the following to the [General] section of your FSUIPC6.ini file: AxisScanOnStart=Yes Let me know if it makes any difference. if not, can you show me your FSUIPC6.log and FSUIPC6.ini files. John FSUIPC6.dll

Not sure what you mean by 'when my Windows 10 PC starts up in administrator mode' - administrator rights are UAC privileges attached to a process. To run any application with Admin privileges, go into the exe files properties->Compatibility mode and check Run this program as an administrator. If you have done this on the exe itself and it is not starting as admin then this seems to be a windows issue.

Thanks for your king words - I will pass on to Pete. Regards, John

Also, this is usually due to a corrupt weather file. Try disabling weather by setting NoWeatherAtAll=Yes to the [General] section of your FSUIPC4.INI file. If this solves it then either your wxstationlist.bin file is corrupt, or one of the .wx files saved with scenarios is bad. To resolve this, delete all of the .WX files from your FS Documents folder (where your flights are stored), and the file "wxstationlist.bin" in your <user>\AppData\Roaming folder for FSX. If that is not the issue, then this can be due to a corrupt FSX installation, most probably in SimConnect. You can try verifying the installation in the Steam client. Otherwise, please show me those files as requested. John

Not sure what you mean by this...I just want to know if your CTD problem has gone, and if the only issue now is that FSUIPC7 doesn't exit cleanly. For issues with LINDA, you need to use the LINDA support forum - I cannot help with LINDA, sorry. But as far as I understand, it is not crashing anymore but just not exiting properly - probably due to either some lua threads or the VRI DevCom thread not exiting correctly. As I said, for this issue I need to see your log with the Lua Plugins and Extras logging activated, as well as your ini file. But for your other issues with LINDA, you need LINDA support. The shutdown issue may also be related to your issue with LINDA, but FSUIPC7 should still exit cleanly. John

First, you posted in the Download Links sub-forum where it explicitly states NOT for support requests. Please take care to post in the correct forum for support. If you have FSUIPC7 installed, then all documentation will be in an FSUIPC7 folder in your windows Documents folder. Offsets are documented in the FSUIPC7 Offsets Status document, and a separate document is available for specific PMDG offsets called Offset Mapping for PMDG 737-700. John

Not only would this be a lot of work for very little (if any) benefit for a small subset of users, it would make the UI a lot more complicated for the average user. No harm in asking for sure, but this one is not going to happen I'm afraid.

First, you posted in the FAQ sub-forum where it explicitly states Not for support requests. Please post in the correct place if you require help. You seem rather impatient...it was around 9pm (here) on a Saturday night when you first posted, and then follow up with this 4 hours later.... Support here is pretty quick, but certainly not 24/7... Can you please show me you FSUIPC4.log and FSUIPC4.ini files, and also your InstallFSUIPC4.log file. I will take a look at them tomorrow. John

Ok, so its not now crashing after 5 or 10 minutes, as your first comment says (as well as the title of this topic), but just failing to exit properly? Can you show me a log file when this occurs, with Lua Plugins and Extras logging activated, as well as your ini file.