Collective is NOT staying inverted...

[Alphamale]

on my throttle. I have Saitek X52 and when I start a mission, it's ok for awhile, but when I go past either the top detent for what should be idle, or the bottom detent which should be full collective power, the stick reverses these to go back to a regular fixed wing plane throttle. Therefore I have to pull totally back on the throttle to land. I have set the Z Axis to invert and saved the profile but as I said it keeps switching back. I don't like flying a helo like this. What is causing this? TIA,

 

AM

[USSR_Rik]

[i suggest, you know about "real" and "game" modes in CONTROLS]

 

1. Do you use Saitek profiler? If yes - please, unload it and try once again.

 

2. "and saved the profile" - how do you saved profile? Please, step by step.

 

3. Set your Saitek Throttle in the middle position, start simulation. Move throttle at approx. 1/5 of full scale forward and back (i.e. not to full forward or full back position) - will the collective axis invert? Check also collective moving using RCtrl+ENTER.

[Feuerfalke]

I'd first check the stick and throttle with the SAITEK Control Panel. See if the throttle has the same behavior there.

 

If not, go to the options-screen ingame and make sure you don't have 2 axes set to throttle. If you have rudders connected as well, it might be that one of the toebrakes is mapped to the throtte, too. Since always the latest input will be used, the toebrake-input might simply override the throttle input.

[PeterP]

Hello- Something similar happened also to me few times in my beginning -

I have a Hotas Cougar and I discovered that it was caused by a faulty calibration of my throttle axis.

That means that when I pushed it full forward it showed up as jumping back to the beginning of the axis in the windows properties.

A new calibration solved it . And it only happened at the last tiny 1% of the axis.

 

At a point I was sick of doing the recalibration each time and I set a small dead zone to the ends of the throttle band - and I had the problem never again.

 

Maybe you have the same with your X52 (probably inaccurate measurement in the end of the axis in the potentiometer)

Check your controller properties in windows - and try a recalibration.

Also try to set a very smal deadzone in BlackShark.

 

Maybe that helps.

Edited May 4, 2009 by PeterP

[Alphamale]

[i suggest, you know about "real" and "game" modes in CONTROLS]

 

1. Do you use Saitek profiler? If yes - please, unload it and try once again.

 

2. "and saved the profile" - how do you saved profile? Please, step by step.

 

3. Set your Saitek Throttle in the middle position, start simulation. Move throttle at approx. 1/5 of full scale forward and back (i.e. not to full forward or full back position) - will the collective axis invert? Check also collective moving using RCtrl+ENTER.

 

Okay:

 

1. Yes, I have the Saitek Profiler software installed, but I never use it. That is, I never load profiles from it.

 

2.I'm talking about saving the key assignments that I make with BS options screen. The key mappings can be saved as a .lua file.

 

3. I will try your suggestion when I get home. But it would seem that If I do that, I will not get the full range of power from the engines even if that does work.

[Alphamale]

Hello- Something similar happened also to me few times in my beginning -

I have a Hotas Cougar and I discovered that it was caused by a faulty calibration of my throttle axis.

That means that when I pushed it full forward it showed up as jumping back to the beginning of the axis in the windows properties.

A new calibration solved it . And it only happened at the last tiny 1% of the axis.

 

At a point I was sick of doing the recalibration each time and I set a small dead zone to the ends of the throttle band - and I had the problem never again.

 

Maybe you have the same with your X52 (probably inaccurate measurement in the end of the axis in the potentiometer)

Check your controller properties in windows - and try a recalibration.

Also try to set a very smal deadzone in BlackShark.

 

Maybe that helps.

 

The X52 is not calibrated within Windows. It is calibrated by its own software interface, at least that's my take on it. In windows, during calibration, I would always be asked to move the input device to its range limits and then center it and then push a button on the device to confirm calibration. The control panel the X52 uses, never asks for that or even gives you a hint that the stick has been calibrated. Sure you get a visual feedback of the device moving through its ranges, but that's all.

 

Next, if the throttle stick has an inaccurate pot at the extreme ends of the range, why would setting a dead zone in the middle help that? I mean the deadzones that I've seen within the BS game are only set in the middle of the range, unless you're referring to the User Curve. But again, wouldn't this then limit my in-game power range?

[USSR_Rik]

2.I'm talking about saving the key assignments that I make with BS options screen. The key mappings can be saved as a .lua file.

There are two ways to save profile: 1. pressing OK in CONTROLS window saves profiles of all devices and 2. pressing "SAVE PROFILE AS" saves only current device profile. BTW, I know at least one case, when user (after assigning of buttuns and axis) just closed CONTROLS window by pressing small cross :) in right-upper window corner

 

3. I will try your suggestion when I get home. But it would seem that If I do that, I will not get the full range of power from the engines even if that does work.

Yes, but this procedure will show the moment of axis reverting back - or they revert in the first small moving, or it is necessary to move throttle full.

 

Please, check also advice of Feuerfalke - "make sure you don't have 2 axes set to throttle"

[PeterP]

Next, if the throttle stick has an inaccurate pot at the extreme ends of the range, why would setting a dead zone in the middle help that? I mean the deadzones that I've seen within the BS game are only set in the middle of the range, unless you're referring to the User Curve. But again, wouldn't this then limit my in-game power range?

 

 

When you set the band as "slider" in the options you are able to set deadzones at the end of the band and not in the middle.

 

As I said - I have a Cougar and I'm not fully aware how the X52 works.

But this helped me with my problem tha the stick"Inverts the input".

Edited May 4, 2009 by PeterP

[Alphamale]

OK I GOT IT!!!

 

Here was the problem. I first started this in Simulation mode to get to learn the controls and panels and see how my stick setup responded to realistic flight. Under Sim mode I had inverted the Z axis as required. Recently I've been playing around in Game mode. What I didn't realize was that the stick settings are not global but need to be set again in each mode, which is kinda weird. Especially the flight controls. Why wouldn't you want it the same regardless of which mode you're in. I want to thank all of you for so courteously responding.

[USSR_Rik]

http://forums.eagle.ru/showpost.php?p=684195&postcount=2

[Alphamale]

http://forums.eagle.ru/showpost.php?p=684195&postcount=2

 

 

Yes I see that now, but didn't know what you meant by that statement when you first wrote it. Thank you very much.