Chris935

Different bombs from a different aircraft, but this sounds very similar to the report I've made here, may be of interest if they have a common underlying cause: Chris

Issue: The JDAM LAR works as expected on targets at low elevations, if you release when the system says it's in range, it hits the target. When the target elevation is higher this isn't the case and the bomb will often fall short, assuming the same aircraft altitude in both cases. The LAR calculation does not appear to be accounting for the elevation of the target. It appears the calculation is using the aircraft altitude above sea level where it should be using height above target. Test: The attached track has two targets at low elevation near sea level and two targets at high elevation, around 18K on top of Mt. Elbrus. The aircraft altitude is 25.8K throughout (per Dos Gringos I did the whole damn mission on altitude hold). Speed is 0.86-0.88 throughout. Each elevation has a GBU-38 and a GBU-32 dropped on it. These are set up as waypoints in the mission editor, and converted to TGT points in the jet using DESG and TOO. All pickle presses are made as the LAR percentage comes up through 20. Results: For given speed and altitude of the aircraft, the LAR symbology gives indications of "20" at the same slant range regardless of the aircraft height above target. In the attached track it's 13 miles for a GBU-38 and 9 miles for a GBU-32. With a height above target of 25K, these slant ranges are sufficient for the bombs to reach their targets. When the height above target is only 7K, the bombs fall short as you might expect. Not shown in the track, it's also possible to get LAR in range indications while below the target. I've attached an image of the LAR coming up through 98 as I'm 5 miles away and 6K feet below the target. The target is in the top right of the HUD. Altitude above sea level is 12.7K, so the 5 miles makes sense if you incorrectly assume a target elevation of 0. Chris AV8B JDAM LAR ALTITUDE ISSUE.trk Tacview-20220816-025611-DCS.zip.acmi

Track link PM'd to Elmo, too big to attach directly. It's a whole multiplayer session but the issue is with the first bomb that is dropped near Ras Al Kaimah. There are two GBU-32 drops in TOO mode. The first one just falls off the jet as though it didn't have any co-ordinates assigned, the second guides correctly. No LAR circles for either because that isn't working, but I did have the upper case probability numbers, so it knew where the target was and thought it could get there. Chris

I find the mimimum RWR volume to sometimes be too loud, is it still possible to edit these gain values and retain functionality of the volume knob? Chris

Thanks for the event, very enjoyable and well organised. Thanks to Bullet for the GCI. Chris

Chris935 - F5

My favourite were the "landing gear" warnings while taxiing. Can also confirm "pull up" while 5 degrees nose up 400kts 16k feet. Chris

The volume knob is also bugged and has to be re-jiggled every so often to get the sound back. Chris

Works for me, are you able to get it uncaged and locked onto a laser spot? Chris

Mine work as normal, killed a SAM about 20 minutes ago on the 104th. Chris

As in the title, you pull the trigger and the nose pulls just as it does when shooting the gun, even though the gun isn't actually shooting. Chris

This has been happening pretty consistently for me after take-off from a cold start on online play. I'll take off, head towards the target area, and double click the appropriate sensor select switch to bring up the LST so I can change the laser code from 1111 to something else. The first two digits enter as normal, but after that the buttons become unresponsive, trying to enter 1688 gives 1, 6, click, click, click... I press ENT, and it goes back to 1111. I start typing the code again and it works properly the second time. I haven't tried bringing up the code with the MPCD button instead, I've always been SSSing to the LST. Chris

I've had this issue before when I had the IRMV boxed in the STRS page, but I also had either GUN or SA boxed, (though not as the active weapon because IRMV was boxed most recently). I'd have assumed that if IRMV is boxed and STBY is displayed that they'd be cooling down. Chris