Jump to content
The simFlight Network Forums

Elevator Trim Offset Control


Recommended Posts

I am trying to get the elevator trim to work as I want it to!  (FSX SE/Alabeo Aztec)    It is much too slow using the button assignment to a button on my Honeycomb yoke and I found a very old post which seems to offer a solution.  It was the same subject in June 2013 to/from a guy called John Fee.  I have followed his approach and as you can see below from the .ini file I have used the offset for the elev trim.

My problem is that if I reduce the increment (256) and then fly, nothing seems to change and on checking I find that the adjusted increment (eg 128) has disappeared and been replaced with 256.   Can you help?  Has something changed since 2013 - I know a lot of things have!

Thanks in anticipation, Pete.


[Buttons.Alabeo Aztec]
0=RA,10,C65607,0     -{ELEV_TRIM_DN}-
1=RA,12,C65615,0     -{ELEV_TRIM_UP}-
5=RA,14,C65607,0     -{ELEV_TRIM_DN}-
6=RA,15,C65615,0     -{ELEV_TRIM_UP}-
12=RA,1,C66243,0     -{INC_COWL_FLAPS}-
36=RA,13,C65615,0     -{ELEV_TRIM_UP}-
38=RA,0,C66244,0     -{DEC_COWL_FLAPS}-
48=PC,0,C66856,0     -{VIEW_CAMERA_SELECT_6}-
49=UC,0,C66851,0     -{VIEW_CAMERA_SELECT_1}-
52=PC,3,C65561,0     -{PAUSE_TOGGLE}-
53=PC,10,C66858,0     -{VIEW_CAMERA_SELECT_8}-
54=UC,10,C66851,0     -{VIEW_CAMERA_SELECT_1}-
58=PA,3,C65758,0     -{FLAPS_INCR}-
60=PA,4,C66079,0     -{GEAR_UP}-
61=PA,5,C66080,0     -{GEAR_DOWN}-
62=PA,2,C65759,0     -{FLAPS_DECR}-
63=RC,7,C66855,0     -{VIEW_CAMERA_SELECT_5}-
65=PC,6,C66857,0     -{VIEW_CAMERA_SELECT_7}-
66=PC,11,C66859,0     -{VIEW_CAMERA_SELECT_9}-
67=UC,11,C66851,0     -{VIEW_CAMERA_SELECT_1}-
72=PC,28,C66052,0     -{STROBES_ON}-
73=PC,29,C66053,0     -{STROBES_OFF}-
74=PA,6,C66416,0     -{PAN_VIEW}-
75=PC,20,C66239,0     -{TOGGLE_BEACON_LIGHTS}-
76=PC,21,C66239,0     -{TOGGLE_BEACON_LIGHTS}-
77=PC,22,C66059,0     -{LANDING_LIGHTS_ON}-
78=PC,23,C66060,0     -{LANDING_LIGHTS_OFF}-
79=PC,24,C66240,0     -{TOGGLE_TAXI_LIGHTS}-
80=PC,25,C66240,0     -{TOGGLE_TAXI_LIGHTS}-
81=PC,26,C66379,0     -{TOGGLE_NAV_LIGHTS}-
82=PC,27,C66379,0     -{TOGGLE_NAV_LIGHTS}-
83=PC,1,C66579,0     -{TOGGLE_CABIN_LIGHTS}-
84=RC,5,Cx42000BC0,xC0010100     -{offset sword decrement, offset 0BC0 (Decr=256, Limit=-16383)}-
85=RC,4,Cx32000BC0,x3FFF0100     -{offset sword increment, offset 0BC0 (Incr=256, Limit=16383)}-
86=PF,4,C66079,0     -{GEAR_UP}-
 

Link to comment
Share on other sites

2 hours ago, rojo2021 said:

My problem is that if I reduce the increment (256) and then fly, nothing seems to change and on checking I find that the adjusted increment (eg 128) has disappeared and been replaced with 256.   Can you help?  Has something changed since 2013 - I know a lot of things have!

How are you changing the increment/decrement delta value?

This is the assignment line for decrement:

2 hours ago, rojo2021 said:

84=RC,5,Cx42000BC0,xC0010100     -{offset sword decrement, offset 0BC0 (Decr=256, Limit=-16383)}-

The delta value is what I have highlighted (0100 hex = 256 decimal). The descriptive text is a comment - you cannot change the value there.
Really you should change in the assignments dialog, but you can also change the value in the ini if you like. However, it is confusing that you say the trim wheel action is too slow, but you want to reduce the delta from 256 to 128 which would make it twice as slow!! To speed it up, you need to increase the delta.

If using a buttons for trim, you can also try lua scripts which can distinguish between a short button ptess (for a small inc/dec) and a long button press (for a larger and repeated in/dec). There is a generic triple-use lua script for buttons that you can use (will obviously need modifying!) here: 

There is also the example Rotaries.lua that you can use, which is for single button rotaries (in each direction) which is the same as using two buttons, so you can adapt that for your needs. I recently adapted this for the Honeycomb Bravo, but you could also do something similar to use the buttons on your alpha in a similar way:

Yet another trick folks use is to duplicate (or triple.quadruple) there assignments, so it sends the same control 2, 3 or 4 times. This works ok for fast movement, and maybe ok for trim, but I woukd onkly do that if using double or truple use in the button, so a long press would result in duplicate large delta controls being sent, but a single press would result in just one smaller inc/dec being sent.
I am using the Bravo for trim. and here are my ini entries (FYI):

Quote

52=P64,6,Cx32000BC0,x3FFF007D     -{offset sword increment, offset 0BC0 (Incr=125, Limit=16383)}-
53=P64,7,Cx32000BC0,x3FFF00FA     -{offset sword increment, offset 0BC0 (Incr=250, Limit=16383)}-
54=P64,4,Cx42000BC0,xC001007D     -{offset sword decrement, offset 0BC0 (Decr=125, Limit=-16383)}-
55=P64,5,Cx42000BC0,xC00100FA     -{offset sword decrement, offset 0BC0 (Decr=250, Limit=-16383)}-
56=U64,7,Cx32000BC0,x3FFF00FA     -{offset sword increment, offset 0BC0 (Incr=250, Limit=16383)}-
57=U64,5,Cx42000BC0,xC00100FA     -{offset sword decrement, offset 0BC0 (Decr=250, Limit=-16383)}-

In those assignments, my two physical buttons for in/dec have been converted to 4 vurtual buttons, one for slow in, one for fast in, one for slow dec, and one for fast dec, and then my fast assignments have been duplicated (i.e. being sent on press and release in my case).

Hope that helps and isn't too confusing....
 

John

Link to comment
Share on other sites

Ah, it went so I'll try to repeat my previous message.

The original button assignment through FSUIIPC was too slow.  The offset was much faster and I have now slowed that thanks to your help.  Presumably I can now delete the entries in the .ini file for other elev trim lines without finding I've upset something else.

The idea of being able to tweak the trim setting by using a single press really appeals so I'm going to try to fathom that now.

Regards,

Roger

 

 

 

Link to comment
Share on other sites

1 hour ago, rojo2021 said:

Presumably I can now delete the entries in the .ini file for other elev trim lines without finding I've upset something else.

Yes - or you can remove them using the assignments UI panel, if they are single assignments to buttons.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • 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.