Harker

Being able to display the drawings would indeed be amazing.

Use the GAIN rocker switch to lower the map brightness. You can also switch to Night mode with the top left switch and then manually adjust the contrast as well, with the lower right switch. Those will help a lot.

I'm not against early access. I was just saying that, based on how long modules take to complete once released in early access, and seeing that the Typhoon probably won't be released until 2023 at the earliest, the 2 years until 2025 don't seem at all feasible for it to reach full module release. It could definitely be released before 2025 (I very much hope so), but it will most likely remain in early access past that. Or I could be wrong and we'll have a feature-complete Typhoon by 2025. But based on the realities of developing DCS modules, this seems unlikely.

Just keep in mind that both the Viggen and the F-14 are still in EA. The latter has been out for almost 3.5 years, the former for longer. I think the Typhoon will be released in EA before 2025, but definitely not be feature complete by then.

Try to run a slow Repair and check again.

Check your radar elevation, your radar is looking way too high. On your radar cursor, you can see the numbers 56 and 67; these represent the lower and upper altitude coverage (in thousands of feet) of your radar pattern, at that range. Also check the small, blue, horizontal marks and the sideways T symbol on the left side; the marks represent vertical offset, with the larger, central mark representing the horizon (so, your altitude). You'll see that you're at 43k ft, while both targets are a bit below you. You can also see that you're scanning above you (56-67) and the T caret is above the horizon. What you need to do is lower the radar elevation, so that you're actually scanning the altitude your targets are located in (in that case, slightly below you). Remember that your radar scan pattern widens as range increases, so you might need to re-adjust radar elevation as you get closer. After you bug or lock a target with TMS Up, the radar will attempt to automatically adjust its scan pattern to maintain the track of the target. Cheers

It's going to be incredibly difficult to locate publicly available technical documents that specifically refer to the APG-73's ability to detect helicopters or anything else, for that matter. It's a far better approach to use radar technical data for deterministic calculations and use any IRL data points to fine tune each radar's model. It's the path of least resistance, only requires access to the radar specs and it ensures a decent approach throughout the sim. More to the question at hand, what can be done is use well established radar equations in order to calculate detection ranges, using the APG-73's specs (which are publicly available and have been shared before) and use publications such as the ones posted above, to calculate an "effective RCS" for rotorcraft.

It is implemented. S/A and AUTO are not meant to select the most appropriate Manual program, they select from built-in programs. The system has no way of knowing which manual program is the best one, since they can be changed by the pilot mid-mission. Thus, it chooses from pre-defined programs that are not accessible from within the cockpit. Normally, they're set up before the mission, according to the expected threats. In DCS, they can be changed by editing the ALE-47.lua file. Hopefully we'll be able to change them using the DTC, when it's implemented.

Are you running any mods, by any chance? Maybe one or more mods for VR, such as shader mods etc? Or a custom cockpit skin? If so, try without them and see if the problem persists. Run a Repair for good measure as well.

I never use tracers and it sparks the same, although I don't think it's a bug or a problem. If you compare it with IRL footage, it looks pretty good.

Video is private

I think that's what they mean. They're trying to designate an L&S by pressing the Undesignate button on the stick and it's not working until some time later. I could of course be wrong, but that's what I understood from there post.

The OP is right, the radar, in A/A mode, should be able to process incoming signals passively in SIL. SIL does not inhibit processing, only transmission. A jamming signal is an incoming signal and thus should be able to be processed with the A/A radar in SIL. AOTs should continue to be received and processed in SIL, as long as they still transmit a jamming signal. @BIGNEWYPM sent.

