John Dowson

The 1.8.15.0 update released yesterday also contains the following in the release notes: Aligned pressure altitude simvar and pitot static altitude calculations to prevent wrong altitude information for external Live ATC services ... Known issue In-sim ATC service radar can still report incorrect altitude (fix expected in World Update 6)

I think this is a know issue after the SU5 update - see https://forums.flightsimulator.com/t/altimeter-problems-altitude-hold-and-atc-altitude/433209 https://forums.flightsimulator.com/t/help-with-incorrect-high-altitude-altimeter-setting/429439/4 And from that second link: From the Asobo post about the hotfix: ATC Incorrect Altitude – The pressure altitude has been brought in line with the new altimeter simulation and ATC should no longer ask you to get to your current altitude if you’re already there. This is addressed in the hotfix. Further improvements to the altimeter and ambient pressure system will be coming in World Update 6. John

If you assigned in FSUIPC7, then thy should not have been "lost" as they are independent of MSFS updates. So I think something else must be going on. If you are not using the latest version, v7.2.6, then please update and try again. If it still fails or already using that version, show me your FSUIPC7.log and FSUIPC7.ini files.

To assign multiple actions to a button, whatever the action (e.g. controls, macro actions, lua scripts, etc) you have to comment out the currently assigned action by editing your FSUIPC .ini file. Find the assignment line in the .ini file (in an editor such as Notepad++), and place a semi-colon character after the index number of the assignment and save the file. Then, in the FSUIPC buttons assignment dialog, click the 'reload all buttons' button. This will reload the edited ini and remove the assignment, allowing you to add the second assignment. You can save (i.e. click Ok) and repeat as many times as you like to add multiple assignments. When done, edit the .ini file again and remove the semi-colons previously added and save the file. Then reload the update .ini once more from the button assignments panel, and you will now have multiple assignments to that button. You will only see the first assignment in the UI, and this will be grayed-out and un-editable. To make any further changes to multiple assignments, you have to manually edit the .ini file. John

I have moved your post to the main support forum as it will attract more attention there. The User Contributions sub-forum is intended as a place to access such scripts, and isn't really the place for such requests.

No problem, glad its all sorted/understood. John

Yes...! Good, I'm glad - happy flying, John

That depends on how you start it. If you double click the FSUIPC7.exe, that will just start FSUIPC7 and nor MSFS. If you opted to install the auto-start component, then FSUIPC7 will be started by MSFS when that is started. If you opted to install the desktop link, that starts MSFS, not FSUIPC7. When started, FSUIPC7 resides in the system tray, not the task bar. You can use the default hot-key Alt + F to show/hide the main window. Please see the provided documentation, especially the Installation guide and the user manual (installed under your Windows Documents folder, in a folder called FSUIPC7). John

Strange, don't know what happened....! You don't seem to be using any of the registered facilities of FSUIPC7. You are using the FBW A320 events (file) but are not actually using it for anything. And you don't have the FSUIPC7 WASM module installed, although you have the WAPI activated for some reason. Not that it matters... Btw, your [General] settings could do with updating. I suggest that you delete everything under the [General] section of your FSUIPC7.ini and let that get re-generated. Also, the log file you attached wasn't complete - you started a continuation log. Best not to do or use this function for generating log files for support, as I need to see the complete/full log file. Just for future reference. John

Hi Frank, do you have your assignments in MobiFlight or in FSUIPC? If the former, then you should ask on the MobiFlight Discord forum (https://discord.com/channels/608690978081210392/749561155424354374) and/or the FBW discord forum (https://discord.com/channels/738864299392630914/750095266937438258). They may know more if there are issues with MF/FBW after the update. If you are assigning in FSUIPC, are you using the MF events or the FSUIPC7 WASM module, or maybe a combination of both? Either way, I would need to see your FSUIPC7.ini and FSUIPC7.log. If using lvars or hvars, also check that they are still available as I have had reports of lvars not being loaded until the a/c is started, although they seem ok to me in the few stock and add-on aircraft that I have tried since the update. I don't use MF or FBW myself, but have it installed on my development system to look into issues on using this with FSUIPC7. I haven't updated to v9 yet - I'll do this next week and take a look. Until then, please report back if you find anything. Cheers, John

No problem. Attached is an example lua script using the wnd library. John FPS_MonitorW.lua Note that when using the wnd library, the position and size information is only used the first time it is ran. The information is then written to the FSUIPC7.ini, where it will be taken on subsequent iterations. You can move and resize the wnd windows dtnamically using the arrow keys and arrow keys + shift or Ctrl (can't remember which!), and the new size/position will also be remembered.

This has been reported many many times now, and my answer is always the same.... If MSFS crashes, it is a problem with MSFS that mist be reported to Asobo. FSUIPC7 is an executable, a separate process to the FS. If FSUIPC7 crashes, it should not affect MSFS. What is more likely happening is that MSFS is crashing, which then causes a fault in FSUIPC7 (as the SimConnect connection is no longer available). FSUIPC7 detects this (and a windows event is raised) butt then exits gracefully. You can verify this by checking your FSUIPC7.log file - it should show that GSUIPC7 has exited gracefully as MSFS us no longer detected. If it doesn't, then please show it to me. Another way to verify this is to start FSUIPC7 manually before the MSFS, and deselect the option 'Exit with FS'. Doing this, when you start MSFS you will get an error (which you can acknowledge and ignore) sating that FSUIPC7 is already running if/when it tries to auto-start FSUIPC7. But when MSFS CTDs, FSUIPC7 will disconnect and keep running. Therefore, please verify that it is MSFS that is crashing, and if so, please check the Asobo forums and/or report to Asobo via zendesk. John Later... Btw, also check the event log for an MSFS crash event before the FSUIPC7 fault event. This should be sent to Asobo, together with the crash report/dump if one is available.

But there has been problems with ipc.display since MSFS launch, so I'm surprised it was working at all for you! As stated in the FSUIPC Lua library documentation: Just checked the SDK documentation on the SimConnect_Text function in the latest SDK version, v0.14.0.0, and it now states: So I don't think there is anything I can do. You should look into using the wnd library, as the documentation recommends. John

Yes, yesterday. I'll post a new one in a couple of days.

Quite a few people seem to be having this issue. If a single left-click doesn't download, you can always right-click and select Save as... That should work. Glad your registration issue is sorted. No idea what the issue could have been there, sorry. John

Here and me! There are so many similar support requests on this now, and - to be honest, I am getting pretty fed-up of responding to those that keep posting for this and have not bothered to read the manual. So, have you read the 'Installing and Registering FSUIPC7.pdf', section Invalid Key Problems? If not, please do that, and follow the instructions provided. If that does not solve your issue, please let me know your order number and I will verify your details here. John

Did you get to the bottom of this issue? Did you check the logs of your acars programs? You FSUIPC7.log file looks ok, although you could change your stall settings in your FSUIPC7.ini as you did have a data stall issue (but not important). Btw, 7.2.6 was also released this morning so please update to that version.

Just checked and it is working here. However, it is extremely slow. If you hold your button(s) down (to send the control repeatedly), then you should see the elevator pitch trim indicator move. If you want larger trim increments/decrements (deltas) for each button press/release, you can assign to the trim offset 0x0BC0 using the offset sword increment/decrement controls, and give the inc/dec delta that works for you. Alternatively, if you have a spare axis, you can assign to the Axis Elevator Trim Set control. You can also duplicate your assignment lines (remembering to change the index number) to have (say) 10 controls sent upon each button press (by duplicating 10 times) and release (if you also assign the control to be sent on release as well). John

Please attach it next time - its a lot easier and there is nothing in there that can't be public. Ok, but this makes no difference to how FSUIPC behaves, only how it is started by P3D. But what I need to see is your log, with the appropriate logging activated (as asked). Can you please attach that (not via PM please!). John PS. I'll also check the trim on the Mooney here....

What error message? Do you have an FSUIPC7.log file? If so, please show it to me. If its a windows error message, see the README.txt provided. Note that there is also an issue with lvar/hvar access in v7.2.5, there is an updated version available from the following link (that I will release shortly):

No change in ipc.display(), but there is an issue with lvar/hvar access in that version. There is an updated version here (that I will release officially shorty):

@LeoSchoonbroodt Please try the attached version: FSUIPC7.exe Seems ok, but I'll do more tests and release officially tomorrow. John

Yes, I have just noticed this after updating on my flight system. Mot sure what happened...I am looking into it now... Sorry about this. John

Those assignments have everything assigned to buttons 3 and 2. Your images show buttons 8 and 9 (with the same control for each). Just do as the OP suggests, and change the button numbers to the ones you want to use, e.g. change the 2 to 8 for engine 1, and the 3 for 9 for engine 2. You should also manually remove any original assignments you have to those buttons numbers as they will be no longer needed. Note also that the FSUIPC assignments window will only show one assignment if you have multiple, and will be grayed out so it cannot be changed. You can only update by manually editing the ini - and once you do this, click the 'Reload all buttons button to reload the modified ini file. John

How is your trim assigned? Can you activate logging for buttons, Events and maybe also Axes controls, load the Mooney Bravo and then try to adjust the trim, then close down P3D and show me your FSUIPC6.log and FSUIPC6.ini files. I'm surprised at this though - could it be that the buttons that you use are outside of the 32 button limit (in FSUIPC5) and you are using lua toggle a virtual button instead? If that is the case, you will either need to re-assign your trim buttons, or add the following to the [General] section of your FSUIPC6.ini file to revert to the old 32-button limit behavior: EnableExtraButtons=No No - by doing that you will be using the default P3D assignments, which will also mean that all your other axes/buttons will/could also be assigned in P3D, which would give you dual assignments. Best to still leave controllers turned off in P3D if using FSUIPC for your assignments. John