John Dowson

Hi André, I don't think this is currently possible as there are no assignable controls/events for this. However, this is already on the 'wishlist': https://forums.flightsimulator.com/t/mappable-controls-to-toggle-labels-aircraft-airport-poi-etc/153732 A zendesk issue has also been raised: https://forums.flightsimulator.com/t/suggestion-keyboard-shortcut-to-toggle-traffic-labels/116033/3 I also though i'd seen a mod that implements this a while back on the MSFS forums, but couldn't find this with a quick search....

I'm not that familiar with the c# library, but I doubt it very much. I think lvar access is a lot simpler via lua, and you would probably have to implement your own 'event' type mechanism. But check the documentation, or you can ask in the client dll for .net sub-forum: https://forum.simflight.com/forum/167-fsuipc-client-dll-for-net/

Sorry, but I can't support ProSim, especially v1. @Pete Dowsonuses ProSim, so maybe he can advise...

Looks like you are running from a fresh install (i.e. no FSUIPC7.ini) as the ini you posted is completely empty. As the ini shows that you do not have 'event' logging activated - please activate that if you want to see the events logged. If you have previously configured FSUIPC7, you need to copy the latest FSUIPC7.exe file to the folder that you previously used to install/run FSUIPC7. Or, alternatively, copy your previous FSUIPC7.ini file to the new folder for FSUIPC7. FSUIPC7 uses the FSUIPC7.ini file (containing all your assignments and logging configuration) located in the same folder as the FSUIPC7.exe file that you are running.

Presume that you mean the initial call of the function, but no, this cannot be prevented. However, you can handle in your function by returning straight away if its on the first/initial call. You can determine this by using a global variable, and checking/changing the initial value in the function, exiting if it is the first call. For most use cases, this initial call is needed to initialise/sync the offset value in the script with the actual offset value.

Is that the "Events" category from the FSUIPC Log menu? No. To activate SimConnect logging, create a file called SimConnect.ini in the FLT UNC Path (or FLT Path), as reported at the beginning of your FSUIPC7.log file (for Steam installs this will be C:\Users\<YourName>\AppData\Roaming\Microsoft Flight Simulator\, and for MS Store installs, this maybe under the LocalCache folder) with the following contents: replacing <path> with the path specification (e.g. file=C:\SimConnect%01u.log).

The SDK contains the following sim variables related to the bus, but nothing for the tie switch (unless its maybe the bus connection): BUS BREAKER PULLED TODO UNITS_BOOL TYPE_BOOL BUS CONNECTION ON TODO UNITS_BOOL TYPE_BOOL BUS LOOKUP INDEX Asobo (bpelmoine) Should be deleted once simvars support multi paramters UNITS_NUMBER TYPE_UINT32 EXTERNAL POWER CONNECTION ON Boolean, The state of the connection between a bus and an external power source UNITS_BOOL TYPE_BOOL If its not the bus connection, think you would need to submit a feature request for an additional event to allow this switch to be controlled.

These buttons don't log any events and there doesn't seem to be anything to control these either in the MSFS assignments or in the SDK events/variable lists, so I don't think this is currently possible. I can raise a zendesk issue/feature request, asking for events to control these be added to the SDK.

This has been fixed in the latest update. The problem was that FSUIPC7 was keeping the UserOpt.cfg file open after reading, preventing it from being updated. @Thomas Richter spotted this - thanks! John

You could try activating SimConnect logging, to see if anything is reported when the crash occurs. other than that, you should raise a zendesk issue with MSFS/Asobo, and include the windows crash report from the event viewer. If you want to test with a fresh ini, you could let FSUIPC7 generate a fresh/clean one, and then copy/replace all sections apart from the [General] section, and also remove the Path variable from the [Sounds] section, together with your missing yoke in the [JoyNames] section:

If the problem is with the client programs that use FSUIPC7, you really need to talk to their support. Do you have any issues with FSUIPC7 when not running those clients? If the previous version was with a build date of 26/09, then there were very few changes between the versions, the main one being the change to simconnect 0.6.0.0. Also, if it was a problem with FSUIPC7 and LINDA or ACARS, I would have thought it would affect many other users.

