John Dowson

👍

Ok..strange though. The installer should automatically detect the previous installation and uninstall that before proceeding... John

Where are you getting the installer from - www.fsuipc.com? There is no such option - there is only FSUIPC7 Documentation (containing User Manuals and Lua Documentation). Are you saying that you get the same error when you deselect this? I cannot see how that can be... Are you extracting/unzipping the downloaded file before running the installer? I really don't understand this issue - if there is an InstallFSUIPC7.log file generated, please show me that. Otherwise, can you take a screenshot of this error or maybe even a short video of the installation process and show me that.

Can you please attach full logs, not partial/continuation ones (i.e. don't start a new log file). Your log shows that the keypresses are being sent to MSFS as assigned: So not sure what has changed...although I am sure there have been many changes since 7.0.6 as that is over 2 years old. Could you generate a log file with the same logging in 7.0.6 and show that to me - it may give a clue as to what has changed. Otherwise, rather than assigning to key press and release, you could try assigning the button press to the key press and the button release to the key release.

Glad its now working! John

Is that error when running the installer or when unzipping the zip file downloaded? Probably the former, and this is usually due to the file already being open when you are trying to install.,

FSUIPC does not store all simulator variables (simvars), only a subset. There are far too many to be held in the available offset area. However, facilities are provided so that you can add any simvar to a "free for general use" offset for both reading and writing/updating (if the simvar is settable) - see the section Adding Simulator variables (simvars) to FSUIPC offsets in the Advanced User guide. As for FSInterrogate, that reads FSUIPC offsets not simvars. The default offsets it shows has not been updated for many years (since FSUIPC4 in 2012!), but the offsets it shows are editable and stored in a *.FSI file, with the default/provided one being FSUIPC.FSI, John

First, you posted in the User Contributions sub-forum where it explicitly states NOT for support requests. Please take care to post in the correct place for support. Yes, using a lua script. You can use the event.control function to listen for the key event, and in the handling function use the the ipc.macro function to execute the macro. Please see the FSUIPC Lua Library document on how to use these functions. John

Please try FSUIPC7 before purchasing - there is a trial license available in a posy at the top of this forum. No. MSFS did recently introduce multi-screen support but I have not yet had time to look into this. Not sure how you would do this on a 2nd PC though, I really can't advise on such issues. You would be better asking such questions on opencockpits.com or on avsim. I can only support FSUIPC and related products and not advise on building a sim, sorry. John

That installation log is from 7.0.4, a version of FSUIPC which is several years old.... FSUIPC does not send keys to other programs, only to MSFS. I have no idea how that worked in your former version - was that 7.0.4? Your ATC will pick up the keypresses sent if they are registered as hot keys by the ATC program - maybe it works that way. I can only check that FSUIPC is sending the key presses (to MSFS). To do this, activate logging for Buttons & Keys in FSUIPC7, and generate a log file showing your issue, i.e. load an aircraft and press the assigned buttons. Then exit FSUIPC7 and show me/attach your FSUIPC7.ini and FSUIPC7.log files. John P.S. I will look into this further and check sending key presses tomorrow. I can't access MSFS now or for the next few hours as I'm updating in another PC....

It is called Mobiflight Presets - although you can inky see the first few letters of the word Presets - I will look into widening the window. You should also read the installation guide: I would also recommend that anyone using presets should take a look at the WASM section of the Advanced User manual, as more details and an overview of how these work are given there. John

Do you have an events.txt file in your FSUIPC7 installation folder? It should be there if you checked to install this component in the installer (should be checked by default). Check your InstallFSUIPC7.log file as well (or post/attach it here) - if it was installed you should see the following lines: If the events.txt file is in your installation folder then I have no idea why it can't be read - if this is the case, please show me/attach your FSUIPC7.log file. John

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