VOGONS


First post, by Joseph_Joestar

User metadata
Rank l33t++
Rank
l33t++

I'm experiencing a weird issue with Quake 3. If I force Anti Aliasing from the Catalyst Control Panel, the game starts, but only displays a black screen. Everything still works, and I can open the console via ~ and type in quit to exit the game.

For reference, I'm using a Radeon X800 GTO with Catalyst 6.2 and DirectX 9.0c running Quake 3 version 1.32c under WinME. I'm guessing this might be driver related since it doesn't happen on Catalyst 7.11 under WinXP. Also, it seems to affect other games which use the Quake 3 engine, such as Voyager: Elite Force.

EDIT - I accidentally found a workaround. For Quake 3, press ~ to open the console, then type in demo four which will simply play back the pre-recorded demo that ships with the game. The demo gameplay should show up on the screen, at which point you can press ESC and the UI should render correctly as well.

For Voyager: Elite Force, first you need to start the game without AA and then create a save file. After that, quit the game, force AA in the Catalyst Control Panel. Then, start the game again, press ESC a few times to skip the intro movie, then press ~ to open the console and type in load eforce0 which should load the save you just made. Pretty clunky, but it does the job, and the UI will render correctly from that point onward.

Leaving this here in case someone else has the same problem.

PC#1: Pentium MMX 166 / Soyo SY-5BT / S3 Trio64V+ / Voodoo1 / YMF719 / AWE64 Gold / SC-155
PC#2: AthlonXP 2100+ / ECS K7VTA3 / Voodoo3 / Audigy2 / Vortex2
PC#3: Core 2 Duo E8600 / Foxconn P35AX-S / X800 / Audigy2 ZS
PC#4: i5-3570K / MSI Z77A-G43 / GTX 980Ti / X-Fi Titanium

Reply 1 of 3, by leileilol

User metadata
Rank l33t++
Rank
l33t++

would a simple /vid_restart work?

apsosig.png
long live PCem

Reply 2 of 3, by Joseph_Joestar

User metadata
Rank l33t++
Rank
l33t++
leileilol wrote on 2024-06-27, 03:51:

would a simple /vid_restart work?

Sadly, no. The screen briefly flashes when I enter that, but remains black afterwards.

It looks like the game needs to render something in 3D before the UI becomes visible. That's probably why the "demo" and "load" commands solve the problem.

PC#1: Pentium MMX 166 / Soyo SY-5BT / S3 Trio64V+ / Voodoo1 / YMF719 / AWE64 Gold / SC-155
PC#2: AthlonXP 2100+ / ECS K7VTA3 / Voodoo3 / Audigy2 / Vortex2
PC#3: Core 2 Duo E8600 / Foxconn P35AX-S / X800 / Audigy2 ZS
PC#4: i5-3570K / MSI Z77A-G43 / GTX 980Ti / X-Fi Titanium

Reply 3 of 3, by leileilol

User metadata
Rank l33t++
Rank
l33t++

I assume the bug's coming out of a conflict with one of the viewports clipped in the UI (i.e. the 3d logo) causing a context of an antialiased buffer to go wrong. I don't recall having this bug, but I remember another AA bug on the x800 with edge ringing on the 3d HUD icons.

r_finish and r_primitives are also worth messing with

apsosig.png
long live PCem