Moonshine

I think there was also something with the limited laser range, as its only about 11nm. Hence if you drop at max range in the DLC and start lazing, the end of the laser beam is somewhere floating mid air, throwing off any guidance either way

okay, log has been wrong, however, whats the answer to the bug at hand of the FCR not showing the proper symbology?

sure, however patchnotes listed it that way... you are right, either way, the symbology is broken as described in the report

i found that in some cases (dont know exactly how to reproduce) after engageing and either losing or killing the target (radar loses lock) the antenna elevation can not be changed at all until either changing radar aspect or entering spotlight mode for a split second. in the track attached you see me engage 2 targets one after the other. upon killing the first one, all is working fine, however after killing the second one the exact same way (RWS-SAM mode) the elevation of the antenna gets stuck and can not be moved until pressing TMS up to enter spotlight for a split second. Controller in use: T50 CM3 Virpil OBS recording: https://drive.google.com/file/d/1hh4NYHeB9LUm9sG7wE56Ic9s8b_gWSHp/view?usp=sharing Antenna Elevation Stuck.trk

you gave yourself the answer. you are in VIS mode. but in order for the MAV to be looking at the active Steerpoint (assuming your target is marked with a Steerpoint or any other SPI) you need to put the MAV in PRE mode (pre-planned)

Bump. Awfully quiet here despite lots of info brought up.

in case you are talking about the F-16 clock not being in sync with the in mission time after a cold start -> been reported here: not informed about other jets having this issue too.

Found this post: in short; no not possible

this is exactly what i said, the radars listed in the link i posted are not considered EWR (at the very least not in DCS), which leads me to believe the video referenced is just not accurate in describing what has been hit in said mission. the radars listed are search/tracking radars, in which case it makes sense that they have been targeted by harms and shirkes, nothing wrong with that. in essence, they are no EWRs and therefore the reference to that mission has nothing to do with the topic of this post.

Seen the video too, it just does not state what he calls an EWR. Could very well just be a SR for the SA2.

could only find this during a quick search about the attack: http://www.ausairpower.net/Eldorado-Canyon.html the radars listed there are: "Flat Face, Low Blow, Straight Flush, Fan Song and possibly Land Roll acquisition radars associated with the Soviet supplied SA-3 Goa, SA-6 Gainful, SA-2 Guideline and SA-8 Gecko surface to air missile systems situated in Tripoli and Benghazi." most of those are in DCS and can still be targeted by HARMS.

After boresighting the first station, pressing MSL step will change to the other station, then the not yet boresighted mav will be slightly off of the position the tgp is looking, should be pretty quick making the adjustment, get a lock and then hit BSGT again. No need to touch the tgp a second time to align the second station

did a short test using a variation of radars/sams (Thin shield, Hawk SR, SA6 and SA11) all of them late activated, via trigger 90s after mission start. all of them showed up on RWR and HTS. to note; all SAM sites had ROE on Auto, which means some were "offline" until i got within reasonable range to them, then started turning on and pretty much immediately showed up on HTS. What Radars did you use? EWRs will no longer show up on HTS since last patch Late_activated_Radar.trk

been an issue and has been reported before, happens when either shooting one missile so the next one is not able to be stabilized anymore or when using TMS aft after a break lock scenario... curious why this post get the "cannot reproduce and missing track file"....

been reported here since november last year;

As for this topic, some data has been collected in the bug report here:

....and the maverick still does not follow the moving SPI of the TGP

never as this does not represent the state of the f-16 block 50 as it was in 2007, which is the year after which ED are modelling the viper in DCS

okay, even weirder. i just remember that all of them were jamming at this point so there might have been a chance it would affect it. i did notice the amraam also missing other aircraft when shot from rear aspect at close range (within 5nm), barely pulling Gs, yet it seemed less frequent than against tomcats.

There might be some weird stuff going on with the Tomcat when its jamming, of course this is just a suspicion Over the last months i had multiple tailchases (within 5nm), shot an amraam and it just never tracked at all. This while shooting in STT. Missile just flew past the target, barely maneuvering at all. In all of these cases it was a tomcat with its jammer turned on.

Might also have lots to do with the lookup/lookdown penalty which is under investigation already

you are absolutely right, markpoint is way off. funny enough, i could only seem to create this with the TGP created markpoints. did it with the A-G radar and that one stayed as it should. here my track showing the issue as described by the OP Markpoint-after-INS-update_1.trk

To fix the markpoint after slewing it (refining its position as you described) you need TMS forward to actually lock the coordinates in. Only then can you press 0 (MSEL) to make it the active steerpoint. then exit MARK page, select the tgp as SOI, press TMS aft (CZ) and it should slew the pod to your Markpoint location

Yes exactly. Apparently thats how it should be based on the EWR modelled in the sim. Just sad there was no info about that change

How sure are you? I tested it by placing every EWR in the ME, making sure they are active and none would show up at all. to my knowledge, a SA2 or SA3 search radar also shows up as „S“ until it is starting to track you. you might be seing those there.