Harker

What sources? And which radar would that be? The (V)9 or the (V)5 which we actually have? It's likely that any person with current experience on ANG Vipers would be using the (V)9 as reference. Right now, the Viper's radar is probably even a tiny bit better than it should be in terms of detection range, based on the fact that RWS and TWS are MPRF-only modes.

That explains it. A lot of aircraft equipped with ECM will turn them on when they're locked in STT. If the OP fired outside the burn-through range (~22 NM), then indeed this is expected behavior based on the correct ECM modeling. And it does look like it as well, the off-board HAFUs seem to be further away than 22 NM.

You need to be below Mach 0.9 and the arrows will appear again.

IIRC the RWR should have a knob near it. As for EHSI, you need to press the CRS knob in (click it), and then rotate it.

Open beta 2.7.8.16140 Currently, TWS AUTO simply centers the TWS scan around the L&S in azimuth and elevation. What TWS AUTO should be: It should maintain as many trackfiles as possible, by automatically adjusting the azimuth and elevation. The elevation can also become 3B or 5B (only controlled by AUTO), but the radar page will show 4B and 6B respectively (the radar set does 3B, but reports 4B to the digital data computer, for example). The scan pattern will be automatically biased to maintain the L&S, DT2 and trackfiles under AMRAAM attack. After the above, the scan pattern will be automatically adjusted to maintain trackfiles, based on rank (e.g., it will not bias towards rank 8, if that means it will lose rank 1). BIAS mode will bias the scan center towards the area the TDC was depressed on, but keeping all trackfiles from 3. within the scan. All trackfiles except those mentioned in 3. can be taken out of the scan, by pilot-commanded BIAS. RSET should remove the BIAS status and return to AUTO, not revert back to MAN. Relevant information can be found in the 742-100, page 106 (011 02, page 6, points 45,46), page 126 (011 03, page 8, point 63), page 500 (043 00, page 9). Relevant info will be PM'd shortly. TWS AUTO does not optimize scan.trk

Open beta 2.7.8.16140 (but it has been present for some time). TWS trackfiles seem to not be extrapolated correctly and will often jump around the RDR ATTK page and the HUD. This is especially noticeable if there are multiple contacts in formation and if the EXP option is used to look at them closely. The HAFU will jump to the new position every time the target is detected and this happens continuously with targets flying straight and level, which would indicate that the extrapolation is wrong. This also leads to HAFU ranks moving around, since closely spaced targets that "jump forward" are promoted, before being demoted again when they jump back on the display, with the expected rank reshuffling that brings. I also tested to see if the this was a result of HPRF range ambiguity by repeating the test with MPRF, but saw no difference in the results. Tracks from both tests are included. TWS contacts jumping around between scans.trk TWS contacts jumping around_PRF test.trk

Open beta 2.7.8.16140 FPAS will stop updating arrival time and remaining fuel for the selected WP, if the HSI page is not visible (SA page does not work either). It seems to not realize you're getting closer: the arrival time will go up and the calculated remaining fuel value will continuously decrease. It operates like you're static and not actually moving closer to the WP. The time to arrive is updated correctly on the SA page and of course all info is correct on the HSI page. When bringing up the HSI page, the FPAS page immediately updates correctly. If navigating to a TACAN station with TCN boxed, it seems to be working correctly, so this seems isolated to WPs (and perhaps MKs, haven't tested that). FPAS WP calculations wrong if HSI page is not up.trk

The RADALT warning set through the HSI A/C page is supposed to reset *once* the plane detects WOW (as in, upon landing). In DCS, this reset takes place continuously as long as there is WOW. And yes, it's a reported bug. Maybe the threads can be merged.

I may have been unclear. NCTR has nothing to do with the CIT. It's purely a function of the radar and it indeed requires STT. Let's completely leave NCTR out of the conversation - it is involved in the ROE matrix that will classify threats as Friendly, Hostile, etc, but NCTR itself is a very different thing than IFF. IFF is simply a system of question and reply. We're talking about manual IFF interrogations, those are done by first depressing the SCS and then quickly bumping it right, when your TDC is over a trackfile. As for whether or not you want to manually IFF stuff instead of using AUTO or L+S IFF, that's up to you. IRL, you can tip other aircraft off that they're being interrogated. And you might not want to automatically interrogate your L&S until you're ready to fire - maybe you are radar silent and your L&S is a donated or FLIR-only MSI trackfile (this can be done IRL, not currently possible in DCS), so you want to delay interrogating it. I'm pretty sure it does nothing in DCS and unless I'm mistaken, none of our modules react to an IFF interrogation.

CIT = Combined Interrogator Transponder. Your IFF system. IFF interrogation is simply the interrogator part, not NCTR. You can control the behavior of the Interrogator in AZ/EL page. By default, it'll periodically interrogate the L&S. You can also set it to periodically interrogate the airspace in front of you. But you can also manually command it to interrogate (maybe you have AUTO disabled in order not to alert or annoy other flights - since IRL, aircraft equipped with the appropriate equipment know when they're being interrogated), by hovering your TDC over a trackfile and the depressing the SCS before quickly bumping it right. Don't confuse IFF and ROE. IFF can only tell you if the target is friendly, not if it's hostile. NCTR is not connected with the CIT or IFF in general, it's connected with the ROE matrix. You need two separate sources for the ROE matrix to declare a target as hostile. A negative IFF reply can be one source, NCTR or off-board data can be used as a second source.

