[FREEZE FIXED INTERNALLY] JDAM Feedback thread

Copy. Thanks

I will just stay away from JDAMs for now. Probably needs a hotfix or two to make it work.

You just need to make sure the selected QTY station and the selected wingform selected station match. The mismatch freeze has already been fixed internally.

That's another issue. When I cycle the weapons, they all seem to be assigned to the last PP target. So I programmed 4 PPTs for each weapon, following your instructions closely. But, all weapons just show me 1 target for all. I assure you that I pressed QTY and selected each station at a time.

1. Attempting a loft release (ie with aircraft pitched up) will result in the bomb guiding into the ground a mile or two infront of the target, so nowhere close.

2. Are JDAMs intended to follow a zig zag trajectory in azimuth guidance?

GBU31 v3

enter target coordinates and elevation

mode pp

release qty stn2

get in range on hud

pickle

game freezes and crashes :\

same issue i have 2 logs files, how can i send?

We need crash logs if you see a crash, please.

how can i send my crash log to you?

Avoided the issue that causes the lock up, but both attempts in PP mode at 20k feet which turned out to be a release from about 10nm, both types of bombs - the 31's and 38's - guided to their targets. They weren't direct hits, but off by about what others have noted, which is roughly .02nm from the target. Targets were a vehicle and a small house. Also, rippling two bombs on one target wasn't an issue - no lockups.

Found out that when using PP mode and setting elevation it seems to only work when entering meters as altitude. Even when highlighting feet on the UFC, it still seems to enter meters, even though it says feet entered over on the JDAM page. It gives a certain point up above the ground in the hud.

My example was target area at 3552 ft elevation. Hud target diamond kept floating above the target, quite far. Then I tried calculating it over to meters and it worked. Hud diamond is now on target and bombs are hitting where they should.

This isnt an issue when using TOO mode and the waypoint designate.

EDIT crashes with GBU-38

Game Crashing When you use pickle bombs... And no crash logs

GBU-38 accuracy

The GBU-38 seems not very effective against multiple ground vehicles in one run.

With multiple JDAM types, if you switch between them, the 10 min alignment countdown starts over. This seems to occur even if the alignment has completed.

i can confirm this. must not switch weapons during/after alignment or you have to wait all over again.

There is something off with the PB mode. Note the coordinates of the location and entered elevation MSL vs the target marker on the HUD.

I guess it's worth mentioning that the intended target is that big factory on the first screenshot.

I'm having the exact same problem. When I'm trying to input target's elevation as shown on F10 map, it places HUD marker either up in the air or deep underground. Tried both feets and meters.

JDAMS crashed for me the first two tries when I pushed the pickle button and had to use Alt Ctrl Delete. Re-looked at WAGS video and noticed what I did wrong. Went back out and everything worked great.

Providing a track file would be helpful.

My run has also ended with CTD, so no log or track unfortunately.

I'm just curious if obtaining target coordinates and elevation from the map is acceptable for JDAM programming at all?

I used the map...

JDAM caucasus coordinate problem

Map caucasus

F18c with 4 jdam ( any )

Problem waypoint from editor is not allowed on the jdam page.

When i setup a test mission i put 4 waypoint on top of 4 tanks

on the X shaped empty airfield N41.50.33 E41.47.50 ( something like that)

BUT when i look at my HSI and data page of my waypoint 1-2-3-4

Then i can see the coordinate that the editor saved when i made my waypoint to look something like N41.50.89

The JDAM page do not accept ( 89, but only numbers below 60 i think )

So in that specific area at the airport and maybe other places, you cannot

trust/read your waypoints and read the coordinates and directly enter them into the JDAM weapon page, you have to manual navigate to the F10 map view and write down the correct waypoint and then enter that into the JDAM page.

Els the coordinate will not be correct.

PS.. im not sure, but i once read something about the caucasus map coordinate are "merged" together on the map and that this in some situation when you navigate and read cordinates can have issues.... not sure if that is the problem of if i remember correctly.

jdam 38 crash

try to rearm with the same jdams and use the pp points I had in the system from the 1st run pickled and got the wait or close crash. no crash report.

As has been noted, we will add PRECISE mode later in early access.

 

Thanks

Hi Wags,

I was playing around with the PP JDAMs and got the impression that decimal seconds already work, if you add them after the first enter press after deg, min, sec input. I could do pretty damn precise drops with that (more about how I actually got the coordinates later ;) ).

Delevero, you need to convert coordinates from decimal to arc second.

See my guide here:

https://forums.mudspike.com/t/f-a-18c-jdam-paveway-targeting/8325

In the current Open Beta, please use meters (not feet) to set PP target elevation for now.

 

Thanks

Hi again, Wags,

I had no problems with ft vs. meters when testing JDAMs (GBU38 ) today. Did I just get lucky? (tested from 23ft to 780ft elevations).