FSUIPC7, Goflight modules not active for Buttons and Switches assignment

[John Dowson]

21 minutes ago, DJJose said:

Example Mooney: gear goes up when I initially bring the gear up. To bring the gear back down, I first put the gear down, then back up, then back down. 

Is that an add-on? I didn't think there was a Mooney included with any version of MSFS. Maybe try a default aircraft. I can't really help with add-on aircraft (that I don't have!).

[DJJose]

10 minutes ago, John Dowson said:

Is that an add-on? I didn't think there was a Mooney included with any version of MSFS. Maybe try a default aircraft. I can't really help with add-on aircraft (that I don't have!).

Yes it is.

I'll try your suggestions and post results.

Best regards.

[John Dowson]

Ok. You can also try offset 0x0BE8 - Gear Handle Position (4 Bytes), writing 16383 for down and 0 for up.

[cburnier]

On 9/11/2020 at 9:25 PM, lonewulf47 said:

I found out that the original GoFlight ESP driver "GFDevESP.exe" works with MFS..

I have found the file and run it,Nothing happens, What do you mean by works with MFS. How do you config your units. Can you provide some more information and L will try it again. Thank you for your help.

Charles

 

[John Dowson]

7 minutes ago, cburnier said:

How do you config your units. Can you provide some more information and L will try it again. Thank you for your help.

I don't use or have this, so maybe someone else can help you with that. But, I assume its an earlier version of the GFDevP3Dv4.exe, to which Pete commented:

Quote

 

It's GoFlight's own driver, and has its own assignments etc. It works completely independently of FSUIPC. The GoFlight facilities in FSUIPC have always been just a more flexible alternative to GoFlight's own provisions, but FSUIPC doesn't handle the displays or LEDs on some Goflight units without using the provisions for GoFlight units in the Lua libraries.

The GoFlight EXE shouldn't be used if FSUIPC's facilities are being used instead.

 

So if you use that, you shouldn't use the GFDev64.dll, which is the one you need if you want to use FSUIPC with your device.

[cburnier]

John,

Thanks for your message,

I cannot deal with the complexities of LUA programming. It is too complex for me unless I find a working example of my units (GFMCPPro, GFMCP, GF46, RP48).

Oskar had mentioned in a message dated SEptember 11, that GFDdevESP.exe works with MSFS and I was looking for this alternative.

Charles

[DJJose]

2 hours ago, cburnier said:

John,

Thanks for your message,

I cannot deal with the complexities of LUA programming. It is too complex for me unless I find a working example of my units (GFMCPPro, GFMCP, GF46, RP48).

Oskar had mentioned in a message dated SEptember 11, that GFDdevESP.exe works with MSFS and I was looking for this alternative.

Charles

GoFlight is currently closed due to COVID-19. Let's hope that they update the software when they get back to work.

For now if anyone has any info on how to get the GoFlight modules to work with FSUIPC/GFDdevESP.exe, I'd appreciate some guidance.

For now all I care about is my throttle and LGT. Throttle already works. LGT is next.

[DJJose]

5 hours ago, John Dowson said:

Its probably sending a press on the up, and a release on the down. Try adding the Gear Down control on the release, under 'Control Sent when button released'.

John,

This worked. I now have a properly working gear handle.

I'm not able to get the elevator trim to speed up a little. I tried setting it up as an AXIS, but FSUIPC does not pick it up.

"Did you try the checkbox 'control to repeat while held' in the buttons/switches assignment dialog?"

I tried the above suggestion but if I try to trim up it continues and it will not stop. Any suggestions?

 

[John Dowson]

12 hours ago, DJJose said:

I tried setting it up as an AXIS, but FSUIPC does not pick it up.

What do you mean by this? FSUIPC7 does not recognise an axis on one of your devices?

12 hours ago, DJJose said:

I tried the above suggestion but if I try to trim up it continues and it will not stop. Any suggestions?

Are you assigning to a switch or 'sticky' button? If it continues, then its not receiving a release event. You can check what events your buttons/switches are sending by logging 'Buttons & Switches'.

[DJJose]

47 minutes ago, John Dowson said:

What do you mean by this? FSUIPC7 does not recognise an axis on one of your devices?

YES! It does not recognize the Elevator trim on the GoFlight LGT as an axis.

As I tried to explain, and please forgive me if I did not do a good job, the way that the trim is being recognized is only as 2 buttons wheel up & 2 buttons wheel down.

The way I set it up: The two buttons for wheel up are set to "trim down." The two buttons for wheel down are set to "trim up." Sent to FSUIPC.

It works, but the elevator trim wheel in the airplane barely moves. I'd like to see it move a little more when I move the GoFlight trim wheel.

[John Dowson]

8 minutes ago, DJJose said:

YES! It does not recognize the Elevator trim on the GoFlight LGT as an axis.

As I tried to explain, and please forgive me if I did not do a good job, the way that the trim is being recognized is only as 2 buttons wheel up & 2 buttons wheel down.

Ah, ok. So one up button should be for fast trim down and one to slow trim down, and similarly for the down buttons gpr trim up. Can you check if/when the trim wheel "button" are sending release codes (by activating 'logging for 'Buttons & Switches').

You could try assigning the first up-button (on trim wheel),  to "trim down" on press only. For the second up-button, assign to "trim down" on press and release. And similarly for the down buttons.

[DJJose]

1 hour ago, John Dowson said:

Ah, ok. So one up button should be for fast trim down and one to slow trim down, and similarly for the down buttons gpr trim up. Can you check if/when the trim wheel "button" are sending release codes (by activating 'logging for 'Buttons & Switches').

You could try assigning the first up-button (on trim wheel),  to "trim down" on press only. For the second up-button, assign to "trim down" on press and release. And similarly for the down buttons.

I'm having trouble figuring this suggestion:

Please explain.

[DJJose]

Here's my .ini

[Sounds]
Device1=Primary Sound Driver
Device2=Speakers (Creative SB X-Fi)
Device3=SPDIF Out (Creative SB X-Fi)

[General]
UpdatedByVersion=7000b
UseSystemTime=No
JoystickTimeout=20
DisconnTrimForAP=No
ZeroElevForAPAlt=No
ThrottleSyncAll=No
ShowPMcontrols=No
SpoilerIncrement=512
MagicBattery=No
RudderSpikeRemoval=No
ElevatorSpikeRemoval=No
AileronSpikeRemoval=No
ReversedElevatorTrim=No
ClockSync=No
ClockSyncMins=5
ClearWeatherDynamics=No
PauseAfterCrash=No
BrakeReleaseThreshold=75
SaveDataWithFlights=No
UseProfiles=Yes
WideLuaGlobals=Yes
InvokeFSUIPCOptionsKey=70,12
AxesWrongRange=No
TCASid=Flight
TCASrange=40,3
AxisCalibration=No
DirectAxesToCalibs=No
AxisIntercepts=No
DontResetAxes=No
ThreadAffinityMask=x0
LuaAffinityMask=x0
LogOptionProtect=Yes
AutoConnectToSim=Yes
AutoExitWithSim=Yes
TimeForLuaClosing=2
WeatherReadFactor=2
WeatherRewriteSeconds=1
TrafficStallTime=1
InitialStallTime=10
NormalStallTime=1
LuaRerunDelay=66
ComReadLoopTime=20
Window=182,182,682,282
Console=No
ConsoleWindowTopMost=No
ConsoleWindow=26,26,1019,545

[JoyNames]
0=GoFlight GF-TQ6 Throttle System
0.GUID={392AC620-DFE9-11EA-8001-444553540000}
1=4-axis, 4-button joystick w/view finder
1.GUID={392D1010-DFE9-11EA-800D-444553540000}
2=4-axis, 4-button joystick
2.GUID={392D1010-DFE9-11EA-800E-444553540000}
A=GoFlight GF-TQ6 Throttle System
A.GUID={392AC620-DFE9-11EA-8001-444553540000}
B=4-axis, 4-button joystick w/view finder
B.GUID={392D1010-DFE9-11EA-800D-444553540000}
C=4-axis, 4-button joystick
C.GUID={392D1010-DFE9-11EA-800E-444553540000}

[JoystickCalibration]
RudderBlendLowest=1
AllowSuppressForPFCquad=Yes
ExcludeThrottleSet=Yes
ExcludeMixtureSet=Yes
ExcludePropPitchSet=Yes
SepRevsJetsOnly=No
ApplyHeloTrim=No
UseAxisControlsForNRZ=No
FlapsSetControl=0
FlapDetents=No
ReverserControl=66292
Reverser1Control=66422
Reverser2Control=66425
Reverser3Control=66428
Reverser4Control=66431
MaxThrottleForReverser=256
AileronTrimControl=66731
RudderTrimControl=66732
CowlFlaps1Control=66162
CowlFlaps2Control=66163
CowlFlaps3Control=66164
CowlFlaps4Control=66165
SteeringTillerControl=0
MaxSteerSpeed=60
MapThrottle=Yes
Aileron=-16380,512,936,16380
SlopeAileron=10
Elevator=-16380,0,512,16380
SlopeElevator=15
Rudder=-15018,-512,512,16042
SlopeRudder=15

[Axes]
PollInterval=10
RangeRepeatRate=10
0=AR,256,D,6,0,0,0    -{ DIRECT: Mixture }-
1=AU,256,D,4,0,0,0    -{ DIRECT: Throttle }-
2=AV,256,D,5,0,0,0    -{ DIRECT: PropPitch }-
3=BX,256,D,1,0,0,0    -{ DIRECT: Aileron }-
4=BY,256,D,2,0,0,0    -{ DIRECT: Elevator }-
5=CR,256,D,3,0,0,0    -{ DIRECT: Rudder }-

[Buttons]
PollInterval=25
ButtonRepeat=20,10
1=P165,2,C65759,0     -{FLAPS_DECR}-
2=P165,1,C65758,0     -{FLAPS_INCR}-
6=R165,0,C66079,0     -{GEAR_UP}-
8=P165,4,C0,0     -{Custom control: <0>}-
9=PC,3,C65721,0     -{BRAKES_RIGHT}-
10=PC,2,C65720,0     -{BRAKES_LEFT}-
11=U165,0,C66080,0     -{GEAR_DOWN}-
13=P165,5,C65607,0     -{ELEV_TRIM_DN}-
14=P165,6,C65615,0     -{ELEV_TRIM_UP}-

[AutoSave]
Next=1
Interval=60
Files=10
SaveOnGround=No
AutoSaveEnabled=No

[GPSout]
GPSoutEnabled=No

[GPSout2]
GPSoutEnabled=No

[WideServer]
WideFSenabled=Yes

[Profile.c172]
1=Cessna Skyhawk Asobo

 

[DJJose]

2 hours ago, John Dowson said:

You could try assigning the first up-button (on trim wheel),  to "trim down" on press only. For the second up-button, assign to "trim down" on press and release. And similarly for the down buttons.

I figured out what you meant, but no luck. Very little movement. The only time I get the trim to move is when I check the "control repeat while held." There has to be a combo that works.

[DJJose]

For now I've settled on this:

The trim turns in the right direction and it stops properly. Slow as hell, but good enough for now.

Thanks for all your help.

[John Dowson]

21 minutes ago, DJJose said:

I figured out what you meant

Ok, good - as you image showed you were selecting for a key assignment, and you need to set 'Select for FS control'.

Doing what I said, don't you get faster movement for the second  (i.e. when assigned on press and release) button?

25 minutes ago, DJJose said:

The only time I get the trim to move is when I check the "control repeat while held."

Did you try logging the press/release events of these buttons? Repeat should work, but as it is continually repeating it seems that the device isn't sending a button release code. This is why I asked you to activate logging to see what your buttons are emitting.

It is difficult for me to advise when I don't have such a device and I cannot tell how its configured and what press/release codes it is emitting.

Also, as its a GF device, do you have the additional GF software running? Does this not let you assign and configure the trim wheel? Or are you just using the GFdev64.64.dll?

If you cannot get the movement you require via standard assignments, maybe you should look into using lua scripts. You can do something based upon the scripts in this post (although they are originally for Saitek trim wheels , but if using buttons to control trim,  it shouldn't make a difference) - but you only want the button functions, and can remove the axes ones (and make sure that you update the joystick and button numbers used to match those of your device): 

 

You can also use that as a basis to write a script to control with 2 buttons for slow up/fast up & slow down/fast down.

 

 

[John Dowson]

2 minutes ago, DJJose said:

For now I've settled on this:

Your images show one button - Joystick#165 button#5 - assigned in the first image to Elevator trim down on press and release, and in the second image to Elevator trim up on press and release. I don't understand how this can work, sorry.

You said that FSUIPC recognised to buttons for up, and two for down. As I said, you should assign the first button (in each direction) to only send the control on the press, and the second (furthest) button to send on press and release.

I really cannot advise any further as I still have no idea what codes your trim wheel buttons are sending.

[DJJose]

1 hour ago, John Dowson said:

Your images show one button - Joystick#165 button#5 - assigned in the first image to Elevator trim down on press and release, and in the second image to Elevator trim up on press and release. I don't understand how this can work, sorry.

You said that FSUIPC recognised to buttons for up, and two for down. As I said, you should assign the first button (in each direction) to only send the control on the press, and the second (furthest) button to send on press and release.

I really cannot advise any further as I still have no idea what codes your trim wheel buttons are sending.

Hi John,

I'm very sorry that I forgot to activate logging. I'll do that and provide any log you need.

I'm using your GFdev64.64.dll because the GoFlight software is not compatible with MSFS 2020. Works great in P3D v4.5.

This is the reason why I decided to try FSUIPC because I'd love to have a working GoFlight LGT in MSFS. I'm so glad that I decided to try FSUIPC. My controllers are working much better and I can use the LGT's Gear & flaps. Trim is the only thing that needs tweaking.

I'll play with the trim and post the log ASAP.

BTW button #6 is the bottom pic. I was just trying different things. I have no idea what will work. There are 2 buttons that show up when you move the wheel up and 2 buttons when you move the wheel down.

Let me enable logging and get back to you.

[John Dowson]

27 minutes ago, DJJose said:

BTW button #6 is the bottom pic.

Ah, ok - difficult tot tell in those images, especially with my eyesight (and as I lost my glasses yeterday, falling into a river while walking the dogs!).

29 minutes ago, DJJose said:

There are 2 buttons that show up when you move the wheel up and 2 buttons when you move the wheel down.

Yes, one should be activated with a small movement and the other with a large movement. For the small movement button, you should assign just to the press, and for the larger movement to the press and release. Well, that was what I was trying to get you to try, to see if that helps.

30 minutes ago, DJJose said:

Let me enable logging and get back to you.

Ok. Would be useful to know if/when its sending button releases. You can also look at the log when you have repeat enabled.

Really, you just need to experiment to see what works for you. If you cannot get it working reasonably with direct assignments, you will have to look into using lua scripts to control instead.

[DJJose]

I enable button logging and set up buttons as you suggested:

[Buttons]
PollInterval=25
ButtonRepeat=20,10
1=P165,2,C65759,0     -{FLAPS_DECR}-
2=P165,1,C65758,0     -{FLAPS_INCR}-
6=R165,0,C66079,0     -{GEAR_UP}-
9=PC,3,C65721,0     -{BRAKES_RIGHT}-
10=PC,2,C65720,0     -{BRAKES_LEFT}-
11=U165,0,C66080,0     -{GEAR_DOWN}-
20=U165,5,C0,0     -{Custom control: <0>}-
21=P165,5,C65607,0     -{ELEV_TRIM_DN}-
22=U165,4,C65607,0     -{ELEV_TRIM_DN}-
23=P165,6,C65615,0     -{ELEV_TRIM_UP}-
24=U165,7,C65615,0     -{ELEV_TRIM_UP}-

I don't think I did it right because it's still slow or the wheel barely moves.

FSUIPC7.log

[John Dowson]

8 minutes ago, DJJose said:

I don't think I did it right because it's still slow or the wheel barely moves.

No, doesn't look right as each button number is different - I was expecting to see both a press and a release on one button assigned to trim dwn, and the same for trim up on another button. However, lookin at the log of button presses/releases, they don't make much sense:

Quote

  ... 
   929875 Button changed: bRef=0, Joy=165, Btn=6, Pressed
   929906 Button changed: bRef=0, Joy=165, Btn=7, Released
   929922 Button changed: bRef=0, Joy=165, Btn=7, Pressed
   930203 Button changed: bRef=0, Joy=165, Btn=6, Released
   930234 Button changed: bRef=0, Joy=165, Btn=7, Released
   930266 Button changed: bRef=0, Joy=165, Btn=7, Pressed
   930297 Button changed: bRef=0, Joy=165, Btn=7, Released
   930328 Button changed: bRef=0, Joy=165, Btn=7, Pressed
   930547 Button changed: bRef=0, Joy=165, Btn=6, Pressed
   930563 Button changed: bRef=0, Joy=165, Btn=7, Released
   930594 Button changed: bRef=0, Joy=165, Btn=7, Pressed
   930625 Button changed: bRef=0, Joy=165, Btn=4, Released
   930672 Button changed: bRef=0, Joy=165, Btn=7, Released
   930844 Button changed: bRef=0, Joy=165, Btn=6, Released
   930859 Button changed: bRef=0, Joy=165, Btn=7, Pressed
   930891 Button changed: bRef=0, Joy=165, Btn=7, Released
   930922 Button changed: bRef=0, Joy=165, Btn=7, Pressed
   930938 Button changed: bRef=0, Joy=165, Btn=7, Released
   930984 Button changed: bRef=0, Joy=165, Btn=7, Pressed
   934000 Button changed: bRef=0, Joy=165, Btn=6, Pressed
   ...

It doesn't surprise me that you had problems stopping the movement when you had repeat on, as you would have to position the trim so that all the 'buttons' on it had triggered a 'release' without any outstanding presses. Looking at the log, thats a difficult position to find!

Assuming 7 is the topmost button, and 4 the lowest, you could add the following (in bold):

21=P165,5,C65607,0     -{ELEV_TRIM_DN}-
22=U165,4,C65607,0     -{ELEV_TRIM_DN}-
23=P165,6,C65615,0     -{ELEV_TRIM_UP}-
24=U165,7,C65615,0     -{ELEV_TRIM_UP}-
25=P165,7,C65615,0     -{ELEV_TRIM_UP}-
26=P165,4,C65607,0     -{ELEV_TRIM_DN}-

This just sends a second control when the buttons are pressed, so should speed things up a bit but I wouldn't expect too much. You can try varying the button numbers (e.g. change one or both of the 7 and 4 to 5 and/or 6), and change the press P to a release U. Ideally you could add these via the UI, as I suggested.

Other than that, you would have to try lua.

[DJJose]

Thanks a million.

5 hours ago, John Dowson said:

No, doesn't look right as each button number is different - I was expecting to see both a press and a release on one button assigned to trim dwn, and the same for trim up on another button. However, lookin at the log of button presses/releases, they don't make much sense:

It doesn't surprise me that you had problems stopping the movement when you had repeat on, as you would have to position the trim so that all the 'buttons' on it had triggered a 'release' without any outstanding presses. Looking at the log, thats a difficult position to find!

Assuming 7 is the topmost button, and 4 the lowest, you could add the following (in bold):

21=P165,5,C65607,0     -{ELEV_TRIM_DN}-
22=U165,4,C65607,0     -{ELEV_TRIM_DN}-
23=P165,6,C65615,0     -{ELEV_TRIM_UP}-
24=U165,7,C65615,0     -{ELEV_TRIM_UP}-
25=P165,7,C65615,0     -{ELEV_TRIM_UP}-
26=P165,4,C65607,0     -{ELEV_TRIM_DN}-

This just sends a second control when the buttons are pressed, so should speed things up a bit but I wouldn't expect too much. You can try varying the button numbers (e.g. change one or both of the 7 and 4 to 5 and/or 6), and change the press P to a release U. Ideally you could add these via the UI, as I suggested.

Other than that, you would have to try lua.

Thanks a million.

Jose

[John Dowson]

14 hours ago, DJJose said:

20=U165,5,C0,0     -{Custom control: <0>}-

Just noticed this....strange. Not sure how this happened - you should remove this line (if its still there).

Did this improve things?

 

[John Dowson]

There are also a couple of other things you can try. If you look in the FSUIPC User Guide, there is a section called 'Offset Increment/Decrement Controls' (around p27) which actually uses elevator trim as an example.

There is also an example lua script provided (in the FSUIPC example lua plugins) which convert the rotary buttons triggered into virtual buttons, toggling one for a slow movement and another for a fast movement. Using this, combined with the offset increment/decrement controls, you could set the slow virtual button to increment/decrement by 64 (say), and the fast by 256 - just vary the numbers until you get the fast/slow speed that suits you.

[DJJose]

2 hours ago, John Dowson said:

Just noticed this....strange. Not sure how this happened - you should remove this line (if its still there).

Did this improve things?

 

Done!

1 hour ago, John Dowson said:

There are also a couple of other things you can try. If you look in the FSUIPC User Guide, there is a section called 'Offset Increment/Decrement Controls' (around p27) which actually uses elevator trim as an example.

There is also an example lua script provided (in the FSUIPC example lua plugins) which convert the rotary buttons triggered into virtual buttons, toggling one for a slow movement and another for a fast movement. Using this, combined with the offset increment/decrement controls, you could set the slow virtual button to increment/decrement by 64 (say), and the fast by 256 - just vary the numbers until you get the fast/slow speed that suits you.

Phenomenal. Thank you!