Zabuzard

As explained in the manual (chapter Mission Editor), the NVGs are there for people who want to make non-historical missions or perhaps a modern conflict, forced to use an old aircraft, or similar. Could also be important for server owners who offer multiple aircraft in a night mission. DCS is a sandbox, so the mission author can decide if NVG is allowed or not for their mission. As you said, NVG were never used on our F4 model within the timeframe it was used by the US.

You got a track or something? It works when tested on our end. That aside, the actual signal is coming from ED plus map metadata. So potentially, if there is actually an issue, we might not be able to do sth about it. But step by step, lets first try to get hands on a short track that reproduces the issue [emoji106]

To be fair, the route tool was added post release. Its not an "oversight" in that sense. But yeah, its on the list :)

Yeah. The main takeaway is that the radar needs to point at the Shrike. Which the SAM has no interest in, it follows you or other aircraft. So that is something you have to keep in mind regarding positioning and similar.

Not necessarily. You have to visuallize the radar beam going out of the SAM station pointing at for example your aircraft. The Shrike needs to ride that beam down, more or less. If you fly elsewhere, the SAM will keep the radar beam on you and your shrike will stop being able to "ride it down" as it now does not sit on the line between you and the SAM anymore. Same happens when the SAM decides to do business with another aircraft that isnt right next to you. Or when it decides to switch to optical tracking, turning off its radar. Or when it sees the shrike and rather turns off their radar last minute to stay alive. There are many cases that result in your missile hitting the dirt.

I believe it was this one:

Yeah, that is correct. Some in-progress pics of the F-14B(U) have (accidentally) been shared a few months ago in various channels. Shortly after the team has confirmed to work on this module in Discord. There is not much more to it yet, as the team focuses on finishing the Early F-14A first (which is part of the F-14 module you guys purchased). The latest "official statement" to the B(U) is:

Yeah exactly. The fix is done and will be available as soon as new Phantom builds are published and make it your way. That has not happened yet but will hopefully soon be the case

That will be difficult to say without a track or video. From my experience watching people debug user reports regarding Shrikes almost on a daily base, I can say that the weapon is very tricky to use and most user reports end up being incorrect usage on their side. For example the SAM site turning off their tracking dish or tracking another player instead. Or you (or whatever the SAM targets) not flying in a way anymore that the shrike rides down the radar beam anymore but sidelobes instead... really complex topic.

Does it work if you disable this setting again? The soundscape is usually optimized and mixed for it being off. Other users have not mentioned such a problem yet, so sounds odd.

Yeah, also works for me. Looks like user error with your procedure. I would suggest following the procedure described in our manual step by step and if it doesnt work still, you can provide a track file or video or just write down a list of your steps so others can check what you might be missing

You would need to properly put out the fire. I am not aware of a way to trigger this magically. Fire goes out when you repair the aircraft (maybe this can be triggered?) or fly fast enough for some time (practice testing: around 10-15s at 0.8 - 1.0 mach). Depends on a lot of conditions of course. Shutting the engine down will not help a lot because once there is a fire it will burn through the engine and set other parts on fire as well. It does not need the fuel to continue burning. It can help in the early stages of some fires when you only got an OVERHEAT but no FIRE lamp and potentially also only see smoke instead of fire coming out of the engines.

What exactly do you mean by "blocks"? You cant select the weapons anymore or they dont appear visually? If latter, only in the mission editor preview or also in-game? The mission-editor preview is fully ED controlled and hence sometimes differs from what it will actually look like in-game. If it works in-game, it would likely be sth for ED to look into.

We have seen the report and it was added to the list [emoji106]

Care to elaborate? I am pretty confident that the majority of users would claim the exact opposite to what you just stated. Very unfortunate if you think this way and if you provide some details I would be happy to clarify :) That said, if you want to critize the module perhaps make your own thread instead of going off-topic in OPs thread, cheers.

Yes

The trimming behavior is implemented correct with respect to real life behavior of the aircraft. You gotta do very short taps, it was known to be wonky. The response by aircrew usually was to "just fly the aircraft". That said, there is a Special Setting available to counter this especially for people who have hardware that physically cannot send super short impulses. Like, for some joystick even if u you click something only for a very short amount of time, the actual impulse send by the hardware to the system is much longer. I believe it was this setting: https://f4.manuals.heatblur.se/dcs/special_options.html#stick-neutral-position-smoothing-period (Trimming in the F-4 acts as a modifier of the lever that the bellows use to pull the stick aft as opposing force to the bobweights who push the stick forward, and is hence heavily dynamic and dependent on factors like speed and G)

(the AI, in contrast to the player controlled module, is not slated after the EF and will come whenever its done - it is being worked on)

You might want to checkout: https://github.com/Munkwolf/dcs-community-keybinds If they are present in this mod, it will end up on the F-14 as well as soon as we come around to integrate the mod like we did for the Viggen already, cheers.

When there is some actual big news, we usually share it on all our channels (Discord, this forum, Facebook, Instagram, ...). Those are just general newsletters called "dev-shoutouts" and is mostly intended for people who want to follow HB a bit closer and stay in touch with the devs - which is what Discord is generally used for. Until then everything you may read essentially boils down to "we are working on it, its there when its there".

We currently cant provide ETAs, sorry. But its ofc coming out eventually :)

That negativity wont get you the fix sooner either. The team and ED are working hard on it already. As explained in the other thread on the topic, something ED did in the last update broke it and it seems not so easy to get it back working. Some other aircraft and weapons are apparently affected as well.

Yeah, so the first one is definitely him still being in FOCUS mode. I suppose he did not understand that this particular bandit died. The "bandit is down" callout isnt coming from his radar code but is a visual observation. So his radar logic likely thought that the bandit could still be there, keeping it focused to get it back on screen. You can just get him back to standard scan by using the context actions - autofocus only happens on targets actually on the screen, so he will not focus thin air. The second one, not sure whats going on there specifically. Possibly he did not understand that you left CAGE mode yourself instead of using the context actions. You can enable the Jester Console (RCTRL+L) to get some insights into what he is doing. I would also suggest to hit context action to get him back to standard scan. Note that you can have Jester leave CAGE mode for you by using the Context Action as well - no need to rotate that knob yourself (potentially losing the target visually doing that). If you can reproduce this a track would be great, then we can have a deeper look. Cheers

Just to make sure, while this might be your personal estimation, such a statement has not been made by any official sources. There is no correlation betwen the two modules in any way. I cant speak for ED and their F-35, but the EF releases when its done as simple as that

I can check them tomorrow, thanks. But what you are describing sounds like focus mode and not general target search. You can use context action double click to leave that (and possibly disable autofocus).