Camera view issue with GTKradiant?

[AEon]

Running the old tools on my XP PC, everything should still be working on that machine, but for some reason, when I load a map and turn on fly mode (right-click mouse in the Camera view, in GTKradiant v1.4) I get something like this:

• [lvlshot]http://aeons.hugelaser.com//tmp/mapping/misc/GTKrad_1.4_Camera_view_issue.jpg[/lvlshot]

50%-80% of the upper window does not get redrawn when I fly through the map, and is gray instead. Apparently a redraw issue. Deinstalled and reinstalled GTKradiant v1.4, but a file compare did not show any .dll or .exe abnormalities (i.e. corrupted files), they were the same.

Since the other installed radiant versions v1.2.13, v1.5, v1.6. etc. all have the same issue, this seems to be some form of display driver issue. ioquake and quake3 run without issues though.

Maybe deinstalling Radiant, and using a clean vanilla install of the game as developer folder, removing any "weird" non-standard content (like shaders or scripts) other that default v1.4 GTKradiant stuff, might be something to try.

Any help appreciated, thanks.

[obsidian]

What GPU?

[AEon]

ATi X800 Pro, under Win XP SP3.

Since all this used to work, it is really strange, did not change the ATi drivers in ages, or any of the hardware, and IIRC the last aeRadiant changes also worked and did not show such weird issues across *all* radiant versions either.

[o'dium]

It does look strikingly like a GPU heat issue or something, I have to say

[AEon]

Hmmm... would playing Q3A not be a lot worse then?

[obsidian]

There's a known issue with a workaround option somewhere for ATI/Intel Display Bug (or something similar) in preferences, turn that on.

[AEon]

• Display, 2D Display/Rendering, ATI cards with broken drivers - bug #802

Tested it yesterday, now turned it on, quit, and restarted, alas still no dice. I am guessing something I deinstalled, some game, may have broken something.

Are there any drivers I might be able to repair or reinstall to make things work? I could try an reinstall the ATi drivers maybe.

Maybe something in a most recent Win XP update broke something on my system, e.g I use very old ATi drivers (several years old) because they gave a better performance, and now they simply do not work any longer?

[Ouija]

It is an ATI driver bug for sure, I remember this one from working on an old 9500. I think it's either the drivers or driver settings, such as hardware anti-aliasing (it's the edges that glitch out, see?) and whatnot. I suggest trying other (older) driver versions, and tweaking some settings in ATI Tray Tools or Catalyst Panel if you have either installed.

[AEon]

OK... will brave it, backup C:\, then reinstall the present driver again, if that fails, try the latest catalyst. Since I am not planning to play anything much on this old rig, a driver related slowdown should not be much of an issue, hopefully.

[AEon]

I deinstalled the ATi drivers completely, then reinstalled my "trusted" age-old v6.08 driver with Control Center. I no longer have the issue... something must have corrupted the drivers or messed up some setting.

Thanks for the feedback folks... now to see if I will actually get some mapping done, e.g. finish AEdm7 (beta 3 seems to have been the last version).

[Ouija]

Confirmed my suspicion then, it's the newer legacy drivers hating OpenGL, simple as that. Glad you figured it out.

[Eraser]

I remember having problems with ATI Catalyst drivers years ago as well. The Enemy Territory demo required me to update to the then latest drivers, but as a result, all other OpenGL games wouldn't work anymore, including Q3 and Half-Life 2. I reverted back to the old drivers and then everything worked again.

[AEon]

Just to be clear, the really old driver I am still using now, v6.08, is exactly the same driver I had previously installed that was causing the issues. Something must have corrupted the driver installation. But as mentioned Q3A worked fine. So I did not actually test anything new... back when I tested the v7.09, that made Two Worlds unplayable, whereas v6.08 barely made the game playable on this P4 2.54 GHz, X800Pro rig.

That did give me a slanted view of how "good" such driver updates actually are, especially if you do not have the latest generation of gfx card installed. Same with my Win7 (PC that has some major PSU fuck-up presently). The ATi drivers I use there are from when I got the PC, 16 months ago, April 2010, and never updated. I did glance at some update change logs, and they would never really mention obvious improvements for my card (ATi HD5850 PRO), so I never bothered. (Boy this is off topic ).

[Kat]

I've got a similar problem to this with a laptop running the Intel 3000 GPU chipset, the ATI bugfix works to a point and definitely doesn't like cameraclip to be 'off'