John Dowson

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.

Its from the PMDG SDK via a Client Data Area - see the PMDG SDK documentation file PMDG_737_MSFS_SDK.pdf. John

From the PMDG SDK - se the document Offset Mapping for PMDG 737-700: 65D0 2 Signed short MCP_VertSpeed John

I do not provide access or support earlier versions - only the latest version is available and that is the only version supported. I can't see how there can be issues, except if they are using one of the 4 offsets that were populated from simvars in the new FuelSystem module which are no longer available, otherwise 7.3.18 corrects some issues with 7.3.17. Please see the history document for details of the changes (or the changes.txt file). What exactly are these issues?

Btw, if you are not using the latest version of FSUIPC7, 7.3,18, can you please update and try with that version. Earlier versions were could be logging hundreds of console messages (in the MSFS console) every second with aircraft not using MSFS's new Fuel System module. This can maybe cause some logging contention issues if something else is also logging a lot to the console. You could also take a look at the console messages to see if there is anything there relevant to this issue (you need to switch to Developer mode to access the console window). John

Strange that this only started in the last 2-3 weeks - what, if anything, changed in that period? Can you first check that you are using the latest FSUIPC7 release, 7.3.18. Also check that the buttons/switches you are using are not also assigned in MSFS. If you get the same issue, can you activate FSUIPC logging for Buttons & Keys and Events. Then generate two log files for me, one showing the issue when the flaps go full down/up, then reload the buttons and activate the flaps inc or dec again, and then exit. Then show/me attach the FSUIPC7.log and your FSUIPC7.ini. For the second test, use the same logging and use an aircraft without a profile, and then try and operate the flaps in the three ways mentioned - using yoke button, VC and keyboard. Again exit before attaching the log. I will take a look at your files tomorrow if I have time, but most likely it will be on Monday. John

Ok, thanks - I would be interested to know the cause of this.... Regards, John

It is reverse polish notation - see https://docs.flightsimulator.com/html/Additional_Information/Reverse_Polish_Notation.htm John