21 minutes ago, Maxis said:

@SimianFlu. since you have a 7800X3D. unless you know how to tighten memory timings or overclock memory (which may or may not provide any tangible benefit anyways) I suggest you not use process lasso, set your Memory Expo, stop tinkering and enjoy your PC.

@SimianFlu the above are also my feelings exactly on this.

PL is a nice tool.  It's just that with a 7800X3D it has much less direct benefit.  If you REALLY REALLY wanted to move some other process to another core then fine, but I've found that Win11 does a good job on its own with that cpu.   With the dual-ccd AMD's and/or Intel cpu's, it's a whole different ballgame.

Once MSFS2024 releases I am going to do a bunch of testing with PL + MSFS2024 to see if anything changes.  I don't think it will.  They're not reinventing the wheel this time (MSFS2024) as compared to MSFS2020, which was groundbreaking.

2 hours ago, Maxis said:

7900X3D and 7950X3D are two CCD units. more user intervention is required to get maximum performance when gaming. What works for those DUAL CCD CPUS WILL NOT WORK for the SINGLE CCD CPUS. So lets not add to the confusion.

Guilty as charged. I guess I just wanted to hear what other people with similar CPUs are doing. Should also be relevant for Intel CPUs with P and E-cores. 

3 hours ago, Maxis said:

stop tinkering and enjoy your PC

"tinkering pc's" had been our daily bread since the inception of MSFS 98, you asking too much of us.

2 hours ago, CarlosF said:

"tinkering pc's" had been our daily bread since the inception of MSFS 98, you asking too much of us.

Lol i've been playing the same tinkering game with PC's going back to 286 days with green screens 5.25 floppies and the first versions of DOS so i completely get that it never really leaves your blood. Its just that by design with these latest round of CPUS you're already getting i would say 90 to 95% (rough guesstimate) out of the chip already. If you know your way around the architecture and bios of socket AM5 and know how to set up your advanced PBO, tighten your primary and secondary memory timings and overclock the Infinity Fabric while keeping it all in sync with no performance sapping hidden error correction by all means have at it and chase down the remaining 5 to 10%. With that said im sure anyone who is willing to chase that last percentage is also willing to put up with all the "work" (Initial research, long memory training, boot freezes, windows crashes, bios resets, bios update procedures, documenting and inputting detailed memory timings and individual PBO per core values, memory and soc voltages + proper testing in a properly repeatable controlled setting) to get there.  They usually know their stuff or have been doing this for a while to understand and respect the ground rules .. which is mainly new architecture = new rules for the way the data is being handled by the new architecture.

So in a nutshell .... If you ....

Have no idea what the terminology in your Bios means and cant be bothered to look them up and understand how it works and affects the rest of your system.

Don't even know how to get into the bios..

Are used to someone building your PC or using a pre built PC and you just run the programs.

recently switched from Intel to AMD and just assembled the parts together (Basic PC assembly) without reading and understanding how a socket AM5 based system works vs a Meteor Lake system and then want to tinker based on assumptions you had from where you switched from

If you fall into any of the above categories i would advise someone to do some heavy research if you are going to do anything apart from enabling EXPO settings and enabling basic PBO on a socket AM5 based system.

I'm not saying your system will necessarily "blow up" if you screw up an overclock (Unless you really mess up your voltage settings) but sometimes what you think is a valid overclock is not really an overclock (framerate increase with worse 1% lows) or something else (like i/o or audio gets messed up because the system cant handle the overclock or someone overclocked by using the baseclock.

 

A properly built system with high quality components appropriately balancing and complimenting each other more times than not is all that is needed nowadays.

Edited October 9, 20241 yr by Maxis

5 hours ago, Maxis said:

7800X3d is a single CCD unit .. As @Bob Scott correctly stated No tinkering necessary. If you do not know what your doing your best bet is to ensure that you have set your Memory to EXPO settings and then step away from the BIOS. If you insist on chasing some performance then i suggest learning how to best set your PBO up if you need to tinker.

7900X3D and 7950X3D are two CCD units. more user intervention is required to get maximum performance when gaming. What works for those DUAL CCD CPUS WILL NOT WORK for the SINGLE CCD CPUS. So lets not add to the confusion.

@SimianFlu. since you have a 7800X3D. unless you know how to tighten memory timings or overclock memory (which may or may not provide any tangible benefit anyways) I suggest you not use process lasso, set your Memory Expo, stop tinkering and enjoy your PC.

i have expo enabled, 6000mhz CL30 🙂 as for overclocking afaik trying that with amd7 is much risk and not much reward. Well i will swap the 7800x3d with the next gen when they arrive

Edited October 9, 20241 yr by SimianFlu

15 hours ago, Cpt_Piett said:

Guilty as charged. I guess I just wanted to hear what other people with similar CPUs are doing. Should also be relevant for Intel CPUs with P and E-cores. 

