Weird radiant preview

[Asvarox]

Well i think it started to happens after i change my videocard to radeon x1650 (supports opengl20)
http://img46.imageshack.us/img46/3117/huhdc4.jpg
It always happens after 1-2 mins of using radiant. No matter if i run radiant @ high details or @ low details (btw. when i set antialias to x6, it makes gird unusable is it possible to fix without turning off antialias?).
PS. No it doesn't look cool for me

[epsy]

erm, i have trouble to tell what went wrong in the pic you posted, and i think others will have too, so
can you describe what's the problem on the picture please? (eg. what we should see instead)

[rotacak]

I have same problem. I switched gfx card from old nvidia to radeon 9550 / X1050 and this happen. Textures are totally messed up after few minutes. Textures still changing their perspective, so you looking to flat wall but you don't know what you really see, because is seems like wall, then like hall, then like glitch, then like ground etc.

[Bissig]

Sounds like a driver problem. Try to find more up to date drivers or a different set of drivers.

There are the new open source ati drivers and there are things like fglrx.

[Asvarox]

erm, i have trouble to tell what went wrong in the pic you posted, and i think others will have too, so
can you describe what's the problem on the picture please? Smiley (eg. what we should see instead)

Sounds like a driver problem. Try to find more up to date drivers or a different set of drivers.

I have most up-to-date drivers (From August i think). I will install a linux tomorrow and check if those opensource drivers work

Btw. I found in options "use alternative texture rendering", i checked it and restarted radiant. Couldnt see anything (like every map file was an empty file)

[n.o.s.brain]

it happens for me too with a radeon x1600, when i rotate anything or select md3 models. i hak it by turning off the rotate tool, and then selecting a surface and opening the surface inspector... updating graphics drivers doesn't help for meh :/

[UniqPhoeniX]

I had the same problem before (also the problem with grid), but I haven't seen it for a long time. Radeon x1950 Pro, have updated drivers a few times, that probably caused and later fixed it . It happened to me almost always when i selected an entity like info_intermission and rotate tool and then moved the 3d view...
Err wtf atm I can't see the arrow showing the angle of an entity...

[Bissig]

It might be a bug in ATI's OpenGL implementation. ATI is kind of famous for having very nice hardware but buggy as hell drivers.

When Tomb Raider first came out, it was unplayable on ATI Rage Pro hardware because the driver reported that the card CAN do alpha transparency in hardware, whereas in reality it couldn't. So, when I tried to play the demo were you need to jump from inside a building out the window onto a ledge, you'd only see a black void where the window should have been.

I don't know if it exists but should Radiant have a "render in software" feature try to use that.

[Odin]

You should turn off anti-aliasing in map editors because quite frankly, you don't need it. When you're editing a map you're not trying to enjoy nice visuals, you just want a fast, responsive map editor.