Jump to content
The simFlight Network Forums

Tools to help assigning buttons & switches


FIN_FLY

Recommended Posts

Hello,

Just purchased your great FSUIPC7 for MSFS and I'm very new to the application.

I'm working on A32nx and creating sort of DIY home cockpit. Axis assignment was easy and no problems there.

Buttons are bit more difficult for me. Some of them are easy e.g.  Altitude Inc./Dec.

But EFIS Mode and Range selectors are not. Is there a way to monitor what kind of command mouse wheel operations send to MSFS and then duplicate them via FSUIPC? Or is there an other way or possibility?

Thanks in advance

Link to comment
Share on other sites

3 hours ago, FIN_FLY said:

But EFIS Mode and Range selectors are not. Is there a way to monitor what kind of command mouse wheel operations send to MSFS and then duplicate them via FSUIPC? Or is there an other way or possibility?

The usual way to find out if there are any controls/events assignable is to activate logging of non-axis events. You can then see what events are being used when you activate the UI control, and use the same event when you program your button or switch.

However, there are currently many reasons why this may not work:
    - some functions may be performed internally by the guage software. If this is the case, you won't see any events.
      In previous FS versions, such functionality could be handled by using lvars (local variables), if provided. Currently in MSFS/FSUIPC7 there is no access to such variables

   - some events that are triggered by activating controls in the UI have no affect when sending them via SimConnect. This is a known issue for many events (e.g. view and slew controls)

   - some controls work in some aircraft but not others. The airliners seem to suffer from this the most, especially the A320Neo. This is probably due to the fact that they model more of the systems than relying on the internal models.

There are various tricks, tips and mods around, especially for the A320Neo it seems. Try searching the forums (here and the msfs/asobo ones).

3 hours ago, FIN_FLY said:

Is there a way to monitor what kind of command mouse wheel operations send to MSFS and then duplicate them via FSUIPC?

Duplicating mouse wheel operations (to program functions not available via SimConnect or using lvars) was a feature of previous versions of FSUIPC (i.e. in v4, 5 and 6). However, the functionality to implement this is currently not available in the MSFS SDK. We will look into adding this back once the functionality is available in the SDK.

Please remember that even though MSFS is now released, the SimConnect SDK (which is what third party products rely on to communicate to the FS) is still at version 0.7.1.
Things should improve as the SDK develops.

John

Link to comment
Share on other sites

18 hours ago, FIN_FLY said:

But EFIS Mode and Range selectors are not.

As well as what John said, it should be noted that in the previous incarnations of Flight Sim (and in P3D) the EFIS controls are local and specific to the gauge module displaying the results (eg the PFD and ND). Such local implementation is not usually subject to an external control offerings and the controls only react to mouse clicks.

In the other Sims supported by versions of FSUIPC the solution has been either using "mouse macros" (programming a button to act like the mouse clicks needed), or L:Vars (Local Panel Variables). Unfortunately as yet such actions are not possible in MSFS -- they are subject to requests made to MS/Asobo.

Pete

 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.