Zabuzard

This is a known issue, thank you.

This is a rare DCS engine bug that we have seen reported a few times since release. Users reported that running a DCS repair and/or getting rid of certain unofficial mods repaired the issue for them. So Id suggest trying out that :)

The WRCS will do the math dynamically. The problem is that the drag coefficient will be slightly wrong. Meaning that the WRCS will calculate with incorrect drag values for your weapon. For low drag weapons the consequences will be less severe, and it ofc depends on what kind of profile you are flying.

DT requires input of the drag coefficient (and a working INS). Drag coefficient depends on release params like speed/alt. To which extend usually depends on the type of bomb used, as well as how extreme your planned profile is. So some form of rough preplanning is required for DT as well. But in many reasonable cases the default drag coefficient would be so close to the real drag coefficient that you would hit as long as you do not deviate heavily from the plan - making it a rather flexible and convenient mode to use.

I dont think we ever put the blame on the users. In fact, I am trying to use every situation I can to make sure everyone (especially in our team) understands that user mistakes are typically due to lack of good documentation/tutorials/reference material. So while its ultimately the users mistake, the best way to improve a situation is to improve the teaching material. Im not sure why ur reaction is so heated. I am sorry if you perceived it differently. Please note that the manual is open source, everyone in the community (you included) can edit it and contribute and improve it for the benefit of every user. We are one big team[emoji106] The explanation of the "Bomb on Target" option shown in the Bombing Tool is explained by the manual in the Bombing Tools chapter: https://f4.manuals.heatblur.se/dcs/bombing_computer.html#bomb-on-target The manual also has a global search function, enter "Bomb on Target" and it will lead you there, cheers.

Yes to both. But it also depends on the radar selection in the WSO pit. Like, if the radar is turned off, selection of this switch wont do much. In practice, for most DCS players it is probably best to just leave it on ON. But there are of course situations in which it might be meaningful to have it off (or standby) while the radar itself is still turned on. Also relevant for ground tests (in particular IRL). Some details here: https://f4.manuals.heatblur.se/cockpit/pilot/weapon_management.html#radar-missile-power-switch More here: https://f4.manuals.heatblur.se/systems/radar/general_operation.html#klystron

Thanks, we will have a look at whats going on with ur sorties. Something I noticed at a quick glance is that there might be a possible confusion on what "Bomb on Target" in the Bombing Tool means. It looks like you guys might think it means how many bombs you want to drop. But it instead means which bomb of your pattern you want to hit the target directly, shifting the bombing pattern forward or aft. For example if you drop 12 bombs and want it to be centered around the target you would enter 5 or 6 as the "Bomb on Target". Consequently, if you enter 12 when dropping 12 bombs, the majority of your bombs would essentially land short (with the last bomb hitting the target). Cheers EDIT: I think I confused this thread with another. We will look into your tracks, thank you. Ill let the above stay though, so that it helps any readers who might have confused Bomb on Target

Jester does that already. But only in modes where it is easy for him to know when you are about to drop bombs. Namely modes where you hold down the Bomb Button for a longer time, e.g. Laydown mode. For other stuff its ofc planned to add more utility, but it will be more difficult.

I was under the impression that we have to do sth extra to support it, cause thats what EDs message implied. But if it works already, that's great :)

Yeah, it has some safety margin. We found some tests that hint at roughly 3min. With seat stuff they are usually super extra careful, as its your only chance of surviving in a really bad situation. So you definetly don't want your seat to catch fire or something.

:D > The seat height mechanism may only be used for max 30s within 10min

If you can read german, move your camera on top of the seat and have a look at whats written there :D

Known issue, cheers

The tracks do work if the person who replays presses pause and then enters the same details into the HB UI as the user did originally doing the real session. So track+acreenshot is usually enough to replicate it :)

then there is either a bug or a user error. perhaps u can share a video or track+screenshot of bombing table :)

Its not a timer. It uses your INS vector to accurately compute that you travelled the entered release range. That means that you for example do not have to fly the prepared altitude or speed, you can fly up and down, as well as change the throttle during your attack run while you hold down the bombing button. You should meet the planned profile at the moment of release though, so that your entered Drag Coefficient matches. In regards to reticle vs VIP, both are valid. They will both match. When you are above the IP, your reticle will be on the target and vice versa. So pick whichever is better in your particular situation.

This bug is due to how MT changed rendering order on the DCS engine for this particular setup. It will not be fixable easily and because we plan on replacing the UI with the new UI (see Phantom) for the long term anyways, we likely will not dump hours into trying to bend this back to working.

Its a bug in the night lighting art.

nope

Lmao, Ill follow up on it, thanks.

Fixed

Fixed

heatblur.se is down since yesterday, we are repairing it. Cheers

Aye, we are on it. Cheers

Cobra said that he will share concrete news on whats the deal with the BU later this year. Until then we have to wait