Chibawang

Are you flying in CATIII?

Brilliant, thanks falcon! Making sure you see this @BIGNEWY nice community here.

Can confirm, the f16 radar is a complete mess.

Thank you both. I regularly experience those issues as well, but you articulated them far better than I could have.

Yes, all radar modes. I've mostly been using RWS as I heard somewhere that it was better, but I've not found that to be true. RWS seems to have better ability to detect targets, but drops lock on a dime and contacts fade in and out constantly. You can see the TD box lag and update every second or two, whereas TWS is smooth. Also it seems bandits are getting a STT warning in SAM mode, but I haven't confirmed that with a friend. If anyone knows how that is currently working I would love to know.

Well, that's what I get for reading your post before I've had my coffee. It does appear you were talking about the correct engagement. If I've judged you too harshly, I apologize. I too think there is a group of people that are expecting too much from the radar, but I don't count myself among them. I only got the module a month ago, I didn't get used to any of the unrealistic performance you speak of. May I ask you, do you fly the F-16 regularly? Online? It seems all who do are in agreement that something is wrong, and all who don't want them to shut up about it. Anyway, I don't think your explanation is really sufficient. A couple other points: I didn't chase him with my elevation, it was mostly centered on him the entire time, save a brief a second at the end before the missile impacted. I did chase him with my cursor, but I don't see how that's relevant or even a bad habit. It's not as though I was being notched. He did a steep dive to offset, presumably while maintaining lock. (Try that in an F-16!) No terrain masking as you thought. If that's all it takes to handily defeat an F-16's radar, I'm shocked. Again I'll point out that this is FAR from the most egregious example, but it's a short and clean track. Setting up some tests is not out of the question if you're really interested, but it starts to feel like I should be getting paid for this lol

Thanks for the update!

You must not have watched the entire sortie, that’s not even the encounter I was talking about. I think it was suspect performance, but I figured you would explain it away with little subtleties like that without making any attempt to confirm whether that was actually the case! Tacview can be recorded from a track, you know. I was talking about the encounter immediately after, flying head on with a fighter above me at 39k I believe. This too could probably be explained away if you really tried again, but I’m not trying to convince you as you seem to be taking a position and will not be swayed from it. As for your other complaints... - you won’t find a shorter multiplayer track than this. I take off and immediately encounter the bandits with no in between time. -my ping is in the 40s, it’s the most lag free server I can find. Others may lag, and that could be a factor. AS I SAID BEFORE, it could be any number of things not to do with radar programming, including lag, server performance, net code. If that’s the case, I would like someone who knows what they’re talking about to confirm it, not some random guy on the forums.

Fine, try this one out and tell me what you think. It's not the most blatantly horrible example mind you; it's short, to the point, and perfectly typical of the average performance. The real horror shows are usually buried within hours long tracks. https://drive.google.com/file/d/1wha_YHcJfGFMIpzRcyP1jzaVOKXQzyAB/view?usp=sharing

Player vs AI is certainly a factor, though it's hard to imagine how in head-on co-altitude scenarios. To say that's the only difference between offline and network play is pretty naïve, however. It could be a server problem, ping problem, net code, etc. As I said, any number of variables NOT to do with the radar code. I have already uploaded a track in another thread, I believe ED is aware of the issues and doesn't need 100s more bug reports or tracks to go through on the same issue.

No mention of the F-15 in his post, to be fair. But according to your source, wouldn't 18 nm be very low for that scenario? In my experience, this is the norm in multiplayer. If it weren't for datalink, I'd think the skies were clear most of the time. This isn't directed at you really, but it's a little tiresome reading all of the contrarian posts that ignore the problem, or assume it's simply operator error.

I get the feeling people arguing for overperforming radar are offline pilots, the radar seems to perform very differently in multiplayer. Way below your most conservative numbers. This could be due to many different variables I suppose, I don't think the answer is a "radar buff."

I’ll take a guess: autopilot/altitude hold was on. It happened to me on take off once

@BIGNEWY Just noticed something about this I don't think is intended. If you press the SJ button while in an override mode such as DGFT or MRM, it appears to be disabled as has already been said. If you then release the override switch back into a master mode, you will find yourself in selective jettison mode! So in other words, it is accepting the input but sending it to another mode's menu structure.

@BIGNEWY I got a track tonight, didn't realize it recorded in multiplayer! It's a big file, but I left the server almost immediately after it occurred... right after I get shot down, in fact. So hopefully that will help you find the right segment to look at. It doesn't go EXACTLY as I reported, no ghosting altitude number for instance. Hopefully this helps, I'll save any more as they come up. https://drive.google.com/file/d/1FYPnD1zzzpksZqtvLid7Vcz47W38fFJ2/view?usp=sharing

I've read several reports related to the radar since last patch, but nothing this specific---hopefully that is some additional help. I wish I had a track to provide, I'll definitely keep my eyes open for this while offline, but that hasn't been much lately.

Occasionally, in RWS a bugged target is lost and while attempting to reacquire, the elevation setting on the cursor is frozen into its previous range. Sometimes either the target altitude or one of the the radar elevation numbers is also stuck on the screen where the target was, a ghost of sorts. I’ve learned that the only way to resolve this is to switch into TWS and back. I’ve only experienced this in multiplayer so far, no track available. Side note but perhaps related, shouldn’t the azimuth and elevation be centered on a bugged target through any maneuvering? I’ve noticed this is not always the case, and I need to manually adjust while doing crank turns.

I too waited until now to learn the F-16, not wanting to spoil my experience with an early alpha module. The training missions are admittedly pretty weak and sparse... I assume they are still WIP, but on the back burner. I'm getting used to the radar issues, when they finally fix them I will feel all the more powerful. Besides, I mostly die to other F-16s, so I can't complain.

@WobblyFlops Not really. In any simulation there will be simplification of systems, some more simplified than others. IR certainly feels like one of those systems, and I've seen no indication that this change will be anything other than visual. If there is anything other than wishful thinking behind this, please share with us. Frankly, I'm not sure I would want the added headache of complex infrared attempted, but I'm sure I'm in the minority there. It just seems to me that the sim already struggles enough with unit calculations, online at least.

Has ED actually stated that these new dynamic textures will be anything more than a VISUAL change? I'm not a programmer, but it seems like a lot of CPU horsepower would be needed for what you guys are hoping for...

That’s 100% the issue lol. The pickle button is still tied to the jettison function, doesn’t matter how many mode buttons you tap.

Sure, I’m aware that’s what the flight manual says, but i thought it might be misleading wording and thought I’d ask a guy who’s seen it working. Otherwise it just seems odd to have a rotating indicator with dots, but there may be an explanation for that.

@Bouli306 I have a related question if you don’t mind. In other sims I thought the speed brake indicator showed different numbers of dots related to the degree of deployment. In DCS it’s two positions only, open or closed. Is this correct?

My solution was to bind the hat to a keyboard macro equivalent to whatever the keyboard bindings for trim are. 1 trim input per press until release.

I’ve never seen anyone address it directly, but Wags notes this within his TWS video in a manner that gave the impression it is intentional. It will be far less annoying with the DTC implemented