Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

SGSS not working on latest NVidea drivers?

Featured Replies

I upgraded my NVidea drivers to the latest 335.23 (GTX770) tonight to try out ShadowPlay.  Afterward, SGSS didn't seem to be working anymore.  Jaggies everywhere.  Checked my Nvidea Inspector settings, reimported them and reapplied them to FSX with no help.  Anybody have any thoughts on this? 

 

Gregg

 

EDIT:  I reverted back to 331.65 and all is well...the world is back to spinning in greased grooves.

Gregg Seipp

"A good landing is when you can walk away from the airplane.  A great landing is when you can reuse it."
i9 64GB RAM, GTX-5090

337.50 beta drivers. Try them. Thank me later.

David Graham Google, Network+, Cisco CSE, Cisco Unity Support Specialist, A+, CCNA

 

I upgraded my NVidea drivers to the latest 335.23 (GTX770) tonight to try out ShadowPlay.  Afterward, SGSS didn't seem to be working anymore.  Jaggies everywhere.  Checked my Nvidea Inspector settings, reimported them and reapplied them to FSX with no help.  Anybody have any thoughts on this? 

 

Gregg

 

EDIT:  I reverted back to 331.65 and all is well...the world is back to spinning in greased grooves.

 

http://www.geforce.com/whats-new/articles/nvidia-geforce-337-50-beta-performance-driver

David Graham Google, Network+, Cisco CSE, Cisco Unity Support Specialist, A+, CCNA

 

  • Author

 

 


337.50 beta drivers. Try them. Thank me later.

 

Doesn't seem to work on that one either.

Gregg Seipp

"A good landing is when you can walk away from the airplane.  A great landing is when you can reuse it."
i9 64GB RAM, GTX-5090

Doesn't seem to work on that one either.

 

Interesting. Are you doing a clean install?

David Graham Google, Network+, Cisco CSE, Cisco Unity Support Specialist, A+, CCNA

 

  • Commercial Member

I found I had to use the NVidia control panel app to reset the defaults after using NI. Also I don't assume NI will work with later drivers.

Steve Waite: Engineer at codelegend.com

  • Author

 

 


Interesting. Are you doing a clean install?

 

Yes.

 

Also I don't assume NI will work with later drivers.

That's probably the case. 

Gregg Seipp

"A good landing is when you can walk away from the airplane.  A great landing is when you can reuse it."
i9 64GB RAM, GTX-5090

Yes.

 

That's probably the case. 

 

It works fine for me.  The main difference is you are using windows 7. I am on 8.1

David Graham Google, Network+, Cisco CSE, Cisco Unity Support Specialist, A+, CCNA

 

  • Author

 

 


It works fine for me. The main difference is you are using windows 7. I am on 8.1

 

Not sure why that would make a difference.  I reverted back to 331.65 again.  I'll wait until a new NI comes out before I try again.

Gregg Seipp

"A good landing is when you can walk away from the airplane.  A great landing is when you can reuse it."
i9 64GB RAM, GTX-5090

I'm using Windows 7 and 337.50 works beautifully for me. In fact I have never had trouble implementing SGSS on any of the Drivers. There must be something else going wrong. Sorry I'm not thinking of anything at the moment though.

 

I do know there is one of the settings that always jumps up to bite me when I update the drivers. It may be  "Nvidia Predefined FXAA Usage - Disallowed" or maybe "Antialiasing Behaviour Flags - None". Sorry I can't remember for sure which, but you may want to check all of your settings before trying again and see if it may be one of these more obscure settings that isn't carrying over. Like I said it always gets me.

 

Are you using DX9 or DX10? Cleared the shader cache? Checked the fsx.cfg Display.Device entries?

 

Hope you can get this puzzle solved. I think the later drivers and particularly the 337.50 Beta have made a big difference. Good Luck!!

Jesse Cochran
"... eyes ever turned skyward"

