Hulkbust44

You could just turn blanking off and use the RECCE to do it manually. Same difference really.

Why? It activates at around 2/3 stick aft travel.

@BIGNEWYAny chance you could share your evidence or where to find it? All of the applicable documents that we have access to support the OP. What you're claiming is correct, is illogical at best, and contradicts everything about the MSI system at worst, based on our available documentation.

After the most recent update (2.7.16.27869) I noticed a couple issues regarding target information. Mission set up. Hornet at altitude head to head with F-16 at altitude. Hornet has E-3 support and D/L is turned on as well as IFF. Upon STT of the F-16, the Attk format no longer displays the lower HAFU from the AWACS. As such, donor IFF for the target is being lost and shown as unknown. Even after an IFF interrogation it remains unknown, not ambiguous. HOWEVER, the SA and AZ/EL show it as ambiguous WITH the bottom half hostile HAFU which is not possible... offboard_hafu.trk

As you can see here, there is a discrepancy between which trackfiles are ranked what between the AZ/EL and SA formats. The SA, AZ/EL, and Attk formats should show the same trackfile information. (Exception being aspect pointers on the AZ/EL) This is still an issue as of 2.7.16.27869 No track, needed just open the Caucasus 8v8 instant action mission and observe the chaos that is the Hornet track rankings.

Yes, it can *recieve* on the ground. What's been seen here are jamming strobes with resolved azimuth. System memory can hold tracks for a while, but what you actually pickup on the ground is from jammers.

Then what is the basis for the time a track is held in DCS?

Would it be possible to have a special option to adjust the distance of the UPLOOK reticles? As it stands it is impossible to use in VR. This is a really neat and useful feature especially for VR users, but it's unusable as the reticles are basically off the screen.

That's since been fixed in later FCS versions, we should have 10.7 iirc

It's not a bug, that's why.

TACAN fix certainly works

With a TOT for WYPT 6, you will have a TOT cue that is always calculated for your current position. The groundspeed cue if set, is only from the last waypoint before the target.

Not a bug, it's mentioned in some WPs.

If you have a friendly aircraft say 20nm away on radar and interrogate it(assuming your APX- is on), it will come back as friendly. If you were to then move the radar away or silence it to where no track exists, subsequent interrogations yield no reply whatsoever. I was smoked by a friendly Hornet in my F-15 today because he didn't know I was there. Had this been working properly, he would've seen my aircraft when he interrogated the bandit across the circle from me and I might've made it back with those 7 air victories.

Yeah, no. ED didn't change anything about guidance, the P in DCS gives you an additional 1kg to the warhead...

No issue. You can see in real-world HUD footage the same thing happening.

But it's just less. You don't actually learn anything about the radar either.

The HUD EW stems are reserved for unknown, lethal, and critical threat emitters. However in DCS friendly emitters such as the air search radars from a USN task force can and will take up all the HUD EW stems if detected first. They shouldn't be displayed on the HUD at all.

This is definitely true, at anything over 20 alpha the roll rate is abysmal compared to the aircraft it should waltz over in that regime.

You should have a track in SP, and ED will need one... It's possible they got some of their logic in the code applied in the wrong place. First thing I think of is the AZ/EL TDC cursor. When slewing the radar scan the right side of the TDC (displays as a +) shows just the altitude of the center of the radar scan volume at half the selected scale/range on the Attk format.

Also EXP 3 is DBSSAR so the resolution should not change with range. The high quality image you get at 4nm you should get at 40nm.

Yes, because (@BIGNEWY correct me if I'm wrong) DCS dosen't actually model the radar, it's just a filtered version of what the map would look like with azimuth limits for the display. Of course you would have those LOS limits IRL. Now in at 80° the radar can still face down enough to map at a distance, but I've seen it track the ground below me in a pure vertical climb.

Absolutely, this also goes with the data refresh rate. It's stated that the maximum L16 track update interval is 12 seconds from a SURV source. In DCS that's the standard across the board... It's stated that a F/F link (therefore local PPLI) is 1/3 the time of a SURV source. So at absolute maximum the update rate is 4 seconds... Then yeah, with that all the data sources are talking to each other helping to build a more accurate picture.

They are certainly underpowered. The jet should be able to hold with brakes in MIL, but can't in DCS.

It's just a C with 2 seats. No new capability. An F is actually a completely different aircraft.