John Dowson

Are those the files from when you go through the procedure? I want to see them when wideserver is already enabled and you start P3D and load an aircraft and be ready-to-fly. After that, wait a minute or so and then exit. Your log file is quite strange as it shows no devices: and there is no log line indicating that everything has been started, such as the following: Nothing will connect until that is logged. Maybe also try re-installing the P3D client - this has been known to get corrupted on occasion and can give strange issues when this occurs. John

Ok - then please show me the WideServer.log file when you get the issue and WideServer is enabled at start-up. Especially now that OneDrive is installed and difficult to remove, even if not used. Ok - put your first WideClient.log has this: which implies that the protocol was not set. It is difficult to tell your actual set-up for each test - always better to include all 5 files (FSUIPC6.log, WideServer.log, FSUIPC6.ini, WideClient.ini, WideClient.log) from each run, generated at the same time and after everything has been stopped (i.e. at the end of the test run). Ok... I get such issues with WideServer/WideClient connections every other week, and these seem to appear and then go away at random. There has been no change in the WideClient/WideServer code for many years, and such issues are extremely difficult to diagnose,,, and usually go away for no reason that I can find, as they appear,,, John

I don't understand this at all - this can in no way be related to that version (only one line of code commented out in the key sending code)...something else must be going on with that test. Did you install 7.3.19 first? Can you please try again to see if this happens again...

What has changed in this timeframe (or just before), if anything? As you are using UDP on the server, you could try specifying this in the clients by adding Protocol=UDP to the [Config] section of your WideClient.ini files. This is strange...I may look into this but we will see.... Ok, so it works when disabled and you enable. What happens on the next run - does it come back to the initial issue (WideClients not connecting, no 'Waiting for...' message in the FS window)? Not finding a WideServer.log file is very strange...and it is difficult to diagnose issues without this file. The FSUIPC.log file does show that WideServer is started, but it is not clear from which test scenario this is from - and it is also not complete, i.e. FSUIPC seemed to be running when this was attached (no close). One thing that does strike me as slightly dodgy is your FSUIPC6 installation location - you have installed under the windows Documents folder. It is always better to choose a non-windows protected folder (e.g. C:\FSUIPC6 or C:\Prepar3D Add-ons\FSUIPC6) as windows seems to be changing access rights on windows-defined folders. So I suggest you first re-install FSUIPC6 into a different non-windows protected folder - you can skip registration and copy across your FSUIPC6.key and FSUIPC6.ini files, together with any other files you may use (e.g. *.lua, *.mcro, *.dll) from your old installation location to the new one. The Documents\Prepar3D v5 Add-ons\FSUIPC6\ folder should just be used for your add-on.xml file that allows the FSUIPC6.dll to be loaded when P3D is started. John

Can you try the attached version please. In this, I have allowed passthrough of key presses sent to MSFS and then received back. This should solve your issue, but I am not 100% convinced that this will be the final solution. I need to do some more testing on this, but would confirm the issue if you could test and report back. To use, re-install the 7.3.19 version, and then use the attached exe (7.3.20a) to replace the one installed. Thanks. FSUIPC7.exe

Ok, now this makes more sense. The older version is setting the HotKey when the keypress sent on the button press is received back: In a later version, I ignore key presses sent as this can cause issues in certain situations with keys being sent and received in an eternal loop. I must admit, I forgot about HotKeys in this situation - and am surprised that this hasn't been reported before. I will look into this and post an updated version for you to test in the next few days (hopefully!). Using the appropriate controls assigned on button press and button release. This should be straightforward if you look at the UI - and read the User guide if its not obvious... But no point in doing this anyway, as the issue is that the HotKey that is registered is not being set. As I said, I will look into this and post an update for you to test, John

👍

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