Quake3World

OK, so I just got my "good" computer back last week. For the past month or so, I had been using a piece of crap built by spares I had lying around. It had 1.25gb RAM and an ATI Radeon 7000 AGP-series (It was some really bad 64mb GFX card). Everything worked fine, albeit slow due to a Pentium 4. But when I got this computer back, complete with its 4850, 2gb RAM (it's an x86 machine which means I can't go past 3gb, so any more would be a waste), and a Core 2 Duo, I get some horrible aliasing in radiant, to the point where I just cannot see the grid, and therefore cannot map. I tried disabling and re-enabling every setting in the Control Center, but nothing changed. I really don't know what to do, so if anyone else has had this problem or knows a solution I would be very grateful.

If I missed any relevant specs or info, I can add it pretty easily. Both computers use Windows XP Pro SP3.

For GTKradiant v1.4, under Preferences, Display, 2D Display/Rendering, OpenGL antialiased points and lines, uncheck that setting (I am on Windows 7 though). You probably need to relaunch the editor after that.

I use 1.5, and I've looked at all the options. None of them fix the problem.

The option AEon mentioned is just for anti-aliasing, but on or off, it should still be perfectly usable. If you are saying you can't even see the grid lines, it must be something else.

Check for Windows updates, update your video drivers.

Make sure you don't actually have the grid disabled ("0" that's the zero key).

Try the latest stable release of GtkRadiant and check if it works better there:
viewtopic.php?f=10&t=47632

If things still don't work, try uploading a screenshot and post it here so we can have a better idea what's going on.

And just to be sure under the Catalyst Control Center, go to the 3D settings, and then set AA to "Let Application Decide", i.e. CCC should not force AA on the applications.

Obsidian, I don't mean the grid is literally invisible, but that it's so heavily aliased that I can't SEE the grid squares as they should be.

AEon, I had actually never thought to try application controlled settings, but that seemed to fix it. Thanks a lot

... had that problem a few years back under XP SP3 as well... the older GTKradiant 1.2.13 did not seem to have that problem, the newer ones suddenly did.