> Almost certainly. Last time I glossed over it, there definitely seemed to be
> some registers missing which would need to be emitted. Though it might be
> easier to just put everything in one single big block and emit that instead,
> since it looks like everything fragment shader related has con
Dave Airlie wrote:
This is not a driver bug. Doom3 with r_renderer arb simply does look
that awful. At least I've tried it with some other OS, and it looked
exactly the same. AFAIK noone has the required documentation to
implement the ati fragment shader extensions, which are required to
enable oth
> [1] current mesa CVS appears to use a number of constants mostly related to
> HYPERZ without defining them. Perhaps I should have followed build
> instructions exactly. I have a patch that gets me through the compilation (it
> is not something to commit, rather to give an idea where the problems
> This is not a driver bug. Doom3 with r_renderer arb simply does look
> that awful. At least I've tried it with some other OS, and it looked
> exactly the same. AFAIK noone has the required documentation to
> implement the ati fragment shader extensions, which are required to
> enable other r_ren
Hello,
I thought I would share my impression of running DOOM3 (250SEK on
sale!) using DRI drivers (free!).
SUMMARY:
- hardware TCL broken.
- some lighting problems with software TCL.
- few lockups (save frequently!).
- average 10 FPS on AMD XP1800+, Radeon 8500LE, 640x480.
FOLLOWUP:
My goal was
Pawel Salek wrote:
Hello,
I thought I would share my impression of running DOOM3 (250SEK on
sale!) using DRI drivers (free!).
SUMMARY: - hardware TCL broken. - some lighting problems with
software TCL. - few lockups (save frequently!). - average 10 FPS on
AMD XP1800+, Radeon 8500LE, 640x480.
F
