These are the Support Forums for FSUIPC and related products.

These forums replace the old support forums which have been running for 20+ years. The old forums contain a wealth of information on all FSUIPC products, but are now no longer available.

Please note that you will need to Register and Login to post for support, and also to download attachments. You can view these forums without registering.

Support is also available via Discord. Please use the following invite link to join the FSUIPC Discord server:
https://discord.gg/zjwUTrxmmE

G3X events issue - ...
 
Notifications
Clear all

[Solved] G3X events issue - FSUIPC 7.5.7 ; MSFS2020

Posts: 3
Registered
Topic starter
(@_robert)
Joined: 1 week ago

Hello,
I'm writing because I need help with something that's been bugging me. It's about events assignment. I am trying to set up my T.Flight Hotas X for the stock NXCub aircraft in MSFS2020. Since MSFS2020 does not natively support the built-in G3X, I decided to try FSUIPC7, which I am running in the latest version.

The problem is that the assigned event does not take effect, even though the console correctly outputs the event, which is bizarre. The output below is for the "Buttons & Keys" and "Input Events" logs. The first line displays the action when I press the "menu" button on the G3X with my mouse. The rest of the lines are the results of hitting the HOTAS button I assigned for this event.

Console Started ...

  1395359 InputEvent received: AS3X_Touch_1_Menu=0.000000 (param='Unknown')
  1399562 Button changed: bRef=0, Joy=0 (A), Btn=12, Pressed
  1399562 [Buttons.Asobo NXCub] 3=PA,12,CIAS3X_Touch_1_Menu,0.000000
  1399562 Executing InputEvent 'AS3X_Touch_1_Menu' [3] with parameter 0.000000
  1399578 InputEvent received: AS3X_Touch_1_Menu=0.000000 (param='Unknown')
  1399656 Button changed: bRef=0, Joy=0 (A), Btn=12, Released

The G3X reacts as expected when I click using the mouse and displays the relevant menu. However, when I press the HOTAS button, nothing happens.

Please find my config and joy event files attached to this post.

I'm unsure about the "[JoyNames]" stanza in the configuration because it displays the same GUID twice. However, this might be due to my use of the entire X kit, which includes T.Flight HOTAS and rudder pedals.

This might be something I simply overlooked but I would appreciate some assistance in troubleshooting this issue. Could someone please guide me and provide me with the necessary steps?

I am on the steam version of MSFS2020 and Windows 11 25H2


5 Replies
Posts: 296
Moderator
(@fsuipc-support)
Joined: 8 months ago

Posted by: @_robert

I'm unsure about the "[JoyNames]" stanza in the configuration because it displays the same GUID twice.

It is shown once with with joy id assigned, and a second time with the joyletter - this is how it works when using the joyletter facilities (which are on my default in FSUIPC7) - see the User guide for details.

For the G3X, you should use the provided presets (which use Hvars) rather than the input events. These can be found under Microsoft->Generic->Avionics (after selecting for presets and clicking 'Find Preset...') and all the presets for the G3X are preceded by the sting 'AS3'. For the menu button, you can use the preset AS3X_Touch_1_Menu_Push.

 

Reply
Posts: 296
Moderator
(@fsuipc-support)
Joined: 8 months ago

Here is a screenshot of the available presets for the G3X (from the MobiFlight HubHop site) - all MF presets are available for assignment in FSUIPC7:


Reply
Posts: 3
Registered
Topic starter
(@_robert)
Joined: 1 week ago

Hi,

I have gone through the user guide and the advanced user guide more carefully, so things are clearer now. Regarding the main issue, I misled myself by looking at the input events when I should  check the HTML vars in the first place. The event name I was looking for, which ends with *_PUSH, makes a difference. Thank you so much for pointing that out to me. Everything works using presets removed link I should prioritise using (L/H)Vars over pre-defined input events — lesson learned.

Everything works. I have just tested the rest of the events, so the problem has been solved.

Thank you. I appreciate your help.


Reply
Posts: 296
Moderator
(@fsuipc-support)
Joined: 8 months ago

Posted by: @_robert

I should prioritise using (L/H)Vars over pre-defined input events — lesson learned.

Not necessarily, and certainly not for more modern aircraft (or MSFS2024 aircraft) which quite often use Input Events. Generally it is always a good idea to look for presets first, and if one exists you can look at the associated calculator code to see what it is using, and either use the preset directly or what the calc code indicates (e.g. it could be just sending a standard FS control, setting an lvar or triggering a hvar). If no preset exists, I would then check for both lvars and input events to see if any looked applicable and then try/test them. HTML vars can be quite difficult to discover, as you can only find them by examining the aircraft behavior (using the debugging tools provided in the MSFS dev mode) - or looking at preset calc. code.

In MSFS2024, you can also trigger/access Input Events as B-type variables in calculator code (presets), but not in MSFS2020. In MSFS2020, you can only use the Input Events directly and not via calc.code RPN.

Also, the community support on the MF HubHop site are very supportive for this kind of thing - if no MF preset yet exists to control a specific button/switch/etc in an aircraft, you can ask about this on the MF Discord server (in MSFS2020 channel, or MSFS2024 channel for that version) and usually someone will have the aircraft and be able to help.

Cheers,

John


Reply
Page 1 / 2