[FIXED INTERNALLY] CCRP-AUTO WPDSG position spontaneously changes

[Martin2487]

When bombing in CCRP AUTO mode, the TGT position changes spontaneously. The deviation is often pronounced. It happens at irregular intervals when you find out that the TGT position is located elsewhere than 2 minutes ago. Critical error adversely affecting the laser dropping bombs because deviation is sometimes considerable.

Edited February 3, 2019 by Martin2487

[Tholozor]

If you have an axis assigned to the TDC, ensure there's no fluttering going on in the controls, try adding a small deadzone in the center to ensure it's not causing the target marker to slew around.

[Martin2487]

Track

 

I attach track with bug. The track is an attack on the ammunition warehouse of Nalchik airport. Although the warehouse coordinators entered correctly, TGT waypoint position changes spontaneously. Therefore, the bombs did not hit the target. The error occurs irregularly.

 

 

Multiplayer, DCS openbeta 2.5.4.27430

 

Track: https://drive.google.com/file/d/1fe9rqBfG__Ihogt7wXIxnPzbYE_VeFdm/view?usp=sharing

 

@Tholozor I haven't TDC on axis.

[Martin2487]

Bug detected also version DCS openbeta 2.5.4.28090. I hope you can fix it in the implementation JDAM. It's frustrating when you TGT waypoint moves.

[Martin2487]

I attach a really short track. TGT waypoint was on the track in Kutaisi. Waypoint shifted spontaneously before the runway. I have already described and documented this behavior on the included track. But what's interesting is how the TGT waypoint literally drifts along the display. I believe the included track will help you remove this bug. It has been appearing for a long time.

 

I would also be grateful if you confirmed this bug as reported.

 

Track:

https://drive.google.com/file/d/1mNVFTa3CUvJG-nTf9lU8GKJVLCQmGCXV/view?usp=sharing

[NineLine]

I am looking into, thanks for the report.

[NineLine]

Hey guys so yesterday I was able to replicate this issue, today I updated my internal version, and went to create a clean track, and now it appears to be fixed. This may be related to the INS issues we are seeing, but as of right now, it seems to be fixed internally. I am marking it as such, but when you get your hands on the next OB and it's not fixed, please feel free to ping me here.

 

Thanks for the report guys!