Sign in to follow this  
phmcr

NVidia 378.66

Recommended Posts

EDIT: topic should read NVidia 378.66

 

 

Hi, just updated the NVidia driver to the latest, 378.66 which then crashed FSX when opening.

Cause according to appcrash was DX10fixerlib.dll.

Reverted back to 378,49 and all is ok again.

 

Menno

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

EDIT: topic should read NVidia 378.66

 

 

Hi, just updated the NVidia driver to the latest, 378.66 which then crashed FSX when opening.

Cause according to appcrash was DX10fixerlib.dll.

Reverted back to 378,49 and all is ok again.

 

Menno

Use the M.S. update download of 376.53  totally FPS optimized!  Ready for Game Mode (W10).   I gained 33 percent FPS in running with it, over 376.33 in very heavy autogen situations, and sliders, full right.  (P3D and XP11)

Share this post


Link to post
Share on other sites

I am not sure that there is a problem to fix, I have tried that driver also and it works without issue.

 

Perhaps your install of it went wrong somehow?

Share this post


Link to post
Share on other sites

I've recently installed FSX:SE ( last week ), the Fixer, and FSLabs A320, and have gone through all Nvidia driver versions starting in the "33", and ending in the latest patch released this week to solve a memory leak in P3D. None created any problems, although I am not using cloud shadows, or any shadows at all for that matter....

 

In my old rig the "only" purpose of the Fixer is to optimize FSX:SE, by making better use of the GTX 960 4 GB video card through DX10 mode...

Share this post


Link to post
Share on other sites

Ok, so I tried again, same crash.

 

But initially after I had 378.66 installed again, FSX would start. I then updated the Nvidia profile and, a lesson from Bojote in the past, set my SHADER_CACHE_VERSION in my fsx.cfg to a new version number, in my case 8. So far I have always set a new number after each driver update, no problem.

But now FSX crashed on start-up.

 

Eventually I set the Shader Version back to 7, and that was the culprit, no crash....

 

So, I guess, I do not need this shader cache version anymore as it now is a cRash version.....

 

Menno

Share this post


Link to post
Share on other sites

The way that I force a recompile of the shaders is to go into the debug dialog of the Dx10 controller and press accept. I have tried that with 378.66 without issue.

Share this post


Link to post
Share on other sites

 

 


Use the M.S. update download of 376.53 totally FPS optimized! Ready for Game Mode (W10). I gained 33 percent FPS in running with it, over 376.33 in very heavy autogen situations, and sliders, full right. (P3D and XP11)

 

I think you'll mean 376.33?.

Cheers, Ed

Share this post


Link to post
Share on other sites

The way that I force a recompile of the shaders is to go into the debug dialog of the Dx10 controller and press accept. I have tried that with 378.66 without issue.

 

Hi Steve, all options are checked there so I guess the controller will do so when needed.

I tried to remove the line from my cfg but FSX won't accept that either, it crashes. So I guess best is to just leave it in and not renumber it again. The Controller will take care of it.

 

Menno

Share this post


Link to post
Share on other sites

I ve just installed this driver with a new GTX 970 card, and my DX10 is showing autogen flashing and water swirling. Has anybody else had similar problems with the new driver?

Share this post


Link to post
Share on other sites

I get bad shimmering looking towards the sun if I zoom right out but I think that has always been the case with previous drivers.

Share this post


Link to post
Share on other sites

Steve, I may or may not have a problem with this new driver. I have been experimenting with your fixer and installed the new driver around the same time. I've now decided for various reasons to go back to DX9 so I uninstalled the libraries and uninstalled your fixer. Since then I'm having problems changing from window to full screen. I get black squares or a completely black screen or sometimes no cockpit. All the time I can hear the sim running in the background but can do nothing to recover the flight.

I found this thread by accident by the driver number while searching for answers. So my question is, is it the driver as some people seem to think, or have I somehow managed to mess up my shaders by uninstalling incorrectly?

I also use Ezdok and suspected this might be a problem so I reinstalled it. I also removed my fsx.cfg file and generated a fresh one. I'm using the Steam version.

Any advice would be greatly appreciated 

thanks, Mike

Share this post


Link to post
Share on other sites

I dont use dx9 so I cannot offer much help...

I haven't noticed any driver issues with the latest driver.

 Dx9 has always been a bit odd if you alt tab out of full screen and try to go back to it.

you can download old drivers from the Nvidia web site.

Share this post


Link to post
Share on other sites

Thanks for the reply Steve. Could you just confirm for me that I have done nothing wrong with FSX by uninstalling the library files in your program and then deleting the program afterwards. I'm concerned that I may have corrupted the original shader files in FSX that are used in DX9. I'm not completely sure how this all works, do the files that are converted into DX10 shader files convert back to the original DX9 files when you uninstall the libraries?  If you can please confirm that everything is in order with the procedures that I have carried out, I can eliminate your fixer from the equation, then I'll try an earlier driver and see what happens. I have never personally had any problems using alt/enter in DX9 before so that is why I'm so puzzled by this recent development.

Many thanks once again,

Mike

Share this post


Link to post
Share on other sites

The fixer is one of the safest addons  to install and install. It changes nothing that has any impact in dx9 and the few things that it changes that impact dx10 it reverses when uninstalled.

All it changes are two textures, the compiled version of dx10 shaders, some dx10 only settings in fsx.cfg and effect files in a manner that can easily be reversed.

Share this post


Link to post
Share on other sites

Ok thanks for the prompt reply Steve. I think I'll try an earlier driver and see what happens. The problem only started around the time that I uninstalled your fixer and updated the graphics driver so obviously those are the 2 things that I'm focusing on. Maybe it's something completely different 😕. I think I might try a new alt/enter thread and see if others have experienced this problem.

thanks again,  Mike

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this