Hover on & off control and altitude hold

[Sleksa]

Hello. I recently started flying the ka-50 again and I've ran into the following problem.

 

When I engage the authover on, the autopilot also automatically engages altitude hold channel on, however when I toggle the autohover mode off, the altitude hold channel remains on. :joystick:

 

On the page 366 of the manual the altitude channel toggling on is considered working as intended, however there's no mention whether the altitude hold channel remaining on when hover mode is cancelled. What I'm wondering is:

 

1) Whether this is working as intended

2) Whether there's a smart workaround over this (some cockpit setting/switch which removes this function?)

[ricktoberfest]

Hover on & off control and altitude hold

 

Working as intended

I just map a button on my joystick to alt hold off

[BitMaster]

Working as intended

I just map a button on my joystick to alt hold off

 

 

You should also map a button for FD mode to override all AP's to be able to dodge and manoeuvre quickly without fighting the AP's.

 

 

Bit

[Sleksa]

Working as intended

I just map a button on my joystick to alt hold off

Thanks.

 

 

You should also map a button for FD mode to override all AP's to be able to dodge and manoeuvre quickly without fighting the AP's.

 

 

Bit

 

Thanks for the swift reply. It seems like a weird setup in the sim especially since toggling the hover off usually also means that a altitude change and maneuvering are imminent but I guess it makes a lot more sense on the actual real life helicopter.

 

I flew the kamov with keyboard+mouse for a year ages ago before finally caving in and buying a logitech extreme 3d pro from a sale last tuesday and the difference is night and day! Flying around has turned into fighting for every traveled inch against the environment and the helicopter into incredibly smooth trimmedtravel and the FD for the violent maneuvering like last night's moment of popping over a hill on target area only to find a whole ground formation right under me :music_whistling:.

 

The setup I have is 4 buttons with 4 extras through using the trigger as a modifier key, mapping the skhval on/reset/lock target buttons and trim + FD, autohover and CM dispense as well as turn on target through the modifier, leaving me with no button for the autohover turnoff. I guess I'll just have to toss a coin to choose between replacing the countermeasure dispensing or the turn on target

[majapahit]

In case you run out of buttons

I bought VoiceAttack ($ 8 ) voice control

 

with a good but cheap Logitech microphone (& Win7 or 8 )

I have my hands on the stick when whispering flight commands in the Mic

 

with a TrackIR its:

 

'Shkval' - 'helmet' - (move head) - 'lock view' (move the gate with modifer_POV till lock) -

- move the copter sideways for the laser on the lock with rudder

- I dont even have to trigger the release button, I can say 'release'

 

thats real cool

(does take hours to set up all voice commands)

[StrongHarm]

I agree, it's important to map Alt AP to HOTAS. I have all AP buttons mapped to the CMS on my WH HOTAS. If you have a WH, check out my control profile.

 

Also, if Alt AP is causing you more problems than it should, be sure you're using your collective brake. It's important. Here's a good explanation by PeterP.

 

Another alternative to VoiceAttack is Voice Activated Commands (VAC). It's inexpensive and very well supported. I can talk with my pipe in my teeth and it still recognizes my commands. Awesome app. You can get my prepared VAC profile, with command reference sheet, here. I only use it for DataLink and interaction with wingmen/tower, but that's over 200 voice commands. You can very easily add your own commands simply by typing what you want to say, then the key that should activate when you say it. No training or any other action necessary. The command builder is the best reason to use VAC.. it's a no brainer.

Edited November 3, 2014 by StrongHarm
meant collective brake, not cyclic brake heheh

[majapahit]

I only use it for DataLink and interaction with wingmen/tower

 

My profile of VoiceAttack has all the keybindings but not the Datalink interactions because I haven't got around to that yet.

 

I only recently upgraded to BS2 and re-started playing black shark with the installation of a better VGA Card capable of BS2.

 

I have a VRinsight flightpanel but to many buttons to remember.

 

Merely voicing 'gear', 'route' is a lot easier on the brain.

 

There are quirks though. I am not a native english speaker (Dutch), and of a long list of all recognized commands,

 

the windows voice recognition engine does not understand me when I say the Uber simple 'hover',

 

even if I try this is in a dozen multitude of ways. How silly is that?

 

One can train a word separately in windows recognition, but I havent gotten around to that either.

 

Since I've entered multiple alternatives for most commands, next to 'hover' I defined 'steady' and 'hold' for the same action binding and these words will execute without problem.

 

2 more cts