TobiasA

Didn't read that in a changelog, but then, it wasn't a placebo effect. Nice

How can I get an AI flight to serve as TDOA member to myself so I have a chance to test this?

Before sliding into position, point your gun cross on the tip of the boom, and stabilise it there for a few seconds. Then slide forward.

We had this in a mission the day before yesterday when (most probably) another flight destroyed the radar we were commanding TDOA on with a stray HARM, or maybe the radar was already dead when commanding TDOA. There was no despawning of units, and no spawning. We ran MANTIS and footholds zone commander, but no active spawning / despawning while the mission was on. I can't provide a track as it is massive... I was the one commanding TDOA, and my wingmen got "DATA" voice messages every now and then until I powered down my left chin hardpoint. HTS was bricked at that point, with no way back. TDOA message was in HUD until I powered down the jet, even after powering down the chin hardpoint.

Yes, but even if it is stretched and compressed, it is still clearer. And the IR textures are a different thing, I fully agree. There are bushes being brighter than a truck when the sun sets.

Probably yes. Although I doubt that the ATP is that bad. Just compare real life footage with DCS. TV is close but IR... seems to be way better in real life. https://youtu.be/Yi9d8bstWsE?si=xsD2N_l0j_Yc6pMJ

Our EF will be a little bit of a mix between Tranche 1 and following tranches. Tranche 1 with what they can add, like the Meteor. More information on the HB discord: https://discord.gg/heatblur-simulations

Double-tap EXP on your stick to go into XR.

Well, if you compare the fidelity of the F4E at launch, and the fidelity of ED modules that just now left EA... You can be quick, cheap, or fast, and you can pick two of these but not all three.

For the sake of DCS, I hope they won't do it again. And I don't think so. But yeah... Maybe. I am curious about the MiG-29 though. Let's see how this will go.

You are both right. Litening has TV and LST but there was the discussion about reworking the current pod into a realistic LANTIRN which would mean that those functions would have been gone on the current pod. I mixed up those two.

The current pod of the Viper is a mix between Litening and LANTIRN, as the Litening doesn't have TV and LST iirc. However, the pod has more issues, like having bushes appearing brighter than trucks at some time of the day. Sometimes, IR has wild textures. And it has a tendency to lock street lights instead of trucks or tanks. It is what it is, and I understand not wanting to change it as of now, as the ATP is around the corner and the Litening pod will be reworked to more closely represent the Litening pod. And I think that that's the way to go.

The development would happen in a time that would proof that the F-16 is the forgotten child... I just doubt that they are so fast. But all I care for is the Tiffy. And my beloved Viper.

I tested 25000ft, no sun, no moon, overcast, rain. Still, I get launched at without warning. Radar stays in search mode, and you die. Just like track-via-missile would do, but the Buk isn't capable of that afaik.

I could not get it to trigger any launch warning in any aircraft, honestly. It's just like it's staying is search mode. We may as well move this post, this is not an F-16 bug.

The SA-11 never triggers a launch w arning on the RWR. Other threats work fine (like the SA-5, or airborne threats). I wanted to attach a track to this report, but I am unable to save a track for some reason. It only saves an old track on the place of the new one. But it is rather easy to test, i attached a small mission. Just fly autopilot to the waypoint. SA-11_test.miz

Since todays update, the radar defaults to A6 scan width instead of the last scan width that was active. If you had A4 then it will still default to A6. This was originally reported here: It says "fixed" in the patch notes, but the bug is just different, not fixed. It now defaults to another wrong scan width, but it still does not save each submode scan width.

The progress post is a good reference about what is there and what is left. However, with the MiG-29 and F-35 on the horizon, I don't think that we will see the missing features anytime soon.

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.