SlippyCheeze wrote: »SiegeMerchant wrote: »OP, before post that false advices like in first post, please reseach first LOL
In fairness, if there was an old default of 1, that would explain the different behaviour; I have a recent clean install, and I know that UserSettings.txt isn't rewritten during patching. So, while not completely covering the reasons why, it seems that the OP may well have a different experience to someone with a new, clean install.
They changed the name of the parameter (made a new one) for the 4.0 release by adding a ".4" to the end of it, so it couldn't have an old value from an old settings file, since it didn't exist before.SlippyCheeze wrote: »SiegeMerchant wrote: »OP, before post that false advices like in first post, please reseach first LOL
In fairness, if there was an old default of 1, that would explain the different behaviour; I have a recent clean install, and I know that UserSettings.txt isn't rewritten during patching. So, while not completely covering the reasons why, it seems that the OP may well have a different experience to someone with a new, clean install.
starkerealm wrote: »It does. “I have an fps increase” does not mean “it uses only one core” in any way. That is a logical fallacy.SlippyCheeze wrote: »not to be the cynic but i would be careful messing with those if your not certain of how it works. I can't say for certain in this case but the "-1" value is usually used to tell the system to use all cores whereas any positive number would tell it to use a specific number of cores. Of course, i can't speak to the hows and whys of your specific experience but just thought I'd point that out so people know to be careful.
-0 would be to use all your system cores, depending on how the games coded im pretty sure, but in most games a "-0" means to use all of X (In this game X being cores)
I'm also running with the default, -1, and ... can tell you with certainty that whatever problem the OP is describing is unrelated to this. Either they had it set to (positive) 1, or something else was causing the issue. The game uses more than one core.
It defiently doesnt use more than 1 by default. If it did, i wouldnt have noticed a good 10-15 FPS increase
Specifically, post hoc ergo proctor hoc, if anyone's keeping score. Though, confirmation bias is also an option, especially given that performance in ESO can vary wildly based on the current scenario in game.
EDIT: Derp. I shouldn't post when I'm this tired. But, yeah, @Woeler's right. The game is supposed to be running on multiple cores now. There've been a number of under-the-hood performance changes this year, including multi-core support. So, this "hack" should be unnecessary.
Additionally, like I said, performance in ESO can swing wildly based on what's going on around you, so saying you saw a 10-15 FPS improvement is fairly meaningless unless it's consistent over an extended period and under controlled circumstances.
For example: run Sanctum Ophidian a couple times, with and without this tweak, and see if it changes anything.
Jayman1000 wrote: »That value is the default -1 for me but cpu utilization is still pretty great, all 8 cores having steady usage for ESO, some of the cores having more than others, but that seems normal. Saw no difference when I tried to change it. But if it works for you and others that is great
@ItsNebula Tried this last night and it didnt do anything different.
Hayden_Knight wrote: »i get terrible fps especially in pvp and i have an 8 core AMD medium / high end rig.. im going to give this a try tonight and change the -1 to -8. if i notice a change for better or worse ill edit this post to say.
EDIT :- Not really noticed anything.
I changed that parameter's value to "@casparian is a mewling newbie" and my game wouldn't launch.
I infer this to mean the setting doesn't do anything.
Also, casparian sounds like Fiona Apple for some reason.