I'm using an ATI 9800 pro and occasionally I'll lose anti-aliasing when alt-tabbing, using the pull down menus, etc.I always had problems getting AA back until I discovered this method. Has anyone tried this before? If not, if anyone out there loses AA in the future during a flight, give it a try and let me know if you were able to replicate it. I'm curious whether this work around is just a function of my particular PC setup.POSSIBLE WORKAROUND: When you lose anti-aliasing, go to the virtual cockpit and pull down the "views" menu and then choose "view options". At this point, I sometimes see a flash in the background like something in the video card is being reset. In the "select view" group of radio button, select the "cockpit" radio button and then press "ok". This puts you back in the 2D cockpit, at which point you cycle the view (e.g., shift-s) back to the virtual cockpit. Anti-aliasing should be back.Note - you might not need to start and end this procedure in the virtual cockpit. This is just the procedure I use because I'm usually in the VC when I notice I've lost AA.

That was a strange phenomena I have never lost my aa on my 9800 in FS 2004? You are using ATI:s aa and not FS 2004:s?

Hi,I use ATI's AA and I lose my AA easily if I use any driver version newer that CAT 4.2's. With the 4.2's I rarely lose it. If I do happen lose it when I'm using the 4.2's usually all I have to do to get it back is to...Make sure I'm in the 2D PanelPress 'ESC' and wait a few secondsPress 'Continue Flying'With any Catlyst version newer than 4.2 I lose the AA very easily and it can be hard to get it back. It will lose AA by going to the kneeboard (F10), ALT-TAB to dekstop and back, pressing ALT to get the menu, going to FSNavigator (F9), ect. I got tired of losing AA so easily. So after using the 4.6's for a while I have decided to go back to the 4.2's. It's kind of a bummer because the IQ with the 4.6's is definitely nicer, but I can't stand to be without my 4x AA.Regards,Jim

I'm running the Omega variety of the Cat 4.6. Never lost AA on these or any previous driver versions. You got something else going on there??

"I'm running the Omega variety of the Cat 4.6. Never lost AA on these or any previous driver versions. You got something else going on there?? "Same experience here. I just tried Jim's scenarios described above and can't make the AA go away. :-hmmm Greg

Thanks for the input. I'm using ATI's AA. I'm also using ATI's Cat 4.6 at 1280 x 1024, FR=24, rending to text and T&L checked, and trinlinear filtering.It could very well be a function of my hardware/software setup. I'm running quite a few addon packages.The loss of AA usually occurs in conjunction with the appearance of brief, garbled screens when I go to the pulldown menus or hit alt-tab.

Thanks for sharing your procedure, which seems simpler so that is definately a plus. With my procedure I don't have to wait a few seconds. I go the view/view options pull down menu and the display resets right away. It is good to fill the tip bag with all the tricks you can get. I have FS9 so heavily modified with addons right now sometimes I'm suprised I get to my destination without a CTD (knock on wood). Both procedures sure beat what I used to do, shut down flight simulator or live without AA for the remainder of the flight.

Yeah, I might have to take another look at Omega 4.6. I did try them initially but not long enough to reach a conclusion about AA stability. BTW, did anyone ever test the ATI Cat 4.6 against the Omega 4.6 back to back?I tried it and received some interesting results. Framerate wise, they both were about the same in a series of tests I ran (2D and 3D). However, both drivers seemed to have seperate strengths in other areas. For example, the Omega seemed to stutter less when banking. However, I also tested both drivers in a resource intensive takeoff roll in the VC of a PMDG 737 at Simflyer's KORD Rwy 27 in partly cloudy weather. Here, the ATI Cat seemed to stutter less. Strange result I know and I'm not even sure the test results are valid (e.g., too subjective or too many other variables). Anyway, that's why I've been using the ATI Cat. 4.6 lately.