Quick question for you @Cpt_Piett. Did you notice a big FPS increase when you installed 24H2 on your 7950X3D? For me it did, even compared to 23H2 with AMD fix.

For feedback, I have FSHUD v2 with 20 active/20 parked and running 90-110 fps at EGLL ( better then on 23H2). Using  Process Lasso I run MSFS on CCD0 and the rest on CCD1. As a bonus, I use Process Lasso to keep screensaver turning on during log flights. For ~%20 on the time, if screensaver turns on, MSFS CTD.

18 hours ago, Maxis said:

Lol i've been playing the same tinkering game with PC's going back to 286 days with green screens

That makes two of us. 

18 hours ago, Maxis said:

A properly built system with high quality components appropriately balancing and complimenting each other more times than not is all that is needed nowadays

Couldn't agree more, but since "tinkering" is in my blood I can't help it, I love to squeeze every last bit of performance out of my rig, I am married to miss efficiency, so tinkering is and will always be my way to extract all I can from my investment. Of course I could just build and be done with it, not me buddy, to each their own.

Edited October 10, 20241 yr by CarlosF

1 hour ago, vincentrouleau said:

Quick question for you @Cpt_Piett. Did you notice a big FPS increase when you installed 24H2 on your 7950X3D? For me it did, even compared to 23H2 with AMD fix.

For feedback, I have FSHUD v2 with 20 active/20 parked and running 90-110 fps at EGLL ( better then on 23H2). Using  Process Lasso I run MSFS on CCD0 and the rest on CCD1. As a bonus, I use Process Lasso to keep screensaver turning on during log flights. For ~%20 on the time, if screensaver turns on, MSFS CTD.

Only a 4% FPS increase and about the same frame time consistency as with 23H2. That was at 4K though - could be different at 1080p. 

Btw I got issues with FSHud when I put it exclusively on cores 9-16 (CCD1). Basically it took up to several minutes for it to recognize my voice readbacks. After I got rid of the core assignments (for FSHud), it's working normally. I still have MSFS on CCD0 and everything else (except FSHud and some system processes) on CCD1. 

Edited October 10, 20241 yr by Cpt_Piett

On 10/8/2024 at 2:13 PM, Bob Scott said:

Agreed--the 7800X3D runs MSFS like a boss right out of the box in stock configuration.  The only change I made to the motherboard's default settings was to enable my 6000 MHz Expo RAM profile.  There hasn't been any need to mess with SMT on or off, micromanaging processor assignments, overclocking, any of that.  It's truly the most "hands-off" configuration I've had in 30 years of flight simming. 

I still find Process Lasso a useful tool for watching what else is running on the computer, for sequestering ancillary processes if needed, etc.

Does MSFS' 'main thread' run on a particular CPU in Process Lasso?  I've always assumed some possible value of masking that CPU from other more demanding processes so as to theoretically reduce interferences as it were.

 

2 hours ago, Noel said:

Does MSFS' 'main thread' run on a particular CPU in Process Lasso?  I've always assumed some possible value of masking that CPU from other more demanding processes so as to theoretically reduce interferences as it were.

I can't say for sure. 

The last time I looked at that, I was experimenting with affinity masking and per-core clocking on my 13900KS machine with MSFS (several years back), and I vaguely recall observing that the last available P-core/CPU (HT off) appeared to be the most consistently heavily loaded, leading me at the time to believe the last P-core/CPU available was running the main thread. 

That said, when running MSFS on a freshly-built 7800X3D now, nothing obvious has jumped off the page at me when observing CPU loading in Process Lasso...but then again, I haven't been looking for it, either.  I just ran it with default settings--SMT enabled, no affinity masking or other special configuration other than enabling my 6 GHz EXPO memory profile.  MSFS ran so well in that default config that tweaking seemed a superfluous waste of time. 

4 hours ago, Bob Scott said:

That said, when running MSFS on a freshly-built 7800X3D now, nothing obvious has jumped off the page at me when observing CPU loading in Process Lasso...but then again, I haven't been looking for it, either.

I've kept an eye on this using the Ryzen Master app. I can't say that a specific core is used significantly more than others. Obviously MSFS runs primarily on CCD0 (the "cache" cores), but other than that, the 8 cores on CCD0 seems to be used randomly. 

On 10/11/2024 at 2:44 AM, Cpt_Piett said:

I've kept an eye on this using the Ryzen Master app. I can't say that a specific core is used significantly more than others. Obviously MSFS runs primarily on CCD0 (the "cache" cores), but other than that, the 8 cores on CCD0 seems to be used randomly. 

I took a specific look at CPU loading today...same observation.  CPU 0 was slightly more (by 5-10%) heavily loaded than the others most of the time, but not so much that I could draw a definitive conclusion.

That said, however the workload is being distributed, it's working well.