Jump to content

Recommended Posts

Posted

The behavior of the SO in DYK is confusing. According to the aircraft's flight manual (the real one), it's designed so that the pipper should be at or above the SO after 2.4 sec after release.

 

According to Stellan Hilmerby, a forum member who was an actual Viggen pilot, you would follow the SO to achieve the correct pull and bomb spacing. He also indicated the release in the real Viggen would occur during the pull, indicating "wing out" would happen a bit earlier than the DCS Viggen does.

 

I'm able to get a good 4g pull without it, but the SO just seems like this erratic thing that doesn't tell you anything useful.

 

It seems like it has something to do with the designation spot and safety altitude, but after countless runs I just can't figure out what that thing is trying to tell me. Trying to follow it at all for any reason leads to incorrect runs most of the time. I really think the thing is just floating out at the 400m safety altitude (if medium is set). If you check out the attached video, freeze it at 3:29 you can see the SOO blow past the reticle in the wrong direction right at about 400m then jump around a bit rather meaninglessly.

 

Here's the video. The first run is garbage but the next two are decent. I was practicing a profile Stellan uses and trying to perfect the technique when I took this video.

 

 

Also, I can confirm that the DYK aimpoint refers to the beginning of the drop, not the middle. 2 patches ago, it was the middle of the group. I don't know if this is intentional or not. Some of said this is how it works on the real jet, but the manual doesn't really say one way or another. Maybe Stellan can comment on this.

 

So, my TL:DR question is this. I know what the SO in DYK is supposed to do in real life, but what is it actually telling us in DCS? Is it functioning as it should and we're all supposed to be flying a specific profile that we're not, or is it not functioning correctly yet and we should ignore it?

Posted (edited)
it's designed so that the pipper should be at or above the SO after 2.4 sec after release.

LRR,

 

Could you further clarify this statement? It just doesn't make sense to me.

How can the pipper be above the steering order? At least in the DCS version, the Pipper disappears when the the SO is displayed, and vice versa. The two do not exist on the HUD at the same time. The SO is also a flight direction command, and the pipper is a display of the (desired, else computed) impact location. How can these two elements align when they use different frames of reference, and move according to different logic?

 

Thanks.

Edited by randomTOTEN
Posted
LRR,

 

Could you further clarify this statement? It just doesn't make sense to me.

How can the pipper be above the steering order? At least in the DCS version, the Pipper disappears when the the SO is displayed, and vice versa. The two do not exist on the HUD at the same time. The SO is also a flight direction command, and the pipper is a display of the (desired, else computed) impact location. How can these two elements align when they use different frames of reference, and move according to different logic?

 

Thanks.

 

The pipper is the dot in the middle you use to aim, not the waypoint marker.

 

The SO uses the pipper as a reference, i.e. in PLAN you follow the SO by keeping the pipper in the SO. The pipper is always on display in ANF.

 

Maybe I'm not using the terms correctly. Below is an image of the pipper and SO being on screen at the same time. (or at least what I call the pipper)

 

viggen.thumb.png.61a525846b3f2aa9fb04667da88f63be.png

Posted

Steering order confuses the heck out of me. If it’s implemented right, I’d love an explanation or video about it from someone.

Virpil WarBRD | Thrustmaster Hornet Grip | Foxx Mount | Thrustmaster TWCS Throttle | Logitech G Throttle Quadrant | VKB T-Rudder IV | TrackIR 5

 

 

AMD Ryzen 5 3600 | Nvidia GTX 1060 6GB | 32GB DDR4 3200 | SSD

  • Recently Browsing   0 members

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