I hate to add insult to injury, but I just read this:

 

http://wccftech.com/nvidias-latest-game-ready-driver-allegedly-killing-gpus-plagued-issues/

 

Lots of food for thought.  For me personally, I've been solid with the 361 drivers and definitely WON'T be updating any time soon now.

 

-Jim

No bricking...just fabulous stutter free and visual performance, driving a GTX680 2GB.   A keeper on my system.  Actually, I have never yet, had a driver set that gave such great blurry-free and high FPS performance in one set.   You always had one or the other...in varying amounts.  This set rocks!

 

You also have to wonder...are those that are having issues...have they over-clocked their card...whereby this driver set already brings out the best of your chip sets.  There's probably a lot of info that is NOT being shared....or forthright.  

 

And...as I maintain a B.S. free zone...the screen captures showing the graphic detail, along with the FPS readings....says it all.

 

Post Edit...after reading on that page link...this is what stood out the most for me:

 

EDIT: YES, MOST USERS WILL PROBABLY NOT HAVE PROBLEMS. It wouldn’t have gotten out of beta if it was a majority issue right? but do you want to risk your system being in that 1%?

Drivers should not brick hardware – at the worst, a rollback should resolve things. if this is happening to any number of systems, something is wrong.

 

 

No bricking...just fabulous stutter free and visual performance, driving a GTX680 2GB.   A keeper on my system.  Actually, I have never yet, had a driver set that gave such great blurry-free and high FPS performance in one set.   You always had one or the other...in varying amounts.  This set rocks!

 

You also have to wonder...are those that are having issues...have they over-clocked their card...whereby this driver set already brings out the best of your chip sets.  There's probably a lot of info that is NOT being shared....or forthright.  

 

And...as I maintain a B.S. free zone...the screen captures showing the graphic detail, along with the FPS readings....says it all.

 

Post Edit...after reading on that page link...this is what stood out the most for me:

 

EDIT: YES, MOST USERS WILL PROBABLY NOT HAVE PROBLEMS. It wouldn’t have gotten out of beta if it was a majority issue right? but do you want to risk your system being in that 1%?

Drivers should not brick hardware – at the worst, a rollback should resolve things. if this is happening to any number of systems, something is wrong.

 

Well considering that

 

1. I didn't write the article.  I saw this post on G+ and thought I'd check it out, considering that I watched this thread last week and felt a correlation was happening.

 

2. I didn't upgrade to this, primarily because of issues other users have had with it and I didn't want the possible aggravation.

 

3. While I to read the whole article and yes, I didn't miss the quote you made from it, bad luck runs in my family and no need to tickle the dragon's tail.

 

Objectively, I would steer clear until a new update comes out, which I suspect will be soon, given the reports that have been coming back about it.  If it works on your system with zero problems then great, I just wanted to contribute with further information being published about it.

 

Oh, and before I forget, there was a part to that quote you left out:

 

EDIT 2: It looks like the entire 364* series of drivers is borked. I would just stay away from all of them. Also, RIP inbox 

 

Read more: http://wccftech.com/nvidias-latest-game-ready-driver-allegedly-killing-gpus-plagued-issues/#ixzz44saS5Me0

 

-Jim

I hate to add insult to injury, but I just read this:

 

http://wccftech.com/nvidias-latest-game-ready-driver-allegedly-killing-gpus-plagued-issues/

 

Lots of food for thought.  For me personally, I've been solid with the 361 drivers and definitely WON'T be updating any time soon now.

 

-Jim

Thanks for the info Jim, have just had a problem with monitor, will go back to previous driver.

 

bob

Well considering that

 

1. I didn't write the article.  I saw this post on G+ and thought I'd check it out, considering that I watched this thread last week and felt a correlation was happening.

 

2. I didn't upgrade to this, primarily because of issues other users have had with it and I didn't want the possible aggravation.

 

3. While I to read the whole article and yes, I didn't miss the quote you made from it, bad luck runs in my family and no need to tickle the dragon's tail.

 

