correct as-is New fuze option - editor and cockpit

[dmatt76]

Despite new fuze options in mission editor, you can still edit them in the cocpit while inflight, like burst altitude of cluster bomb, arming delays etc. Do they override the mission editor options or will not work? I've noticed that some fuzes add more options but even if you don't choose the FMU-152, you can still change some arming delays in the cockpit. So, what you should really set on the ground and what should be available also on MFD?

[razo+r]

From what I understand you chose what you want to use on the ground and then once inflight you tell the computer which fuze you have loaded for proper release and impact calculations. 

[SeeYouAtTheMerge]

6 minutes ago, dmatt76 said:

Despite new fuze options in mission editor, you can still edit them in the cocpit while inflight, like burst altitude of cluster bomb, arming delays etc. Do they override the mission editor options or will not work? I've noticed that some fuzes add more options but even if you don't choose the FMU-152, you can still change some arming delays in the cockpit. So, what you should really set on the ground and what should be available also on MFD?

For the bombs without the FMU-152, the cockpit options for arming delay doesn't actually change the arming delay of the bomb, its just telling the jet what the arming delay of the bomb is to compute when to show the LOW symbology 

[dmatt76]

I have the first, simplest fuze, set 4 and 0 in mission editor and still can change it to 2 and 8 inflight. Cluster - set 300 in ME, then can change it inflight to 1500 or else. I wonder is that correct and new fuzes just give us option to delay detonation to 24h and air burst for GP bomb or something should be not available inflight with the old fuzes...

[Furiz]

1 hour ago, dmatt76 said:

I have the first, simplest fuze, set 4 and 0 in mission editor and still can change it to 2 and 8 inflight. Cluster - set 300 in ME, then can change it inflight to 1500 or else. I wonder is that correct and new fuzes just give us option to delay detonation to 24h and air burst for GP bomb or something should be not available inflight with the old fuzes...

You can edit in cockpit but it will not change anything on the actual bomb, unless you have FMU-152 on the tail. The edit options in cockpit is to tell the onboard computer what configuration you have on the bombs so it knows what symbology to show and when.

 

This is why we need these kind of updates to be followed with manual update. People get confused.

 

[dmatt76]

7 minutes ago, Furiz said:

The edit options in cockpit is to tell the onboard computer what configuration you have on the bombs so it knows what symbology to show and when.

I don't get that...

What you set in Mission Editor is on the MFD, in the cockpit - so what do you want to tell the computer?? It seems to know everything already

Edit means "change" settings and you can still change them inflight - but is it a bug or "correct as it is"....

Edited May 28, 2024 by dmatt76

[Furiz]

9 hours ago, dmatt76 said:

I don't get that...

What you set in Mission Editor is on the MFD, in the cockpit - so what do you want to tell the computer?? It seems to know everything already

Edit means "change" settings and you can still change them inflight - but is it a bug or "correct as it is"....

 

No, you can't change them in flight, except for the FMU-152 tail fuze.

In flight you can only adjust settings in the aircraft to match bomb settings you made on the ground or mission editor.

[dmatt76]

4 hours ago, Furiz said:

No, you can't change them in flight, except for the FMU-152 tail fuze.

In flight you can only adjust settings in the aircraft to match bomb settings you made on the ground or mission editor.

I've just showed you on the screenshots that you can change it... So are the changes a bug? Don't matter anyway? Will be removed in future updates?

[Furiz]

43 minutes ago, dmatt76 said:

I've just showed you on the screenshots that you can change it... So are the changes a bug? Don't matter anyway? Will be removed in future updates?

No it is not a bug,

onboard computer does not know what ground crew has set on the bombs, it only recognizes the bombs.

So you need to tell the computer what setting are set on the bombs. Thats why you can change settings in the CNTL menu.

But it is not to set up the bombs, it is already done on the ground instead it is only to tell the onboard computer what settings are set on the bombs.

I don't know to say this in more simple way.

[dmatt76]

Ok, I will try to make it simple YES or NO questions

I set in ME cluster bombs with airburst 1200 ft. I click fly and I can see on MFD my CNTL setting 1200 ft - precise as I set in ME.
- So I assume my computer already knows all the settings? I don't need to insert the same settings again to confirm that?
- Still, I can edit on MFD the airburst altitude to i.e. 1500 ft. So will this mess with the attack, because bombs are still set to 1200 but the computer is set to 1500ft?

The same with GP bombs - I set in ME M90E4, arm delay to 2 sec and tail fuze AD to 2 seconds
- still I can change the arming delays inflight on MFD to i.e 4 seconds. So does it mean it wont affect the bombs? They will still arm after 2 seconds? (I know that Arming Delay really doesn't matter in DCS but as a content creator of detailed guides I will have to explain how it works ;))
- even with FMU-152 as tail fuze you cant change on MFD function delay on GP bombs - only on JDAMs - ist that correct or WIP?


 

Edited May 29, 2024 by dmatt76

[Moonshine]

44 minutes ago, dmatt76 said:

- So I assume my computer already knows all the settings? I don't need to insert the same settings again to confirm that?

yes, no need to insert it again, just "double check" to make sure it matches what you set it as via the ME or the Rearm/refuel menu

44 minutes ago, dmatt76 said:

- Still, I can edit on MFD the airburst altitude to i.e. 1500 ft. So will this mess with the attack, because bombs are still set to 1200 but the computer is set to 1500ft?

exactly, it will mess with the attack as it calculates release parameters that your bomb does not have

46 minutes ago, dmatt76 said:

- still I can change the arming delays inflight on MFD to i.e 4 seconds. So does it mean it wont affect the bombs? They will still arm after 2 seconds? (I know that Arming Delay really doesn't matter in DCS but as a content creator of detailed guides I will have to explain how it works ;))
- even with FMU-152 as tail fuze you cant change on MFD function delay on GP bombs - only on JDAMs - ist that correct or WIP?

havent tested or verified that, however the post in the viper mini update mentiones that the only fuze you can change mid air is the FMU-152 tail fuze which exists for GBU-12 and GBU-38. so changing those values should carry over to the bomb on the jet 

[dmatt76]

Thanks!
FMU-152 is also selectable for Mk82 etc but I've already seen comments that "what is available where" is not correct now and will be updated in June patch

Edited May 29, 2024 by dmatt76

[Rac3rX]

I don't understand why BA is even adjustable onboard if it messes with the attack profile. You set a SPI, and the bomb should land there. Now if you're setting a release angle for a toss, that makes sense (as you'll need to follow the PUC). 

[Dragon1-1]

BA is adjustable because IRL, these parameters are loaded from the DTC, which is itself set up before flight. If, for instance, you tell the chief to make a last minute adjustment to your bombs' BA while sitting in the cockpit, or you realize, while starting up, that you forget to change the DTC setting from your usual one, you probably won't have time to run back to the briefing room and update your DTC. In such cases, you'll need to do that from the cockpit. The jet doesn't magically know those settings IRL, and in DCS, it only does because we don't simulate the DTC yet.

[Rac3rX]

Understood, but it seems the BA has an effect (since the last update) on release timing: that shouldn't be. If you're below the set BA, the bomb should burst immediately, after the delay fuze is reached. 

Edit- yes, BA would adjust release timing, but it should do so in relation to the SPI, not moving the SPI based of BA

Edited May 31, 2024 by Rac3rX