MBot Posted July 31, 2016 Share Posted July 31, 2016 The CBU-52 bomblet patters seems too small. This is the drop profile used: Notice fuze function time 4.0 sec (which corresponds with what we have in DCS), fuze function altitude 1800 ft and impact patter diameter 692 ft. This is the drop with ok parameters. Impact pattern about one runway width. Runway width is 200 ft. Bomb pattern diameter should have been 700 ft. Link to comment Share on other sites More sharing options...
MBot Posted July 31, 2016 Author Share Posted July 31, 2016 Arg, I just saw I did a little mix-up with the numbers, but it doesn't greatly change results. Just tried again with a 15° dive KIAS 540/KTAS 560 drop at 2900 ft (100 ft low). Bomb opened after 4 sec. at 1900 ft, 100 ft above planned height of burst (expected it to open 100 low at 1700 ft). Pattern diameter was again about 200 ft. Link to comment Share on other sites More sharing options...
diditopgun Posted July 31, 2016 Share Posted July 31, 2016 (edited) It's well what I have thought... And you prove it. Good job ! :thumbup: Edited August 2, 2016 by diditopgun [sIGPIC][/sIGPIC] Intel I7 8700K / RTX 3080 / 32Go DDR4 PC21300 G.Skill Ripjaws V / MSI Z370 Gaming Pro Carbon / Cooler Master Silent Pro Gold - 1000W / Noctua NH-D14 / Acer XB270HUDbmiprz 27" G-synch 144Hz / SSD Samsung 860EVO 250Go + 1To / Cooler Master HAF X / Warthog+VPC WarBRD / Thrustmaster TPR / Track-IR v5 + Track Clip Pro / Windows 11 64bits. Link to comment Share on other sites More sharing options...
Azazel Posted August 1, 2016 Share Posted August 1, 2016 Well done, about 1/3 of what it should be. My Rig: EVGA GTX 1070 x 2 | EVGA x58 SLI classified | i7 X 990 CPU | 24 GB RAM | Windows 10 Home 64 bit| Track IR Pro | CH Fighter Stick | CH Throttle | CH Pro Pedals | [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
OutOnTheOP Posted August 5, 2016 Share Posted August 5, 2016 This problem is also affecting the Mk20 on the Mirage2K; it might well be an ED weapons coding issue rather than a Belsimtek module coding issue. Either way, it is incredibly frustrating on both modules. I would be interested to see how altitude of release actually affects the in-game impact pattern; on M2K it doesn't seem to have any effect at all: release from 3000ft AGL or 20,000 ft AGL seems to have exactly the same pattern size. It's as if the submunitions just stop spreading out after a certain point. Link to comment Share on other sites More sharing options...
Sarge55 Posted August 6, 2016 Share Posted August 6, 2016 Doesn't matter what altitude you drop the bomb at, it is the "burst" altitude setting which dictates the bomblet pattern/size. Unless of course you release below the burst altitude. [sIGPIC][/sIGPIC] i7 10700K OC 5.1GHZ / 500GB SSD & 1TB M:2 & 4TB HDD / MSI Gaming MB / GTX 1080 / 32GB RAM / Win 10 / TrackIR 4 Pro / CH Pedals / TM Warthog Link to comment Share on other sites More sharing options...
OutOnTheOP Posted August 13, 2016 Share Posted August 13, 2016 (edited) Doesn't matter what altitude you drop the bomb at, it is the "burst" altitude setting which dictates the bomblet pattern/size. Unless of course you release below the burst altitude. If you're using a radar-fuzed CBU like CBU87, CBU97, 103, or 105, sure. But Mk20 and CBU52 don't have a radar proximity fuze. Instead, they have a time delay fuze. They dispense at a pre-determined time after separation from the aircraft, NOT based on height above terrain. Therefore, the higher the altitude of release, the higher the altitude of CBU opening for Mk20 and CBU52. The Mk20 was retrofitted with an FMU-140/B radar proximity fuze at some point, though. I'm pretty sure CBU-52 never was. Either way, the variants modeled in DCS at the moment are time-fuzed. That *should* mean that higher releases result in wider dispersion of bomblets. But right now, it does not. So, something is broken in the weapon modeling. Edited August 13, 2016 by OutOnTheOP Link to comment Share on other sites More sharing options...
Svend_Dellepude Posted August 14, 2016 Share Posted August 14, 2016 ... So, something is broken in the weapon modeling. Not implemented is my guess. [sIGPIC][/sIGPIC] Win10 64, Asus Maximus VIII Formula, i5 6600K, Geforce 980 GTX Ti, 32 GB Ram, Samsung EVO SSD. Link to comment Share on other sites More sharing options...
OutOnTheOP Posted August 14, 2016 Share Posted August 14, 2016 Not implemented is my guess. "It isn't done yet" and "it's done wrong" both result in broken modeling. What it seems like to me is that the bomblet dispersion is done as a single "entity", where each bomblet disperses out on a scripted path, and the whole formation then moves as a unit, rather than having each bomblet individually tracked along their trajectory the way cannon shells are. Once the bomblets reach the maximum scripted dispersion, they just fall in formation. Unfortunately, that means they never get very far apart. Link to comment Share on other sites More sharing options...
Holbeach Posted August 15, 2016 Share Posted August 15, 2016 The bomblets form a shallow, rather tight disc and not spun off sideways as the real ones are, so you end up with a shotgun, or torch pattern hit. The only way to spread them, is lengthwise, using a low flat approach. You can just make them out in this sequence from a video. ASUS 2600K 3.8. P8Z68-V. ASUS ROG Strix RTX 2080Ti, RAM 16gb Corsair. M2 NVME 2gb. 2 SSD. 3 HDD. 1 kW ps. X-52. Saitek pedals. .. Link to comment Share on other sites More sharing options...
ED Team cofcorpse Posted November 11, 2016 ED Team Share Posted November 11, 2016 Thank you for feedback! We'll look into this issue and will correct Link to comment Share on other sites More sharing options...
MBot Posted February 4, 2017 Author Share Posted February 4, 2017 Any news on this? CBU-52 are still almost useless, while it should be one of the primary A-G weapons of the aircraft. Link to comment Share on other sites More sharing options...
Pipe Posted February 15, 2017 Share Posted February 15, 2017 Yes please...any news on this would be great Thx i7 4770k @ 4.5, asus z-87 pro, strix GTX 980ti directcu3oc, 32gb Kingston hyperX 2133, philips 40" 4k monitor, hotas cougar\warthog, track ir 5, Oculus Rift Link to comment Share on other sites More sharing options...
Vlerkies Posted February 20, 2017 Share Posted February 20, 2017 CBU's work just dandy on a A10C, box of matches dropped into a pond with the F5E, hopefully an oversight and a quick fix. Thermaltake View 91, Z390 Gigabyte Aorus Ultra, i9 9900K, Corsair H150i Pro, 32Gb Trident Z 3200, Gigabyte Aorus Extreme 2080ti, Corsair AX1200i, Warthog A-10 Hotas, MFG Crosswind pedals, TiR5 Pro, HP Reverb Pro Link to comment Share on other sites More sharing options...
Pipe Posted July 18, 2017 Share Posted July 18, 2017 Thank you for feedback! We'll look into this issue and will correct Still waiting for this correction!.....thx i7 4770k @ 4.5, asus z-87 pro, strix GTX 980ti directcu3oc, 32gb Kingston hyperX 2133, philips 40" 4k monitor, hotas cougar\warthog, track ir 5, Oculus Rift Link to comment Share on other sites More sharing options...
Dino Might Posted July 20, 2017 Share Posted July 20, 2017 Question: Should a CBU-52 with pattern coverage on a Shilka be able to kill it? Link to comment Share on other sites More sharing options...
MBot Posted August 8, 2017 Author Share Posted August 8, 2017 We would appreciate some developer feedback on this. Link to comment Share on other sites More sharing options...
ST0RM Posted September 5, 2017 Share Posted September 5, 2017 Bump. CBUs are still unusable. Link to comment Share on other sites More sharing options...
ST0RM Posted September 12, 2017 Share Posted September 12, 2017 Bump. Or will working CBU-52s be a payware addon? Link to comment Share on other sites More sharing options...
ST0RM Posted October 12, 2017 Share Posted October 12, 2017 Bump. Seems this is being ignored. Link to comment Share on other sites More sharing options...
Nooch Posted October 12, 2017 Share Posted October 12, 2017 I see his baro altitude is 3000 ft but the airfield could be above sea level. So it might have a noticeable impact on the results here. I don't know, just suggesting. [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
MBot Posted October 12, 2017 Author Share Posted October 12, 2017 I see his baro altitude is 3000 ft but the airfield could be above sea level. So it might have a noticeable impact on the results here. I don't know, just suggesting. Target elevation was just 60 ft, so neglecting. Link to comment Share on other sites More sharing options...
cicimicikiller Posted October 24, 2017 Share Posted October 24, 2017 Still not fixed, first time reported 31.7.2017 Smash 1-1 | Hawk Link to comment Share on other sites More sharing options...
MBot Posted October 24, 2017 Author Share Posted October 24, 2017 Still not fixed, first time reported 31.7.2017 2016 ;) Link to comment Share on other sites More sharing options...
johnv2pt0 Posted November 20, 2017 Share Posted November 20, 2017 For anyone interested in this thread, Belsimtek has responded: https://forums.eagle.ru/showthread.php?t=195293 Basically, all bugs that they know about are not going to be addressed until they are done with their part of the F-18C module. Don't expect anything soon... Link to comment Share on other sites More sharing options...
Recommended Posts