Simviation Forums

I have looked at some of the other threads about configuring the settings for FS9 by using nHancer.  I recently updated the drivers (FW169 I think). The jagged lines are present still, even after I follow the instructions on what settings to choose.  So I'd like some input on other suggestions for configuring FS9

Specs
2.4 Ghz Core 2 Duo
2 x 512 XFX 7590GT (not in sli)
4GB DDR2 Ram

Screenshots:



Thanks in advance!

Make sure AA is NOT ticked in the FS9 settings as well.

It is not checked.

Do this.

http://www.simviation.com/cgi-bin/yabb2 ... 1183998514

[quote]I have looked at some of the other threads about configuring the settings for FS9 by using nHancer.

The way i got around it was by Renaming the main fs9 executable (FS9.exe) and setting up a new profile for that

The way i got around it was by Renaming the main fs9 executable (FS9.exe) and setting up a new profile for that

That is an option with FS9 since it does not have massive dependancies based on the .exe name/ location. With FSX it would probably not be a good idea

I would really like to know what is causing the problem. more than likely its something in the drivers (as usuall) because nvidia is breaking titles to get crysis to run

There is no option for 8XS supersampling.  The max I see is 4x.  It is by far more clear at Combi 8XS than SuperSampling 4X.
Thx

Credit to Tom for telling me how to fix this problem

All you do is back-up your original FS9.cfg,and go to your main fs9 directory and back up your FS9.exe to a safe place,then rename the fs9.exe to something like wew424sfs9.exe,and go into nHancer,now duplicate the MS FS9 profile,and with the copy set your settings,once that's done set the main FS9 profile's executable to wew424s.fs9.exe,now go out of nHancer and rename the FS9.cfg to wew424sfs9.cfg,that should sort out the AA problem in FS,disable AA in the sim,and it should now run AA from your card.

Credit to Tom for telling me how to fix this problem

All you do is back-up your original FS9.cfg,and go to your main fs9 directory and back up your FS9.exe to a safe place,then rename the fs9.exe to something like wew424sfs9.exe,and go into nHancer,now duplicate the MS FS9 profile,and with the copy set your settings,once that's done set the main FS9 profile's executable to wew424s.fs9.exe,now go out of nHancer and rename the FS9.cfg to wew424sfs9.cfg,that should sort out the AA problem in FS,disable AA in the sim,and it should now run AA from your card.

I only have have one word to say  :-? boy that was a clean miss do you mind putting that in English.
Or in other words run that by me one more time. You lost me at the last turn. :-?

Well if you didn't understand that then there is seriously something wrong,because I could'nt of put it any clearer,but though to avoid conflict I'll explain again,hopefully in a way you can understand it.

1.)Back up you original FS9.cfg

2.)Go into your main FS9 Directory C:/Program Files/Microsoft Games/Flight Simulator 9/

3.)Scroll down whilst in the main FS9 directory until you find the FS9.exe,once you've found the FS9.exe,back up the FS9.exe to a safe place.

4.)After backing up the FS9.exe,rename it to something like GarysFS9.exe.

5.)Now go into nHancer,and duplicate the MS Flight Simulator 2004 Profile

6.)Set the settings NickN said to set for the duplicate profile,example AA,AF etc,make sure the settings for Global and Profile are the same.

7.)Make sure the original FS 2004 Profile in nHancer has got the same settings as the duplicate one.

8.)Set the original (MS Flight Simulator 2004) profile's executable to GarysFS9.exe,remember when we renamed it earlier?

9.)Go out of Nhancer and rename your FS9.cfg to the same name as the FS9.exe,we named the FS9.exe to GarysFS9.exe,so rename the FS9.cfg to GarysFS9.cfg.

10.)Go into FS9,and uncheck AA,Fly.


Did you understand me now?,hope it works for you,it did me and Tom who kindly showed me how to fix the problem,not sure if it's wise to rename the FS9.exe or FS9.cfg,but it worked,and as NickN has said in this thread,you can probably do that with FS9.

Thanks for the info
I thought that is what you were trying to say but the file name wew424sfs9.cfg threw me a little.. I have to admit I am a little Leary, I do not like the idea of renaming the EXE file that is taking somewhat of a chance and I am not sure if it is worth it.

I haven't experienced any problems with renaming the exe,infact my sim runs much better after using nHancer,things are smoother and performance is the same strong at 30fps,as Nick says FS9 doesn't rely on the exe name being default much,but if it were FSX it would probably be a bad idea.

Try it and if you're not comfy with it after awhile,change it back to FS9.