While you're here, please consider supporting GamingOnLinux on:
Reward Tiers: Patreon. Plain Donations: PayPal.
This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Reward Tiers: Patreon. Plain Donations: PayPal.
This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Login / Register
- Founder of Baldur's Gate 3 developer blasts publisher greed
- Proton 9.0 (Beta16) brings more regression fixes, updated Steamworks SDK
- Windows compatibility layer Wine 9.5 released
- Backpack Battles has sold 500,000 copies in two weeks on Steam
- System76 release upgraded Lemur Pro laptop, plus a desktop sale now on
- > See more over 30 days here
-
The Triple-i Initiative gaming showcase is coming April…
- Pengling -
Oh Snap! Canonical now doing manual reviews for new pac…
- redneckdrow -
EA anticheat arrives for Battlefield V in April, will b…
- hell0 -
EA anticheat arrives for Battlefield V in April, will b…
- Purple Library Guy -
SDL 3 will prefer Wayland Over X11, if certain protocol…
- nwildner - > See more comments
Latest Forum Posts
- Probably quite slow for the next 9 days
- redneckdrow - How to find out if a game is native for sure?
- Myrhan - Logitech G29 steering wheel - Snowrunner support
- njasd2w - Weekend Players' Club 3/22/2024
- Pengling - Nintendo-style gaming, without Nintendo!
- Linux_Rocks - See more posts
View PC info
This is less of an issue if you have fast RAM.
View PC info
Well I'm running DDR4-3600...
View PC info
I just tried this method, limiting TW3 to first 8 virtual cores (Ryzen 7 1700X has 4 physical, 8 virtual on each of two "core complexes" ). I don't see a major improvement really. Same good 40 fps on average. Limiting it to just 4 virtual cores on the first CCX as you described, degrades performance to around 25 fps. Anyway, there is no point in limiting it more than amount of virtual cores on one CCX.
performance governor does help to avoid periodic framerate drops though. I think in my case the game actually hits RX 480 GPU limit and isn't so CPU bound, so may be with Vega it would go higher.
View PC info
0-3 : ~29fps (47% GPU load)
0-7 : ~25fps (40% GPU load)
All cores : ~21fps (33% GPU load)
Sitting in White Orchard 1080p. I also see a more stable frame rate when limiting to the first 4 virt cores.
Badly CPU bound here...
View PC info
This should be solvable by just not moving your mouse at all after loading the save game. The camera view should stay constant when loading the same save file. That way you could eliminate the different view having a different impact on resources.
View PC info
What CPU do you have? Such low GPU load surely means you are CPU bound.
UPDATE: from your profile, it looks like you are using Intel i7 2600k. That's quite old (Sandy Bridge). And I thought you are using Ryzen that's why you are limiting cores. I don't think there much point to do that for Intel.
So in your case, getting a recent CPU would help a lot.
View PC info
View PC info
Without forget wine dont use correctly many cores, is most common use a few cores (real cores) but with higher frecuencies
However him have at stock speed and wine improve with higher single thread and higher frecuencies
At 5.0ghz will be interesting, in this point is around 50% more strong in single thread than ryzen overclocked
Buy ryzen cpu thinking about wine is bad choice but in other tasks case video encoding, 3d rendering, virtual machines is really good
^_^
View PC info
As I said :)
Nope, this rig has a TR1950x in it.
View PC info
So that's 16 physical cores, 32 virtual ones and using 4 core complexes. So why is limiting to 0-7 worse for you than 0-4? Something surely doesn't work right.
I guess Thread Ripper support in the kernel is still flaky.