However, simply rolling back to 1.26.7 netted me a solid 30 - 40 fps gain, back up to where I was prior to the 1.27 update and switching to Ryzen (the 1.27 update hit while the PC was down to switch out to a Ryzen 1700 from an i7 4790k). FPS on 1.27 sits at mid to low 20s on average with peaks in the low 30s, as well as major stuttering issues in cities and inclement weather. Well, I can tell you right now (at least with Ryzen for sure) that locking down the game to a single core was a bad idea. ETS2 is actively developed by good people with more time and resources than I have. The others (FSX and MSTS) had stopped active development years ago, so application performance and behavior was set in stone and could only be "fixed" externally. Honestly, I don't want to worry too much about it I'd really rather not do a deep dive into performance-monitoring and tweaking ETS2(and ATS) like I have other, older sims. It could be blamed on process management, or it could be something else entirely. What was a noticeable stagger, like an accumulation of micro-stutters, has turned into more of a hard stop and then everything continues like nothing happened. But when they happen, they seem to have more impact than they did under 1.26. There are still some occasional major stutters, probably when crossing major area boundaries on the map, and probably aggravated by my using a spinning hard drive and not an SSD. On the other hand, under 1.27 any micro-stutters that I've seen mentioned by various users seem to have disappeared. A quad- or more core CPU and Windows 10 should be able to sort things out well enough by itself, and any further tweaking might be better left to individual users through optional configuration toggles - maybe with a rudimentary detection of CPU, number of cores and OS version that auto-selects the default behavior at game startup. In general, I'm not sure if the game should be doing this at all - except as a workaround for older, primarily dual-core CPUs on versions of Windows older than Win10. Arbitrarily selecting Core 1 can be an OK workaround, but as a whole solution it's one-size-fits-none. It's hard to tell which core is the most suitable without benchmarking the CPU. On almost every CPU, one core will run hotter than the rest. Locking a process that maxes out a core carries some downsides - Not all cores perform equally well it varies from one CPU to the next. With "Game Mode" announced in the next major Windows 10 upgrade, it appears that Microsoft is applying exactly these plus some additional low-level optimization tweaks that can only be done at the OS' own access level. Along the way, the effects of tweaking them got more and more subtle as Windows' own process and memory management improved. I played with these settings on the same hardware through Windows XP, Windows 7 and Windows 10. Dual-core CPUs will show more degredation in other process' performance compared to quad-core CPUs. It's the best performance, but the most tradeoff. This will give the most stable performance, but might constrain other processes that need the resources - like broadcasting your game. If you elevate a process' priority to "High" and lock it to a particular core, you Windows will largely stay out of the way and won't micro-manage the thread quite so much, and it will fall back to shuffling priorities and cores on the rest of the CPU for other processes, while mostly leaving your chosen process alone to do its thing. This may or may not affect the game's performance, but it keeps it from impacting other threads quite as much. If you elevate a process' priority to "High", Windows will shift routine threads around it and do a better job of keeping other threads out of its way, no matter what core it runs on - but it may still bounce the thread around amongst other cores to balance out the CPU workload. If you lock a thread to one core, it will stay assigned there, but Windows may still grab that core if it thinks the thread has or can be paused/suspended. I think this is because Windows asserts its thread and process management above all else you have to work with it and give it the right hints, or you'll wind up working against it an get no performance gains or only erratic ones. On its own, it's more random in having any effect. One thing I found is that setting the affinity mask works best in conjunction with elevating process priority. I'm quite familiar with affinity mask tweaking as well as process priority tweaking - I've done quite a bit while running Flight Simulator X and MS Train Simulator on older hardware.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |