SJBMX

Test #2: Tested with GBU-54 and GBU-38 at maximum DLZ range from 20,000ft, 10,000ft, and 5,000ft MSL, against a steerpointed, invulnerable target at 33ft MSL, with no wind conditions and standard barometric pressure. All bombs come up very short except for the 5,000ft GBU-38, which overshoots and impacts over 50 meters past the target. Target is approximately 10m in length for reference. Test # 2 Track File Test #3: Dropped three GBU-54s and three GBU-38s from 10,000ft MSL, between 4.9 and 4.1nm horizontal distance to target. Same target and conditions as above. Three bombs come up very short, and three impact within 15m of the center of the target. Test #3 Track File Test #4: Dropped GBU-54s from 10,000ft MDL at 4.5, 4.0, and 3.5nm horizontal distance to target, came around, and did the same with GBU-38s. Same target and conditions as above. All three GBU-54s and one GBU-38 impact 10-15m from center of target. One GBU-38 appears to land around 5m from center of target. One GBU-38 comes up very short. Test #4 Track File

Thank you! From what I've seen, it seems to be the case for all altitudes, although the degree to which the bombs came up short at maximum range was significantly less. IIRC, I had tested it at 10,000, 7,000, and 5,000 feet. I will do a test run and add tracks ASAP.

JDAM/LJDAM DLZ Staple: The DLZ Staple for GBU-38 JDAM and GBU-54 LJDAM indicates a significantly longer range than the bombs are actually capable of. In the below example, the staple indicates that you are within the launch zone at around 7.8nm when at 20,000ft, for a target near sea level, for both types of bombs. However, actually releasing from this range results in the JDAM/LJDAMs falling approximately 3/4 of a mile short of the target, as shown in the video and image below. The actual maximum range from this altitude seems to be somewhere between 5.5 and 6.0nm, from what I've seen. [ATTACH=JSON]{"alt":"Click image for larger version Name: Views: 0 Size: 61.7 KB ID: 7127551","data-align":"none","data-attachmentid":"7127551","data-size":"full"}[/ATTACH] JDAM/LJDAM CEP: The DCS 2.5.6.57624 patch notes indicate that the Circular Error Probable (CEP) for the GBU-38/54 is 5m (16ft) when GPS-guided, and 5 times that (25m/80ft) when inertially-guided; from my understanding, CEP means that there is a 50% probability of impact within the given radius, with increasingly lower potential for further misses (ie: bombs not landing within the CEP radius are more likely to land nearer to the target than further from it). From what I've seen, GBU-54s dropped within a reasonable range will always hit within 15m of the target, which seems somewhat reasonable (after all, there's only a 50% chance of them landing within the 5m CEP radius), but GBU-38s are considerably less accurate from what I've seen. I probably released 40 of each yesterday, and the GBU-38s consistently underperformed compared to the the GBU-54s, in some cases being off enough to miss small buildings. Both bombs in the example image below were dropped from 10,000ft and 3.5nm on a steerpoint set at the center of the target and at the ground elevation, without wind conditions or modified altimeter setting. For reference, the tank pictured is approximately 10m in length. The GBU-38 landed approximately >30m from the target and the GBU-54 landed about 15m from the target location (both bombs overshot - the GBU-38 was pickled from the opposite direction). The GBU-54 in particular was observed to make an erratic last second correction that resulted in the overshoot. [ATTACH=JSON]{"alt":"Click image for larger version Name: Views: 0 Size: 721.2 KB ID: 7127552","data-align":"none","data-attachmentid":"7127552","data-size":"full"}[/ATTACH]

Well, that explains a lot: It's not even listed in the manual. Thank you, Shadow! Having it hidden behind RCTRL+F10 as a keybind is pretty bizarre.

Picked up CA on sale yesterday, and... maybe it's just me, but does anyone else find that radar-guided/cued SAMs having to visually acquire and lock aircraft (or spam lock over an area of sky) rather than using the radar to do it to be an incredibly clunky and obtuse design decision?

​I believe he means the line between the upper and lower portions of the MFCDs. Upper portion is the top 5 OSBs, and the lower portion is the bottom 3. ex: https://www.digitalcombatsimulator.com/upload/iblock/199/Screen_200814_013841.jpg​

Great update today, with the horizontal CDU. Thank you!

I have not used this and can't confirm that it works, but: https://www.digitalcombatsimulator.com/en/files/208117/

In my experience, it seems like manual entry really only makes a real difference for WCMDs. Comparing 105s dropped on the same SPI and using the same settings, the one with manually-entered wind data always seems to be more effective than the one without.

Installed mine today, and I'm having the same issue. It only seems to happen when making an abrupt change from diagonal to vertical or horizontal movement.

Thanks for the response!

Glad to hear it! Regarding the bug, do you mean that it's on the DCS end and not the app end?

Liking the app a lot! Let's me stay heads up while working with the A-10C's CDU. A few suggestions: Add an option to add a menu at the top or side of the screen allowing you to "click" and select the active display, as opposed to swiping through them. Add an option to split the A-10C CDU so that it can be displayed horizontally (since it's too tall to practically letterbox). A-10C radio controls. Also, I spotted a minor bug with the A-10C II CDU display on SYS -> LASTE -> WIND -> WNDEDIT -> PG 2/2: The temperature value shown adjacent to LSK R3 is the presently detected temperature, rather than the temperature that you have entered, as shown below.

True, but it's worked fine for me for the past several years. Once we get the ARC-210, I'll be revisiting it, of course. (Or get VoiceAttack/VAICOM so that I don't need to deal with the in-game comms menus anymore.)

I do a combination of WH Throttle controls, keyboard binds, and the mouse. Mic Switch Depress - SRS PTT Mic Switch Up - Discord PTT Mic Switch Forward - VHF AM Menu Mic Switch Down - UHF AM Menu Mic Switch Aft - VHF FM Keypad 1 - Select SRS Radio 1 (VHF AM) Keypad 2 - Select SRS Radio 2 (UHF AM) Keypad 3 - Select SRS Radio 3 (VHF FM) Keypad 7/4 - VHF AM Volume Up/Down (In-Game and SRS, simultaneously) Keypad 8/5 - UHF AM Volume Up/Down (In-Game and SRS, simultaneously) Keypad 9/6 - VHF FM Volume Up/Down (In-Game and SRS, simultaneously) Mouse - Change radio channels, turn radios on, adjust presets, etc. Keypad Plus - In-Game Voice Comms (I have yet to see anyone actually ever use this, so I have yet to actual try it.)

Typo of 42.50 mHz?

I would really like to see this, except for *everything* within the Stats pages. (Not that I mind changing my TGP slew rate every mission.)