already known CBU-97 Burst Altitude

[mukisuki]

Hi all,

Burst Altitude (BA) in the Viper is set standard to 4559ft or something simmilar. Which is not ok with CBU-97. And i can´t change it in the cntl page. Before the update it was ok and set to 1500 ft.

Also with cbu 105 there are some Problems. The range is now as half as before. 

Can you please check on your Vipers, maybe some file gets corrupted at my site.

Thanks

 

Edited April 13, 2024 by mukisuki

[Nealius]

Noticed the same, however actual BA is still 1,500ft regardless of erroneous number on SMS page.

[NineLine]

This should be sorted as the fuse work is completed as listed in the roadmap. Thanks!

[mukisuki]

Sorry, but i am understand  it correct that you took a working system (which was in 2.9.3) where i can set my BA Altitude correct and also throw CBU 105, break it, and "maybe" in 4 or 6 weeks with next update i will get it back working with a new fuse system?

 

My personal finding, thats not how updates should work guys, why not keeping a working system till the new system is ready  

 

 

Edited April 14, 2024 by mukisuki

[Dragon1-1]

It is working correctly, from what I gather, this is just a display bug. FYI, the BA you set on the MFD does not actually affect the bomb, the setting is a physical switch on the casing that has to be set on the ground (something we can't do in DCS yet), and you later set it on the MFD to match, so that the jet provides you a proper solution cue. Since you can't have it at anything other than 1500ft, the setting on the MFD doesn't actually matter AFAIK.

New fuzing will introduce both a way to change the actual BA, and necessitate the proper data entry for it to work.

Edited April 14, 2024 by Dragon1-1

[void68]

Load CBU-97, edit Burst Altitude, Arming Delay and Release Angle. While AD and RA are updated in SMS, BA is set to something like 4631ft. Whatever you enter, it's always the same value. However they seem to burst at the set altitude.

 

What about the malfunctioning (broken in prior patch) Parking Brake switch when flipped by an external device (f.e. Bodnar Board) and what about ejecting with just one keypress (for homepit users with an ejection handle) instead of three? No update yet, no info on when this will be fixed.

 

I don't believe that squashing these bugs requires more than two lines of code.

Edited April 16, 2024 by void68
typos

[BIGNEWY]

thread merged, please keep the feedback constructive and one issue per thread. 

As explained above the new fuse work will give more options once added. 

thank you 

[_SteelFalcon_]

20 hours ago, BIGNEWY said:

thread merged, please keep the feedback constructive and one issue per thread. 

As explained above the new fuse work will give more options once added. 

thank you 

But doesn't that mean, that the current displayed burst altitude, which is totally wrong as compared to the previous patch, is a bug? why is this a wishlist item now?

I agree that the fuzing improvements are a wishlist item. more options etc...

But the displayed burst altitude being completely wrong and totally misleading should remain as a bug tbh.

[mukisuki]

Why you move my problem to "wish" section....

it´s not a wish, i allready had it in the last version of DCS. It was all working before!

[BIGNEWY]

Hi, 

moved to wish list for the variable altitude, before it was incorrectly fixed at 1500 feet

the new fusing in the rearm menu will help with this. 

thank you 

[adriansito123]

So i discovered this when doing some pop up attacks training with the cbu-87's against SAM sites (the first mission of FIWOS campaign) and noticed that the bombs always landed long of the target. After some investigation I saw that i ignored the AD and BA settings of the bomb, which at that time where set at AD 1.000 secs and BA 4921 ft. When i tried to change those settings so they would fit my engagement parameters, the values I entered where ignored, meaning that when i leave the CTRL page and go back to the SMS page the values for AD and BA would still be the same as before (1.000 secs and 4921 ft respectively). I report this as a bug because I've just seen older videos of this exact same procedure working correctly.

I've also tried the same in a simple mission I created to see if it was a mission bug or setting special to that mission but i gathered the same results.

[rob10]

Check out this thread:

 

[adriansito123]

hace 1 hora, rob10 dijo:

Check out this thread:

Thanks man, seems like they are working on it from what I can read. I searched specifically for bugs regarding the 87's and couldn't find this thread.

 

[rob10]

4 hours ago, adriansito123 said:

 

Search function on the forum can be a little hit and miss.  Sometimes your better off to use Google.  And for specific issues it can be worth checking the individual modules.

[DavidL15]

Sort of related problem.  CBU-87/97/105 are dropping OK, but are not deploying submunitions.  Release altitude is at least 5K above the ground & NSTL fuzing is selected

[gonvise]

Hello, I'm sure it's my fault, but Is there any bug currently that could cause me not to be able to change the BA altitude of a CBU-87?

I try to change it in the first mission of "Weasels over Syria", but although I validate that it is 1500ft on the CTL page, when I go back I get it shows 4921ft.

Any idea?

Thanks in advance.

[Tholozor]

Burst Altitudes (for CBUs in general) are getting reworked with the new fuze system, but 4921ft equates to approximately 1500m, so probably just a conversion bug.

 

[dutchili]

@BIGNEWTacview-20240523-130353-DCS-CBU test.zip.acmiY: which yesterday's update BA is set to 300 ft (AGL) but the CBU-97 doesn't burst. Also tried with BA 3000ft, nothing happens. Track attached.

CBU BA issue.trk

[dutchili]

update: when set in ME to 1500 it does work

[JeffreyC]

Been trying to figure out the same problem. Air start did work with 300ft set trying with an air start but not on ramp cold start. I suspect a bug in the new fuse system.

Tested and confirmed setting to 1500ft does work on cold start. Great find for a workaround dutchili

Edited May 26, 2024 by JeffreyC

[FusRoPotato]

Can't configure the CBU-97s. The BA is stuck on a bugged value. Others in a multiplayer setting have reported the same problem. Bombing mode doesn't appear to matter, and changing the values doesn't affect it. It remains frozen at 4291 ft, 1 second. Release angle can be changed only.

Best way to replicate I've seen so far is to load a dry hot start onto a runway, then use the loadout menu to select a TER-9A pack of 3 on pylons 4 and 6.

If you select any other configuration such a singles on 3 and 7, the settings may work correctly. After that, reloading the original bugged loadout may also allow correct settings. Reloading a bugged configuration repeatedly however does not clear the bug.

In addition, if you've noticed, when the settings work correctly, the AD matches 2.23 seconds along with the BA of 1500 ft. When the settings are bugged, the page settings show 2.00 seconds and 1500 ft in the control page, but 1 second and 4921 ft on the selection page and 2.23s/1500 ft in the fuse page of the loadout menu.

Edited June 23, 2024 by FusRoPotato

[Tholozor]

Already known (4921 feet roughly equates to 1500 meters, so probably just a conversion display error):

 

[FusRoPotato]

This should probably be merged then, but it doesn't appear this specific case and reproduction is known. The new fuze settings have already been deployed so it needs to be looked at again. This bug was discovered when the bombs were found detonating far too high and overshooting their drop point by miles so it's not just a display issue. The setting also cannot be changed when this bug occurs and renders the bombs unusable.

What's most likely is that there's a data structure sizing or indexing error and the data that is supposed to fill those settings is coming from a memory location that has the converted default value. The proof is that 2.23 seconds is 1 metric second.

Edited June 25, 2024 by FusRoPotato

[BIGNEWY]

threads merged