Gunfreak Posted August 7, 2021 Posted August 7, 2021 So I get the target on my panel, I have master arm on, AA, AMRAM selected, move the slew over, but can't lock on it. i7 13700k @5.2ghz, GTX 5090 OC, 128Gig ram 4800mhz DDR5, M2 drive.
Lace Posted August 7, 2021 Posted August 7, 2021 Is it a RADAR return (white dot) or Datalink symbol (red triangle)? You can only lock a primary return, DL symbology there for information only. Laptop Pilot. Alienware X17, i9 11980HK 5.0GHz, 16GB RTX 3080, 64GB DDR4 3200MHz, 2x2TB NVMe SSD. 2x TM Warthog, Hornet grip, Virpil CM2 & TPR pedals, Virpil collective, Cougar throttle, Viper ICP & MFDs, pit WIP (XBox360 when traveling). Quest 3S. Wishlist: Tornado, Jaguar, Buccaneer, F-117 and F-111.
Gunfreak Posted August 7, 2021 Author Posted August 7, 2021 1 hour ago, Lace said: Is it a RADAR return (white dot) or Datalink symbol (red triangle)? You can only lock a primary return, DL symbology there for information only. It's a red triangle, with ID number on, but no white dot. i7 13700k @5.2ghz, GTX 5090 OC, 128Gig ram 4800mhz DDR5, M2 drive.
Lace Posted August 7, 2021 Posted August 7, 2021 That'll be why then. The red triangle are DL symbols shared via other flights or AWACS aircraft. In order to lock you need your aircraft to detect the target. Most likely reason it won't is your antenna elevation - your RADAR needs to be scanning the right bit of sky, both in azimuth and elevation in order to detect the returns from the target aircraft. Azimuth is achieved by moving the TDC cursor over the target, but your antenna may still be scanning over or under the target. You need to move it up or down until you get a white dot indicating a solid return (which may or may not be in the same place as the DL symbol, but should be close), or a solid red triangle (indicating a correlated return). Fortunately, the number on the red triangle is the DL target altitude. The two numbers on your acquisition cursor are the upper and lower altitude limits of your scan. If the red number is between the two white numbers then your RADAR should pick up a return. However, this is a huge topic and well worth further reading if you want to get the most from DCS. The Viper manual is a good place to start and I'm pretty sure the APG-68 manual is out there somewhere too... 1 Laptop Pilot. Alienware X17, i9 11980HK 5.0GHz, 16GB RTX 3080, 64GB DDR4 3200MHz, 2x2TB NVMe SSD. 2x TM Warthog, Hornet grip, Virpil CM2 & TPR pedals, Virpil collective, Cougar throttle, Viper ICP & MFDs, pit WIP (XBox360 when traveling). Quest 3S. Wishlist: Tornado, Jaguar, Buccaneer, F-117 and F-111.
Gunfreak Posted August 10, 2021 Author Posted August 10, 2021 I've now run this mission more than I can bare, always something gonig wrong, each time, I have the enemy plane in my rader, I'm searching angles 12 to -5 , the enemy is a angels 02, so my only conclution is that there is a moutain or somethnig between us. But I'm flying at angels 10-15 so should be able to pick up at target at angels 02 even if they are behind a mountian. i7 13700k @5.2ghz, GTX 5090 OC, 128Gig ram 4800mhz DDR5, M2 drive.
Exorcet Posted August 10, 2021 Posted August 10, 2021 Even if you have line of sight to the target, they may be getting lost in ground clutter in a look down situation. I've noticed that the F-16's radar seems kind of weak in look down and likes to break lock even at low angles. If you know where the enemy is, try narrowing the azimuth scan to 10 degrees for maximum update rate. In general I never use the 60 degree azimuth if I can avoid it. It's just too slow. Awaiting: DCS F-15C Win 10 i5-9600KF 4.6 GHz 64 GB RAM RTX2080Ti 11GB -- Win 7 64 i5-6600K 3.6 GHz 32 GB RAM GTX970 4GB -- A-10C, F-5E, Su-27, F-15C, F-14B, F-16C missions in User Files
Gunfreak Posted August 10, 2021 Author Posted August 10, 2021 6 minutes ago, Exorcet said: Even if you have line of sight to the target, they may be getting lost in ground clutter in a look down situation. I've noticed that the F-16's radar seems kind of weak in look down and likes to break lock even at low angles. If you know where the enemy is, try narrowing the azimuth scan to 10 degrees for maximum update rate. In general I never use the 60 degree azimuth if I can avoid it. It's just too slow. I havn't used the 10 but I have used the 30 and still couldn't get a lock, however last time I tried this mission my wingman had managed to get 2 of them on his tail on the way back, the migs followed him almost to our airstrip(and none of the other allied planes seemd to care) but I turned around and at that time I was at angels 3 and that I did mange to pick them up(even in 60 degrees) So it must be some interferance from the ground, I guess I can try and go low towards the objective next time. But I burn a lot of fuel, even if the mission is only like a 20-30 minute mission, I like to have have spare fuel. i7 13700k @5.2ghz, GTX 5090 OC, 128Gig ram 4800mhz DDR5, M2 drive.
Gunfreak Posted August 10, 2021 Author Posted August 10, 2021 Yet again tired. And I can't find a reason for not finding it. I flew towards it. I'm not at angels 2-3. It's at angels 2. No mountains in the way. I watched the replay and it flew right past me. However on the way back, I was chased, I turned around and find them on my radar right away and have no problems locking on. It must be a bug or is it possible there is some scripting involved? i7 13700k @5.2ghz, GTX 5090 OC, 128Gig ram 4800mhz DDR5, M2 drive.
Recommended Posts