Strange issue with FSX:SE and 'Elevator Trim Set'

[ZarahNeander]

So I registered FSUIPC and tried the example from the user manual: Zero trim aka 'Elevator Trim Set 0'.

 

What's happening:

 

1) change trim by any means (doesn't matter)

2) press the zero key --> works

3) repeat Step 1

4) repeat Step 2 --> doesn't work

 

Then I programmed a stick button to do the same thing and now it's gets really wierd..

 

In step 4 the stick button works, so key/button works, key/key doesnt

 

The reverse is also true: button/button -> non luck, button/key -> works

 

I'm completely lost and would appreciate any help

 

kind regards...Pia Kraft

[Pete Dowson]

Sounds like you have two different things interacting.

First, make sure you are testing with a default aircraft, and that you have nothing also happening in FS.

Try using FSUIPC's event logging to see exactly what controls and parameters are being sent.

Pete

[ZarahNeander]

Thank you for the prompt reply.

 

I did log and FSUIPC sends the event just fine...

 

Only vanilla aircraft and nothing's going on..no ap..just starting position with engines turned off..no other simconnect processes running. Unplugged my stick, doesn't help

 

I have the nagging feeling that might be a SE problem.

 

Edit: in fact none of the 'set' events int the 'control surfaces' category work more than once. Others do though, i.e AP_ALT_VAR_SET_METRIC works, AILERON_TRIM_SET only works once

Edited January 11, 2015 by ZarahNeander

[Pete Dowson]

Thank you for the prompt reply.

 

I did log and FSUIPC sends the event just fine...

 

Only vanilla aircraft and nothing's going on..no ap..just starting position with engines turned off..no other simconnect processes running. Unplugged my stick, doesn't help

 

I have the nagging feeling that might be a SE problem.

 

Edit: in fact none of the 'set' events int the 'control surfaces' category work more than once. Others do though, i.e AP_ALT_VAR_SET_METRIC works, AILERON_TRIM_SET only works once

 

 

Ah, I know what is going on. The "... SET" commands are all treated as axis inputs, although FSUIPC (not FS) allows you to assign them to anything.

 

FSX and FSUIPC alike only take note of CHANGES in axes. The INC/DEC controls you assign to buttons are different, obviously. The change is not whether the axis is different to what the current value is but whether the axis has been moved. If you want a button to zero trim and you aren't using a trim axis for trimming, then you'd need to send two values, one non-zero and then one zero. You can do that on a button by assigning one to "press" and the other to "release", or editing the INI file and entering more than one assignment. It might be better to have a two line macro instead, then you can assign to button or key easily.

 

Pete

[ZarahNeander]

Wow...it works

 

thank you so much and well..outstanding support

 

Pia Kraft

[ZarahNeander]

....It might be better to have a two line macro instead, then you can assign to button or key easily.

 

Pete

 

It's a rough ride:)

I can't get macros to work. I created a file A.mcro

 

[Macros]
1=Blub
1.1=C65706,64
1.2=C65706,0

and the file appears in the MacroFiles section of the ini file. But that's it. I assumed that something like 'A Blub' shows up in the drop-down menus (the documention claims it does) but no dice.

 

Again I must be missing something obvious...*sigh*

 

Thanks in advance..Pia Kraft

[Pete Dowson]

 

It's a rough ride:)

I can't get macros to work. I created a file A.mcro

 

[Macros]
1=Blub
1.1=C65706,64
1.2=C65706,0

and the file appears in the MacroFiles section of the ini file. But that's it. I assumed that something like 'A Blub' shows up in the drop-down menus (the documention claims it does) but no dice.

 

Again I must be missing something obvious...*sigh*

 

Thanks in advance..Pia Kraft

 

Yes, it most certainly should do -- but if you've created the file whilst FS is running you'd need to press the "reload" button on the relevant assignments tab. Otherwise the list isn't regenerated.

 

It will appear as "A:Blub" in alphabetic ordering in the normal FS controls assignments, in all lists -- Buttons & Switches, Key Presses, and Axis Assignment. I've just done exactly that with your macro.

 

Where are you looking?

 

Pete

[ZarahNeander]

Turns out Notepad++ was set to UTF-8 encoding. Converting to ANSI did the trick.

 

Thanks again!

[seiermax]

Just an addititonal remark (I just fiddled around with the same problem): If you want to center rudder, aileron and elevator trim by a keystroke with FSUIPC4 (I have the Acceleration Pack, not the Steam Edition, but thats probably not the issue), and if you dont want to go into Macro programming:

 

-

 

 

[seiermax]

OOPS - my contribution was posted befoer I was ready - sorry for that: So again

 

1) Under the KeyPresses register set a key combination (e.g. Tab+Ö)

2) Select as contol sent when keys pressed: "Aileron Trim Set" (or Elevator/Rudder Trim Set)

3) Add as parameter for the key press some small value, e.g. 1

4) Select the same control as in step 2) (i.e. "Aileron Trim Set") also for the control sent when main key released

5) Set the parameter for the main key release: 0 (i.e. center the trim)

6) Confirm the selection of this key combination as usual.

 

Now if you want to center the trim, you just press and release button combination. When you release it, your trim will be centered, and thats what you probably want to happen. Theoretically there is a little notch in the trim when pressing the key combination but you wont notice that.

 

It works stable, also when you repeat it several times. Whether you change the trim by a joystick button or with the mouse doesnt matter. I checked it with the standard FSX Beech Baron 58 for elevator, rudder and aileron trim with the latest FSUIPC4 version 4.938f.

 

Thaths how it looks like in the .ini-file:

[Keys]
2=192,24,65706,1,65706,0
4=222,24,66731,1,66731,0
6=191,24,66732,1,66732,0

 

(P.S.: Dont bother with the 192, 222 and 191 keys, they are those "Kraut" umlaut-keys Ä, Ö and the # on my German keyboard)

 

Maybe that helps someone who comes up with the same problem