antialias efficiency

[araman]

Hi all
with my gf4ti4200 , only the x4S mode works but with blurry panels
x2 , x4 or quincunx modes have no effect
Is it normal ?
Araman

AthlonXP2000
512 RAM
Prolink gf4ti4200 128
WinXPpro

[Simon Evans]

Use 32-bit colour, not 16-bit.


Simon Evans

[araman]

thank you
it works for 1280x1024x32 resolution
But in FS2k2 i have not 1600x1200x32 in the resolution box (only 1600x1200x16 )
Is it because of my monitor limits ?
Araman

[Simon Evans]

Probably. Are you using the correct drivers for your monitor, per the monitor manufcturers website?

Q: Why do you even need FSAA at 1600x1200..? How huge is your monitor?



Simon Evans

[sgreenwood]

Araman,

Have you set the display to 1600x1200x32 in the Control Panel/Display Properties/Settings dialog?

If you cannot, you probably won't be able to do so in FS2k2 either.

If you have, there is a problem with FS2k2. The list of settings available in the Hardware dialog seems to depend on a combination of current resolution when FS2k2 is started and some "historical" information it has about your display. Which may be incorrect.

I reinstalled FS2k2 to resolve this problem, but there may be a less drastic solution, probably involving editing the Registry.

Someone recently suggested one could delete/rename fs2002.cfg to force the sim to reset the display characteristics (to solve an unrelated issue). I have not tried this yet, but it seems worth trying before going through a reinstallation. Then restore the former fs2002.cfg.

Regards,

Steve
www.fs-traveler.com

[Bigshot]

Just open the FS2002 cfg file and manually change the res to whatever you want. There's a line in there for resolution.

[Simon Evans]

That sometimes works. Most times it just defaults to the highest available setting as soon as the sim launches.

Simon Evans

[sgreenwood]

