Bug with the collective brake?

[jermin]

It is said in the manual that in order to hold the altitude in the auto hover mode (Alt Hold button engaged), the collective brake should be engaged while moving and released after it is moved to the wanted position. Then the helicopter will stay at that high stably. And the auto hover Wag did in his producer's note did look very stable. But in my practice, the collective brake works just in the opposite way. I have to hold the F key (keep the brake engaged) in order to maintain the altitude. Once I release the key (brake), the helicopter starts to either descend or ascend. What have I done wrong?

[ZaltysZ]

Altitude channel must be engaged and vertical speed must be 0.

[My Fing ID]

I use this all the time and it works pretty well. I bound the collective brake to the m-wheel on my x52 throttle, so every time I change collective, I push in the wheel, then release when I'm where I want to be.

 

Anyways the key is to balance out the collective. If it's high, you'll still go high. Low you'll still go low. Try to keep it where you think it needs to be to hover and release the brake. Then watch your meter to the upper left. If you're still going high or low, make a small adjustment. There's a pretty small zone where the alt hold actually works, but it's there.

[EinsteinEP]

Jermin,

 

Any chance you can post a track? A number of things could be going on, but doesn't sound like a bug. If you post a track, this community can give you better feedback on what's really going on.

[isoul]

In general...

 

The Altitude Hold should be engaged. At desired altitude(and when the collective is almost at point 0) you can press F key to set the desired altitude.

 

At all times remember that :

1) Altitude Hold, as every other autopilot channel, has 20% authority over your input.

2) The collective should be kept at point 0(no ascend or descent) in order to maintain the altitude.

3) The altimeter should be set to Radar(not Barometer) in order to keep the same Above Ground Level altitude.

4) When flying above steep slopes the ALT HLD may not be able to keep up with the ascend/descend rate...

[Frederf]

Yeah the ALT hold function can only add or subtract a small bit of collective to do its task. It's very easy for the necessary collective to be well outside the authority exercised by the hold.

 

The collective brake is a "squeeze to move" brake that actually keeps the collective handle in place. In the real Ka-50 it would be hard or impossible to move the collective as it is a physical brake. In the sim you can move the handle easily without ever squeezing the brake off... which is something I wish ED would fix.

 

In addition to its physical brake the lever is attached to the ALT hold electronics. It is effectively the "trim button" for the ALT hold system. The hold is suspended while the brake is squeezed and captures a new value when relaxed.

 

You're supposed to squeeze the brake every time you change the position of the collective lever or whenever you want the ALT hold function temporarily suspended. I have my X-45 rudder on HOTAS control set up to be my collective brake but I am bad about remembering to do it.

[Martillo1]

3.1) The altimeter should be set to Barometer (not Radar) in order to keep the same Barometric altitude.

 

Just my 0,02 €

[jermin]

I built myself a mission which starts from the tarmac with a cold black shark. The Alt Hold function finally acted like what the manual describes. I had been familiarizing myself with the controls in the Ka-50.miz mission, which starts in the air. I think the bug might have something to do with it.

[26-J39]

My thoughts: As Frederf mentions the "collective brake [F Key]" as such actually has no function in the sim. It's only real purpose in the sim is to set a new alt for the Alt Hold AP or held down to change alt while your Alt Hold AP is on.

 

Also selecting either baro/radar will keep you in hover fine. Radar is usually used close to the ground, baro is obviously better at higher altitudes and especially when flyin over uneven terrain.

[slug88]

I built myself a mission which starts from the tarmac with a cold black shark. The Alt Hold function finally acted like what the manual describes. I had been familiarizing myself with the controls in the Ka-50.miz mission, which starts in the air. I think the bug might have something to do with it.

 

Until you provide a track demonstrating it, no one will believe that you've actually spotted a bug. (Hint hint)

[isoul]

3.1) The altimeter should be set to Barometer (not Radar) in order to keep the same Barometric altitude.

 

Just my 0,02 €

 

The actual term is Above Sea Level(ASL)... for that you ll get just 1 cent intead of 2! Barometric Altimeter is used to let you cruise constantly at the same altitude. This is used for higher altitudes where there is no danger of flying into a slope of mountain peak.

[26-J39]

No actually not... Martillo1 is right .. BAROMETER.... like he said to keep you at the same Barometric altitude...

[ZaltysZ]

Radar altitude hold has few pitfalls.

 

If you are trying to hover over rough surface and have some drift, than you will be drifting not only in horizontal plane, but in vertical plane too. If you are cruising, radar altitude hold will try to keep set distance to the ground and so autopilot will constantly increase/decrease blade pitch, this will result in more burnt fuel, than flying without radar altitude hold.

 

I personally use radar altitude hold only when I need to fly really low at night. In all other cases: barometric altitude hold is better for me.

[isoul]

No actually not... Martillo1 is right .. BAROMETER.... like he said to keep you at the same Barometric altitude...

 

Yeha but since I hat only 1 cent to give away I needed an excuse!:smilewink: