reported earlier DTOS question

[DD_fruitbat]

I don't know if this is a bug or not, but feels like it probably is, the drop cue in the HUD doesn't synchronise with the timer count down for bomb release in the HUD, see from 1:30 onwards,

Edited January 27, 2022 by DD_fruitbat

[Furiz]

Is it correct that countdown in DTOS mode doesn't go down to 0 when the bomb release que reaches flight path marker and bomb releases?

[Northstar98]

5 hours ago, Furiz said:

Is it correct that countdown in DTOS mode doesn't go down to 0 when the bomb release que reaches flight path marker and bomb releases?

I don't think so, no.

AFAIK the countdown timer should show the time until the next action event. The full list of events is as follows:

1. Time to steerpoint (pre-designation)
2. Time to pull-up for toss attack - not present in DCS
3. Time to first solution cue (bombs release for toss attack) - not present in DCS.
4. Time to second solution cue (bombs release for level attack).
5. Time to impact (for at least LGBs).
6. Time to steerpoint (if the target is undesignated or at least I think).

Once the preceding action event passes, the timer should reset and count down to the next.

Edited January 28, 2022 by Northstar98
pull-up angle is something you can set AFAIK, not necessarily 45°

[Furiz]

Ok, but the problem is that DTOS countdown doesn't stop with bomb release (when time delay cue reaches flight path marker), in fact the countdown doesn't reach 0 at that point, it is set to higher number, depending on aircraft altitude,

so if I release GBU-12 at the moment when TDC reaches FPM the DTOS countdown that continues reaches 0 when bomb impacts the ground. Then when the bomb impacts the ground a new countdown starts.

 

Shouldn't that countdown reset when TDC touches FPM and bomb is released?

You can see that on my track.

DTOS countdown.trk

[FoxOne007]

1 hour ago, Northstar98 said:

I don't think so, no.

AFAIK the countdown timer should show the time until the next action event. The full list of events is as follows:

1. Time to steerpoint (pre-designation)
2. Time to 45° toss cue - not present in DCS
3. Time to first solution cue (bombs release for toss attack) - not present in DCS.
4. Time to second solution cue (bombs release for level attack).
5. Time to impact (for at least LGBs).
6. Time to steerpoint (if the target is undesignated or at least I think).

Once the preceding action event passes, the timer should reset and count down to the next.

 

So basically we have another half-assed system that ED has implemented. What else is new I guess…

[Northstar98]

49 minutes ago, Furiz said:

Ok, but the problem is that DTOS countdown doesn't stop with bomb release (when time delay cue reaches flight path marker), in fact the countdown doesn't reach 0 at that point, it is set to higher number, depending on aircraft altitude,

It sounds like it isn't giving you the time to go for the solution cue, and is instead giving you the time to go for something else.

Pre-designation, the time to go should display time to the currently selected steerpoint, once designated it first displays time to go for pull-up for toss attack (not in DCS), once that is reached it then displays time to release for the first solution cue (bomb release for toss attack - again not in DCS), once that has passed it shows time to release for the 2nd solution cue (bomb release for level attack).

Once bombs are released I think the time-to-go should be time to impact (at least for LGBs).

The HAF -34-1-1 for the Block 50 clearly states that time to go should be for pull-up and release.

49 minutes ago, Furiz said:

so if I release GBU-12 at the moment when TDC reaches FPM the DTOS countdown that continues reaches 0 when bomb impacts the ground. Then when the bomb impacts the ground a new countdown starts.

Hmm, sounds like its only giving you time to impact, it should give you time to release.

49 minutes ago, Furiz said:

Shouldn't that countdown reset when TDC touches FPM and bomb is released?

AFAIK, yes, and it does appear to do so in your track.

And it should either give you time to impact, time to level release cue (in DCS, seeing as we don't have the pull-up cue or the time to toss release cue) or time to steerpoint if the target is undesignated.

49 minutes ago, Furiz said:

You can see that on my track.

DTOS countdown.trk 439.77 kB · 0 downloads

I think it's giving you time over designation point, when it should be showing you time to release.

When you release, the timer resets to show you time to impact (in the instant before release, the timer reads 30 seconds, and at the moment of release it shows 35 seconds), and then once the time to impact reaches 0, it resets to show you time over designation point again (and starts counting up as you're flying away from it).

However, once designated, my understanding is that it should show you the time to level release (seeing as we don't have the pull-up cue or the toss release cue).

Edited January 28, 2022 by Northstar98

[Furiz]

Time to release is wrong as I see it.

[Northstar98]

31 minutes ago, Furiz said:

Time to release is wrong as I see it.

The problem is that it's not giving you time to release at all, in your track the timer didn't reset after you designated the target, so its giving you time over designation point, instead of time to release.

Edited January 28, 2022 by Northstar98

[Furiz]

Well its a bug I guess?

 

You can even see it here on Matt's video at 02:03

 

 

Edited January 28, 2022 by Furiz

[Northstar98]

Yeah, missing the time to release.

Once we have toss functionality, we should also see the countdown timer display:

1. time to pull-up
2. time to release for toss (accompanied by the PUAC)
3. time to release for level/dive release

In that order, and the timer should reset and display for the next event once the timer for the current event reaches 0.

The -34-1-1 (for Greek Block 50s) explicitly mentions that there should be a time to pull-up and time to release displayed by the timer.

Right now there's just time to designation point and time to impact.

[Furiz]

Yep, we were talking about it here 

 

 

 

[BIGNEWY]

this is already reported by the team and they will investigate the timings 

 

thanks