Zabuzard

Fixed the issue. Available with the next build, cheers Looks like DCS changes lead to the CATM not reporting "is infrared seeker" in the API anymore. So our F4 code didnt recognize it as Sidewinder variant anymore.

Mh, looks like the files you attached are "not available" anymore.

Try out your livery with an AI, I think it would work because with AI aircraft barely any of our code is executed. Its almost exclusively ED code then. In which case nothing would be fighting your choice of draw_arg. And yes, no workaround available. Id offer to just make a quick draw-arg that hides the pilot body that isn't used/overwritten by any code. But im not an artist, so this is sorta out of my domain. Ill bring it up though, maybe it's just a 5min thing :)

For an AI or player controlled aircraft? If latter you have the HB code of the F4 fighting your livery setup. The livery will set the draw_args only once but the F4 code will attempt to set them constantly in order to correctly represent the ejection sequence state (which these draw_args are actually used for). So your choice of values is then overwriten.

Looks like this, so potentially okay-enough for the use case:

Sidewinder issue fixed, available with next build. Front-Aspect seems to work again as well from a quick test.

Sidewinder issue fixed, available with next build.

Sidewinder issue fixed, available with next build.

Sidewinder issue fixed, available with next build.

Sidewinder issue fixed, available with next build.

Just FYI in case it wasnt clear, this subforum (DCS: Eurofighter) is not referring to any user made mod, it refers to the full fidelity module that Heatblur is currently developing

aaand fixed, available with the next time HB uploads a build to ED the trigger signal was correctly send to the A2A weapons but the pylon wasnt armed.

It will not be included in the existing deal, the extra work is quite massive in comparison. Details are unclear at the moment as the B(U) is still out a bit. Focus currently lies on the Early-A. There will be more time to talk about the B(U) later, cheers.

That would be unrelated to this thread though. Here it is about replays/tracks. When you say the TGP shakes, I am going to assume you mean the TGP on the pilots screen only? That is expected behavior, the TGP is computed on the WSOs computer and results are synced to the pilots machine, while it is smoothed out on their machine locally. This causes slight "jumping" as the pilots machine receives the new data of where the TGP is looking at from the WSOs machine. There is no way around that on a technical level, that is just the effect of your and your friends ping.

Lol, that is an interesting observation. Something for the others to check in their tracks as well, I guess

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.