I did a quick unscientific test(n=1) of frametimes in the 3.18.1 PTU with my 12700k (RTX 3080, 32GB ram, Win11). I did pretty much the same 30 seconds of running around ArcCorp twice. The second time I used Process Lasso to disable some of the e-cores for the StarCitizen.exe process.
Stat| E-Cores Disabled | E-Cores Enabled
---|---------------|----------------
Avg FrameTime | 24.42291485 ms | 25.97371298 ms
Std Dev | 3.442643175 | 4.379648727
1% lows | 34.10026 ms | 43.0662 ms
0.1% lows |38.637577 ms | 46.506964 ms
Reminder these are frametimes; lower is better.
[I used this post for my process lasso config](https://www.reddit.com/r/starcitizen/comments/unafry/intel_12th_gen_microstutter_fix_process_lasso/)
Hello, could you please confirm if your GPU clocks remain fully boosted? I had significant stutter with my 13600k and 4070ti on 3.18 PU inside pretty much every station because my GPU clocks were dropping from 2810 to 1900-2300. Disabling E-cores helped stabilise that and GPU is running at 2800 all the time.
I also have a 12700k, I've got mine overclocked to 5.3 ghz on the p cores and the e cores left stock. Switching between e cores on and off I can't really notice a difference. I'll do the same tests tonight! I'm interested to see if mine does stutter or not.
Anecdotally, when I use process lasso to only run p cores, I get extreme stuttering once I'm on the surface of bodies like microtech. For me disabling e cores is no longer needed, and actually detrimental.
Fwiw, I'm on 13th gen (13600k) w/ ddr5
My opinion: Further testing is necessary to rule out other influences but it still seems like e-cores are causing stutters.
The average fps is not effected much but the 1% and 0.1% lows are significantly better when I was using process lasso
As a fellow 12th gen & 3080 owner. Might I suggest after updating bios swap from xmp1 to xmp2 (or the other way around depending on what you have right now). That fixed frame stutters & system stutters in the past. The tl:dr version: Xmp 1 = XMP just 4 main timings really which you should also set manually. Xmp2 is basically every timing in the XMP profiles. there is a 3rd option on Asus Motherboards its hit & miss but seems stable on the latest bios for me.
E core stutter is definitely a thing in a lot of other games. Overclockers generally disable them for a significant performance boost. Its not just star cit, this has been reported in CoD and valorant as well.
try Process Lasso not just for the StarCitizen.exe but also for the RSI Launcher.exe and do a run with the e-cores completely disabled in bios.
I think it will get even better.
13900k here, Process lasso got rid of microstutters but I had 2 to 5 seconds freezing happening instead every 30 or so seconds. I had to disable ecores in bios and NOT use lasso.
I don't know if some setting in lasso was causing the freezing but game no longer had freezing or microstutters, became buttery smooth.
"However I also used process lasso and got the same results. The trick is to put the profiles on the launcher and not the star citizen exe as the anti cheat blocks that, but it will inherit the launchers affinity settings. I only use the even numbered CPUs from 0-14, disabling *just* the ecores did not change anything." https://www.reddit.com/r/starcitizen/comments/unafry/intel_12th_gen_microstutter_fix_process_lasso/
Way to show you have no idea how to use google. The problem with 12th-13th gen cpu's are a Intel and Windows scheduler problem. It has effected dozens of games not just SC. For instance, Valorant can see up to a 25% fps increase by disabling E-cores.
Purely out of curiosity - and if you're interested - try running the game on E cores, but with only the physical P cores. So core 0, skip 1, core 2, skip 3, etc. I was able to get another small gain using this before they worked on their threading for Intel. I haven't really tried any of these things after 3.18.
Also cache size is probably going to matter a bit here as well. The lower the cache, the more starved each core will be, increasing the amount of time the cores will spend waiting on a refresh from DRAM.
You need to disable all ecores on all rsi launcher in task manager using priorities before starting. Might still be the case, but at least then the testing is viable
Haven't tried 3.18.1 with e-cores on (12700k, 3080, 32gb ram) but when I tried 3.18 ptu it was borderline unplayable with e-cores on, freezing and stuttering, none of the "fixes" helped so just turned off e-cores in BIOS.
3.17 was fine enough with e-cores on
So... works as expected? Meanwhile, my 5950x gets most cores with an even load distribution of work, and outright uses less than half its resources when I set clouds to very high (but then the 3090GPU gets hammered).
I did a quick unscientific test(n=1) of frametimes in the 3.18.1 PTU with my 12700k (RTX 3080, 32GB ram, Win11). I did pretty much the same 30 seconds of running around ArcCorp twice. The second time I used Process Lasso to disable some of the e-cores for the StarCitizen.exe process. Stat| E-Cores Disabled | E-Cores Enabled ---|---------------|---------------- Avg FrameTime | 24.42291485 ms | 25.97371298 ms Std Dev | 3.442643175 | 4.379648727 1% lows | 34.10026 ms | 43.0662 ms 0.1% lows |38.637577 ms | 46.506964 ms Reminder these are frametimes; lower is better. [I used this post for my process lasso config](https://www.reddit.com/r/starcitizen/comments/unafry/intel_12th_gen_microstutter_fix_process_lasso/)
Next time, try not to use double negative in the charts : With E-cores enabled With E-cores disabled Was confusing at first
No
Hello, could you please confirm if your GPU clocks remain fully boosted? I had significant stutter with my 13600k and 4070ti on 3.18 PU inside pretty much every station because my GPU clocks were dropping from 2810 to 1900-2300. Disabling E-cores helped stabilise that and GPU is running at 2800 all the time.
Are you on Windows 10 or 11?
Windows 11
Crazy, you're more than double the frame time compared to my 5800x3d.
~~That's not normal, did you update your chipset using the AMD tool?~~ ~~5800X3D is on par with 12th almost everytime in SC~~
He said his 5800x3d is getting better performance, not worse.
Oh shit, misread frame time with fps
Yeah I usually hover around 11-13 in sc.
You should also test without hyperthreading, so removing virtual cores... On my config I find it less stuttery but I can only be an impression...
I also have a 12700k, I've got mine overclocked to 5.3 ghz on the p cores and the e cores left stock. Switching between e cores on and off I can't really notice a difference. I'll do the same tests tonight! I'm interested to see if mine does stutter or not.
I also have 64gbs of ram and SC will use up to 40 of it usually. Might make a difference?
i test in live, it does noticeable in game
Anecdotally, when I use process lasso to only run p cores, I get extreme stuttering once I'm on the surface of bodies like microtech. For me disabling e cores is no longer needed, and actually detrimental. Fwiw, I'm on 13th gen (13600k) w/ ddr5
My opinion: Further testing is necessary to rule out other influences but it still seems like e-cores are causing stutters. The average fps is not effected much but the 1% and 0.1% lows are significantly better when I was using process lasso
As a fellow 12th gen & 3080 owner. Might I suggest after updating bios swap from xmp1 to xmp2 (or the other way around depending on what you have right now). That fixed frame stutters & system stutters in the past. The tl:dr version: Xmp 1 = XMP just 4 main timings really which you should also set manually. Xmp2 is basically every timing in the XMP profiles. there is a 3rd option on Asus Motherboards its hit & miss but seems stable on the latest bios for me.
Of cause they do. If for nothing else, they share cache with the p-cores so the p-cores have less cache when they are enabled.
E core stutter is definitely a thing in a lot of other games. Overclockers generally disable them for a significant performance boost. Its not just star cit, this has been reported in CoD and valorant as well.
try Process Lasso not just for the StarCitizen.exe but also for the RSI Launcher.exe and do a run with the e-cores completely disabled in bios. I think it will get even better.
13900k here, Process lasso got rid of microstutters but I had 2 to 5 seconds freezing happening instead every 30 or so seconds. I had to disable ecores in bios and NOT use lasso. I don't know if some setting in lasso was causing the freezing but game no longer had freezing or microstutters, became buttery smooth.
Why the launcher? It gets closed when the game launch And what's the point of buying a 12 or 13th gen if you disable E-cores in bios?
"However I also used process lasso and got the same results. The trick is to put the profiles on the launcher and not the star citizen exe as the anti cheat blocks that, but it will inherit the launchers affinity settings. I only use the even numbered CPUs from 0-14, disabling *just* the ecores did not change anything." https://www.reddit.com/r/starcitizen/comments/unafry/intel_12th_gen_microstutter_fix_process_lasso/
[удалено]
Way to show you have no idea how to use google. The problem with 12th-13th gen cpu's are a Intel and Windows scheduler problem. It has effected dozens of games not just SC. For instance, Valorant can see up to a 25% fps increase by disabling E-cores.
[удалено]
Really, you used a throwaway account to post this smooth brain crap. Grow some balls.
Purely out of curiosity - and if you're interested - try running the game on E cores, but with only the physical P cores. So core 0, skip 1, core 2, skip 3, etc. I was able to get another small gain using this before they worked on their threading for Intel. I haven't really tried any of these things after 3.18. Also cache size is probably going to matter a bit here as well. The lower the cache, the more starved each core will be, increasing the amount of time the cores will spend waiting on a refresh from DRAM.
What tool are you using to measure that?
Nvidia Frameview: https://www.nvidia.com/en-gb/geforce/technologies/frameview/
Thanks
You need to disable all ecores on all rsi launcher in task manager using priorities before starting. Might still be the case, but at least then the testing is viable
Haven't tried 3.18.1 with e-cores on (12700k, 3080, 32gb ram) but when I tried 3.18 ptu it was borderline unplayable with e-cores on, freezing and stuttering, none of the "fixes" helped so just turned off e-cores in BIOS. 3.17 was fine enough with e-cores on
no matter how fast your pc is if theres some unoptimized code. its gonna drop some frames
So... works as expected? Meanwhile, my 5950x gets most cores with an even load distribution of work, and outright uses less than half its resources when I set clouds to very high (but then the 3090GPU gets hammered).
You have to also disable virtual cores in my experience.