The latest documents should already be included in your FSUIPC installation. For FSUIPC4 & 5, this will be in your FSUIPC Documents folder, under your Modules folder. For FSUIPC6, you need to select the documentation during installation, and it is installed in a folder called FSUIPC6 under you windows Documents folder. You don't need this. FSUIPC has its own lua interpreter. There are various documents included with FSUIPC on the lua interface provided. However, for an introduction to lua or its standard libraries, please google.

Hi Marc, so MSFS is crashing, but why do you think this is related to FSUIPC? With FSUIPC now being an exe rather than a dll, it should not crash the sim. Even if its a problem in the server side of simconnect, it is still an issue with MSFS. There will be nothing in your ini that would cause this. You can try disabling the option 'Exit with FS', and FSUIPC7 will then still be running once MSFS has a CTD.

Yes, I'm not changing the version number at the moment, just the build date. This should be in the properties, as well as logged in the first lines of the log file.

You can see if its assignable in MSFS. If so, you can assign it to a keypress there, and then assign your switch to the keypress. If you do find something, let me know and I'll see if there's an available simvar or event that I can add. I'll also check the documentation to see if I can see anything that resembles this...

The "latest" release is always the only one available, and available from the same place. I suggest you follow the announcement page, where I comment when a new release is available (last release was 20 mins ago):

To control the eyepoint, I assign a hat switch to 'Select for Keypress' and then to Up, Down, Left, Right (i.e. numpad 8,2,4,6 with numlock off) on repeat, and that seems to work for me. For quick view, I assign the same keys but with a ctrl modifier (to a different hat switch!), and this also gives me quick-view functionality. John

But what version of FSUIPC6? If you are not using the latest (v6.0.10) can you please update and retry. There was an update for a bug in event.key that was fixed in that version. For support requests, either specify the exact version you are using or, better still, attach you log file so I can see what version you have + other information that is useful to me in helping you.

Can you please let me know what sim and what version of FSUIPC you are using (or show me your FSUIPC log file) Ok, so different from your original post....! You are saying that your script worked, but when you added the extra event.key call + function then it stopped working - correct? Does your aftertakeoff() function get called when you press the '191' key? Is you loop function still getting called by the timer? Have you tried activating logging for lua plugins?

Btw, is your lua even running? i.e. are you starting in somehow (e.g on a button press) or have you added it to your [Auto] section?

What sim and version of FSUIPC are you using? You could try activating key press logging, to see what VK keycode is logged when you press your key. Key code 191 is Numpad 7 (with NUMLOCK ON) according to the manual, BUT these keys vary from keyboard to keyboard. On my keyboard, Numpad 7 with NUMLOCK ON is vk=103. So it previously worked? What has changed? Maybe your NUMLOCK is OFF?

@EdwardSm Please try as Thomas suggested and use an installation folder for FSUIPC7 outside of the MSFS folders and report back, thanks.

This question has been asked many times before - please check the forums before posting such questions, e.g. etc

What crashes - MSFS or FSUIPC7? As I said, if its MSFS, you need to report to Asobo. If its FSUIPC7, I need more information - you FSUIPC7.log for a start, and also any crash entry in the Windows event viewer. But multi-player and AI traffic type are different settings. You can have aircraft traffic type set to AI Offline or Real-time Online (or Off), and also multiplayer data set to on/off independently So, are you saying MSFS crashes or FSUIPC7 crashes, and is this when you have aircraft traffic type set to Real-time Online AND multiplayer data set to on only? Sorry, but I need more information as I don't understand what the problem is or what you are requesting.

I have a steam installation, and I've tested this and experience the same - my settings aren't saved if I close and restart with FSUIPC7 still running. Very strange. There is nothing in FSUIPC7 that could prevent this - its only a SimConnect client as far as MSFS is concerned. I'll do some more tests and maybe report to Asobo.