Discussion in 'Videocards - NVIDIA GeForce Drivers Section' started by MrBonk, Nov 5, 2015.
May i ask, (probably a silly question)
Any plans for amd cards?
Thanks for the update. Is there any reason we have to use a separate app to launch the profile editor now? The previous implementation allowed for quick access and I was rather fond of it.
frame rate limiter is working or not?
I found 3 new settings that I didn't see before:
1. Icafe settings
2. Maximum GPU power
3. List of Uniwersal GPU ids
What are this settings and what they do?
"weird font" must be intentional. I do have a right vertical scrollbar on 188.8.131.52 (2.11). FWIW, I'm on win7.
Does any one know what all the Frame rate limiter options do? cause there is over 2 dozen of them?
Also you can change Gsync into ULMB from now
Btw in 184.108.40.206 the font look weird also look like it might be tearing with scrolling almost like happens in Firefox when HW acceleration is off which to say it font looks wierd and it start to tear, and .net does use hw acceleration , i though i think . net should have hw acceleration enabled by default unless it manual disabled
Btw is there reason why there is no 30, 60 , 75 , 90 , 120 fps option for framelimiter now??
I just noticed according to AB/RTSS framerate counter both nvidia inspector and RTSS limiter limit to number they set to, where as before I Was seeing 1-2 fps devation from nvidia inspector implementation and would like to set nvidia inspector to 60 fps, though going from 220.127.116.11 which said 60fps to 18.104.22.168 with out touching settings that 60 fps was listed as 61.8.
When u limit something on nvidia inspector, it actually limits almost 2 fps higher. Now in this update it just displays the fps in the correct number.
For example 65 fps on the old inspector, in-game was actually almost 67 fps.
so it never really had 60fps option? which why RTSS framecounter never really show 60fps?
Gahthering this just how nvidia implemented the option? and RTSS limit is only one that can really limit it to what it set too aka 60 fps and not the 61.8 inspector show of the 60 fps option?
well at lest driver changes since I last really check, fix the 1-2 higher and lower fps that was shown when 60 fps pick, as month ago RTSS use show 60fps which is now 61.8 according to nvidia inspector droping to 58 fps and jumping to 62 fps at random, now it actual show fps that was picked.
Still think profile manager has hw accleration disable in it which would explain why font looks weird and it seem to tear when scrolling.
RTSS is the only option that really limits the fps on what u really want. And its the best in terms of lag.
The division game, doesn't like RTSS's frame limiter, i have some mouse stutter while using it, and im stuck with nvidia inspector. Also in-game fps limiter also sucks, because ruins the smoothness.
so i am right in thinking inspector is just exposing the OPTION hidden in the nvidia drivers, I still want to know why Nvidia put the function in the drivers and actual told people the option is there but still to this date have it hidden, why is the option still not listed in the NVCP??
Dunno, inspector runs for some good years. Probably at a time nvidia will overhaul their drivers, and make them like AMD did with their drivers, then they will put an official frame limiter option there. But it will not be as good as RTSS. AMD's driver frame limiter is not that good in terms of input lag or some sort.
oh RTSS is better imo, if I could set RTSS limiter with out actual have RTSS running I would use it to limit. Swtor is engine is mess to begin with so any stuttering inspector introduces irrelevant compared to own stutters
those can be manually edited in the inspector cfg files. I remember talking to orbmu2k about it years back, and he explained to me how it's done. But I didn't bookmark it.
Pretty sure it was on guru3d though.
I dont have CustomSettingNames_en-EN any more i deleted it think it would be recreated when 22.214.171.124 started but it wasnt remade
I dont think the cfg works anymore in the new version, since he separated the actual software from the driver tweaker.
When i updated i had my cfg tweaked to my fps numbers.
But this new version is better, has very dense increments in fps, u can use what fps u want. Problem is that the program doesn't cap it at a fixed number, as it shows into the fps table now.
yah 126.96.36.199 dont support CustomSettingNames_en-EN.xml or use it any more so this is not an option with 188.8.131.52, but atlest i atlest i found mirror to 184.108.40.206
Beside the manual way the wouldnt mater the 3c shown for hex number in 220.127.116.11 for 60fps is 61.8 in 18.104.22.168
But you have every fps you want, there. Also, the hex values are kinda wrong, or its fishy how it measures the fps.
For example 60.7 fps, hex value in the software is 3B. And 3B hex value is for 59 fps, not 60, and not 61.
And the other hex values from other fps limits.
EDIT: I think is the same hex values from previous version. But now instead of fixed numbers, it just shows the actual fps you are gonna see in games.
it dont have 60fps or 75 fps etc my point was why dont it have exactly those limits?? is cause that is just how Nvidia implemented the function and inspector is just doing what the drivers allow?
any my other points was hex values are the same from 22.214.171.124 to 126.96.36.199 but the actual framerate value show is diffrent, but the new fps values are actual fps value i got threw RTSS fps count which where not the same fps vaules inspector showed as being used.