Sylosis Posted 6 hours ago Posted 6 hours ago (edited) I had been on a DCS hiatus for a while and I'm jumping back. Up until now, I had always used labels, because I always thought spotting targets and bandits on a 32" monitor is more difficult than from a real cockpit. But, I decided to give a try to turning off the labels. My struggle is both BVR and also within 10 nm with Jester. Any bandit at 10 nm is mostly just a couple of pixels and I can't visually identify them. But Jester, He doesn't always tell you that you're locking a friendly even though you did, he's often losing lock, he more doesn't know if a target is friendly or foe (airborne unknown), etc. Finally, after maybe 10 campaign missions (Operation Sandworm), my AIM-54s have missed 100% of the time, although I do try to shoot them when being high and fast, within probably 40nm of my targets. Any tips on how you guys manage BVR with Jester (PvE) and how you make your Phoenix hit the targets? Edited 6 hours ago by Sylosis Windows 10-64bits, i7-8700k, GTX 1080Ti, 32 Gb RAM, MSI Monitor 32in 165Hz. Mirage 2000C, F5-E, Mig21bis, A10-C, FC3, F-18, AV-8B N/A, F-14, F-16, SuperCarrier
Czar Posted 5 hours ago Posted 5 hours ago (edited) Everything within 20nm use pilot acquisition modes (high/low vsl and pal). Yes Jester is unreliable up close, but regardless, you're much faster using the pilot acquisition modes, especially if the target is above the canopy frame using vertical scan high. Relying on Jester as locking "magic" is a mistake where a friend of mine used to do too much within 20nm. Just use him for spotting if the bandit is near. Using the command: lock enemy in front (or something similar) for Jester is a bit of a trap. If I recall correctly, it only works on highlighted contacts on the radar screen (white hafu). Further than 20nm, use TWS and the computer will do the rest with Phoenixes. If you want to STT a bandit (flying with a buddy), use jester wheel to grab the bandit using the distance and azimuth as reference that's written, or the contact number if you're in TWS. Phoenixes against bandits (fighters): NEVER launch beyond 20nm. Unless you want it to go defensive. Anything within 10nm is close to 100% kill. Max range are for bombers. You can use it like a Sparrow within visual range but you need to take into account its massive mass, although I've experienced a phoenix do a close to 90º turn right after launch when I was merged with a MiG-19. Big tip: Do some mission editor duels against ACE AI to get the handle of the Phoenix. Edited 5 hours ago by Czar 1
Czar Posted 5 hours ago Posted 5 hours ago A few more things: When you want to ID a target, use the TCS (nose camera). It is also a good sensor to check for target aspect ratio, if it is coming back at you after a defensive maneuver. If you couldn't lock using the pilot acquisition modes: go defensive and keep looking behind you to check if you're being chased going away fast. Re engage when you see a contact. If you're with a buddy, comms is golden. Use the TCS to positively ID before launch. I haven't used labels for more than 13 years now. Just make sure your monitor has the right sharpness value set up and it is close enough from your eyes to spot the dots. Horizontal scan has a range of 20nm. Zoom keys on your hotas, especially one that sets zoom back to normal is highly beneficial. 1
Ivandrov Posted 3 hours ago Posted 3 hours ago (edited) Never launch beyond 20 miles? Regularly launch at 35 miles with success against fighters. You might as well be using Sparrows if you only want to launch within 20. Key with long-range Phoenix use against fighters besides understanding it is a big fat missile and it wants high altitude launch and high altitude targets is understanding how the flight profile works and how much it is affected by bandit aspect. If you are chasing a bandit your range massively decreases, side on shots also have quite a reduced range. Hot high closure bandits are where you can comfortably stretch the range of the Phoenix. Even 50 mile shots are possible against high speed Foxhounds for instance. Keep in mind with Jester in PD TWS, he will have several blind spots when it comes to a target's closure. You have a Notch and a Hardware filter. So, Jester won't be able to see targets that are in drag aspect moving left or right of you (Closure equals your aircraft speed +-133 knots) or if they're matching your speed in a chase (Closure equals 0 +-100 knots) Edited 3 hours ago by Ivandrov
Recommended Posts