Rongor

Having launched an AMRAAM on a bugged target in CRM, so in SAM mode, I turned away. Eventually the relative angle next to the target locator line in the HUD showed 79° with the radar still following the target. 1. I am a bit surprised to see this, as I expected the radar to only have a maximum scan zone of 60° off the radar boresight. So what is the actual maximum angle off the gun cross, the radar can still track targets? 2. Also considering the enemy being almost at my 3 o'clock in the horizontal plane, how can the smaller attack steering circle not be completely outside the larger ASE circle yet?

Thanks guys. Also thanks for the video link. So the manual is outdated on this and the little circle has switched to a totally different meaning. Gonna learn these M/A/F meanings now to make use of them

I have this HUD while going head on towards a Fulcrum which already launched at me and I am close to launching an AMRAAM myself. I am a bit confused about two things here: 1. What does this "12M" below the closing speed tell me? Couldn't find anything about it in the manual 2. This little circle symbol below the R aero triangle is very likely meant to be the Radar activation range (as the only little circle along the DLZ is representing exactly this as per the manual). So since the range to target marker has already wandered below it, wouldn't this mean I am already within radar activation range? Contradicting to this, the countdown to activation is still showing A15 (instead of a T-value), so something is wrong I guess...

Yes, I tried the bullseye thing and it is replacing this info with accurate bullseye information. Thank you for clearing this up, so it is only an outdated manual thing but working correctly. To the Time-to-go issue, I can add that I even had a time countdown displayed in one occasion and it seemed to be inconsistently connected to whether I had weapons loaded or not. Yet the timer clearly didn't calculate anything weapon-related (like impact countdown for a dropped weapon) and was in fact only affected by my flight path. Thank you

Oh, sad to learn this inconvenience is actually how it is in realworld. So no bug, thank you for clearing this up.

The B/R data field in the bottom left of the FCR format page isn't showing the bearing/range from ownship to the radar crosshair location. Instead it shows bearing/range from the current steerpoint to the coordinates of the radar crosshair. Only range data to the radar crosshair location is shown corrently in the HUD. Also the "Time to go" is shown in the HUD correctly, while it is always zero in the FCR format page bottom right time to go data field. The bearing from ownship to the radar crosshair is unavailable. FCR_no_br.trk

Does this mean the manual in its current state is incorrect on this and what I described is in fact the way it should be? If yes, does this include the non-functional time to go data field in the bottom right of the FCR format page?

I am not sure how to interpret this. - is what I experienced and reported accurate and correct? - is it accurate and correct due to the refinements made and only are not reflected in the manual? - is what I reported indeed incorrect and inaccurate, yet refinements have already been made and are awaiting to be patched in to match the manual again?

As demonstrated by Wags in his Mark Points demonstration video (linked at the bottom), you should be able to adjust the dimension of the selected submode (EXP, DBS1, DBS2) by selecting the range with OSB 19 and OSB 20. Instead my track will show that pressing OSB 19 and OSB 20 actually resets the submode, returning to NORM, with the new range setting, often having the crosshair then being outside the displayed range. You then again have to cycle to the desired submode by pressing OSB 3, which leads back to the actual crosshair location but the whole process is an inconvenient step which also isn't appearing in Wags' video. Also while Wags can then change the scan azimuth with OSB 18 to enjoy faster image refreshing in the closer zoom steps of these submodes, this is currently not possible, as pressing OSB 18 is ignored and hence the submodes are stuck with a 60° azimuth scan and A3 and A1 are unavailable, leading to pointless long scan times. The only way to enjoy A3 or A1 for faster refreshing currently is to select one of these while still in NORM and then enter the submodes. GM_submodes.trk

Ok let's assume it's the bullseye or maybe the current steerpoint, By testing I can confirm its showing bearing and range from to the current steerpoint to the radar crosshair. This is contradictory to the manual and also I would of course prefer to know bearing and range to the crosshair from my ownship location. Also I can't find any way to have the time to go indicate anything but zeros.

So like freezing the image and then flying into it? Interesting. Never considered this to be a thing

