Jump to content

Recommended Posts

Posted

Do you guys know what the conditions are when the ground speed indicator on the hud disappears. And when it happens, how to reenable it.

 

I noticed that it happens when your autopilot channels shut down. I also noticed that it tends to happen when you have too much yaw trim. But I can't put my finger on what exactly makes it shut down. As its a vital instrument when you're going into a hover, I'd like to know :)

 

I tried searching the forum and the manual, but didn't find anything about it.

Posted

I assume you already know it, but just in case: whenever you have a weapon system active and selected.

 

(Oh, and the vital system when going into a hover is Eyeball Mk1. That -should- be all you need. If it isn't, you're looking at more practice.)

  • Like 1

[sIGPIC][/sIGPIC]

Daniel "EtherealN" Agorander | Даниэль "эфирныйн" Агорандер

Intel i7 2600K @ 4.4GHz, ASUS Sabertooth P67, 8GB Corsair Vengeance @ 1600MHz, ASUS GTX 560Ti DirectCU II 1GB, Samsung 830series 512GB SSD, Corsair AX850w, two BENQ screens and TM HOTAS Warthog

DCS: A-10C Warthog FAQ | DCS: P-51D FAQ | Remember to read the Forum Rules |

|
| Life of a Game Tester
Posted

(Oh, and the vital system when going into a hover is Eyeball Mk1. That -should- be all you need. If it isn't, you're looking at more practice.)

 

Eyeball Mk1? That old piece of equipment? Need a newer generation... :)

[sIGPIC][/sIGPIC]

Posted
.....Need a newer generation... :)

 

Eyeball Mk1 Delux.......

 

Added Contact Lenses :D

Novice or Veteran looking for an alternative MP career?

Click me to commence your Journey of Pillage and Plunder!

[sIGPIC][/sIGPIC]

'....And when I get to Heaven, to St Peter I will tell....

One more Soldier reporting Sir, I've served my time in Hell......'

Posted (edited)

Using visual references for hovering or any precise maneuvers in a simulation is not necessarily the best system to use. For one thing, in real life visual cues are supplemented by the spatial movement detected by the inner ear. If you only have one of those to work with, especially after being used to having both senses to work with, accuracy goes down the toilet. Secondly, visual cues in a virtual word are not 100% accurate depictions of the simulated spatial geometry. When you pan from left to right do you notice how the scenery grows as it reaches the edge of the screen? That can have a huge impact on spatial awareness when you are working with very precise and minute control inputs when limited to only visual cues.

 

In my opinion the best system in-game to bleed off speed and come to a hover would be use of the IAS guage while at speeds over 30 kph and the HUD's ground speed indicator (with glances at the ground/horizon if fairly low to the ground) at or below 30 kph. Without the sensation of movement it is neccessary to check the guages frequently to compensate for the lack of sensory input.

 

As for getting the sometimes missing ground speed indicator on the HUD to come back up it almost always only involves a Targeting Mode Reset (Backspace). I've never noticed the issue with too much yaw trim negating it since most of the time when I've had too much yaw I had no clue what I was doing. I was reading is another thread on the forums that for the most part yaw in anything more than small tweaks is actually bad for the KA-50 as it causes a much higher chance for the the two rotor discs to intersect. If you can keep your yaw to a minimum and instead rely mainly on bank turns with touches of yaw I think you will find the helocopter much easier to control, I know I did, plus less of a chace to loose the ground speed indicator.

 

For reference here is the post that informed me quite a bit about yaw and flight mechanics, it is a very enlightening read.

http://forums.eagle.ru/showpost.php?p=671731&postcount=12

Edited by enigmatics
Posted
Using visual references for hovering or any precise maneuvers in a simulation is not necessarily the best system to use. For one thing, in real life visual cues are supplemented by the spatial movement detected by the inner ear. If you only have one of those to work with, especially after being used to having both senses to work with, accuracy goes down the toilet. Secondly, visual cues in a virtual word are not 100% accurate depictions of the simulated spatial geometry. When you pan from left to right do you notice how the scenery grows as it reaches the edge of the screen? That can have a huge impact on spatial awareness when you are working with very precise and minute control inputs when limited to only visual cues.
(Bold is mine)

 

Hi enigmatics,

 

Spot on. While attempting precise maneuvers at low speed and altitude, I struggle to get my bearings on where my Ka-50 is actually going.

 

