Jump to content

Recommended Posts

Posted

Was just starting my second mission, on the first campaign, flying along, minding my own buissnes :music_whistling:, and zooming in, and out ,of my highly detailed cockpit:thumbup: , when bang straight into the side, of a mountain, with no, ground warning whatso ever.......is it a bug, or did i do something wrong?, apart from not looking were im going:pilotfly:

regards

Tbone

Posted (edited)

If I understand the radar altimeter correctly ( not saying I do :D) The Radar altimeter look directly under the aircraft and can not see, for example, if you are getting to closed to a mountain ahead of you. That is why you probably did not get a warning.

Edited by mvsgas

To whom it may concern,

I am an idiot, unfortunately for the world, I have a internet connection and a fondness for beer....apologies for that.

Thank you for you patience.

 

 

Many people don't want the truth, they want constant reassurance that whatever misconception/fallacies they believe in are true..

Posted

As described above, the Ka-50 has no forward-looking radar sensors, so there is no way to foresee upcoming terrain. The radar altimeter and the Doppler Speed and Drift Indicator both point straight down, so a ground collision warning can only be provided based on terrain elevation data below you, which is not always the same as the terrain elevation in front of you. :)

 

You're flying a helicopter - gotta keep your eyes open. I've run into mountains before as well when checking out external views and such. Luckily, we can try again.

 

Note, you can set the radar altimeter warning altitude manually by turning the knob on the radar altimeter gauge.

- EB

[sIGPIC][/sIGPIC]

Nothing is easy. Everything takes much longer.

The Parable of Jane's A-10

Forum Rules

Posted

Probably. It's easily changed while in the cockpit by the lower-right knob, click and drag. If you regularly fly "through" the RALT warning and are below it, that is a big safety no-no. The RALT warning only sounds when passing through the RALT warning altitude, and will go off some altitude below it.

 

One should set the RALT warning to the minimum altitude you accept to fly at and never violate it. If you violate it you shouldn't relax until you are back above it. In fact I think the official realistic settings for RALT warning are to 0m on take off and landing to reinforce the notion that the RALT warning tone means serious business 100% of the time and that never is ignoring it OK.

 

P.S. is there a way to set the alt. bug on the barometric altimeter? It's not clickable.

  • 9 months later...
Posted
Is there a value anywhere in a .lua file where you can change the default setting for the Rad Alt?

 

Wow, this long and no useful answer. Dev's, anything?

Posted

The actual answer is that the RALT warning setup should be part of your startup as well as ingress/egress checks.

[sIGPIC][/sIGPIC]

Reminder: SAM = Speed Bump :D

I used to play flight sims like you, but then I took a slammer to the knee - Yoda

Posted

I'm sure it can't be, but I don't know where. In addition, it might be stuck somewhere deep in a file that'll trip the protection mechanism for online games.

[sIGPIC][/sIGPIC]

Reminder: SAM = Speed Bump :D

I used to play flight sims like you, but then I took a slammer to the knee - Yoda

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...