Jump to content
The simFlight Network Forums

GoFlight and the QW BAe-146 under P3DV2 = no love :(


Recommended Posts

Hi Pete anyone versed in the GoFlight key processing ... working with FSUIPC 4.927a (purchased version).

 

I've read the documentation and solicited help from fellow AVSIMers but I'm still not able to get my GoFlight buttons/switches to work with many of the controls.

 

This specific Aircraft it the Quality Wings BAe-146 ... I aimed a simple first test on a switch I know my GoFlight works with "Strobe Lights" ... my process:

 

1.  GFConfig, set switch to "no assignment"

2.  Load P3DV2

3.  Bring up FSUPIC

4.  Switches & Buttons tab

5.  Set "Specific Profile" and hit the button on my GF-P8 and FSUIPC registers it

6.  Select FS Controls checkbox

7.  Select "Strobe Light"

8.  Hit OK

9.  Unpause, and click button on GF-P8 and Strobe switch works

 

All good so far, so now I aim at Avionics 1 and Master 2 (these operate as a pair) switches.  The standard FS Control "Avionics Master" doesn't work, so I use the handy Logging feature and record to log the events that occur when I press the switch in VC.  It triggers 4 events Fuel_Selector_2_Set related events .... so I use the first event's code (think it was 65962 with param of 2) ... using "Custom Control" option, enter the value and then enter the param ... go to VC, get out of pause and test the GF-P8 button ... nothing.  So I try using the other 3 codes and parameters hoping on of them will work ... sadly none work.

 

So the next step was to try and use a Mouse Macro ... more reading and start the process of recording the mouse ... now according to information I've read I should see a green bar with FSUIPC message letting me know the button has been registered ... I click the button but never see this message.

 

So am I out of luck, is the QW BAe-146 200 just not going to support my GoFlight controls?  Or am I missing something?

 

Thanks, Rob

Link to comment
Share on other sites

All good so far, so now I aim at Avionics 1 and Master 2 (these operate as a pair) switches.  The standard FS Control "Avionics Master" doesn't work, so I use the handy Logging feature and record to log the events that occur when I press the switch in VC.  It triggers 4 events Fuel_Selector_2_Set related events .... so I use the first event's code (think it was 65962 with param of 2) ... using "Custom Control" option, enter the value and then enter the param ... go to VC, get out of pause and test the GF-P8 button ... nothing.  So I try using the other 3 codes and parameters hoping on of them will work ... sadly none work.

 

If FSUIPC logs the name of the control, then you can assign using that name in the drop down list! "Custom controls" are for unnamed controls added by aaircraft such as the PMDG 737NGX. You don't need to use "custom control" for 65962 -- see the FSX Offsets list in stalled in your FSUIPC Documents folder. You will see 65962 is "Fuel selector set".

 

I very much doubt that any aircraft would use "Fuel Selector Set" for "Avionics master". And if operating that switch sends 4 controls in sequence, then presumably you'd need to do the same thing -- which would need a macro or at least a sequence of assignments edited in the INI file. More likely that the add-on code ses the Avioics switch change and reads the fuel selector switches and sends them to FS at that time.

 

So the next step was to try and use a Mouse Macro ... more reading and start the process of recording the mouse ... now according to information I've read I should see a green bar with FSUIPC message letting me know the button has been registered ... I click the button but never see this message.

 

Mouse macros only work with add-on code gauges using the C/C++ gauge SDK issued by Microsoft. Unfortunately very few do these days, and even Microsoft didn't.  Most new add-on gauges use XML encoding, so Local panel variables (L:Vars) are more likely to be useful. FSUIPC can log those as well -- a list using the buil-in FS control or dynamically showing changes using a supplied Lua plug-in.

 

Did you first not check whether the add-on is supplied with keyboard shortcuts for these things?

 

So am I out of luck, is the QW BAe-146 200 just not going to support my GoFlight controls?  Or am I missing something?

 

It's nothing to do with whether it is GoFlight or any other joystick button or even keyboard you want to program. it's whether the add-on programmer has bothered to think about those who like to use hardware with their product. The laziest thing to do is simply write gauges without making any such provisions whatsoever.

 

Have you tried their support forum?

 

Regards

Pete

Link to comment
Share on other sites

If FSUIPC logs the name of the control, then you can assign using that name in the drop down list! "Custom controls" are for unnamed controls added by aaircraft such as the PMDG 737NGX. You don't need to use "custom control" for 65962 -- see the FSX Offsets list in stalled in your FSUIPC Documents folder. You will see 65962 is "Fuel selector set".

 

Yeah, tried that also, actually your FSUIPC is smart enough to realize the value is "Fuel Selector Set" as when I come back in again it shows that selection in the dropdown rather than 65962.  I did try sending the Avionics Master (via CF Config initially) but that didn't work ... set button to No assignment and then tried using FSUIPC to send the "Avionics Master" and still no go.

 

These are the event in the log from Avionics On and Avionics Off:

 

125862 *** EVENT: Cntrl= 65561 (0x00010019), Param= 0 (0x00000000) PAUSE_TOGGLE
   125955 KEYUP: VK=80, Waiting=0
   126782 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 2 (0x00000002) FUEL_SELECTOR_SET
   126782 *** EVENT: Cntrl= 66523 (0x000103db), Param= 2 (0x00000002) FUEL_SELECTOR_2_SET
   126782 *** EVENT: Cntrl= 66568 (0x00010408), Param= 3 (0x00000003) FUEL_SELECTOR_3_SET
   126782 *** EVENT: Cntrl= 66576 (0x00010410), Param= 3 (0x00000003) FUEL_SELECTOR_4_SET
   127780 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 2 (0x00000002) FUEL_SELECTOR_SET
   127780 *** EVENT: Cntrl= 66523 (0x000103db), Param= 2 (0x00000002) FUEL_SELECTOR_2_SET
   127780 *** EVENT: Cntrl= 66568 (0x00010408), Param= 3 (0x00000003) FUEL_SELECTOR_3_SET
   127780 *** EVENT: Cntrl= 66576 (0x00010410), Param= 3 (0x00000003) FUEL_SELECTOR_4_SET
   128779 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 2 (0x00000002) FUEL_SELECTOR_SET
   128779 *** EVENT: Cntrl= 66523 (0x000103db), Param= 2 (0x00000002) FUEL_SELECTOR_2_SET
   128779 *** EVENT: Cntrl= 66568 (0x00010408), Param= 3 (0x00000003) FUEL_SELECTOR_3_SET
   128779 *** EVENT: Cntrl= 66576 (0x00010410), Param= 3 (0x00000003) FUEL_SELECTOR_4_SET
   129793 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 2 (0x00000002) FUEL_SELECTOR_SET
   129793 *** EVENT: Cntrl= 66523 (0x000103db), Param= 2 (0x00000002) FUEL_SELECTOR_2_SET
   129793 *** EVENT: Cntrl= 66568 (0x00010408), Param= 3 (0x00000003) FUEL_SELECTOR_3_SET
   129793 *** EVENT: Cntrl= 66576 (0x00010410), Param= 3 (0x00000003) FUEL_SELECTOR_4_SET
   130791 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 2 (0x00000002) FUEL_SELECTOR_SET
   130791 *** EVENT: Cntrl= 66523 (0x000103db), Param= 2 (0x00000002) FUEL_SELECTOR_2_SET
   130791 *** EVENT: Cntrl= 66568 (0x00010408), Param= 3 (0x00000003) FUEL_SELECTOR_3_SET
   130791 *** EVENT: Cntrl= 66576 (0x00010410), Param= 3 (0x00000003) FUEL_SELECTOR_4_SET
   131790 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 2 (0x00000002) FUEL_SELECTOR_SET
   131790 *** EVENT: Cntrl= 66523 (0x000103db), Param= 2 (0x00000002) FUEL_SELECTOR_2_SET
   131790 *** EVENT: Cntrl= 66568 (0x00010408), Param= 3 (0x00000003) FUEL_SELECTOR_3_SET
   131790 *** EVENT: Cntrl= 66576 (0x00010410), Param= 3 (0x00000003) FUEL_SELECTOR_4_SET
   132788 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 2 (0x00000002) FUEL_SELECTOR_SET
   132788 *** EVENT: Cntrl= 66523 (0x000103db), Param= 2 (0x00000002) FUEL_SELECTOR_2_SET
   132788 *** EVENT: Cntrl= 66568 (0x00010408), Param= 3 (0x00000003) FUEL_SELECTOR_3_SET
   132788 *** EVENT: Cntrl= 66576 (0x00010410), Param= 3 (0x00000003) FUEL_SELECTOR_4_SET
   133334 *** EVENT: Cntrl= 66293 (0x000102f5), Param= 0 (0x00000000) TOGGLE_AVIONICS_MASTER
   133802 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 2 (0x00000002) FUEL_SELECTOR_SET
   133802 *** EVENT: Cntrl= 66523 (0x000103db), Param= 2 (0x00000002) FUEL_SELECTOR_2_SET
   133802 *** EVENT: Cntrl= 66568 (0x00010408), Param= 3 (0x00000003) FUEL_SELECTOR_3_SET
   133802 *** EVENT: Cntrl= 66576 (0x00010410), Param= 3 (0x00000003) FUEL_SELECTOR_4_SET
   134800 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 2 (0x00000002) FUEL_SELECTOR_SET
   134800 *** EVENT: Cntrl= 66523 (0x000103db), Param= 2 (0x00000002) FUEL_SELECTOR_2_SET
   134800 *** EVENT: Cntrl= 66568 (0x00010408), Param= 3 (0x00000003) FUEL_SELECTOR_3_SET
   134800 *** EVENT: Cntrl= 66576 (0x00010410), Param= 3 (0x00000003) FUEL_SELECTOR_4_SET
   135799 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 2 (0x00000002) FUEL_SELECTOR_SET
   135799 *** EVENT: Cntrl= 66523 (0x000103db), Param= 2 (0x00000002) FUEL_SELECTOR_2_SET
   135799 *** EVENT: Cntrl= 66568 (0x00010408), Param= 3 (0x00000003) FUEL_SELECTOR_3_SET
   135799 *** EVENT: Cntrl= 66576 (0x00010410), Param= 3 (0x00000003) FUEL_SELECTOR_4_SET
   136345 *** EVENT: Cntrl= 66293 (0x000102f5), Param= 0 (0x00000000) TOGGLE_AVIONICS_MASTER
   136797 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 2 (0x00000002) FUEL_SELECTOR_SET
   136797 *** EVENT: Cntrl= 66523 (0x000103db), Param= 2 (0x00000002) FUEL_SELECTOR_2_SET
   136797 *** EVENT: Cntrl= 66568 (0x00010408), Param= 3 (0x00000003) FUEL_SELECTOR_3_SET
   136797 *** EVENT: Cntrl= 66576 (0x00010410), Param= 3 (0x00000003) FUEL_SELECTOR_4_SET
   137811 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 2 (0x00000002) FUEL_SELECTOR_SET
   137811 *** EVENT: Cntrl= 66523 (0x000103db), Param= 2 (0x00000002) FUEL_SELECTOR_2_SET
   137811 *** EVENT: Cntrl= 66568 (0x00010408), Param= 3 (0x00000003) FUEL_SELECTOR_3_SET
   137811 *** EVENT: Cntrl= 66576 (0x00010410), Param= 3 (0x00000003) FUEL_SELECTOR_4_SET
   138810 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 2 (0x00000002) FUEL_SELECTOR_SET
   138810 *** EVENT: Cntrl= 66523 (0x000103db), Param= 2 (0x00000002) FUEL_SELECTOR_2_SET
   138810 *** EVENT: Cntrl= 66568 (0x00010408), Param= 3 (0x00000003) FUEL_SELECTOR_3_SET
   138810 *** EVENT: Cntrl= 66576 (0x00010410), Param= 3 (0x00000003) FUEL_SELECTOR_4_SET
   139808 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 2 (0x00000002) FUEL_SELECTOR_SET
   139808 *** EVENT: Cntrl= 66523 (0x000103db), Param= 2 (0x00000002) FUEL_SELECTOR_2_SET
   139808 *** EVENT: Cntrl= 66568 (0x00010408), Param= 3 (0x00000003) FUEL_SELECTOR_3_SET
   139808 *** EVENT: Cntrl= 66576 (0x00010410), Param= 3 (0x00000003) FUEL_SELECTOR_4_SET
   140775 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 2 (0x00000002) FUEL_SELECTOR_SET
   140775 *** EVENT: Cntrl= 66523 (0x000103db), Param= 2 (0x00000002) FUEL_SELECTOR_2_SET
   140775 *** EVENT: Cntrl= 66568 (0x00010408), Param= 3 (0x00000003) FUEL_SELECTOR_3_SET
   140775 *** EVENT: Cntrl= 66576 (0x00010410), Param= 3 (0x00000003) FUEL_SELECTOR_4_SET
   149574 LogOptions changed, now 00000000 00000001
 
These are the supported Keypresses for the QW BAe-146 per documentation:
 
KEY_TOGGLE_AFTERBURNER1 LNAV Button Press
KEY_TOGGLE_AFTERBURNER2 VNAV Button Press
KEY_TOGGLE_AFTERBURNER3 TCAS Knob (1 left mouse click, 2 right mouse click)
KEY_TOGGLE_PADLOCK EFIS control panel APT button press
KEY_UNLOCK_TARGET EFIS control panel NAV button press
KEY_TOGGLE_DAMAGE_TEXT EFIS control panel GRP button press
KEY_TOGGLE_ENEMY_INDICATOR EFIS control panel Map Range Increase
KEY_STOP_PRIMARY_GUNS EFIS control panel Map Range Decrease
KEY_BAIL_OUT EFIS control panel Format Increase (left click)
KEY_LETTERBOX EFIS control panel Format Decrease (right click)
 
I just checked the Log to see if my "programmed" GF-P8 sends and it's the same as the above (when I mouse click the switch) ... so what appears to be happening is that the setting is being made, but the switch is NOT being reflected/updated to show that the event happened (I do make sure I'm not Paused everytime).  On the QW BAe-146-200 I've notice this behavior on a few of the other switches ... for example Landing Light switch does actually turn the landing lights on/off but it's visual switch position is NOT being reflected on the overhead panel.
 
