BaronVonVaderham Posted May 29, 2024 Posted May 29, 2024 (edited) So today for some reason my F16 was dropping all 10 CBUs at once, even when set to single drop and ripple set to 1. This was on the TDCS EU server. flying an F16 Log attached Track is too big at 113MB Edited May 29, 2024 by BaronVonVaderham
BaronVonVaderham Posted May 29, 2024 Author Posted May 29, 2024 so I tried this again, by restarting DCS, and this time I could drop single CBUs, but this tome they refused to deploy. Attached track and log. This is flying the F16. again no track file thanks to tracks being so fing big. dcs.log
BaronVonVaderham Posted May 30, 2024 Author Posted May 30, 2024 Did another test today. First test today the CBUs were set to 300ft air altitude on the rearm page. Again they did not deploy submunitions. Note, target is at about 1200-1500ft pressure altitude. Second test I set the air altitude at 1500ft on the rearm page. This time CBUs deployed. A little low for my taste, but on target. Conclusion is that air altitude on the rearm page is pressure altitude for submunition deployment altitude. That seems inefficient as you don’t always know the target elevation. I was told the deployment altitude is supposed to be in ft AGL. That’s not the case now, as I need to set pressure altitude ASL. therefore this is a bug.
AndrewDCS2005 Posted June 1, 2024 Posted June 1, 2024 @BaronVonVaderham my understanding is that CBUs are always ASL-driven since they don't have radar altimeters to measure AGL precisely, and are set to atmosphere pressure.
Northstar98 Posted June 1, 2024 Posted June 1, 2024 12 hours ago, AndrewDCS2005 said: @BaronVonVaderham my understanding is that CBUs are always ASL-driven since they don't have radar altimeters to measure AGL precisely, and are set to atmosphere pressure. The Mk 339 fuse on the Rockeye is time-driven (functioning after a specific time after being dropped) and the CBU-87/97/103/105 are radar proximity. Modules I own: F-14A/B, F-4E, Mi-24P, AJS 37, AV-8B N/A, F-5E-3, MiG-21bis, F-16CM, F/A-18C, Supercarrier, Mi-8MTV2, UH-1H, Mirage 2000C, FC3, MiG-15bis, Ka-50, A-10C (+ A-10C II), P-47D, P-51D, C-101, Yak-52, WWII Assets, CA, NS430, Hawk. Terrains I own: South Atlantic, Syria, The Channel, SoH/PG, Marianas. System: GIGABYTE B650 AORUS ELITE AX, AMD Ryzen 5 7600, Corsair Vengeance DDR5-5200 32 GB, NVIDIA GeForce RTX 4070S FE, Western Digital Black SN850X 1 TB (DCS dedicated) & 2 TB NVMe SSDs, Corsair RM850X 850 W, NZXT H7 Flow, MSI G274CV. Peripherals: VKB Gunfighter Mk.II w. MCG Pro, MFG Crosswind V3 Graphite, Logitech Extreme 3D Pro.
KlarSnow Posted June 2, 2024 Posted June 2, 2024 CBU-87/97 and CBU-52, and CBU-99 all have radar proximity detectors in the nose. If you are setting an altitude, it is an AGL altitude, not ASL. If you are not setting that, you are setting a time after release that the weapon opens.
AndrewDCS2005 Posted June 2, 2024 Posted June 2, 2024 4 hours ago, KlarSnow said: CBU-87/97 and CBU-52, and CBU-99 all have radar proximity detectors in the nose. If you are setting an altitude, it is an AGL altitude, not ASL. If you are not setting that, you are setting a time after release that the weapon opens. Ok I meant CBU-99 in my post above and though that FMU-140 is measuring atmospheric pressure and hence the altitude is in ASL. BTW this is why I asked for fuze documentation from DCS in separate thread. Thanks to folks sharing the links, I stand corrected - FMU-140 fuze has a radar, so it should be using AGL altitude - which makes more sense and is more practical for its use. FMU-140/B Dispenser Prozimity Fuze (tpub.com)
Recommended Posts