snowplow.trk The track will show 1. while in snowplow, TDC inputs are still accepted and moving the non-snowplow crosshair in the background 2. when reducing the beam azimuth, any crosshair location off the centerline will have the radar scan zone not being centered when activating snowplow 3. Using the TDC while in snowplow with reduced beam azimuth will move the radar scan zone off center and also have the crosshair begin at a different location when exiting snowplow.

How could my own aircraft possibly be inside the radar image? Wasn't aware we have 360° radar coverage...

While in snowplow, I can still move the crosshairs around while they are invisible. Meaning any adjustments with the TDC do affect the crosshair and so its location will have changed when returning from SP mode. Is that accurate?

I am flying with a heading of 139°. The radar crosshair in the GM radar format page is indicating the SPI. Radar range is 20 and the crosshair is dead ahead. I would expect the B/R showing like 139/16, instead it shows 074/77. It's clearly not to my left at 074° and also not 77 NM distant. Also the time to go doesn't show anything. What is going on?

OFF/STBY/LOW/NORM/EMER I am totally aware this doesn't really affect anything in DCS (sadly), yet the DCS F-16C has bindings for these in stock. So please add them here as well

Is it really missing?

20230205_031545.mp4 Instead the front square is black. Pressing the lights test easily reproduces this, therefore no trackfile attached.

After shutting down by moving both power levers into off, the Ng remains at 60ish %. Ground services are denied due to running engines. Restart of engines fails. Actuating start switches doesn't commence start, only displays start on ENG page as long as switch is hold. Unable to stop the engines entirely. Happened after being on a MP server for an hour so there is no way to provide a trackfile.

This is indeed the main problem in MP. Having to apply 3-4 Hellfires from 3 to 4 km to eventually hit that T-72 while having clear LOS and stable flight conditions is a rather frequent occasion. George doesn't seem to make use of the image tracker, but this isn't the cause. You can see the laser spot in perfect aim dead on target and the missile simply ignore's it and misses by 40 meters behind. I could upload new tracks daily if ED's track file system wouldn't condem us to present huge files which are a pain to review.

Hey there. I know that as per MIL-STD-291 the interrogating and reply frequency pairs are cut down to 1025-1150 MHz in mode Y, instead of using the full range of 962-1213 MHz in mode X. Also when switching to A/A while a channel is set to mode X, we essentially get the Y pairings. The only difference in A/A between X and Y seems to be the pulse spacing of 36 μs for mode Y instead of 12 μs in mode X. So what is the deal here? What are the benefits, what is the idea behind these different pulse spacings? Why does Y use the longer spacing? In A/G, mode Y also has the longer spacing, yet its only 30 μs there. Why?

If the emitter is still active and the missile has sufficient energy to reach the target, the HARM will hit, regardless if you carry the HTS or not. The HTS becomes irrelevant the moment the missile is launched. Before, the HTS provides a much better sensor than the one onboard the missile to generally detect emitters across a wide azimuth zone. Even if you reach PGM 1 precision in your triangulation, there will still be an error ellipse of which you can read out the diameter on the HAD. The HTS triangulation is meant to offer you a location precise enough to slew other sensors to it and for example to be able to determine the exact location close by with your TGP's E/O-sensor. The HTS is not magically feeding the HARM with pin point coordinates, it is not turning the HARM into a JDAM. Assuming the very likely case that the emitter you attacked went off the air while your HARM was homing in, the "misses" in your pics are actually remarkably precise on target.

Acoording to admittedly Wags' rather old Startup video, the FLCS PWR TEST (2nd startup item, MAIN PWR is on BATT)) should show the FLCS PMG light on while holding the FLCS PWR TEST switch to TEST. This corresponds to the startup flow in the manual (current revision 30 NOV 2022) on page 137. Yet ingame the PMG light doesn't illuminate. What am I missing?

This thread title actually made me hope there would be a DCS themed door mat for sale somewhere

how can this work technically? It's like looking on a helmet mounted display, the distance between the projection and my eyes seems ever the same. Yet it isn't. This doesn't make any sense by optical rules. 20221212_212441.mp4