TobiasA

Ah nevermind, that issue is already reported but I missed it.

When switching modes, the radar will not return to the scan width it had before, which would be the expected result. Instead, it always falls back to A1 in NAV or A6 in MRM. To reproduce, simply switch MRM and back to NAV or vice versa, switching the azimuth scan value in between. The radar should remember the scan volume for each mode independently, which it does not since the latest patch. In the attached track, I am using DGFT and MRM override and switch back to NAV in between. AG / NAV works as well to show the issue. F-16_radar_mode_switching.trk

Any updates on this?

Well you could read on the HB discord that the cockpit got a complete overhaul. We haven't seen any overhauled cockpit yet. We have seen a pretty nice 3D model though.

I think it happens when someone commands TDOA while a TDOA is already ongoing. TMS left resolves the issue in some cases. I don't know if it is the same problem though.

Yes, but there is TrueGrit as well. I don't know who the main developer is, but TrueGrit is only working on the Typhoon.

The one thing I really want to know is if it's the multiplayer crowd that owns the most modules, or if it is people playing singleplayer. I bought maps I had no interest in only to be able to participate in group events. But then, we know that the vast majority of DCS players are mostly single player oriented... Anyway, the people buying the Eurofighter are probably mostly already in DCS, and everyone buying any Heatblur module has a high risk of buying all of them... Which is good for DCS as a whole.

Yes, but I doubt that the majority of the people that get into DCS and can afford it stop after a few modules. However, we don't know and nobody will tell.

I know no one that only owns one module. Just saying. Most of them have a ton of modules but only fly like 20% of them regularly. Like I do with my strike eagle...

I'm not suppressing any questions, I am saying that you won't get an answer, and I already named the reasons for that. Just remember, the second it is written here, Reddit will have a screenshot of it and the storm will rise. I will never try to suppress this question, as I am very well interested in the EF and it is my most anticipated module besides the Tornado, even more anticipated as the possibility to see my hometown in DCS.

It's because they got one hell of a storm for the Phantom being delayed... They made it very clear what their plan was, the plan didn't work out due to some UI issues, and then it got released several months later and people were utterly p***ed. Some of them took a week off and flamed HB for destroying their holidays. It's just the consequence of those actions.

I had the same question. And I would like to have an answer. The answer I got when asking it was "I can't tell anything about the release date of another developer" and "we are working on it" and "still a lot of development to do". However, I don't think that analysing that one sentence there word for word and grammatically analyse it about in what reference the words are doesn't bring an answer to that question. The one thing that would bring an answer would be if HB would say "We will release it in Q3/2025" or something, but I'm afraid that this won't happen. However, the AI Draken that was teased for only a second or so, will most probably be released in 2025... I'm not losing my hope. But an answer to that question is not at reach, and I think it was probably intended to tone down the Eurofighter hype train.

You all are interpreting NineLines words like people read the book of revelation. Nobody knows, and the one who knows won't tell. We have seen quite a few shots indicating that the EF already flies, with moving control surfaces and other features. While the F-35 hasn't been started yet. And to be honest... It takes like half a year to develop the sniper pod, what makes you believe that the F-35 really will be ready in 2026? I personally think it is unlikely. The EF is ahead in terms of development time, even though the video indicates that the C-130 is way closer to release. The truth is that nobody knows. But I am pretty sure that Heatblur is very careful to not repeat the F4, being delayed over and over due to issues with newly introduced features. They got a lot of hate for it. I am pretty sure they will come around with EA all of a sudden when it is ready, probably only releasing tutorials just a few weeks before. And not drop a word before to avoid toxic attacks from the community. We reap the consequences of our own actions.

I looked it on the mobile and I guess I got a few things wrong there. Still a lot of Eurofighter footsge up there.

Guess I should not have watched it on the mobile...

There was a HUD, 3:15

As people tend to interprete the F-35 FAQ that the Typhoon will release after the F-35 in 2026, would you share this opinion or is there hope for a release in 2025? I would count "No date yet" as not 2025. However, I am really looking forward to this module and was very happy to see it featured in 2025 and beyond, with an obviously working 3D model, beautiful liveries, working weapons, a HUD and probably even working multiplayer as I saw two EF on a tanker with a third one behind it. I would absolutely appreciate updates on the current state, but I also understand if you do not want to share more yet.

My guess is that pre-order starts. It's been a year after the Phantom, I think.

I will try. I think it'll be possible with that description, no need for a track. Thanks!

Can someone of you provide a track? I tried loaded barrel rolls with asymmetrical loadout in high altitude, but I can never get into a deep stall. The nose comes around a bit and then I let go of a the stick and it settles itself. I am genuinely interested in how you depart. Don't get me wrong, I believe you but apparently I am doing it wrong.

I have never spoken to a real Viper pilot, so I can't tell. I just haven't been able to depart the F-16 yet.

It seems correct though.

I need to try that.

I haven't been able to enter one yet. But I have seen people getting into one.

Yes, I do have the module and I am flying it a lot. Probably a few hundred hours by now. Yes, I think the pitch ladder is readable to a realistic amount. Yes, I understand what you showed in the video. No, I was not replying to you but to the one above me (whom I quoted). And it was about overlapping datapoints (or pictures, in this case) on different frequencies which is part of my daily work. But since you want to discuss it... I think it is realistic even though probably not being perfect. A similar effect can be seen on this video during the GCAS pullup, you see the pitch ladder not being perfectly stabilized on the horizon. It always moves a bit as a result of HUD updating frequency. Also, the speed and altitude readings are updated slower than the pitch ladder is. Also note that the Youtube video is at least one fourth the speed (no slower than that), probably recorded on the HUD itself, and your video is way slower than that and recorded in very high resolution. 20Hz is 50ms update rate, which would result in a 1 degree "jitter" at a 20deg/s turn. Which is about the same in that video I posted. Probably a bit faster, but as it is recorded on a tape, it is hard to tell. Also, GCAS tops out at like 8G so no full 20deg/s. HUD videos showing pure pull-up or pull-down are pretty rare, and the VHS frequency of 24Hz doesn't really make it possible to claim the update frequency to be higher or lower. However, the amount of movement in the pitch ladder up or down in rapid and sharp pulls will allow for some guessing because of the jitter from one picture to another caused by the update frequency on the data displayed on the HUD, and based on that, I think 20Hz comes pretty close. This video also shows a similar effect, watch the horizon line passing through as the nose passes through. And then there is this one, showing the lag during pitch and roll (see the horizon line lagging behind) You are free to explain why you think that the HUD update rate should be higher based on evidence supporting it. The stage is all yours, I was just discussing frequencies when filming and displaying sensor data and as to why those aren't necessarily the same and why it is wise to record data matching a multiple of that frequency. But this is a complicated topic, English isn't my native language and I'll see myself out, leaving that material in here so you all might discuss that topic.