Redwing_204

same here. restarting doesn't help

Thank you both for your feedback - very helpful. This is exactly what I was looking for. Much appreciated.

Good to know. I’m running DLSS. Thanks for that tip.

I'm returning to the F-14 after more than a year away flying other aircraft, and it would be really helpful to have a quick summary on the status of things - what works, what's bugged, etc? I'm aware of Heatblur's announcement of October 25, 2023 (https://store.heatblur.com/blogs/news/dcs-f-14-development-update-aim-54-phoenix-improvements-overhaul). More specifically, here are some things I'm observing as I return: I'm having no luck with the phoenix missiles (C or A). I'm firing at above 30,000 feet often at or near Mach 1 at the time of launch, at targets typically about 35 nm - 40 nm out, who are usually at an altitude of 10 - 20,000 feet. I have had zero success with a phoenix kill in TWS. I'm bafffled - I would have thought that I was well within launch parameters. Any thoughts on this would be gratefully received. With a TWS launch of the phoenix, I have noticed that the phoenixes are not showing their terminal status any longer, specifically, the blinking pattern that would activate in the last 10 seconds of flight denoting that the missile had gone active. Is that blinking status still a thing, or was it deprecated? If it is still a thing, what am I doing wrong? - why is that state not being achieved by the missile? Phoenixes are working well for me in STT mode and ACM mode, inside 20 miles. So I'm using these missiles like glorified AIM-120s right now. That's it for the moment. I'd be grateful for any thoughts on the current state of the F-14 generally, and specifically, any thoughts on the phoenix missiles and my remarks above. Thanks in advance for your interest. Cheers, Redwing

Let me give some more context on what I did in Process Lasso that ended up working for me. In Active Processes, right click on DCS.exe and choose: CPU Priority select "Always", select "High"; CPU Affinity, select "Always", select "Select CPU Affinity", select "P-Cores"; I/O Priority, select "Always", select "High"; Memory Priority, select "Always", select "Normal"; Power Profile, select "High Performance"; Efficiency Mode, select "Always", select "Off"; and Limited Number of Processes, select "No Limit". Under "Main", select "Performance Mode Enabled". Your mileage may vary, but that's what I did. Hope this helps someone else experiencing this F10 fps problem.

Sorry, not really is the honest answer. There are a number of setup parameters that many of the Youtube videos recommend. Setup is easy - less than 5 min. But I can't isolate which of those particular parameters made the difference for this issue. I just know at the end of it that this problem is now resolved for me.

Likewise, I've had this issue for a long time now as well - certainly more than a year. Exactly as you all describe above - massive drop off of fps when coming out the F-10 map view and back into the cockpit. I'm running an HP Reverb G2, with a RTX 3080ti, i912900k chip, and 64 Gb RAM on an SSD drive. Currently trying Process Lasso to see whether that helps with this problem, and have had mixed results. While I can't yet recommend Process Lasso as a cure for this problem based on my own experience over the past couple of days, it may nonetheless be worth a try - YMMV. Update 3 days later: Process Lasso is consistently working for me to resolve this F10 fps problem. I now exit F10 at the same fps I entered it (typically around 80 fps). This has resolved a problem I've had for well over a year. If you're experiencing this problem, this is well worth a try.

Ok, here's a possible fix - it's working for me. Hope you have some success with this too. Run OpenXR Toolkit Companion app, and deselect Open_Composite_DCS (DCS.exe). Run OpenXR Toolkit Companion app as usual. Run XRNeckSafer as usual. (I'm running the Beta 5a version of Necksafer). Cheers, Redwing

Same here. Was working fine earlier today prior to the update.

Did you ever resolve this problem? I have exactly the issue you describe above - MFDs not "seen" by DCS or Windows 11.

I had the opposite experience today. Mk 60A, fired in TWS at 38,000 feet at Mach 1.25 at 35 nm at two MiG-29s set in easy mode. Here’s the result, which is about typical in my recent experience - The first phoenix lost lock on the first MiG; the second phoenix killed the trailing MiG. Two more phoenixes fired at the lead MiG, the first immediately after the first phoenix lost its TWS lock. That third missile also lost lock and sailed off into the void. The last (fourth) phoenix was fired PAL inside 10 nm. It missed, spoofed by chaff apparently. I killed the last MiG with a Sparrow. Four phoenixes launched in pretty much optimal conditions, and one kill recorded. YMMV, of course. But I’m pretty much through with the tomcat at this point. There are other modules to fly. Wish you the best of luck with the phoenix.

Great feedback. Those stats would be very consistent with my recent experience also. In particular, you point out the need for launch at 30k or higher, and at Mach 1 or greater, with nose up at the time of launch. Like you, using those parameters, my PK is also probably around 40%, certainly no higher (and probably lower to be honest). That would be relative to targets out to about 45 - 50 nm, no further, and with a sweet spot closer to about 35 nm. Beauty is in the eye of the beholder though, I guess - for me, that PK is frustratingly low, particularly when you compare it to the performance of the AIM 120C right now which is flying well. (Yes, I know that's not an apples to apples comparison). The thing I'm interested in though is the claim of 55 - 60 nm kills at angels 25. That I have not seen, not even close. My experience is that the phoenix bleeds speed very rapidly in launches below angels 28 or so. To be candid, what I was hoping to hear is someone pipe in with some secret remedy, beginning with "Oh, what you need to do is choose [such and such a phoenix variant] and here are the launch parameters, and you'll be getting a high PK of 70% or greater at 60 nm again when launching at angels 25." I live in hope.

Could you post a tacview showing a 60 nm kill with the phoenix fired at angels 25? That's not at all my current experience with those missiles. At angels 30 or higher, and flying at better than Mach 1, I'm seeing the kill range closer to 35 nm. Below about angels 28, the phoenix seems to bleed speed very quickly from what I've seen. I'd be grateful if you'd post a tacview so that I can see your 60 nm kills with the phoenix fired at altitudes below angels 30 in particular (but frankly any kill at 60 nm with the phoenix right now would be interesting to see).

JoNay is right - if you can find a human RIO, that's absolutely the way to go. If not and you're flying alone, then I still think VAICOM is preferential to the Jester wheel. In the "go big or go home" category, if you find yourself looking for more information on the F-14, you can purchase the USN Pilot Operating Manual for the F-14 (NAVAIR 01-F14A.A.A-1) in two volumes on Amazon - F-14 Tomcat Pilot's Flight Operating Manual Vol. 1: United States Navy: 9781935327714: Books - Amazon.ca Enjoy the Tomcat.

Nice note. You mention this, but you should really check out VAICOM Pro and its extension AIRIO. IMHO, they're game-changers when flying the tomcat. Nice CF-14 livery, by the way. Enjoy.

I have this problem as well. I go through the sequence described above OK, and the various lights illuminate right up to AP/CPLR. I’m flying on speed AOA, lined up on the needles. But when I depress the nws button, the ACLS does not engage. Occasionally, I see the CMD Control light rapidly illuminate and then blink out. I don’t have a lot of experience with the ACLS, so I’m not sure if the problem is with me or not. I should add: I’m describing a MP experience.

This may be your problem - taken from today's open.beta update log file: Partial fix to AP altitude hold not engaging and holding properly (WIP).

This worked for me. Helpful detail in your instructions above. Many thanks.

Thanks for this response. Let me carry this information away. I can’t swear I wasn’t experiencing this problem previously with a Sidewinder.

In my case, I do not get the roving cursor appearing over the HUD, nor (as far as I can tell) the functionality of locking a target within range. What HUD mode would not show those indicators? Maybe that's my problem. I appreciate these settings (PAL / VSL) are limited in range -- that's not the issue I'm raising here. I also don't think the issue I'm raising has anything to do with PLM, in the sense that the circumstances in which PAL / VSL did not activate for me were independent of my trying to utilize PLM.

Yes, agreed - sometimes I'm not able to get VSL or PAL to work either. (I came onto the forum this afternoon to ask about this very point, but spent a moment first looking around at previous topics before raising it, which is how I came across your post.) It does seem very random, and relatively frequent - I find it occurs at least once a day for me (and I get between maybe 2 - 4 hours flight time in the tomcat, on average, per day). I was not aware of the fix you propose above - recovering this VSL / PAL functionality after asking Jester to lock someone. Will give it a try. Thanks.