Discussion in 'Videocards - NVIDIA GeForce Drivers Section' started by kens30, Sep 19, 2014.
Yeah, that's called a temporary solution
So it's possible that my 680GTX will support that DSR in the future, nice (I still want to use my 680GTX till next generation)
Standard bilinear downsampling (custom resolution in Nv control panel) looks blurry, and when I used programs like gedosato downsampling tool (it use lanczos resampling) I could immediately tell the difference in clarity (perfect sharpness after lanczos resampling). Hope this Nv scaling will look similar, because gedosato compatibility isnt good (no dx11 games). IMHO lanczos resampling provides perfect AA and clarity, even MSAAx4+SGSSAA looks worse
It's not a bug. Nv card is just reading EDID information from your HDTV (so HDTV is to blame, not Nv). For example sony HDTV + Nv card in PC mode works fine (0-255) without any efforts
Hey guys, was all excited for these, but ran into a problem on my son's rig (mine is fine).. These drivers WILL allow me to install even though they crashed right in the middle of installing, reboot loop followed.
My son has SLI'd 660Ti's & GTX285 for PhysX
There in lies the problem (as I figured out afterwards that these are only for 400 SERIES CARDs and up) the driver doesn't halt when "checking compatibility'
Quick thinking and a switch of the cards allowed my to boot again but others may not be so lucky.
This is my son's son's pc, my personal installed fine. This is win 8.1 x64
So, even though I already know the answer, is there ANY WAY around this? Simply to use this card for PhysX makes games like Metro & Batman AO MUCH more enjoyable and fluid.
This means, going forward, I can't use ANY drivers on his rig the way it sits now? That is really a bummer, I can't believe im the first one to have this issue!
Let me know what you guys think.
test this version
http://www67.zippyshare.com/d/89217937/18/Media player upscaling edition 1.1 setup.exe
Fermi can definitely downsample from 4k, I've done it at 50hz and worked perfectly for the older games which can actually run at a respectable framerate lol.
My point was to offer mid-way DSR options(even in fermi), like 1440/1620/1800p, it doesnt have to be straight 4k. And my hypothesis is because they downsample anyway its possible, just save us the trouble of having to create custom resolutions.
Try a modified INF to include the GTX280 and then try again, if it works, then in future just use modded infs. But yes if it doesn't work, then pretty much sucks for everyone. IMO its a deal breaker, you can use your old cards as physX anymore.
Hell why didn't I think this would happen when they dropped support for the Dx10 GPUs.
The driver doesn't support the GTX285. After installing the new driver, try to update the driver for the GTX285 via device manager or you will have to buy a gt640 for PhysX.
Has the "Out of Range" G-Sync/Asus Swift bug been fixed with this driver?
(The one reported HERE)
In my case i lost 1000 points in fire strike from 13600 to 12600 whit this driver
getting the same in Diablo 3, after OKing it a few times the game runs ok. This is how nvidia welcome me back to the green side, go figure.
I'm having exactly the same issue, game comes up with the same error, if I OK it a few times, it'll launch just fine.
It's SweetFX/ENB wrappers/injectors, not NVidia
They changed something and this broke SweetFX.
kk, let me try.
EDIT: Can confirm deleting SweetFX fixed the problem for me.
SweetFX still works fine for me (although via RadeonPro since I'm on 8.1)
We must ask Balatour a new injector
Original or Balatour injector? With Balatour's one I got the same problem.
yeah, that could be it, I had the actual files in the D3 folder.
The Divinity: Original Sin SLI profile has a mistake in it.
The app name is 'eocapp.exe' not 'aocapp.exe'.
I wondered why my performance had tanked and, firing up Nvidia Inspector, saw that only one card was being used. Checking the profile revealed the above mistake for the associated executable.
Skyrim (without mods) launches fine for me.