I tried that as well. The problem is, even if it works when the sim starts, the first time you change any setting that requires reloading textures, ..., the sim falls back to the option highlighted in the Hardware dialog, not the cfg setting. This gets tedious very quickly. :(

It can confirm the nature of the problem, however.

Regards,

Steve
www.fs-traveler.com

[YourMomma]

>I tried that as well. The
>problem is, even if it
>works when the sim starts,
>the first time you change
>any setting that requires reloading
>textures, ..., the sim falls
>back to the option highlighted
>in the Hardware dialog, not
>the cfg setting. This gets
>tedious very quickly. :(
>
>It can confirm the nature of
>the problem, however.
>
>Regards,

Hi Steve,

The FS2k2.cfg will get re-written only if you open the settings menu and then click "ok" regardless if you have made changes or not, Fs2k2 will not however re-write the fs2k2.cfg on reload, re-start etc. just make all your settings adjustments, then manualy change the cfg file and it will stay that way until the next time you make any changes in the setting menu.

Take Care,

[sgreenwood]

Hi YourMama,

>Fs2k2 will not however re-write the fs2k2.cfg on reload, re-start etc.

FYI, this is not entirely accurate. FS2002 can re-write the cfg file without any user intervention.

This is easily demonstrated.

I have TERRAIN_MAX_VERTEX_LEVEL=21 in fs2002.cfg. If I set this value to 21.5, start the sim, shut down, and check the cfg file, the value is reset to 21! With no use of the menus at all, except to shut down the sim. The cfg file was clearly rewritten by the sim with no intervention on my part.

If I check the cfg value while the sim is running, the value of 21.5 is still there. To confirm the cfg settings, you must wait a few seconds to give the sim time to update the cfg file after shutting down. Then reopen the cfg file in your editor.

The sim will probably not change the resolution setting in the cfg file unless you change the value in the menu, as you suggest, but is dangerous to generalize beyond this.

>just make all your settings adjustments, then manualy change the
>cfg file and it will stay that way until the next
>time you make any changes in the setting menu.

But the basic problem remains. I rarely operate for an entire session without changing any settings.

When the menus are used to change any value that requires the sim to reload Scenery textures, 3D objects, ... (even if in another menu branch - Season or Airport, for example), the sim will then use the resolution selected in the Hardware dialog, not the value in the cfg file. And continues to do so until you shut down. If the 1600x1200x32 option is not in the list, it will not be used for the remainder of that session. Shutting the sim down and restarting to restore the resolution after each setting change is not convenient.

This is why I chose to fix my FS2002 configuration problem, rather than continue to work around it.

Cheers,

Steve
www.fs-traveler.com

[oslpchris]

You know, I don't even use anti-aliasing.. I wish I could, I love the way it looks but my framerates drop in half when I do. oh well.

chris

[araman]

My monitor is a 19' with the last driver
i finally selected the quincunx mode , it works with 30.30 driver and not with Omega 1042c
i use 1600x1200x16 because my FPs is correct ( locked at 24 )
But i will try the modification in fs2002.cfg
Thank you all

Araman

[YourMomma]

You are correct Steve, FS2k2 will right to the cfg from other menus, but the fact remains that it will not re-write the display unless you use the settings menu, and as far as I know there is no work around but it would be nice to find out what is limiting this as I get have the same problem.

my desktop can use 1600x1200x32 as I am using a 19" Samsung 955df and it is driven with an GF4TI4400 so Fs2k2 should give me the setting but it doesn't. I have used the manual method ever since Fs2k2 came out.

Take care,

Mom

[csautter70]

I think there is a way to get FS to rebuild a new cfg file, but am not completely sure how to do it. I remember it has something to do with hold the CTRL key down, maybe when you launch the program or just after the splash screen comes up.

Christopher Sautter
Tucson, Arizona

[sgreenwood]

Hi Mom,

I have seen this problem reported in forums from time to time. I assume there are many more who experience it, but choose to live with the problem, one way or another, as you have so far.

I have fixed the problem on my system. Since I do not know what caused it in the first place, I cannot recreate it, so I cannot do further testing - at least for now. I am reluctant to think that others cannot enjoy the same success by "simply" reinstalling the sim, but maybe not. Perhaps you can help enlighten us.

Several questions come to mind. Reinstallation worked for me; have you tried reinstalling the sim? Installing a second copy, preferably on another drive? Have you tried recreating the default fs2002.cfg? Did you do any hardware upgrades after the sim was installed? I don't know if FS2002 uses any FS2000 config information during the install, if available, but that could be a problem as well.

I have to wonder how the sim handles the situation when the graphics card/monitor is upgraded to one with significantly more capability. If this is not the source of our problem, it seems like it would create a similar challenge. Since such upgrading seems to be common today, it would be nice if we could identify a simple fix, if there is one.

My problem was due to incorrect information in my fs "configuration". My first thought was that I might have had my display set to 1600x1200x16 when I installed the sim. I decided to install fs2002 on a "clean" test machine, several times!

When installed with the display set at 1600x1200x16, that was all that appeared in the hardware list. But when I exited, set the display to 1600x1200x32 and restarted the sim, the higher value appeared in the hardware list. So it seems the resolution of the display when the sim starts limits the options available in the sim. But when installed, the sim did store the correct information about the capability of the display subsystem, and would use all that capability when possible.

I then searched the Registry of my problem system fairly carefully for a setting that might be causing the problem, but could not find one (I expect it is in there, however).

Finally, I installed another copy on another drive on the problem pc, and the 1600x1200x32 resolution was available, so I knew reinstallation would repair my problem. But this is not a convenient solution. (And perhaps not a universal solution?)

When FS2002 is first installed, there is no fs2002.cfg file. It is created when you first run the sim (I did not check to see if it is created when the sim starts, or only after it shut down :) ).

While it is likely that the critical display information is stored when it is installed, it may be stored when the cfg file is created. If this is true, then having the sim recreate the cfg may cause it to update the display information as well.

This would be a more convenient solution, and is easy (for you?) to test. As I suggested above, you can rename the fs2002.cfg and restart the sim. When restarted, the sim finds no fs2002.cfg and creates a new one. Problem solved? Then delete the newly created cfg (or rename it so you can keep it for reference) and restore your older version with all your customized settings.

If this does not solve the problem, then a Registry edit or reinstall appear to be the next step.


Good luck,

Steve
www.fs-traveler.com

[araman]

Hi
I've tried your suggestions ( fs.cfg , registry , monitor driver and inf , except reinstall)
the only way for me to get 1600x1200x32 is to change first Windows display to that resolution , then launch fs2k2
But i have to do that each time i launch it
Regards

Araman