That's not the issue discussed here, no one is asking for a full simulation. All we care about is that it looks and feels correct according to available information. In the list of examples that @toilet2000mentioned, all of them have nothing to do with actual radar wave and E/M interaction simulation. They merely require the correct logic to be implemented, and with the exception of MSI, all others exist in some form in other modules, which proves they can be done within the context of DCS (I'll also add a correct TWS AUTO myself). None of this is about the simulation of a real, physics-based radar (although I'd personally love it if some aspects were actually simulated). The combination of the Hornet's radar and MSI (both indispensable to A/A and extremely integrated into each other, alongside other MSI sources), is something that would be a first in DCS - true sensor fusion. It is an amazing capability and the Hornet is tailored to fight using it (a lot of the HOTAS logic and various options in different pages only make sense with MSI correctly implemented - notice the lack of Radar Slave on the ATFLIR, it's because the ATFLIR generates its own trackfiles, you don't need to slave the radar, you can just designate them). We just want to see this already nice module reach its full potential - or come close to it.

I'm 99% sure that switch was never needed or if it was the case, it was changed very quickly. I don't think I've ever used it myself and I use LST from time to time. The ATFLIR and LITENING have integrated LST modules, that switch would be used for power delivery to a separate one, as was Tholozor pointed out.

That's all that's available right now. And for differences between SP and MP (IFF Mode 2/3 and MIDS A/B), they only matter for LotATC and SRS, which are 3rd party software.

It's how it works in DCS. If you spawn in an already started jet, you don't have to align the HMD. It's already aligned, same as the INS, for example.

2.7.16.28157 Open Beta Similar to the previous bug of the designation moving Waypoints around, but it now affects Offsets. Set up an Offset on a Waypoint. Have HSI open on DATA->WYPT on another display as well, to see the bug clearly. Press WPDSG and O/S -> designation is created on top of the Offset. With TDC priority to FLIR, depress the TDC, to drive the designation via the FLIR. Move the designation around and observe that the Offset data in the WYPT page of the HSI changing. Undesignate and observe that the offset symbol has permanently moved. FA-18C_designating with FLIR after offset permanently moves offset.trk

The same manual also lists this as correct. Explicitly de-selecting an INS guided weapon will remove power and thus the alignment will be lost. You can choose other weapons over it, (have J-82 boxed and then selecting 82LG will switch to the GBU-12. Deselecting 82LG will take you back to having the JDAM selected), but you cannot explicitly deselect it without losing the alignment.

Update on this. Run another test, which shows the issue more clearly. I unboxed HITS, so I can only view the trackfiles. I am able to designate trackfiles in TWS with the NWS/Undesignate button, which do not show up until designated (they show up after a certain number of sweeps). I can also place the TDC over the space they should be and they'll show up out of nowhere. This means that the trackfiles are ready and able to be designated, but do not show up on TWS until a higher number of sweeps are performed. Trackfile HAFUs should show up as soon as they're created and valid. FA-18C_TWS does not display HAFU as soon as trackfile is ready_part2.trk

2.7.16.27869 Open Beta Set up an Offset to a Waypoint. Switch to the SA page. Press WPDSG to designate the WP. -> A designation is created on the WP location and O/S shows up. Press O/S in order to designate the Offset location. -> Nothing happens, the designation remains on top of the WP location and the O/S option remains visible. Switch back to HSI and observe that O/S works correctly. Small addition to https://forum.dcs.world/topic/292704-offset-point-still-wrong-since-available-wrong-mark-sa-page-possition/ , didn't want to make a separate report. I have observed that the Offset symbol on the SA page will simply move with the aircraft (you move +5 nm East, the Offset symbol will also move +5 nm East on the SA page. It resets to the correct position when you switch to the HSI, only to start drifting again once you switch to the SA.) FA-18C_Offset doesn't work with SA page.trk

Just an update. I tried to reproduce and I've been unable. Strange, as it was initially reproducible when I posted the original track (I restarted with Shift+R just to make sure). Could be that merely quitting DCS in the meantime, fixed whatever was happening. I'd say this is not this is not reproducible for now and I'll keep an eye out for it.

Seems to be a combination of two issues I reported already. During my testing, I found that there are two separate issues at play. I'm not sure what goes on under the hood, but perhaps it's better if we treat these two issues separately. 1st, valid trackfiles (with resolved azimuth, altitude and velocities) cannot be designated as soon as they're ready. Trackfiles are objects generated by MC2 in the Hornet, so having "unusable" and "un-designatable" trackfiles makes no sense, based on what I've read on IRL manuals. This is reported here: /topic/305485-valid-trackfiles-cannot-be-designated-immediately/ 2nd, TWS takes more sweeps to display a trackfile, even if the trackfile is ready and can be designated manually (NWS, TDC Depress). The trackfile is already visible in the SA and AZ/EL pages, it's only not shown in TWS, on the RDR ATTK page. This makes no sense, since TWS should display valid trackfiles for up to the 8 highest ranked targets, as soon as they're available. This goes beyond the previous issue, since the trackfile now can be designated, but it's not yet displayed on TWS. This is reported here: /topic/305484-tws-on-the-rdr-attk-page-does-not-display-hafu-as-soon-as-trackfile-is-ready/

Nice one. Should definitely be doable, since other modules, such as the Harrier and M-2000 have cockpit elements that can be toggled. Here, it can be tied to the selected pod instead of a user option and the change is much easier, because the only thing that needs to change is the textures.

No mods for this one (just a custom cockpit livery via Saved Games). I'll check again after a Repair, maybe something is off on my end, and let you know. If it does occur, I'll record a quick video.