Camera zoom out @ mission start.

[Sammi79]

Hi, sorry if this has been asked before I have searched but I am unsure what keywords to use to describe this;

 

Is there a way to stop the camera doing that slow zoom out thing at mission start? It is really starting to bug me when testing missions from the editor. Possibly it is only on ramp start as I always do that.

 

Also can someone explain the 'collective brake' and 'trimmer reset' to me and should I have them mapped on my x52pro or are they not that important?:joystick: don't appear to do anything...

 

Regards, Sam.

Edited April 14, 2012 by Sammi79
1 more question

[PeterP]

Yes,

it had been asked before and before and before, but I'm sure it will be asked again and again and again... :)

And I have a good set of links - so its manly only a copy'n'paste job for me to answer.:D

 

 

Trimmer reset is the function to overcome the discrepancy that you can't feel how the "virtual" cyclic is deflected with a non-FFB controller after trim. So you may want to use it if your trim is FUBAR. (BTW: there is no such option in the real helicopter)

 

The collective brake is essential if you have the Alt-Hold AP-channel on. It sets a new flight-level.

(I have a "replica" collective - and I'm forced to hold down the collective-brake to set a new rotor-pitch, and it makes a real difference in stability of your flight path! I Fly now only with Alt-Hold on.)

So, if you want to have a relaxed left hand - and don't want to always fine-tune your rotor-pitch to fly level - you should have mapped it at a prominent place where you can always reach this function.

 

 

so, (I'm looking at your post-count) please read this:

Coaxial helicopter dynamics: http://www.simhq.com/_air13/air_427a.html

Trimming the Black Shark: http://www.simhq.com/_air13/air_428a.html

The Ka-50 Autopilot: http://www.simhq.com/_air13/air_429a.html

 

Have also a look here if you are using rudder-pedals instead the twist-stick:

How to unchain the rudder from trim

 

 

About the zooming view:

I had a deep look in all related files to switch this off - I found no answer.

 

I think the Developers implement this that fellow simmers on weaker 32bit system will have no heavy stutter and long loading times while the GPU/CPU have to pre-load the data for the visible scene.

 

Imagine it would be instantly fully zoomed out at mission start - this above named systems would probably get stuck for some time because the CPU would be stressed by requests of the GPU.

 

But if it is gradually zooming out the GPU have time to catch up and fill the V-ram with textures one-by-one.

 

But as it normally only takes 5 sec... - use the time to do something useful - like scratching your head or scratching somewhere else... ;)

Edited April 12, 2012 by PeterP

[BaD CrC]

yes. It is really annoying indeed. Don't know what came through the dev's mind when they added this feature. Only thing I am doing is to press the zoom in key even before it starts unzooming so the whole "effect" is cancelled.

 

trimmer reset is mostly useful when landing as your previous trims might prevent your chopper to completely halt even with brakes on as the rotor keeps pulling you forward. This can be vital when landing on small platforms like on boats.

I can't remember that the collective break is implemented in BS, at least as a brake. But you do use the collective handle to mark the altitude you want to maintain with the autopilot. this is worth having on your stick if you have enough buttons.

[TurboHog]

press 'numpad /' or 'numpad *' fast then press 'numpad enter' for default zoom.

 

Collective brake is used to set you current altitude as the assigned altitude. Works only when FD is off and AP alt hold mode is on or when in hover mode of course. Never use collective brake actually...

[Sammi79]

One More Question regarding auto-hover

 

OK thanks, I'm fine with trimming and hover and not making rotor blade salad, just wandered if I was missing anything regarding those 2 controls, I keep altitude without the alt-hold ap by just watching the vvi and carefully setting the collective. I got into the habit of dumping the throttles with the collective on touchdown followed by quick wheel brake, to stop rolling forward. (maybe bad practice but it works pretty good)

 

Hmmm, no rudder pedals yet (maybe in future) but I think unchaining the rudder from trim sounds like a good idea anyhow, I never want it trimmed with a constant yaw. If I want to orbit I will trim to bank anyway, and the amount of times the I set the trim only to find I'm yawing at a high rate... maybe this is why.

 

It doesn't matter what I do with zoom controls, until the slow zoom out has finished they are inactive. Look around and click works but no zoom until its done its thing... which makes those battery switches hard to hit on my screen... ah well, never mind. It is only 5 seconds after all. Looks like I picked the wrong day to give up cigarettes. grrr..

 

Cheers for the replies folks, :thumbup:

 

Regards, Sam.

Edited April 14, 2012 by Sammi79
1 more query.

[Sammi79]

OK, again sorry I have looked through various threads, I am trying to find out what the rule is for engaging auto-hover. It seems as though it only works after I've been flying around for a while, I.e if I trim the Ka50 in a 'non auto-hover' 10+ meters above the ground, the HUD will never change to show my airspeed and the auto-hover just cancels the AP channels. Only after getting up some forward speed does the HUD start to show airspeed after which point I can slow down and engage the auto-hover.

 

What exactly is the rule for engaging it? I saw something about doppler navigation but when does this engage - is it part of the INU?

 

Regards, Sam.

Edited April 14, 2012 by Sammi79

[Nate--IRL--]

Once the Doppler radar starts to provide speed information on the HUD you can then engage Hover hold, not before. it should only take a minute or two after start up.

 

Nate

[Sammi79]

Once the Doppler radar starts to provide speed information on the HUD you can then engage Hover hold, not before. it should only take a minute or two after start up.

 

Nate

 

Sweet, thanks. It seems I was just being impatient. :doh:

 

Regards, Sam.