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.

Nvidia appears to be ignoring 7800GT/GTX simmers...

Featured Replies

Thanks George, I figured that but I like my 4x 8x, looks good. As you can see by my post above looks like I am going back to the 78.05 anyway. I guess my setup just doesn't like any of the 8x drivers...-PaulLiquid CooledAMD 4000 San Diego2 Gigs Kingston Corsair XMS CL2Dual 7800 GTX 24 inch widescreen dual 19 inch LCDRaid-0psolksig.jpg

Have a Wonderful Day

-Paul Solk

Boeing777_Banner_BetaTeam.jpg

  • Replies 148
  • Views 15.3k
  • Created
  • Last Reply

Top Posters In This Topic

Doing a long range flight, my fs9 crashed after 3.5 hours with the new 81.98 drivers. There was a massive texture flickering every 2-3 seconds. I tried to recover by switching from windowed to full screen mode, but then my main monitor (out of two) went black. After a while, the only thing I could do was to shutdown the PC with the help of the second monitor and the task manager.Prior to the texture flickering, I switched to another application (total commander) to do some file operations. FS9 was running windowed in the background quite nice for a while, but after ~10-15 minutes the mess started.I will try the flight again and keep fs9 in foreground, then see, if this happens again. Please report if you have similar problems. Thanks.Greg7800GTX, 256MBAMD X2 4000+

Greg,Have you tried using WideFS? WideFS is a great solution for running multiple FS related apps/operations and it helps keep the main full screen FS9.1 app running smoothly as the other FS related apps run on a separate PC. But more importantly you don't have to run 3 monitors in FS9.1 which definitely pushes the envelope of hardware stability.Did you get any error message from FS9.1? I've had similar lockups but only after several hours of flying -- it turned out to be my overclocked FSB -- overclocking worked in every other game/app I had, but in FS9.1 it would crash after hours worth of flying.You may also want to run Dr. Watson so you can atleast log where and possibly what caused the crash. If you have Microsoft's Visual Studio you can also debug a process (any process) -- this might help you determine the exact cause.Rob.

>Doing a long range flight, my fs9 crashed after 3.5 hours>with the new 81.98 drivers. There was a massive texture>flickering every 2-3 seconds. I tried to recover by switching>from windowed to full screen mode, but then my main monitor>(out of two) went black. After a while, the only thing I could>do was to shutdown the PC with the help of the second monitor>and the task manager.>Prior to the texture flickering, I switched to another>application (total commander) to do some file operations. FS9>was running windowed in the background quite nice for a while,>but after ~10-15 minutes the mess started.>I will try the flight again and keep fs9 in foreground, then>see, if this happens again. Please report if you have similar>problems. Thanks.>>Greg>>7800GTX, 256MB>AMD X2 4000+My 6800 GTO , also crahed to desktop after a couple of hours of flying. Going to give it one more chance, and if it happens again I am going back to an older driver.

I've had no problems with a long flight (>4 hours), however, if I run FSNav windowed in FS9 full-screen mode, that part of the FS screen from the top of the FSNav window to the bottom of the screen is not updated. The upper part of the screen is. If I run FS9 in windowed mode, it works fine.George2 x XFX GeForce 7800GTX 512mb Extreme XXX Edition in SLIDELL 24" Widescreen TFT 2405FPW

Hi all,I've been running FS9 with 81.98 and 82.12 drivers for a couple of days. I'm using a LCD monitor as primary display and CRT as secondary in dual view. This is what I've discovered so far:FS9 comes to an allmost complete stop when I go from windowed mode to full screen. This is after I've undocked some panel windows and dragged them to my second monitor. This only happens when I have AA on (4x).If I have AA off I'm able to display panel windows on the second monitor and run FS in full screen. But the textures on the second monitor get corrupted if I move or resize any panel window on the second monitor. I remember having this problem a couple of graphic cards back in time.In general I experience more flickering on the monitors when FS9 starts and when a scenery is loading. Compared to the 77.77 drivers.Ulf BMobo: ABIT AN8 Fatality, 3GB RAMCPU: AMD 64 Dual Core 3800+G-card: Single Gigabyte 7800GTX 256MB

  • 2 weeks later...

Ulf B,I have a 6800GT and got the exact same results as you with the 81.98 drivers trying to run dual monitors full screen. I have not noticed this particular problem with any of the earlier drivers I have tried. The only thing our systems have in common is an Nvidia card.I reverted back to the 71.89s until I find something better.3.0 Pentium, MSI 865PE Intel chipset based board, 1 ghz ram, XFX 6800GT. Ted

[email protected] ghz, Noctua C12P CPU air cooler, Asus Z77, 2 x 4gb DDR3 Corsair 2200 mhz cl 9, EVGA 1080ti, Sony 55" 900E TV 3840 x 2160, Windows 7-64, FSX, P3dv3, P3dv4

I also experienced many of the same issues posted here and have gone back to the 78.01 so I can actually fly. 81.98's did nothing for me except cause trouble. Keep working on it NVidia.Jay EklundCAT VI Senior Captain KDENhttp://online.vatsimindicators.net/812321/764.png

Jay EKlund

UVA/GCVA Pile-it

I ran the 81.98 drivers also, didn't fix any of the 16XSLI issues at the create a flight screen -- all AC still don't show. But other than that the drivers still work as before in FS9.1, no texture corruption for me. The only thing I did notice is that if I select SLI Render mode of "Multiple GPU Render" (should be set to "SLI Antialiasing" per nVidia) the create a flight screen usually gets so corrupted it becomes unusable. Actual flight is fine with the "Multiple GPU Render" however frame rates do not change at all (frame rates should increase) so I suspect nVidia just force "SLI Antialiasing" regardless of what SLI render mode is selected -- this would explain why frame rates don't change.You can confirm this by renaming FS9.EXE to FS10.EXE switch to Global and create a new performance profile and point to your renamed FS10.EXE -- all of a sudden none of the SLI rendering modes work and you have to pretty much revert to single GPU with 4X AA and application controlled AF. So obviously nVidia are just disabling features based when it finds FS9.EXE regardless of what your profile setting is. Take that for what it is worth -- there must be something deeper that is preventing nVidia to revert to older 78.01 code set if FS9.EXE is used cause right now it looks like they are just trying to "Fool" the end user.

>> -- all AC still don't showHave you tried this in windowed mode? It works for me.George

I can get the AC to show if I don't use SLI AA and use standard 4XAA.I like to run full screen mode to avoid resizing distortions, but I'll see how Window mode works to for the #### of it.

You only need to window for the "Select Aircraft" dialog.

"You only need to window for the "Select Aircraft" dialog"Well not totally true for me at least, for instance with 8xS AA I can not call up the knee board, run FSNav in an docked window, or use the EFB Electronic Flight Bag add on without part or all of the panel going totally blank. Problem for me is the 8xS just seems so much better than 4x that I just put up without those "luxuries".Sure hope it gets fixed someday . . .Joe Lorenc

Joe Lorenc

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.