Bug report: Community Bug Reporting System
I tried the new GBU-62 LJDAM-ERs during some matches and noticed they weren’t hitting anything. I thought I must be doing something wrong (laser issues) but it turns out this bug happens on GBU-39 JDAM-ERs as well. It certainly wasn’t doing this before the major update because I was hitting everything with the F-15E just fine.
Since you mention 30km, that is the maximum distance from which you can designate a spot using the TGP. So what ends up happening is that the designated point will be located in the air, which the bomb “hits” but then flies past, so it tries to turn around to hit it again. That’s my guess at least.
If you want to hit positions more than 30km away, you have to set the POI using the map like this, and it should work.
Note that once you’ve set a point at 30km+ and go back into the TGP, make sure to not move the camera (manually) at all, or it will reset it to the 30km limit.
Thanks. Yes I have a bug opened for the targeting pod limitation: Community Bug Reporting System
Is this not a new issue then? I don’t remember having an issue dropping these with the F-15E before the major update. Maybe it’s just because I’m trying to use the new LJDAMs on the various F-18s that I’m not able to get close to the target as quickly so I end up out of range.
Is the 30km limit intentionally set? If yes, we need a more precise way to mark GPS coordinates on the map. Zooming in an clicking isn’t very accurate.
It’s not a bug, it’s intentional, before stuff like grom and jdam-er was added i believed it was either 10 or 15km, they upped it back then.
If you’re attacking bases, then just set a keybind for ‘switch mission bombing target’
otherwise, beyond 30 km you’ll have to zoom on the map, which is still accurate enough for me 90% of the time