Jump to content

Recommended Posts

Posted

The CBU-52 bomblet patters seems too small.

 

This is the drop profile used:

 

attachment.php?attachmentid=145537&stc=1&d=1469962572

 

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.

 

 

attachment.php?attachmentid=145533&stc=1&d=1469962041

 

This is the drop with ok parameters.

 

 

attachment.php?attachmentid=145534&stc=1&d=1469962041

 

Impact pattern about one runway width.

 

 

attachment.php?attachmentid=145535&stc=1&d=1469962041

 

Runway width is 200 ft. Bomb pattern diameter should have been 700 ft.

Screen_160731_124153.thumb.jpg.162b2875cde75cb041da022f31ff7c61.jpg

Screen_160731_124259.thumb.jpg.6318c76f441a3e000491b9f62234e5b2.jpg

Screen_160731_124322.thumb.jpg.f1d4642d9b8b7dd886a757b2c36b4ce5.jpg

cbu52profile.thumb.jpg.bfaa341aac715b3f4eb094fbb7ea2d5f.jpg

Posted

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.

Posted (edited)

It's well what I have thought... And you prove it. Good job ! :thumbup:

Edited 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.

Posted

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]

Posted

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.

Posted

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

Posted (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 by OutOnTheOP
Posted
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.

Posted

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.


..
 
  • 2 months later...
  • 2 months later...
  • 2 weeks later...
Posted

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

Posted

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

  • 4 months later...
Posted
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

  • 3 weeks later...
  • 4 weeks later...
  • 5 weeks later...
Posted

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]

Posted
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.

  • 2 weeks later...
  • 4 weeks later...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...