Objectively, I would steer clear until a new update comes out, which I suspect will be soon, given the reports that have been coming back about it.  If it works on your system with zero problems then great, I just wanted to contribute with further information being published about it.

 

Oh, and before I forget, there was a part to that quote you left out:

 

EDIT 2: It looks like the entire 364* series of drivers is borked. I would just stay away from all of them. Also, RIP inbox 

 

Read more: http://wccftech.com/nvidias-latest-game-ready-driver-allegedly-killing-gpus-plagued-issues/#ixzz44saS5Me0

 

-Jim

You speak true...you have to go with what works for you.  What I believe is happening, is that this particular set, really leverages the chips...and no over-clocking is necessary.  Like I said, I have never seen such great performance from my card...and when at idle, it sits at P8, at 40C.   I've been running it now for two days..pretty solid, and not one issue of which is being conveyed on some sites.  So...again...one does, what one does...or doesn't

 

For myself, I still can't get over the visual texture quality being dished out now, for FSX and P3D.  I can actually count the grass shoots in a clump at Friday Harbor.  I never knew there was such detail in the ORBX textures...but with the clarity and cohesion I now have...it's like all the scenery is new.

 

Yesterday, on one of my screen captures of Friday Harbor, running this driver set, and at the threshold...the asphalt and its wear is as life-like as if I was looking at it through a piece of glass....and I have never been able to say that, since even purchasing the GTX680 a few years ago.  I am certainly not of the 1 percent that might find problems...nope, not at all.

 

Post Edit:  Actually, it even extends to my desktop...and videos.  I just sort of noticed how clear and crisp, just desktop operations are now.  I would say, that this set is a hot-rod....and that could be a problem for some systems, the way they are presently configured.

 

Cheers,

You speak true...you have to go with what works for you.  What I believe is happening, is that this particular set, really leverages the chips...and no over-clocking is necessary.  Like I said, I have never seen such great performance from my card...and when at idle, it sits at P8, at 40C.   I've been running it now for two days..pretty solid, and not one issue of which is being conveyed on some sites.  So...again...one does, what one does...or doesn't

 

For myself, I still can't get over the visual texture quality being dished out now, for FSX and P3D.  I can actually count the grass shoots in a clump at Friday Harbor.  I never knew there was such detail in the ORBX textures...but with the clarity and cohesion I now have...it's like all the scenery is new.

 

Cheers,

What's funny is that I finally get that same detail with the 361 drivers on my rig...go figure.  Drivers in combination with P3D v3 has finally worked the way it should on my system and I get much better performance now.  I can tubeliners properly and get scenery that contributes positively in the immersion department.

 

"One does, what one does"...that is so true.  Some folks out there think they MUST update their drivers to keep up with the latest, not realizing it can do more harm than good.  Patience is a virtue, right?

 

-Jim

What's funny is that I finally get that same detail with the 361 drivers on my rig...go figure.  Drivers in combination with P3D v3 has finally worked the way it should on my system and I get much better performance now.  I can tubeliners properly and get scenery that contributes positively in the immersion department.

 

"One does, what one does"...that is so true.  Some folks out there think they MUST update their drivers to keep up with the latest, not realizing it can do more harm than good.  Patience is a virtue, right?

 

-Jim

Right, Jim.  I sat for a long time with the 388.x...somethings driver set...but I was never fully satisfied with the output of 'what' I thought my GTX680 should have given me.  Well...so here and there, I'd drop the coin...and update.  A few times, I went back from updating to the 388's...but as the comments of the O.P. really intrigued me...I drop the coin once more..and am I so EVER glad that I did.  I just shut down from an intense flight over ORBX's San Francisco...and man oh man...32.8 out of my locked 33 FPS...simply outstanding visuals...life-like, and my card only running at 64C in P0 state!!!

 

I actually will now probably retire from updating...for the GTX680...simply because I can't do better in visuals...than what I am getting across all my flight simulators...as well as banging at the 33 FPS locked ceiling in all of them, that this driver suite is pumping out.

 

So...this set is my 'sunset' set...until I get a new card at some point in time.

 

