![]() ![]() Most of the other suggestions here have just been a list of everyone's personal preferences. Well I'll back you up and say that I agree yours is the best way to go about it. Revelene님이 먼저 게시:My original statement was never about what was good or bad. I never mentioned that at all.Īpplication settings < Nvidia Global settings < Nvidia per-app settings If you are talking about setting per application settings, under Nvidia control panel. If you have something set in global, it will take effect, regardless of application setting. Global settings are exactly that, global. Per Apps BS is what NVIDIA wants as defaults, yea makes sense. If you don't know what you talking about, don't reply. If you actually look in Program Settings per app you see that the only global ones are the ones left alone by the app settings. ![]() Too many people do not seem to understand that when they enable Nvidia settings, the entire Global setting will take effect. You'll run into a whole lot less of issues, if you are not aware of what you are doing. Revelene님이 먼저 게시:As I always recommend, especially to people that do not understand the settings, just leave it set to "let the 3D application decide". I may be wrong or maybe games need added support for fast to use it well, but once I upgrade it will become very applicable I think. I'm at the point of achieving 60-80fps on most with settings I want and so not really helping me too much. I saw that here recently and have been experiementing, but seems from what others have said and so far I can't prove them wrong that it's more for games that you can run at higher frames(like 120+fps using a 60hz monitor) to begin with. There's also fast sync in Nvidia's vsync settings, which allows a game to have a higher framerate without tearing. fullscreen or borderless in-game may help with this too though depending on game. others like far cry 4 for example adaptive or vsync on much smoother and lag isn't a huge issue when playing an easy game against npc's. ![]() Introduces latency lag whatever you want to call it though. I think its a bug, as I have owned many previous gen cards and they never had this behaviour.īut curious if anyone else has noticed this, note its probably not going to be an issue in modern games which load up the gpu, also if people are not capping framerate.Mikel3113님이 먼저 게시:Avoid vsync/triple buffering in-game and in here most of the time, but some games it seems like some combo of fps limiter/adaptive or vsync combined with triple buffering is the only way to get no screen tears and/or stuttering. ![]() game stutters when exiting menus as it has to get out of idle clocks, so I tried prefer maximum performance, and its going down to 2d clocks, and not only going down it seems to do it a lot, the game was a stutter fest. I noticed when playing fable anniversary if I use optimal performance its not that bad but it isnt perfect, e.g. So expected behaviour based on all my old nvidia gpu's, is that when this option is selected the gpu clock speed will never fall below base 3d speed (typically somewhere in the mid to high 1000mhz range.), the benefit of this option is for older games where the gpu is overpowered so it falls down to 2d clocks, but then this causes stutters as 2d clocks wont be enough to run game smoothly, so typically in these games the gpu can have a problem of looping between 2d and 3d clocks, which "prefer max performance" fixes. Seems this isnt working properly for me, unless its changed by design. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |