tekwoj

I think I know what my issue with bombs was, the LS6 bombs need the 3m30s for alignment, but the alignment doesn't start with master arm, master arm needs to be on AND you need to select the weapon group. In my case I was approaching with 250 selected, so they had time to align, when I swapped to 500s closer to the target they just started alignment and I launched them without paying attention.

Have you checked the response in the bug thread you posted?

Ok, had it happen on Shadow Reapers pve yesterday. 2 LS6-500 missed their targets, but fell in the distance from each other that was about the same as the distance between the targets, so it does look like drift. Weird thing is that 2 LS6-250 launched 10s after the 500s hit their targets precisely. What was different between the drops is the 500s were launched on point track targets, the 250s on area track. The GB6 I dropped on another occasion was perfectly on target, so it seems to be very inconsistent.

Mind if I ask on which server, if it was a public one, you had problems?

Yes. Cold start, fast nav align, nav align coordinates entered by ground crew, I just tapped in the initial heading.

That's weird, I played last weekend on multi and my ls-250 would hit within 2-3m of target just fine. GB6 might be bugged right now if there's some wind on the map. Edit: Might be worth to mark that I was on blue side as it was a coop game.

Do you designate targets with tpod or enter coords?

Detection of ground targets going above 70kts would make absolutely no sense because the only thing that would get detected, military wise, would be fast moving helicopters. At 100+ kts I think you can already use A2A radar to pick up helicopters. As to why there would be only 8kts difference between gates - no idea, maybe related to weapons.

Here's google translate of the manual from the docs:

Does it happen without wind or only with wind? There's this bug reported recently

You do realize that weapons have only certain probability of hitting within x meters of target?

Sure, but it's even less interactive than sending AShM. For AShM I can at least program the flight path that helps it avoid the terrain, I can send some LD-10s in sync to saturate AA defenses a bit. Here it's literally just a button press. 150 miles means I can land before switching to the F6. I can watch better quality explosions on yt.

802AKG is not standoff? GB6 is quite standoffish too. Like, cool that maybe they're adding it, but I would rather have them fix the 802AKG which right now doesn't work as it should. It's anyway a missile with a range that makes game boring. Wow, I've pressed a button 150 miles away from the target, now I'm going home.

I've been doing cold starts with SH since forever and I've never had an issue with gb6 accuracy

It shouldn't if mission is set up properly. If your bombs are still missing in a mission with no wind then it's gps/navigation problem, if it hits with no wind but misses with wind then it's the bug linked above. Edit: better wording

Could be related

Currently the Mk20 CCIP and CCRP markers are off. According to this topic it's supposed to be fixed in the module.

No, because it's ED taking care of the weapons and it's a weapon bug. This impacts pretty much every plane and it's been close to 6 months since it was reported. The fuzes don't work the way they should and the CCIP/CCRP are wrong.

Since at least 2 updates AKG is a supersonic cruise missile. On top of the issue above when steering using target designation it doesn't aim correctly.

It's only JF17 because only JF17 uses this weapon. All weapon implementations are done by ED and it's them who's supposed to fix them. That's why this forum section is separate from the 3rd party modules. I've had it behave correct when I swapped station before release (nose wheel steering press).

I think a bit of a problem is that besides stabilizing by radar in the front hemisphere below 20nm it should also stabilize optically below 5nm all around, allowing for the TGP to remain stabilized after bombs are dropped/rockets are launched.

The default settings are exactly what I described should happen - main fuze 1.2s, optional 4s. Either the weapon is bugged - then ED should fix it, or the plane doesn't pass the set fuze info correctly so Deka should fix the plane. And regardless which one it is, the release point is calculated wrong.

Yep, they are absolutely bugged. It seems like right now they always drop with a 1.2s fuze and the CCIP/CCRP is very off. If I understand wiki correctly, nose fuse should have dispenser open after 1.2s, n+t should be 4s and tail only should result in failure. Right now the dispenser opens after 1.2s regardless of fuze settings.

I haven't tested yet, but according to the patchnotes it should work now. Relevant part of the changelog:

That track looks more like the problems I encounter. To reduce a bit the risk of TGP going crazy after you drop the bomb start a turn and avoid passing directly above your target. You'll still get the shaking because of the lack of stabilization, but it's less probably that it will point 100m away. It's not perfect but it maybe it will make the campaign missions less frustrating.