HUD always running away from home

[unipus]

After flying a good bit of Viggen, I ended up taking almost a year off from DCS until 2.5 released. Now I'm back at it, and having a problem I don't remember having before, at least not nearly this bad: the HUD data is often sliding way out of view. I know this is to some degree inherent in the design but here's what I was seeing yesterday:

 

 

Trying to do dive bombing. Weapon selector DYK, radar mode ANF, target waypoint set, QFE set. I see the target waypoint O in my HUD. I climb, roll out, then go into a dive with trigger safety released. And the HUD slides right by at the exact moment I need it. More often than not I'm looking at a completely blank HUD after about 8 tries at different degrees of dive. Checked Chuck's guide to make sure I wasn't missing something. Watched videos. Really not sure what I'm doing wrong, or is this a new bug?

[Holton181]

I'm no expert, really never used bombs yet, but from what I read earlier trigger safety release shall not be performed until the reticle resting steady on the intended target point. Something about trigger safety release initiating a reference point of some sort. Did you go trigger safety released like that or directly when you first initiated the dive, before lining up with the target?

[Rudel_chw]

... Trying to do dive bombing. Weapon selector DYK, radar mode ANF, target waypoint set, QFE set. I see the target waypoint O in my HUD. I climb, roll out, then go into a dive with trigger safety released. And the HUD slides right by at the exact moment I need it. More often than not I'm looking at a completely blank HUD after about 8 tries at different degrees of dive.

 

 

Last time I tried a dive bombing it was working fine, here is a video of mine, so you can check the steps ... I start the mission in-air, so at the start I use active pause in order to have time to setup the aircraft:

 

 

owsdXiP6S_Y

 

 

When I start the dive, I release the triger safety, you can tell because the "o" dissapears to decluter the HUD.

 

 

Best regards

[unipus]

I'm no expert, really never used bombs yet, but from what I read earlier trigger safety release shall not be performed until the reticle resting steady on the intended target point. Something about trigger safety release initiating a reference point of some sort. Did you go trigger safety released like that or directly when you first initiated the dive, before lining up with the target?

 

You're right, I did it earlier in most of these runs. I'm not sure this explains losing the HUD entirely, though. Like I can generally watch it slide off the top or bottom of the glass in a hurry.

 

 

 

Last time I tried a dive bombing it was working fine, here is a video of mine, so you can check the steps ... I start the mission in-air, so at the start I use active pause in order to have time to setup the aircraft:

 

When I start the dive, I release the triger safety, you can tell because the "o" dissapears to decluter the HUD.

 

 

The only thing I see that you're doing differently is the degree of dive, which here looks like about only 10-15 degrees (that low I'm surprised you didn't hurt yourself with low drag bombs!). I've been coming in anywhere from 30 to 70 degrees. Edit: I see two other systems differences, one is that is you switch your HUD to low mode. I thought high mode was to be used for dive bombing. The other is that I have not been disabling target motion ranging (221), but again I doubt how that would have a drastic effect like this on the HUD display.

Edited July 25, 2018 by unipus

[Rudel_chw]

The only thing I see that you're doing differently is the degree of dive, which here looks like about only 10-15 degrees (that low I'm surprised you didn't hurt yourself with low drag bombs!). I've been coming in anywhere from 30 to 70 degrees.

 

 

It works the same at steeper dives, here is a similar video at 30º (more or less) .. on these practices I was striving at accuracy, and diving angles higher than 30º were less accurate (probably because its harder to keep the aiming point on the target):

 

 

aWCIXCRBpV8

 

 

Edit: I see two other systems differences, one is that is you switch your HUD to low mode. I thought high mode was to be used for dive bombing. The other is that I have not been disabling target motion ranging (221), but again I doubt how that would have a drastic effect like this on the HUD display.

Can you record a video of one of your attempts? .. I'd like to watch the "running away" :)

 

 

Cheers!

[Cobra847]

We're looking at some issues involving dive bombing accuracy and HUD indications currently.

[RagnarDa]

It should be fixed in the next release to open beta. Thanks for the reports!

[rainyday]

Great! I was wondering why dive bombing hud disappears when my nose drops below the horizon, just when I start my dive, what Im doing wrong. Will wait for the fix to try again. Until then - high drag CCIP bombing is keeping me entertained :joystick:

[unipus]

We're looking at some issues involving dive bombing accuracy and HUD indications currently.

 

Well that's a relief. I thought I was taking crazy pills. As it is I can now usually get it close enough for guesswork and hit some targets, but it's sure not ideal.

[Kozality]

I was going nuts the other day with this issue myself, but I thought I'd traced it to an incorrectly set QFE. While that helped to an extent, I always use DYK mode with the HUD in High HOA, leaning in towards my monitor with my TrackIR in order to "see over the nose" and view the pipper. It works, but it's not quite ideal.

[unipus]

Yes, I was doing that too but having to lean in a huge amount. I thought "this can't be the way this is supposed to work."

[Polito]

I'm a rookie in Viggen but the same thing happened to me, you've checked if you have the Hud in bombing position too an attack angle too high makes you miss information about the Hud