Mrwhitey998;n9197361 said:
Was my title edited to hang then? I knew I never said it lol
I edited the title for clarity -- forgot to mention it in the post. Sorry!
Mrwhitey998;n9197361 said:
Well I stick to 144hz for CSGO because it takes the piss switching between them and it's not noticeable any problems, unlike Skyrim lol, physics engine just fails above 60hz on that.
Also I've tried with both 60fps and Unlimited on, always causes the error, it's rare tho, you have to really switch quick. You try it?
Various games will require various settings, and that will likely always be the case. Consoles do not have to worry about it, since the games are specifically built around the exact parameters of the console's hardware and OS. If we're gaming on PC, we have to take the time to set our systems up for each title. Just the nature of the beast. You should be able to switch between Refresh Rates in a matter of seconds through your GPU's Control Panel.
As for CS:GO, that would definitely be a game that would benefit from blazingly fast FPS. For complex RPGs, where the game needs to sync a great many things simultaneously, FPS will often be necessarily limited to avoid issues. Frame-timing is vitally important for games like The Witcher, Skyrim, Fallout 4, Dark Souls, etc. If your FPS get too high, the game falls out of sync and problems arise.
In order to avoid issues with TW3, ensure
Vsync is
ON (necessary to avoid dropped frames),
Refresh Rate must be
60 Hz or LESS (PhysX calculations require this), and you should set your
Frame Limit to
60 or LESS (also to avoid dropped frames). Personally, because of FPS jitters and fluctuations, I've presently got the game running at a locked 48 FPS, and it has never moved. Rock solid performance throughout the game. You can give that a try as well, as it should leave plenty of performance overhead (which is a
very good thing for RPGs and Simulations).
I did see if I could recreate it last night, but it's not happening on my end. Couldn't get it to lock up using either the keyboard or the gamepad. I even tried firing off multiple different signs in rapid succession using a Blizzard potion. A lot of Nekkers were killed during the test, but everything worked well here.