michaelray

Awesome thank you for the input. I just started using PL as a way around the core parking. However I like the idea of moving other apps off of CCD0. I will do as you suggested and let the drivers do their thing and just use PL to place the other apps on CCD1.

Ok I now seem to have core parking working consistently. Problem is I am not really sure what fixed it as everything appears the same to me. Four flights with MSFS2024 (all re-launches of the app) and consistent core parking every time. So fingers crossed it stays this way.

I am using AMD Ryzen Master. I make MSFS 3/4 screen and make sure it is in focus. I will go back to the start and check every thing again before I do a full re-install. can I ask why you are not a fan of PL?

Just upgraded to the 9950X3D. ‘Same issue here. I have followed all the advice with multiple attempts and can not get core parking to activate. Currently using Process Lasso to put MSFS on CCD0. This is frustrating but I will continue to tinker. I did put a fresh copy of Win 11 over my existing copy in the hope it would fix it as others have suggested. Maybe it’s time to bite the bullet and just do a fresh install.

Yes those instructions look daunting. However once you read through them a couple of times and then just make a start and work through line by line it is not too bad. I use 1024 and find the visuals to be more than adequate. Well worth the effort.

So here is where I get confused. Marcus further down the thread you said that with MSFS that you could see 6 parked cores when it was in focus. So is MSFS effectively only running on 6 cores? That is 2 less than my 7800x3d, although you are running at a higher frequency. If I were to invest in upgrading the CPU, would a 9950x3d make more sense as with MSFS cores parked it would utilise 8 cores. Is there some reason the 9900x3d is considered a better choice?

Thank you very much for your summary Marcus. I look forward to any future comments you have regarding this CPU. I currently have the 7800X3D and are thinking about an upgrade. FPS is not that important to me but smoothness is.

I tried to follow Ian’s method as well. All ok up to the point where ‘Override DLSS-SR presets” is not showing. Just like wined posted. Hope somebody can jump in with some thoughts on this. I am on the latest Driver 572.16 NPI is on 2.4.0.8 DLSS is 310.2.1.0

This is how I fixed for MS2020. However I don’t believe these settings are in the config for 2024. It is just rubbish we don’t have more control.

@ ashepard316 I fly in and out of UK2000 regularly in the AS320 and sometimes the NGX. I can maintain 30fps (not much headroom to spare though). I have a i3930K @ 4.7GHz with a GTX980. You have not mentioned what traffic you are using. I see the traffic slider set at 50%, that can be a lot of traffic at Heathrow and AI traffic is very CPU intensive. I use MyTraffic6 in conjunction with Aircraft Traffic Optimiser to limit the number of aircraft in my vicinity at any given time. If I had 50% traffic set at UK2000 Heathrow and no traffic optimisation my frame rate would tank. I set traffic to 25% and limit the number of aircraft with the traffic optimiser to 30. If you do a forum search for Air Traffic Manager that will give you some details. Air Traffic Manager does not work with all AI options though. They are fairly high settings you have dialled there. Have you tried backing those off a little? ​There is also another excellent topic running at the moment titled "A Frame-Time Analysis of P3D v3 -- Effects of CPU Affinity, Frame Lock, and HT". Not sure if you are already utilising some of those enhancements? I use a combination of them to achieve smooth performance at Heathrow. Out of the box I would not be able to achieve that. Regards Michael M

I remember reading in one of Rob Ainscough's posts a while back that LM had actually looked at working on excluding clouds from AA. I believe LM cited issues with comparability as the reason they did not go ahead with it. This was back in V2.5. I was hoping that we may have had this with V3 but unfortunately not. Without some level of SGSS I find it difficult to achieve the level of AA I am satisfied with. Michael M

Yes definitely doesn't work. Closest option is to set the refresh rate of your monitor to 30Hz, if your monitor does support this. Michael M

Excellent been wanting a fix for that. Thank you for the heads up. Michael M

I had also notice this while sitting at the gate. For example UK2000 Heathrow, CPU was bogged down for a couple of minutes initially then would improve. I would then enable Traffic Manager and the CPU utilisation would increase around 20% for another couple of minutes before dropping back. For me it was the Jetways operating that was causing the issues. In V2.5 I had this disabled but forgot to do the same in V3. On my system these have a huge hit on resources. If anyone is looking to disable it, it is hidden in your MyTraffic6 folder then MyTraffic/Aircraft. Somewhere in there is Manage_Aircraft_Config and this will let you disable the Jetways. I am still finding that in V3, MyTraffic6 in loading more AI for a given setting then in V2.5 so have had to adjust levels accordingly. Michael M

Yes Jay I am. If I go into the traffic sliders and reduce to zero all is good again. I am testing like for like against V2.5 compared to V3 in the way of settings. Only difference for me is I do not have FTX Global and OpenLC installed yet. I am not sure if the Traffic Manager is releasing the traffic immediately after it does the "delete" cycle. So even at MT6 @ 20% and Traffic Manager @ 20 aircraft I have to wait around 2 - 3 minutes before the stutters are gone. If I reduce traffic sliders they are gone immediately. Also when I monitor the Traffic Manager after the console window shows it has deleted x number of aircraft the "Last Count' figure stays on the original aircraft number. The last count does not decrease until around the 2 or 3 minute mark. Even when I feel that the Traffic Manager has released the aircraft I definitely can not carry the same settings as V2.5. Can I ask if you could check your Traffic Manager and see if its behaviour is identical to what you had in V2.5 in terms of time to delete. Regards Michael M I will try the standard AI later and see what results I get.