I have the blue flashing bug on this driver. The only way that worked was to disable bloom. That should help some users. Boris, maybe you should take a look at that?
Enb 0.123.
Nvidia 310.70 WHQL
- Author
- Message
-
Offline
- *blah-blah-blah maniac*
- Posts: 17549
- Joined: 27 Dec 2011, 08:53
- Location: Rather not to say
Re: Nvidia 310.70 WHQL
Damn, i'm just one person to fix all driver bugs. If i do this, then ati users will start to ask the same for each driver version. Meh... i'll install that crap drivers now.
_________________
i9-9900k, 64Gb RAM, RTX 3060 12Gb, Win7
i9-9900k, 64Gb RAM, RTX 3060 12Gb, Win7
-
Offline
- *blah-blah-blah maniac*
- Posts: 17549
- Joined: 27 Dec 2011, 08:53
- Location: Rather not to say
Re: Nvidia 310.70 WHQL
I don't see this bug or any similar yet with default files.
_________________
i9-9900k, 64Gb RAM, RTX 3060 12Gb, Win7
i9-9900k, 64Gb RAM, RTX 3060 12Gb, Win7
-
Offline
- *master*
- Posts: 175
- Joined: 10 Dec 2012, 17:23
- Location: Sweden
Re: Nvidia 310.70 WHQL
Oh sorry forgot to tell you what enb...ENBSeries wrote:I don't see this bug or any similar yet with default files.
this one:
Kalicola Enhanced Graphics ENB
http://www.2shared.com/file/cLCXerJq/62 ... hics_.html
Default settings caused the blue flashes.
Can I replace the enbbloom.fx
With another mod? or is there anymore fx file that bloom depends on?
EDIT: nevermind...
Found the solution : http://enbdev.com/enbseries/forum/viewt ... &start=270
You can delete this post if you want
-
Offline
- *blah-blah-blah maniac*
- Posts: 17549
- Joined: 27 Dec 2011, 08:53
- Location: Rather not to say
Re: Nvidia 310.70 WHQL
I'll keep it for future generations.
_________________
i9-9900k, 64Gb RAM, RTX 3060 12Gb, Win7
i9-9900k, 64Gb RAM, RTX 3060 12Gb, Win7
Re: Nvidia 310.70 WHQL
this driver sux i have the same issues even in css my textures flickering so download alternate version
-
Offline
- Posts: 20
- Joined: 02 Jul 2012, 06:02
Re: Nvidia 310.70 WHQL
After installing 310.70 with ENB 0.119 I started having hang issues with the ENB Injector after I play Skyrim and exit the game. If I start Skyrim again I don't get the ENB active. If I close the injector and start it again it hangs. I have to reboot to get it to work again. None of this happened before 310.70 though. I'm using SkyRealism which was configured with 0.119 although I can try 0.125 to see if it makes a difference.
-
Offline
- Posts: 4
- Joined: 26 Dec 2012, 06:55
Re: Nvidia 310.70 WHQL
I just installed ENB for Skyrim and tried 1.02 and 1.25 as well as the most recent Nvidia drivers (both beta and normal) and I can not stop the blue flickering with SSAO or DOF enabled. If I turn those off it runs mostly fine (some sluttering when in a new area) but I love the DOF effects and miss them. Also when I run the game without SLI the flickering is always there no matter the settings so only enabling both 580s and disabling DOG and SSAO can I be rid of those terrible blue flickers! I decided to go with 1.25 and it has been great so far.
I hope there is a fix for it sometime, I absolutely love the ENB mod.
[EDIT] Upon further play time I was actually wrong about there being no blue flicker, I have it no matter what setting I have on. I tried turning all off and all on useing the cool GUI in 1.25. It appears I just can not use ENB at the moment with my system, the blue flashing is just too much. [EDIT]
I hope there is a fix for it sometime, I absolutely love the ENB mod.
[EDIT] Upon further play time I was actually wrong about there being no blue flicker, I have it no matter what setting I have on. I tried turning all off and all on useing the cool GUI in 1.25. It appears I just can not use ENB at the moment with my system, the blue flashing is just too much. [EDIT]
Last edited by SargentChimera on 26 Dec 2012, 20:57, edited 1 time in total.
-
Offline
- *sensei*
- Posts: 288
- Joined: 24 Mar 2012, 16:21
Re: Nvidia 310.70 WHQL
When will people learn, that newest driver is not always best driver?
If a new driver is released, ALWAYS read release notes first to see, if there are any changes that will affect the games you play.
If not, ignore that driver.
And even if: does that driver solve problems you have? Or other way round: You have no problems with a certain game, but that driver will solve some bugs that might appear. As you don't have problems: DON'T use it.
As conclusion: driver x solves problem y with game z - you own game z, you have problem y - only then there is a need to upgrade to driver x. In any other case stay with the driver you have.
If a new driver is released, ALWAYS read release notes first to see, if there are any changes that will affect the games you play.
If not, ignore that driver.
And even if: does that driver solve problems you have? Or other way round: You have no problems with a certain game, but that driver will solve some bugs that might appear. As you don't have problems: DON'T use it.
As conclusion: driver x solves problem y with game z - you own game z, you have problem y - only then there is a need to upgrade to driver x. In any other case stay with the driver you have.