IIRC, IL-2 had a small circle that indicated where your aircraft was flying towards. A thing like that would help a lot in DCS Black Shark. Just to compensate the lack of inner ear sensory input.

 

Cheers,

  • Like 1
Posted
(Bold is mine)

 

Hi enigmatics,

 

Spot on. While attempting precise maneuvers at low speed and altitude, I struggle to get my bearings on where my Ka-50 is actually going.

 

IIRC, IL-2 had a small circle that indicated where your aircraft was flying towards. A thing like that would help a lot in DCS Black Shark. Just to compensate the lack of inner ear sensory input.

 

Cheers,

 

The Ka50 does have this kind of graphical representation like IL2, sort of. Its a line that extends from the centre of the HUD when below a certain speed. Ill quote the manual for better explanation:

Page 247 of Flight Manual

31. Velocity Vector. When airspeed is below 50 kph, a velocity vector line is drawn from the center of the Aircraft Datum. This line points in the direction that the aircraft is traveling and the length of the line represents the aircraft‟s relative speed. The line will be longest when the aircraft is traveling at 50 kph in any direction and shortest when the aircraft is at or near a hover. The Velocity Vector line is a useful tool when used in conjunction with the Hover Point Deviation Marker to hold a battle position.

 

^this is my main tool for achieving a steady hover

Specs: GA-Z87X-UD3H, i7-4770k, 16GB, RTX2060, SB AE-5, 750watt Corsair PSU, X52, Track IR4, Win10x64.

 

Sim Settings: Textures: ? | Scenes: ? |Water: ? | Visibility Range: ? | Heat Blur: ? | Shadows: ? | Res: 1680x1050 | Aspect: 16:10 | Monitors: 1 Screen | MSAA: ? | Tree Visibility: ? | Vsync: On | Mirrors: ? | Civ Traffic: High | Res Of Cockpit Disp: 512 | Clutter: ? | Fullscreen: On

Posted
The Ka50 does have this kind of graphical representation like IL2, sort of. Its a line that extends from the centre of the HUD when below a certain speed. Ill quote the manual for better explanation:

Page 247 of Flight Manual

31. Velocity Vector. When airspeed is below 50 kph, a velocity vector line is drawn from the center of the Aircraft Datum. This line points in the direction that the aircraft is traveling and the length of the line represents the aircraft‟s relative speed. The line will be longest when the aircraft is traveling at 50 kph in any direction and shortest when the aircraft is at or near a hover. The Velocity Vector line is a useful tool when used in conjunction with the Hover Point Deviation Marker to hold a battle position.

 

^this is my main tool for achieving a steady hover

 

Ey BTTW-DratsaB! :thumbup:

 

Sure, that's a great aid and I use it a lot.

 

I'm actually longing for a sort of flight path vector (FPV) or velocity vector symbol in DCS Black Shark. I know the real Ka-50 doesn't have it, but it would help to compensate the lack of sensory information.

 

Thanks!

Posted

I can hover it by watching an object in the distance, though I can't react as well since I can't feel the minute accelerations. I don't think an FPV would help you much in that respect either - but maybe I'm wrong.

[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 (edited)

Another thing that really helps hovering in real life is peripheral vision. Inner ear, peripheral vision, and also keeping the eyes focused distant rather than up close (in actuality shifting focus between points). Early in my training I could not get my eyes out to the horizon because I was so fixated on holding a spot. Things got easier when I moved my eyes out front more and let peripheral vision do more of the work. In the sim, peripheral vision can really only be utilized with multiple monitors or, to some extent, FOV increased with a 'fisheye' effect. Not sure if FOV can be adjusted in DCS, so I just wind up TrackIRing all over the place as I slow to zero gs.

 

As for flight path vector (the circle showing the path the helicopter will "fly through"), that was modeled in Longbow 2, IIRC. That was a great tool. Not sure it that's part of the real HUD in the Longbow or Apache, but assume it is.

Edited by Rangoon
Posted

The AH-64A does not have a flight path marker like many fixed wing aircraft have. It does have a velocity vector, which is almost identical to the velocity vector on the Ka-50 (a line that extends from the center of the HUD outward where the length represents your ground speed). For the AH-64A, in hover mode, the line represents 0-6 knots ground speed, while in transition mode it represents 0-60 knots ground speed. Cruise and Bob-up modes do not have a velocity vector at all.

  • Recently Browsing   0 members

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