• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Lost anti-aliasing...

khaos_56k

khaos_56k

Messages
366
Country
us-maryland
I've come upon an odd situation and wondering if anyone else has experienced or heard of this...

I built a computer for a fellow FSer and all was fine until a few months ago. He lost anti-aliasing in FS but antistropic filtering looks like it's trying to work. I figured a card change would solve it... but it didn't. I've tried a variety of settings via the display properties (nVidia) and then within FS with no change. The new card is an 9-series nVidia and I've even tried it with nHancer even though I believe nHancer is only for 8-series cards. The "old" card was a 7-series...

Unfortunately I don't have another PCIe system to test the cards on but I'm starting to think the motherboard has a bad PCIe (x16) slot... it's an ASUS V8M-VM.

Any input from anyone?
 
Hi
This is normally driver/registry related gets worse as you change driver and or cards.I do this ever time I change the drivers,its a pain but only takes a few min.
Please note the warnings.... the following was posted on another board and relates to fs9 but just replace the fs9.exe with fsx.exe when reading it.
Ive done it a few times and its always worked.....for me :) It gets the card doing the AA so you dont need the AA checked in fsx.Basically it gets rid of the FSX profile in the nividia drivers so fsx then uses the global settings
Wozza

+++++++++++++++++++++++++++++++++++++++++++++++++++++++
1. Go to C:\WINDOWS\system32 and copy nvapps.xml and nvapps.nvb (if it is present). Paste these into a safe folder - these are your backups if things go awry!
2. In C:\WINDOWS\system32 open nvapps.xml with notepad and do a find for "fs9". It should come up with some text like the following:

<PROFILE Label="MS Flight Simulator 2004">
<APPLICATION Label="FS9.exe"/>
<PROPERTY Label="multichip_rendering_mode" Value="0x0240000E" Default="0x0240000E" Itemtype="predefined"/>
<PROPERTY Label="prevent_cpl_aa" Value="1" Default="1" Itemtype="predefined"/>

3. Change FS9.exe to FS99.exe
4. Save it.
5. Do the same for nvapps.nvb

6. Now the nasty bit. In the Run box (Start, Run) type in regedit and hit enter. This will open the system registry. If you are not familiar with this then be very careful what you actually edit. This is the system's view of the software structure on your system. It could be a worthwhile experience to read up on this before doing anything further.

7. In the registry navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Video
In there you should see "folders" that are named with numbers like the following - {23A77BF7-ED96-40EC-AF06-9B1F4867732A}.
Open thoe folders and you should see additional folders called 0000, 0001 and video.
In either or the 0000 or 0001 will be a long list of values with names like - _+menu.exe:D3DOGL_67207556 or _freedom.exe:D3DOGL_67207556.
These are the application profiles from the control panel coded into your registry (thanks NVidia!). What you need to do is find those that relate to FS9 - examples are _FS9.exe:D3DOGL_67207556 & _FS9.exe:D3DOGL_70835937.

8. Once you have found them, delete them. You will need to go through the numbered folders (e.g. {23A77BF7-ED96-40EC-AF06-9B1F4867732A}.) looking at the 0000 and 0001 folders.

9. If you have numerous ControlSet folders you may well need to the above for them as well.
10. Reboot open Nvidia control panel and make your settings - you should now have AA for FS9.

This has worked for me but it is a drastic move. Do this at your own risk.

Before messing with the registry take a backup of it and read up on it.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 
Thanks for your input!

Since I'm no stranger to the registry this won't be an issue at all. I'll copy the info and try it with the "afflicted" PC this weekend.

Hopefully it works!!
 
THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU!

Your instructions resolved not only the "original" problem PC but ALL my nVidia machines! I am so HAPPY to finally rid my PCs of nHancer! The only reason I resorted to running that additional program was for anti-aliasing... NO MORE!

I wish I could shake your hand and buy you a pint... or two!

THANK YOU!
 
You must log in or register to reply here.
Back
Top