Thoughts?
 
Thanks, Rob.
Link to comment
Share on other sites

These are the event in the log from Avionics On and Avionics Off:

 

Looks to me as if the fuel selector controls are being sent automatically in any case, at regular intervals. Presumably their code is doing that each time it scans its switch settings. Annoying. I wish folks would only send controls when they actually need to change something. It's just another overhead.

 

I just checked the Log to see if my "programmed" GF-P8 sends and it's the same as the above (when I mouse click the switch) ... so what appears to be happening is that the setting is being made, but the switch is NOT being reflected/updated to show that the event happened (I do make sure I'm not Paused everytime).  On the QW BAe-146-200 I've notice this behavior on a few of the other switches ... for example Landing Light switch does actually turn the landing lights on/off but it's visual switch position is NOT being reflected on the overhead panel.

 
Not good programming then. Unlees there's a local panel variable (L:Var) you can use to operate the visible switch I'm afraid you'll have to put up with it, or change to a better aircraft.
 
Regards
Pete
Link to comment
Share on other sites

Appreciate your responses Pete, I've brought this up with Lars/QW support forum and see if he/they have any suggestions ... but from what I've gathered, their v1.4 update is final for this aircraft.  Some switches do work (panel is updated) like the Strobe light, others do not like Landing Lights (lights go on, but switch isn't updated on panel).

 

Cheers, Rob.

Link to comment
Share on other sites

This turned out to be my fault ... mouse macro's are working VERY well with this Aircraft.  I didn't realize I needed to use the 2D panels (just for macro) to make it happen -- only need them to setup the macro, once setup I'm back to VC.  VC is working very well now and I'd like to thank you for providing such a wonderful tool in FSUIPC.  Finally I can enjoy my GoFlight modules in just about any aircraft supporting 2D panels.

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.