Target update problem

[hsth]

Hi,

 

This is a question about the update from version RC_22_10_2010 to RC_2_12_11_2010.

I've already raised this point with the Thrustmaster support but they reckon all works as it should. So I'm wondering if anybody has noticed the same behaviour or that it's just on my system. I don't have another system to test with.

I'm using the Warthog in combination with FC2. In my script I have the following code to control the flaps:

MapKey(&Throttle, FLAPU, PULSE[color=#ffffff]+[/color]Flaps_Up);                                     [color=#32cd32]//Flaps Up [/color]
MapKeyR(&Throttle, FLAPU, PULSE[color=#ffffff]+[/color]Flaps_Up_Down);
MapKey(&Throttle, FLAPM, [color=#ffffff]0[/color]);
MapKey(&Throttle, FLAPD, PULSE[color=#ffffff]+[/color]Flaps_Landing_Position);                     [color=#32cd32]//Flaps Landing[/color]
MapKeyR(&Throttle, FLAPD, PULSE[color=#ffffff]+[/color]Flaps_Up_Down);

 

When I test this in de Event Tester I get the expected commands in both TARGET versions.

With version RC_22_10_2010 this is also true in FC2.

But, with version RC_2_12_11_2010 it changes. Then the switch from Flaps Up to Flaps Down suddenly acts as on/off in FC2.

 

This is best seen by putting the plane on the runway as starting position. Then you can see clearly how the flaps react.

 

Using the keyboard isn't a problem at all, all fine.

 

Can someone please point me in the right direction? I've run out off ideas.:(

[Teej]

I don't have any MapKeyR commands.

 

Try this:

 

MapKey(&Throttle, FLAPU, PULSE+Flaps_Up);

MapKey(&Throttle, FLAPM, PULSE+Flaps_Up_Down);

MapKey(&Throttle, FLAPD, PULSE+Flaps_Landing_Position);

[hsth]

@Teej,

 

Sorry it took me while to come back. In the meantime I have re-installed Windows 7 from a clean system image and then re-installed all the latest Thrustmaster software & drivers.

The flaps work perfect now.

 

Don't know why :( but am pleased it's solved.:)

 

Thanks for your help.