Harker

I don't think the OP argues that it's wrongly implemented (it's not, TDC Depress allows to slew and TDC release commands the new point, that's OK). I think the request is about removing the need to press and hold the TDC to slew, for users who uncheck the "Realistic TDC" option, since they cannot Depress and Slew at the same time.

I'm not at my pc this week, so file names etc will be all over the place. I took the canopy glass texture file, repainted everything to an almost black color (something like 10,10,11) and set the alpha to ~98%. I then added a custom roughmet file, like Megalax, red, with a little bit of green (something like 250,30,0), with the green level varying a little bit in places, to simulate scratches etc, kinda like how the F-14's canopy has, but much more subtle. This roughmet file will allow dynamic cockpit reflections to show up and from what I can tell, they're based on the external cockpit model, not the internal one, although the latter has an effect as well. I've also noticed the problem with the out of place DDI green reflections, in front of the canopy bow, and I think it's because their their reflection effect is not occluded from the front console, as it should. I'd say that the Hornet's canopy has the potential to have great reflections, but the cockpit model and textures need some rework in order to get things just right. One last thing, I noticed that I'll have dynamic reflections some times and some other times not. I always have them on my first mission after I start DCS and then I can lose them in a later mission. It resets with each restart. Weird.

Very interesting! I've been using a glass texture without baked in reflections, so I only get the dynamic ones, but this mix looks promising. I'll play around with this in a few days, see what I can come up with.

You can do the latter step. If you want to move the IMAV seeker with the AG designation, you can designate with the FLIR, move the FLIR and uncage the IMAV to the new location. You can also move the AG designation through the HUD or JHMCS, or with any other available way.

What I realized is that the canopy will reflect the external cockpit model, to an extent at least. I could be wrong though. In any event, we need higher res textures and higher poly geometry, for the reflections to look as good as in the F-14, for example.

Excellent work!

It's a long standing bug. IRL, the RDR ALT warning resets upon WonW (one time), but the bug is that in DCS, it keeps resetting as long as you have WonW and thus can only be set once you are airborne.

Looking at the screenshot, it appears that there is an additional bug though, as the OP points out, since RDR ATTK has bricks and the ACQ Point Cue, indicating that the ownship radar is seeing at least one target, yet the AZ/EL shows nothing.

The Hornet lacks a roughmet for the canopy glass, that's why it looks like it's plastic. If you create one yourself, you will see the reflection effect, similar to the F-16 and F-14, but they won't look as nice, due to the Hornet's low res cockpit textures in the external model.

Agreed about the current wrong state of the threat bands. On the ALR-67(V)2 that we have, the pilot should still be able to prioritize certain threats using the priority knob, which is not currently implemented. This will also help with friendly ship emitters not showing up as highest priority, half of the time.

I haven't checked it in a while, but this cannot be correct. BRA and BULLS of the TDC or L&S are absolute quantities and display scales should not affect the readings at all. This would defeat the whole purpose of them.

Agree. But it's not how it works in DCS. I don't even know if the new FLIR tech will help with that, because as I understand it, the latter is a texture mask rework, whereas the issue is with the system logic itself.

Try it with good weather and lighting, during the day. Not too early in the morning, not too late in the evening. IRL, the ability to track is based on contrast and image clarity, but in DCS, it depends on other factors and two important ones are time of day and distance.

This isn't necessarily wrong, because the coordinates (and north arrow) are generated by the ATFLIR directly, while most the OSB options are generated as DDI video output, by the MC itself.

You can indeed. That'd be the best option for the Hornet as well, a coefficient for the HUD and another one for the displays. The slew axis can be left as is and the coefficients can simply multiply the input from, let's say 0.5 - 2.0. That'd be the cleanest way to deal with this.

The SA having different ranks than RDR ATTK is not new, although it very much is a bug. But this is all very wrong in general, RDR ATTK, AZ/EL and SA should all show the same track information, both for ownship and for off-board tracks. Track processing is done in the MSI system and the same output is shown in the three displays.

Sure, you can't arm the laser, that doesn't mean you shouldn't be able to change the frequency though.

That shouldn't be an issue, that's why you have settings. Correct optimization can affect the number and complexity of assets shown on the screen, foliage, draw distance, terrain mesh detail etc. ED already offers options regarding these things and allowing users to select which areas they're willing to compromise on, to achieve better framerates. The main relevant problem with DCS is that it's quite unoptimized and that might be a limiting factor in development. But it's unoptimized for everyone.

One thing not implemented yet is the ability to choose between radar and jammer priority. It can be selected in the RDR ATTK page and is also automatically selected whenever the radar is supporting an AMRAAM launch.

At the very least, you shouldn't be able to select an option that doesn't show up on the DDI.

You can experience both positional drift and attitude drift, without AINS. It's overmodeled though. The drift is way too much and the attitude accuracy loss is insane, at times, which makes no sense (GPS isn't used for attitude). It's like the source is the standby attitude indicator or something and it's nothing like what other, non-GPS aircraft experience.

Nothing changed, you only see the A/G designation, not the FLIR LOS on the HUD.

Glad to see that it helped. But be advised, a track file does not necessarily correspond to the target's real location. A track file is generated by the MC, based on raw hit information, and extrapolated between raw hits. So, if you're losing a track with the 4 seconds setting, it means that it didn't get an update for 4 seconds and got dropped. If you have 32 seconds, it'll keep the track for longer, but it'll still be updated slowly. Worst case scenario, you can have something like 30 seconds since the radar actually got a raw hit back from the target, but still have the track file maintained, although that track now likely refers to a target that isn't there anymore (unless they fly straight and level). Anecdotally, I've sometimes tried entering STT on aged tracks and couldn't, because my radar couldn't find anything there anymore. Maintaining tracks for longer is helpful, since it allows for better situational awareness, but it can lead to situations where the track does not correspond to the target. You should always check your track quality by observing the brick (raw hit) trail in RWS or TWS with HITS boxed. If you want to have good quality, ensure a fast update date by either going into TWS with tight settings or even better, STT.

RDR ATTK page, lower right, you have the DATA option, which takes you to the DATA sublevel. Then, the track aging option I'm talking about is on the top right. It's just a number. It defaults to 4 for the AMRAAM. Press the OSB on top of it, to change it. You can then exit the DATA sublevel by unboxing DATA. After you set up your parameters the way you want them, you can go RWS and select SET, on the right. It'll make them the new default for that A/A weapon. I personally like to select 80 NM, 4 bar, 16 or 32 aging.

When switching to AMRAAMs, go in the radar data menu and increase the aging option on the top right from 4 to 16 or 32. It's likely that you were losing the tracks because of the very short memory time.