Posted by Yakumo @ 09:18 GMT, 4 November 2017 - iMsg
As a few things in here have really helped a bunch of people I threw together a little steam guide to try and spread the word, and will update if any other specific issues pop up -
It's really sad when a game runs so bad, people feel they need to write a whole page worth of tinkering out of desperation just to try make it run a bit better. What's even more sad is that these actually don't do jack sh*t either. Win10 fall update did absolutely nothing to the stuttering, coz it never was windows fault. Wiping the config folders does nothing either, why would it? That's anecdotal/superstition level BS right there. Updating to latest drivers is likely to make things worse for many players actually. Turning antialiasing off, etc, you gain like 2 frames, useless, that's not the problem, the problem is garbage netcode causing abysmal hitreg and all kinds of bizarre gameplay artifacts like fragging someone/ walking through an armor/items and not seeing-hearing it happen, you even turn back... than like 0.7 secs the game tells you "oops, it did happen", lol, I'v never even seen anything like this, it's "big rigs over the road racing" level fakap. ID??This game runs choppy on power rigs making 250+frames, most of the time looks like you are back to your old 60hz monitor. You try all these settings and guess what? Nothing happens, it's still choppy af :)
Edited by WunderKind at 02:37 GMT, 6 November 2017
This guide is nothing to do with solving network latency, game bugs or magically completing unfinished work in a beta product.
This guide is to help people ensure baseline system performance, so they can be fairly sure any issues from that point onwards are with the game and not their system or config.
Each point was added after it was noted it had had a significant effect for various people including myself, in several cases an absolute night vs day change after many days of being unable to play from severe fps loss.
The issues you're listing (rubber banding/failed item pickups) are very obviously lag and prediction related not your own client system performance, the same pickup issue is easily seen in Quake Live on a bad connection if cg_predictLocalItems is left at 1, the default. It's my hope when the prediction and net code is finished that if such things occur still at all that a similar option to the aforementioned from QL is added to give the user a choice as to the pickup behaviour.
Since you're in touch with id maybe you can get a statement why did October 5 patch took ours 20% fps? I am playing at "low" so there aren't any new visible graphic changes to admire.
It's under active development, not every change especially experimental ones can be FPS neutral. They've said that the November update's focus is primarily on performance, to the point that there's probably going to be no new content, so maybe all of that and more will be back.
The guide has nothing to do with anything since these do nothing to improve the experience. I know, I tried. The one thing that did help was a FB post where the guy pointed out that rolling back to a particular nvidia driver, about 4 months old(?), makes the game smoother, with FPS graphs as evidence instead of anecdotal BS. That worked. That's why I said getting the latest driver is NOT a good idea. The guide is BS, don't waste your time fiddling ppl.
Edited by WunderKind at 18:47 GMT, 6 November 2017
Yes this is all anecdotal but for myself disabling Game DVR, Game Mode and the Game Bar actually made it possible to play at all while streaming on a few builds, I didn't test them all, however dropping only ~2fps using nvec instead of 60+ as it had been otherwise for me was far beyond the realms of placebo and as such, and also on the basis of reports or performance problems with the features elsewhere, I'm happy to recommend disabling them to ensure they can't be interfering.
Moving to the Fall Creators Update while it was part of the Windows Insider program enabled me to play smoothly for 10+ games regularly instead of being forced to restart the client after every 3 (before the patch that made this possible for most other users), and made client side stutter (specifically local frame stutter, not enemy players suffering lag/their own client problems) that was prevalent in every game with the builds at the time almost entirely non existent. Others reporting the same and Microsoft themselves in a rare case of openly acknowledging a problem (game stutter) caused me to add that.
There are other causes of stuttering, but they're pushing performance for the November update particularly and it won't be the last time. The Windows Fall update is not a fix all nor could it be or has it ever claimed to be, however installing the update ensures that at least the issues Microsoft discovered will not be a factor.
Resetting my game config improved FPS overall in game, a quick clear and easily noticeable and replicated reference in the game was checking animation sequences in the menu FPS was going from consistently never peaking over 245 to not dipping below 285 as one character example. Several others reported going from what they considered an utterly unplayable in game experience on ~100fps and lower on gtx1080's in 100% of games over a week, significantly worse than a lesser card such as the 1060 on the same settings, to the expected over 200 after a reset. Many users that thought one of the last updates had severely lowered their FPS reported getting most if not all of it back after a reset. Some time later reports and tests showing this helped caused the Bethesda Community Manager to sticky it in the forums
I can't count the number of people who have had Windows Update replace their GPU driver or who have been through tens of driver upgrades without clearing everything which can cause problems. I'm not going to recommend specific driver versions when they're GPU specific as to which ones will give the absolute best performance for any given title, I would only advise anything other than the latest if it was known the latest caused a significant problem, anecdotally 388.00 Nvidia drivers were bad, but the the 388.13 seem to be fine for most people discussing them and earlier drivers do cause problems for other games, hence 'latest'.
At no point has this guide made any claim to guarantee solving any issue. Hence it was titled "Ensuring baseline system performance" and clearly stated "there is no guarantee your own specific issues may be solved", rather than titled "boost your FPS 40+" or similar.
Sure. Of course you will insist that you have one those '"magical" versions of QC that fixed it's own stutters with the fall update / obsolete config folder delete, while for me and my buddy f.e. who's game on his comp I tried, absolutely nothing improved at all... which in line with basically everybody I ever chatted with in-game. But I guess It's kindergarten time again :)
I just wanna save people from wasting hours of their lives with useless tinkering: you won't fix this game with this BS, because it's broken by the devs. Go see a movie with a nice gal or something instead :)
Edited by WunderKind at 11:45 GMT, 7 November 2017
After the last couple of updates the game runs quite well on my rig now. There are no stutters whatsoever, even in FFA (except for some warping enemies).
I found out that assigning not all CPU cores improves smoothness a great deal on my end:
1) install Process Lasso (free) so the settings below will be applied automatically each time you launch QC
2) within Process Lasso, remove one CPU core in quakechampions.exe's CPU affinity settings. In my case, i disabled core 0 (so that core 1-3 remain).
3) within Process Lasso, set quakechampions.exe's priority class to "high".
4) profit.
other settings:
QC: 1680x1050, 80% scale, medium textures, all other settings low, FPS capped to 180
just swallow your pcmr pride, forget you just bought a 1080ti or run a 144hz monitor and limit your fps to 100. you'll run 98-100 which is much better than 200-80 rapid spikes. your mouse aim will be smooth and the game wont be choppy.