Moonshine

it was fixed once yet since the last 2 patches its busted again. 97 fall short and 105 drop far (curious how that happens since its a WCMD.. anyways..). besides that 87 and 103 dont really do damage still. bottom line, no cbu is currently useful as the one with effective submunitions are inaccurate and for the other ones you migh as well bring mavericks or use the gun

no issues with the default one. since as you said it would be loaded via DTC anyways, we better off just wait for that. as every pilot has his preference in MFD setup, your suggestion for a new default would take me much more time getting things to be the way I like it than it does with the current one as my MFD setup looks very different from yours. so as it will favor you, it will definitely bother me and surely some other pilots too. hence leave as is and hope DTC isnt years away from being implemented.

i dont think you can disable it. for level drop, just ignore and continue

reported here:

question: in RWS long pressing TMS up in an empty space on the radar screen activates spotlight mode. the longer the press is held, the more sweeps it does. however, even a very short press of TMS up will enter Spotlight mode. is this supposed to be like that or not? Spotlight.trk

Sorry to bring it to you, the last statement is just „feelings and impressions“ and have nothing to do with factual evidence proving or disproving the function this topic is about and therefore adds nothing to the discussion, only derailing it from its original intention.

any news on this? i get it, lower bar settings do not increase radar power so you technically dont get more range out of the radar. however lower scan area, more scans, more returns should in fact apply as TheBigTatanka said here: at the moment with how hardcoded the radar values are (same example is the lookdown subject) i bet it just wont make a difference to what bar setting you put it to, as skywalker explained in his original post.

same for me. instantly goes to STT upon promoting a target manually. this makes TWS unuseable. hope for a hotfix for that stuff. TWS_direct_STT.trk

Yeah some weird things seem to happen (focus on the missile going for the left target). In final stage of flight as the bandit passes the notch, the missile goes crazy, wobbling around terribly and then going straight up. so still some weird things going on, however the missile feels better than before the patch. Credit to that. Tacview-20220921-180256-DCS-TWS_TEST.zip.acmi

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: