unable to reproduce [UNABLE TO REPRODUCE]Post-Designate Issues-Bombs fall way short

[bcl816]

In post designate , it looks like bombs are falling significantly short of where the pipper last showed. Track attached. In the runway bombing we tested, the pipper was lined up at the closest threshold of the runway. No significant weather conditions were in the server.

[bcl816]

Also this issue seems to be far worse when using ripple counts >1.

[Deano87]

Also this issue seems to be far worse when using ripple counts >1.

 

Be sure you’re not being effected by the HUD offset bug as noted here

 

https://forums.eagle.ru/showthread.php?t=263441

 

 

 

This can cause weapons to fall short as the CCIP pipper is offset.

 

There is a workaround here:

https://forums.eagle.ru/showthread.php?t=265289

 

When that bug isn’t present I find Mk82s and 84s to be pretty accurate.

[Frederf]

By post-designate I assume it means CCIP using the delay cue. Yeah I find the same, a few hundred feet short. I don't know why. CCIP without the delay cue seems pretty much spot on.

[bcl816]

Be sure you’re not being effected by the HUD offset bug as noted here

 

https://forums.eagle.ru/showthread.php?t=263441

 

 

 

This can cause weapons to fall short as the CCIP pipper is offset.

 

There is a workaround here:

https://forums.eagle.ru/showthread.php?t=265289

 

When that bug isn’t present I find Mk82s and 84s to be pretty accurate.

 

 

The air craft were hot start. would that still effect the HUD?

[Deano87]

The air craft were hot start. would that still effect the HUD?

 

If the horizon line doesn't match the horizon then the bug is happening. I'm not sure if it effects hot start jets or not.

 

Oh I should ask, are you in Open Beta or Release?

 

the Mk82s in release landed short generally, but the Mk84 was pretty accurate.

 

Since 2.5.6 the Mk82 accuracy is much better, the HUD bug notwithstanding.

[Frederf]

No, CCIP is perfectly accurate. CCIP with delay cue is short. If the HUD was misaligned then CCIP wouldn't work.

 

It's possibly the manner in which the system is storing the target location using the LOS through the delay cue'd pipper dot. Right now there is no AGR ranging. It might be using the steerpoint elevation (which can't be edited) or who knows what else.

[bcl816]

Apparently my track reply didnt attach. This link is to a replay. https://drive.google.com/file/d/15NjRylQvmduC8XcyyYzRoY82JjQCu68i/view?usp=sharing

[BIGNEWY]

If you rearm are you aligning your INS again?

[bcl816]

If you rearm are you aligning your INS again?

 

no, not for this particular test. but i have experienced this with a hot start and bombs already set. Is that the issue is INS needs to be realigned?

[BIGNEWY]

no, not for this particular test. but i have experienced this with a hot start and bombs already set. Is that the issue is INS needs to be realigned?

 

Possibly, INS should be realigned after loadout change.

[Frederf]

Possibly, INS should be realigned after loadout change.

Issue exists with an air start.

[BIGNEWY]

Issue exists with an air start.

 

Please do a short air start track replay and I will take another look thank you

[Eagle7907]

[iNVESTIGATING]Post-Designate Issues-Bombs fall way short

 

Also this issue seems to be far worse when using ripple counts >1.

 

 

 

I’ve griped about this before and was edumacated by several on Discord that, when rippling, the designation point is from the middle of the ripple distance for all bombs set.

 

In other words, you set 4 bombs to ripple, at 500’ spacing. The computation is set in the middle of 1500’ run.

 

Example:

Pickle <500’> Pickle <250’>designation point<250’>Pickle <500’>Pickle

 

Try to make your aim point in the middle of your intended release path.

 

 

Is this correct? I don’t know and never heard of it until recently, but it does work when aiming this way. I dropped 8 CBUs over a length of about 4000’ with tanks. No mercy.

 

Sent from my iPhone using Tapatalk Pro

Edited March 5, 2020 by Eagle7907

[Frederf]

It occurs with single bomb releases as well. Yes center of aim point coincides with center of bomb pattern in the real F-16 (and appears to be in DCS as well). This applies to CCIP, DTOS, and CCRP.

 

Attached is simple track with a few CCIP-delay-cue attacks. I found that the first attack only a few seconds after mission start resulted in immediate weapon release despite a significant delay cue size (obviously landed well short). Other attacks it's eh 100-300' short.

Viper Bug CCIP Delay Cue Short.trk

[Deano87]

It occurs with single bomb releases as well. Yes center of aim point coincides with center of bomb pattern in the real F-16 (and appears to be in DCS as well). This applies to CCIP, DTOS, and CCRP.

 

Attached is simple track with a few CCIP-delay-cue attacks. I found that the first attack only a few seconds after mission start resulted in immediate weapon release despite a significant delay cue size (obviously landed well short). Other attacks it's eh 100-300' short.

 

Have you tried with different bomb types to see if that has an effect on the error?

[BIGNEWY]

I have reported this to the team,

 

thanks

[BIGNEWY]

We are having problems reproducing this, it seems to work correctly for us during testing.

 

Please ensure you are holding down the weapon release trigger until the release cue passes the FPM

 

let us know if it helps

[Frederf]

Included is track plus mission track is based on. Point of aim was at first edge of building. Point of impact was about 1 building length short.

Viper Bug CCIP Delay Cue Short2.zip

[Emmy]

In the training mission by Bunyap, he says that Post Designate CCIP “split” the aim point.

 

ie, a stick of six bombs puts three before the point and three after.

 

Is it possible that single bombs are trying to drop based on a given spread as if there were multiple bombs being dropped?

[Frederf]

Good thinking but I have the same impact short at single 999' and 10'.

[Emmy]

It was worth a shot...