TobiasA

Yes. Of course. If it was implemented as you say, then the error should change with range. It does not. It should be perfect at your boresighted range, and then it would drift away the further you are away from that range. But that's not what it does.

The thing is that in the original direction, the error is negligible and 90 degrees to the left or right, it is sideways and the handoff won't work. Even though that in the original direction it is fine. It should be the same error in every direction you are flying, and if you are aligning at the same range and about the same dive angle then the result should be somewhat close even if you come from a different direction. I hope this was understandable, sometimes things are hard to explain with words.

Thanks for taking your time to watch the track! I am fully ok with the amount of the error. It's a bit hard to explain, but the issue is that the error is always pointing south. If you come from the south as I aligned, it will be a bit short but ok when you lock at about the same distance. It works as intended there. However, if I come in from the west the error points south (to my right) and if I come in from the east then it still points south (to my left). Offsets should be angles (with parallax error of course) but not north or south. It's an angular error, not a cartesian one. It should always be short / left / right then, no matter the direction I am flying too.

My genius is frightening, sometimes in a positive way, sometimes in a negative way. Thanks for pointing that out, I forgot about that. Stupid me copied the file from a buddy. Attached is a track. I align south to north. I can handoff my mavs. Then I turn to the left, and fly in from the west. The target is offset to the left, the maverick points to a point south of the target. Handoff kinda works at larger distances, but not a bit closer, because the lateral offset becomes too large. I fly over the target, come in from the east, and target is now offset to the right, maverick still points south. I come in from the south, I can handoff. So the mav doesn't have an angular offset but an offset in north / south / east / west direction which would explain why people like me that align mavs on their way in, usually in a different direction as the final attack, almost never are able to handoff, and other people never have this issue. It should be an angular offset, like always 0.003 degrees to the left and 0.05 degrees up, or probably depend on range since TGP and mavs aren't in the same axis. It should not be "always south". Drop me a line if I messed up the track, I think it worked now. Maverick_test_boresight.trk

I tried just that, I saved tracks earlier, but it saves the same old track over and over again. One from last year... Don't know why. I am 7nm out.

I have no idea why I can't save tracks, that feature somehow got broken and it copies the same track over and over again. I am unable to save tracks, it just saves an old one each time, no idea why. Will try to fix it. So maybe someone can record a track for this. I think I found out that if you boresight your mavericks flying south to north, then boresighting the mavericks will have a slight error along the length axis, so it will deviate a bit before or aft of the target (little bit to the south, little bit to the north). If you now attack from east to west, the error will be to the side (still a bit north or a bit south, instead of long or short of the target), and maverick handoff will fail, because the error now matters, and you will land a significant distance away from your target. The error needs to be a angular one, not meters to the north / south / east / west something. Steps to reproduce: - Align your mavericks in the air, flying south to north. Check if they return to the target with TMS down, they will. - Now fly around that target, and attack the same target with a 90 degree offset (west to east). You will see that your mavericks are now shifted left or right. - Attack from the south, and alignment will be better again, because the error doesn't matter as much now (as you are a bit in front of or aft of the target, but the seeker will still point right at it) Maybe someone can test that and record a track... Because my track feature broke. Attached a mission file to test, there is a single target a bit south of the others. Boresight your mavs and that target, fly out east and notice the direction and visible amount of the error. Let me know if you see the same or not. Sounds weird, I know... So thanks for taking a look. Hope my description was understandable. Tested with the ATP but I'm pretty sure it's the same with the Litening. Mav_test_boresight.miz

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 good, 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.