cesarferrolho

Well, since i don't really want to open a new thread on the related subject. I would like to ask this: In the current DCS version (2.9.19.13478) What is the AIM-54 top speed (in mach) and what would the ideal conditions be to achieve it? (I assume it may vary for each Phoenix model, of course)

Holy smokes... 100+ thousand feet, sustained. Just tested real quick the 31K variant, nice work! Steering on the ground is a bit wonky. There is some small white noise during the afterbuner sound, sometimes. Other than that seems pretty cool

Cool! Do you need to first get into a Su-25T cockpit before getting into the MiG-31K ?

You can also practice the training mission for Case I recovery that comes with the Tomcat module. It has a simple diagram in the briefing screen, but with some nice info. And the mission itself even has those green squares to aid in doing the proper circuit. Sadly there is no Case III training one, only Instant Action missions

I assume Jester did not go to P-STT, i got the lock at around 60nm or so, the target was an il-78 tanker, the lock remained steady and accurate several minutes after it landed.

at least 3 minutes after it landed, i still had a lock. I Launched one Aim-54 before and another after he landed, both failed to hit

Should that be possible? An STT lock that is maintained long after the target has landed?

I'm afraid the actual link for download doesn't work

Doesn't seems like a smart move for 11. So you can't manage it? Or thrid party software is needed for Win 11?

I'm using Win 10 and i can assure you my DCS log pointed out to parked cores in the beginning of the log file. And once i disabled E-cores in my BIOS, it showed no more parked cores and i stopped having problems (Stutters and Freezes). I also used to have stutters in another completely different game, before disabling E-cores

No, i'm using Windows 10. Half the power? No, it's a 12th gen i7 12700. Only a few cores are E-cores. I don't notice any loss of processing power at all. Seems to me like Intel really droped the ball with that E-Core BS. I'm not inclined to install more third party software to solve bad engineering/programming from Intel and/or MS. It's good as it is now, for my needs

Ok, but ultimately, when i looked at the DCS logfile, it complained about core parking in the first lines (now i remember it better) and although i had used some registry alteration or something along those lines to unpark, it remained the same, in terms of the DCS logfile. Disabling the E-cores in BIOS was my only remedy, at the end of the day

Like i said, i had tried just about everything. I used, for like a year or more, Process Lasso, which does that: bounding DCS with P-Cores alone (or any config i want). Then, ED, after some update, advised to not use Process Lasso anymore, and indeed, it wasn't needed in general and using it would cause problems. But, some more updates after, the problems came back, and this solution of disabling the E-cores has been great so far, with no performance downside that i can observe. I'm not saying it's the best solution overall or that it will work with any Intel processor, but in my case, it was the best solution i found.

..For me, the proper solution was to disable E-cores in the BIOS. I had tried everything else. And solved the problems not only in DCS, but also another game.

Did you make sure you are using a Tanker with basket? Like the KC-135 MPRS, for instance