>I'm running the Omega variety of the Cat 4.6. Never lost AA>on these or any previous driver versions. You got something>else going on there?? Well, I also have a lot of addons. Not sure if that makes any difference concerning this issue or not. I suppose I'd have to run a default installation of FS2004 to check it out. FS9.cfg settings also might have something to do with it, not sure. But I have had this same loss of AA thing happen on this newer system and on my older system, WITH anything newer than CAT 4.2's. As I said, with the CAT 4.2's I rarely lose AA so this whole thing really isn't too much of a concern to me as long as I'm using 4.2's.I do push my card pretty hard probably. But I have had the card for a long time and it has been extremely stable. I just keep wondering what it is about anything newer than 4.2's!!?! :-hmmm I have not tried any Omega's.System Specs:Intel 3.4C(C = Northwood) on Asus P4C800-E Deluxe, 1 GB Muskin '222' Special PC3200 RAM, NEC MultiSync FE2111SB 22" Monitor, ATI Radeon 9700 Pro Videocard with v4.2 Catalyst Drivers, DirectX 9.0b, Creative Audigy2 Soundcard, 250 GB w/8 MB Cache Western Digital HDD, WinXP Pro SP1My settings are 1600x1200 resolution, 4X AA(in-sim AA unchecked), and in-the-sim Trilinear Filtering selected. I use MyTraffic 2004 with AI Traffic slider at 100%. Everything else in the sim is turned on and up all the way, sliders full right except the following...Terrain Complexity(Mesh): 85%Autogen: Very Dense (I'm also using a file in the Avsim library named: fs9xml.zip)Water effects: Low-- FS9.cfg --[DISPLAY.Device.RADEON 9700 PRO.0]Mode=1600x1200x32RenderToTexture=0TriLinear=1[DISPLAY]UPPER_FRAMERATE_LIMIT=24TEXTURE_BANDWIDTH_MULT=120 <-- Does this even matter if you have RenderToTexture=0 ...?RUNWAY_LIGHTS_SURFACE_SCALAR=2.2RUNWAY_LIGHTS_VASI_SCALAR=2.5RUNWAY_LIGHTS_APPROACH_SCALAR=2.3RUNWAY_LIGHTS_STROBE_SCALAR=2.4[TERRAIN]TERRAIN_ERROR_FACTOR=85.000000TERRAIN_MIN_DEM_AREA=10.000000TERRAIN_MAX_DEM_AREA=200.000000TERRAIN_MAX_VERTEX_LEVEL=20TERRAIN_TEXTURE_SIZE_EXP=8TERRAIN_AUTOGEN_DENSITY=4TERRAIN_USE_GRADIENT_MAP=1TERRAIN_EXTENDED_TEXTURES=1TERRAIN_DEFAULT_RADIUS=9.900000TERRAIN_EXTENDED_RADIUS=9.900000TERRAIN_EXTENDED_LEVELS=4Cheers,Jim

I had heard of this issue before, but have never been able to make my AA go away. And I've tried every (Omega) driver released since I went to ATI 14 months ago.I wonder if this is a chipset issue? Though Bigshot is running an Intel system as you are, Jim. fs3tofs9 what system are you running? I'm running an AMD/nForce system (and I believe Oqvist is as well).Perhaps the Omega's might have something to do with this. Or, one should say, the ATI drivers. I know the ATI tweaker has many more options than the Omega's (which, in my world, means there are more ways to screw up the drivers). The Omega offers few options (Omega does the tweaking), so they are more of a "fire and forget" install.This is getting more interesting...Greg

Because of this thread, I decided to give the Omega drivers a try. I downloaded the latest version and installed them without difficulty. My machine works fine with them. However, fs9 doesn't run. On launch, I get the splash screen and then I get a black screen and nothing more happens. I don't get to the setup screen. I can exit the black screen and return to my desktop by pressing ESC. Does anyone have any thoughts about what might be the problem.Also, if I ever get fs9 to run with these drivers, I noticed that these drivers use "application preference" for the AA and AF settings. It was my understanding that it was always best not to use the fs9 AA settings and to set them in the ATI control panel. For fs9 ought these settings be adjusted or should I follow the instuctions that come with the Omega drivers indicating that you shouldn't mess with their settings?Thanks.Macwino

Did you uninstall the ATI Control Panel before installing the Omega's? It can't be on your system if you plan on using the Omega's.You can set the AA and AF in the Omega CP. He leaves it at Application Preference so folks with slower system can tweak to their choice. I have a 9800 XT and run AA at 4X and AF at 16X, Performance mode (I don't see any difference between Performance and Quality modes with regard to IQ).Hope this helps,Greg

Greg, thanks for explaining about the settings.I did remove the pre-existing ATI control panel as directed. Also, let me reiterate that the drivers seem to work fine with my machine in general. I just can't seem to open fs9 since they were installed. Since my original post, I tried launching fs9 with a pristine fs9.cfg file and I was able to get to the setup screen. So I guess there's something in my fs9.cfg - which was tweaked for MegaScenery among other things - that is causing the problem. Now, I've just got to figure out what it might be.

LOL... just before I read your reply I thought about the driver call in FS9.cfg. Yep, you need to make sure the previous driver call is removed from the FS9.cfg.Let us know what happens with your AA now with the Omega's.GregP.S. What are your sys specs (basic)?

Sure, I'm running an AMD 64 3200+ with a VIA K8T800 chipset.