Cheers!

 

Mitch'er

I hate to add insult to injury, but I just read this:

 

http://wccftech.com/nvidias-latest-game-ready-driver-allegedly-killing-gpus-plagued-issues/

 

Lots of food for thought.  For me personally, I've been solid with the 361 drivers and definitely WON'T be updating any time soon now.

 

-Jim

 

361 Rock solid here & glad I didnt jump on these newer video drivers - thanks for heads up Jim

I have been using the 337.88 forever. I have tried others but no improvement. These seem to offer a little better AA for the buck.

I am running a 4 gig 760.

 

Bob

I may not have brought this up before, here at AVSIM, but I do get quite a bit of enjoyment from reading other people's posts about their flights, whether it be through pure literary description, or with pictures or even video.  I follow a few folks on Youtube and I watch almost everything they post now because I do learn a lot from their experiences across the board.  My posting of this info wasn't meant to upset, anger, worry, frighten or otherwise, but just to inform.  I'd hate to see the good people who take flight simulation seriously, make a bad mistake with something like this.  There's nothing worse than to inadvertently update a driver or reinstall an OS, only to have further issues with simming.  I fly like everyone else, but on a different scale and with a lower level of experience, so again, I do appreciate what everyone contributes here.

 

You all are most welcome for what I posted and I hope you all continue on your path, whether it be career or hobby, I for one, greatly appreciate the contributions.

 

-Jim

I was running the 361.43 driver, updated to the 364.72, everything seemed to be fine, but upon importing my NI profiles P3D profile imported just fine but I get an unexpected error message whilst importing my fsx profile, tried to reset all my NI setting manually and upon setting them into fsx the same error appears, rolling back to 361.43 no problems, any ideas? NI 1.9.7.6

 

Rod.

Thank heavens for this excellent thread.

 

And thanks to you, Mitch, Rich, and Jim for revealing things about Nvidia's screw-up that most folks without your knowledge of where to look(like me)would not know is happening with drivers released by Nvidia that totally screw-up existing systems.

 

Like you Rich, gone back to 361 and will stay there.

Thank heavens for this excellent thread.

 

And thanks to you, Mitch, Rich, and Jim for revealing things about Nvidia's screw-up that most folks without your knowledge of where to look(like me)would not know is happening with drivers released by Nvidia that totally screw-up existing systems.

 

Like you Rich, gone back to 361 and will stay there.

 

Anytime Rick  :wink: this is what I am using works very good but cant compare to any newer ones either (361.91) 

but I get an unexpected error message whilst importing my fsx profile

 

The new drivers have changed the name of FSX in nvidia inspector

from" MS Flight simulator X" to "Microsoft Flight simulator 10"

 

To get your profile to upload properly again all you have to do is open your NIP file with notepad and change the header name from the old to the new.

 

e.g

 

(<ProfileName>MS Flight Simulator X</ProfileName>) to

(<ProfileName>Microsoft Flight Simulator 10</ProfileName>)

 

Worked for me anyways!

Hi,

 

Hate to say it but the 364.72 driver set seem to be working fine here and appear rock solid since I installed them a few days ago. I suspect something else is afoot to explain the problems experienced on some systems.

 

Mike

Never try to use the same NVidia profiles after updating drivers or NI versions unless you like "mystery problems".

 

 

After updating NVidia drivers, always go to the NVidia Control Panel and Select each profile and "Restore/Apply". At this point the NI profiles will be gone. Before closing NCP make any one change in the profile and "Apply". At this point a new profile will appear in NVidia Inspector and it will not upset your system.

 

 

Obviously the profiles will have to be set up again, but in my experience hardly takes a minute...

 

 

Here's one of those "mystery problems":

 

I was running the 361.43 driver, updated to the 364.72, everything seemed to be fine, but upon importing my NI profiles P3D profile imported just fine but I get an unexpected error message whilst importing my fsx profile, tried to reset all my NI setting manually and upon setting them into fsx the same error appears, rolling back to 361.43 no problems, any ideas? NI 1.9.7.6