P3D v5.3 Professional, Windows 10 Professional, Jetline GTX, Gigabyte Aorus X299 Gaming 7 mobo, i7 7740X @ 4.9 GHz, Corsair H115i Liquid Cooling, 32Gb SDRAM @ 3200MHz, Nvidia GeForce GTX1080Ti @ 11 GB

ORBX Global + NALC, ASP3D, ASCA, ENVTEX, TrackIR, Virtual-Fly Yoko Yoke, TQ6+, Ruddo+ Rudder Pedals

  • Author

 

 


Are you using DX9 or DX10? Cleared the shader cache? Checked the fsx.cfg Display.Device entries?

 

I am using DX9.  Don't know how to clear the shader cache.  Every time I revert the driver back, everything goes back in order.  Thanks for the tips.  I'll refer to those when I do the upgrade next time.  It looks to me that, after I upgrade, none of the smoothing is working at all.  I do the same thing when I upgrade as when I roll back...reimport my FSX configuration for NI and reapply the settings to fsx.exe. 

Gregg Seipp

"A good landing is when you can walk away from the airplane.  A great landing is when you can reuse it."
i9 64GB RAM, GTX-5090

You need to delete any existing base FSX or P3D profile.  When you install a driver it will install new base profiles so if you have your own profile they will now conflict and it will be hit and miss as to which profile is actually used (I believe it's order of date creation - meaning the most recent profile is used - so if you had a profile setup and then install a new driver it will use the profile from the new driver as that is more recent).  You can delete the base profile using NI - just find FSX or Prepar3D in the list and then hit the X button.  

 

Profile loading is triggered by .exe ... if you have two or more profiles pointing to the same .exe then the most recently created profile is used.

 

Cheers, Rob.

  • Author

 

 


Profile loading is triggered by .exe ... if you have two or more profiles pointing to the same .exe then the most recently created profile is used.

 

When I install new drivers it has a profile called "MS Flight Simulator" to which fsx.exe is assigned.  I do remove the assignment (have to).  I then import my old settings (thus, creating a new profile) and assign fsx.exe to it and apply the settings.  Seems right.

Gregg Seipp

"A good landing is when you can walk away from the airplane.  A great landing is when you can reuse it."
i9 64GB RAM, GTX-5090

I am using DX9.  Don't know how to clear the shader cache.  Every time I revert the driver back, everything goes back in order.  Thanks for the tips.  I'll refer to those when I do the upgrade next time.  It looks to me that, after I upgrade, none of the smoothing is working at all.  I do the same thing when I upgrade as when I roll back...reimport my FSX configuration for NI and reapply the settings to fsx.exe. 

 

To clear the Shader Cache just go to "User"/AppData/ Local/ Microsoft/FSX and remove the Shader folder. You may want to move it to a safe location in case you want to replace it later. When you start FSX next the folder will be rebuilt.

 

I'm just thinking that the profile isn't properly applying one or more of those settings that I mentioned but then when you revert to the former driver it is once again properly recognized. It just sounds convincingly like what happens to me. Once I get that one or two settings replaced, all is well. Just next time you try; it might be worth your time to write down all of your settings (or do like I do and keep a screenshot of the settings) so you can check them.

 

Once again, The Best of Luck to You!!

 

Jesse

Jesse Cochran
"... eyes ever turned skyward"

P3D v5.3 Professional, Windows 10 Professional, Jetline GTX, Gigabyte Aorus X299 Gaming 7 mobo, i7 7740X @ 4.9 GHz, Corsair H115i Liquid Cooling, 32Gb SDRAM @ 3200MHz, Nvidia GeForce GTX1080Ti @ 11 GB

ORBX Global + NALC, ASP3D, ASCA, ENVTEX, TrackIR, Virtual-Fly Yoko Yoke, TQ6+, Ruddo+ Rudder Pedals

  • Author

 

 


Once again, The Best of Luck to You!!


 

Thanks Jesse, I'll need to upgrade at some point so this will be helpful. 

Gregg Seipp

"A good landing is when you can walk away from the airplane.  A great landing is when you can reuse it."
i9 64GB RAM, GTX-5090

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.