Search the Community

The manual says that two things are filtered out. Things with no ground speed, such as mountains and a notching aircraft, and things with no relative speed, such as an aircraft moving away from you at the same speed as you. My question, is why is it like this? Do these both create no doppler shift? If so, why? Since a mountain is not moving, it should create no doppler shift, so it is filtered, then why is an aircraft moving away from you at your same speed filtered out? It is moving away; shouldn't it create a doppler shift? Otherwise, why does a mountain not create a doppler shift? The mountain is still moving towards you. My question is, why do these both create no doppler shift? I would thing one would create no doppler shift and the other would create a doppler shift.

I'm learning about the different radar modes of the F-14 and analyzing the capabilities and numbers of each mode I just realized that RWS has a range of 90nm, but the radar doesn't create any tracks of the targets to shoot the AIM-54. TWS also has the range of 90nm and it does create profile targets to shoot the AIM-54. So my question is, why would you use RWS, when you have TWS with the same range and even more capabilities? Edit: I just realized that RWS allows you to have any config of Bars and Azimuth, while TWS forces you to some configuration of less bars and less azimuth. Is that the only difference between the two?

Hi guys, I don't know where to post this question, but I'll just start here I'm trying to export info from LoGetTWSInfo() export function yet it keeps being Nill. LoIsSensorExportAllowed() // returns true in my case (it's single player anyways) There is other functions that get Sensory data that work. So I'm curious why this one isn't. I've been testing with the F-16. Anyone got some pointers?

I've seen some reported bug on the TWS issue in the current built. One of the topic talking about the F18 radar confused between more than 1 contact. Recently, I found that the TWS seems messed up by the "ghost" targets when launching the missiles on multiple targets. Basically, when I try to launch 10 AIM120C to 10 targets that is work perfectly in the previous build, the radar seems to be messed up by some very close targets and losing lock to the original targets during the missile launch. I initially think that it is due to the own missiles being scanned by the own radar. However, when I try to pick up one of that mysterious target and chase it. I found that it is a "ghost" target. Therefore, it seems that the TWS is messing up with some unknown emission during the missile launch, and may explain why someone report previously that the F18 radar confused between more than 1 contact. I attached the track file and the tacview file here for your reference. I record them in DCS open beta DCS 2.7.5.10869. Many thanks. new tests: 1. 2. TWS bug (ghost target).trk TWS bug (ghost target).acmi

SW 2.7.18.30765 TMS right in TWS to set all track targets as system targets (as expected). Cursor then nicely snaps to the targets and moves with them. null In EXP view, moving the cursor over the same target (now at 13,000 ft and in the centre of the screenshot below) the cursor snaps to the position of the target in the NORM view (upper left quadrant as shown in pic 2). This results in the cursor not tracking the target in the EXP view like it does when snapping to a target in the NORM view. null

NWS/undesignate pushbutton works fine to cycle targets while in TWS but once I inadvertantly lock up a "FRIEND" I can't seem to unsedignate without selecting "SIL" OSB or turning radar to standby momentarily. Has anyone else had this issue? I thought previously that there may have been more discussion about it but I can't seem to find anything.

Original post: Since ED stated that the “TWS ghost contact: fixed” in the DCS 2.7.12.23362 Open Beta update on 28 Apr, 2022. I updated the game and tested it again on 30 Apr, 2022. However, I found that my TWS lock is still messing up by unknown contact when launching multiple AIM120s. In this mission I firing AIM120s to five IL-76MD, I suddenly locking an unknown target (170Vc, 0.7RNG; as you can see in 1:20 in the attached video) when I switching targets. This clearly not the own missile (as the own missile must be negative Vc), and not the IL-76MD (as all of them are at 900Vc, 2X.X RNG). The unknown contact messing up my TWS, and I finally losing tracks for all the previosly launched AIM120s. Although the AIM120s finally hit targets, it is only due the the current build of AIM120 able to turn on their own radar in the final phase to aquire the target, my own radar already losing tracks for the AIM120s at the time when detecting and losing the unknown target. Therefore, the ghost contact issue is not completely fixed, it only disappear faster than before, but I can still detect it easily when switching target in multiple AIM120s launch. This test finally merged into the original post and seems haven't reported again so I put it here again. As following @BIGNEWY advice to wait the new patch DCS 2.7.15.26783 Open Beta releasded on 22 Jun, 2022 and test it again. I've done the same test today 23 Jun, 2022 with the same mission, actually the issue is reproducible. This time I also use the HMD to tace what is being tracked, and I found that I have tracking something behind, which is improssible because no matter IL-76MD or own miissiles sholud be in front of me in this scenario. I inclued all the track files and tacview files on the tests done on 28 Apr, 2022 and 22 Jun, 2022, as well as the mission file here if you want to try. I hope that this issue can completely fixed in the coming patch. Tacview-20220430-222445-DCS-1 vs 5 AIM120 train.zip.acmi TWS bug 20220430.trk Tacview-20220623-095334-DCS-1 vs 5 AIM120 train.zip.acmi TWS bug 20220623-2.trk 1 vs 5 AIM120 train.miz

Hello. I just got back into the hornet and have encountered a real challenge when in BVR engagements. A head on, no threat scenario is all and well, but I am struggling to perform BVR tactics like cranking when being engaged by a serious threat without loosing my contacts when maneuvering. I figured out there is a spotlight function which follows the TDC, but it seems rather unintuitive to have to first select the target, and then activate the spotlight function as well as adjusting elevation if the target starts to maneuver as well. So, how do you most effectively work the radar in BVR, in both RWS and TWS modes? Thanks for any inputs!

I have just picked up the Hornet and I have some questions about TWS and its functions. 1. When "locking" a target in TWS mode and firing an AIM-120C, pressing Undesignate/NWS switches targets, does this "lose" the lock on the original target and cause the missile to go pitbull 2. If so, does this give the bandit an RWR warning BEFORE the missile goes pitbull assuming I still see him on my own radar

On radar screen, we now how extra strange dectection "GHOST" BRICK, which is jumping closer as soon a real detection brick will catch it. Will be still there, no matter how many BARS, azimuth scan angle, RWS or TWS... PG-73_radar_bricks_BUG.trk

i noticed an issue with the radar during southern watch quick mission where in TWS modes mode Jester allocates and detects 1 target as hostile so i am no longer able to ripple fire the Phoenix's off if i go to STT i noticed jester can see one target in yellow and the other 3 are blue (DL) targets, that i can select for STT.