![]() ![]() And yes, I did search for solutions, I know the rules. The game runs fine with all settings to max. To the others, there’s nothing wrong with my i7. I still don’t understand how external views wasn’t affected by this? The poly count can’t be that much higher? This disparity was centered on Nvidias Vysnc option and forcing it to ‘off’ so BMS can handle it on its own and ther’d be no conflict between driver and software. This just goes to show how system testing is required of all end users as roughly around the time where the NVidia drivers stopped causing the micro stutter problem for me I was also able to stop using NVidia Inspector and just set everything through the NVidia driver this (maybe?) it can help somewhere : īrilliant, thank you Dee-Jay! I-Hawks solution in the second link was exactly what I needed. BUT don’t blame me if it doesn t work every serious Tweaker will know that its much dependent on someones rig and personal preferences in terms of settings. Maybe someone will gain benefit from this too. Have to go back to the days when 306.97 was to go-to NVidia driver to see when that was a problem for kind of setting turned out the best - in terms of Vsync & Tearing (at least on MY RIG), was: I have VSync turned on in BMS to tame the wing rock monster and haven’t had micro stutter problems in a long time. BUT don’t blame me if it doesn t work every serious Tweaker will know that its much dependent on someones rig and personal preferences in terms of thats what I’ve observed too: If you turn Vsync in BMs 4.33 ON, then you will get, most likely, microstutters in some situations when you turn it OFF, it runs much smoother - but you`ll have tearing all the time - especially in pit view.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |