Jump to content

Recommended Posts

Posted

I'd like to report a bug that seems to be occurring since the fuze update.

When using Mk82s, we usually set the fuze settings before take off, for example nose, inst, ret with qty, mult, and int.

It seems that several of us during flight have found that these settings seem to be resetting themselves (some more than once) so that we have to re-input them mid flight.

This is happening to several of us during multiplayer missions.

Posted
14 hours ago, Lord Vader said:

Hi all.

Please include a track replay with a short flight for our analysis.

Thanks for understanding. 

Hi, we have just tested the issue out tonight and the same thing happened. I have been able to identify the exact moment it happens.

So, during normal start up I select the mk82 snakes on the stores page and change the fuze settings. For example to Auto, nose, inst, ret. The on the UFC select qty 4, mult 1, int 80. That all seems fine.

In our loadout we have a centreline tank. So I set bingo to tanks dry 10200.

Following all the normal start up procedures, I take off and fly the route. I then arm the master switch and A/G. The Mk82s are live. Then when the bingo call comes, I ensure the centre tank is selected and jettison. At this moment the 82XT becomes crossed out. I press OSB5 to deselect 82XT, the press again to reselect. It is at this point that all of the fuze and bomb settings reset.

This has happened to several of us this evening.

I have added a track file for your perusal. This was a simple straight out flight until bingo and jettison. Hope it helps.

fuze issue.zip

  • ED Team
Posted

Ah! Ok, the fuel tank jettisoning creating issues with ordnance is a known issue. We're trying to fix it as soon as possible internally. 

We're sorry for the inconvenience.

  • Thanks 1

dcsvader.png
Esquadra 701 - DCS Portugal - Discord

Posted
12 hours ago, Lord Vader said:

Ah! Ok, the fuel tank jettisoning creating issues with ordnance is a known issue. We're trying to fix it as soon as possible internally. 

We're sorry for the inconvenience.

Since updating to the latest patch this now appears to be fixed. Thanks.

  • Recently Browsing   0 members

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