LOST is displayed when time-to-go is decreased to zero. It refers to the last missile in flight. It in no way refers to the jet's kinematic state after the missile is launched. 742-100, page 274. PM'd the specific parts.

Hello, No, ED reverted the changes, you can use that file without failing IC.

This wasn't a dig at the team, merely some criticism (which could've been worded better, perhaps). I was referring to the radar, not the entire module. The radar has been plagued by major, known bugs for a very long time now, namely the trackfile memory issue and the designation drifting problem, which restrict its usability unless you rely on workarounds. The radar has been unreliable for a long while now. Plus, it seems that it's modeled more after the older APG-65, than the APG-73 RUG2, which is what we should have, one example being EXP3 limited to 30 NM and just being another zoom level, instead of working as medium resolution SAR Again, it's "OK" as a radar, if you don't consider these major bugs, but it's also not working like the radar we should have. I saw the latest Mini-update, which mentions that further tweaking will take place, so I'm hoping that we'll eventually get the radar we're supposed to have.

Can you please zoom in on one of them? See if it changes shape as you zoom in?

I've been unable to reproduce it today. I also have my elevation axis mapped to two buttons, so no axis shenanigans there.

It should be slaved to the SPI though, no? So, just regular PRE mode.

I managed to replicate it by having a target above me, manually increasing the elevation to find it in TWS MAN and one I make it the L&S, switch to TWS AUTO. The elevation jumped up above the target and it eventually timed out. It looked like TWS AUTO applied an adjustment to the elevation as if it it was starting from its default value, not the already manually adjusted one I had set. (let's say it should go to +15 and it already was at +12. Instead of adding +3, it still added +15, so it ended up at +27. Arbitrary numbers)

It's nowhere near finished. Besides the bugs, a bunch of things are either half-implemented or completely missing. It has come a long way and it's certainly playable (to an extent, the radar is kind of a mess, the designation logic is not entirely correct etc etc), but it still requires a lot of fixes, changes and additions.

AACQ means that the radar is placed in an automatic acquisition condition. It should remain in AACQ until the latter is canceled and it should work like other automatic acquisition modes - as soon as there is a valid target to pick up, it should do so. If it's not working like that, then it's bugged or wrongly implemented.

Yep, I noticed this some time ago. Every human player's rank 1 target will have the dashed line on the SA page, even if it's not the L&S.

Two pyramids at grid BA74. You can see my current position on the F10 map. Version 2.7.7.15038.

I wouldn't say that LTWS is bugged in DCS, it's just implemented wrongly. They need to correct the behavior, but it's working as the devs intent for it to work. When I say manual IFF, I simply refer to the action of commanding an interrogation with SCS Depress + Bump towards the radar page. IRL, you can interrogate at will (and even receive IFF-only trackfiles) without needing to interrogate a specific target, you can simply interrogate the airspace in front of you. In DCS, it seems that you can only manually command an interrogation on a trackfile and since LTWS in DCS does not generate any trackfiles, you cannot manually command an interrogation on just a brick (according to what you said, I haven't tested it). L+S IFF and AUTO IFF are indeed separate, the first automatically periodically interrogates the L&S and the second periodically interrogates the airspace (without generating IFF-only trackfiles, however).

If it's not working correctly with LTWS Off, then it's a problem with the implementation in DCS. It seems to be tied to the presence of a trackfile under the TDC. IRL, LTWS is just a display option, nothing more. I think in DCS, LTWS toggles whether or not RWS will create trackfiles at all, but IRL, trackfiles are created with LTWS Off as well, they just always show up as bricks in RWS. This could be the reason why manual IFF might not be working with LTWS Off in DCS right now.

Yes. I have the Hornet grip from TM and unless I'm mistaken, it's not possible to keep the SCS depressed and bump it towards another direction at the same time. IIRC you need to bump it towards the radar page within 0.8 seconds of depressing it.

I've noticed the same thing as well. AFAIK, it simply shouldn't build a trackfile with only one return, prior to obtaining velocity.