OglX version 0.1


Image Insert:

31.91 KB

I think those damn DXTC textures cause this dreadful image. I think the only way is to convert those textures. Maybe it can be done manually, every texture can be accessed. But I am not sure if the map will give errors like can't find texture.

yes ,this is possible to do
with map isnt problem ( Q3 have in maps textures without extension and in loading function testing what texture type exist on HDD)




Image Insert:

57.75 KB

Is the last image a example of how it looks with normal textures???
Or are these still the normal DXtc ones, look at the arm that seems to look normal? And I thought that some of the textures in CoD are not Dxtc, which is probably why tha arm looks correct.

textures converted into .jpg


Image Insert:

48.02 KB

@Doom nice work,
About those .jpg textures. Didn't the .tga textures work as well as the .jpg ones? You where right with the lighting being incorrect, maybe something can be done by software emulation? I don;t know what exactly has been changed in the Quake3 engine in the lighting department, but I do now that exactly the lighting in the CoD engine is changed I will search if it is something that the V2 can't support.

yes .tga textures works ok, but i dont have HDD space fot .tga
lighting problem is now fixed:

Image Insert:

83.68 KB

The pictures are surprizing !
(what's the problem with the hdd ?)

no realy problem , only .tga files are much bigger than .jpg

OglX 0.2

Image Insert:

74.79 KB

Image Insert:

115.53 KB

wow....
it's really a improvement compared to the initial screenshot to the screenshot now...
Doom, you've done another fantastic job!!

Indeed, Doom your very good/talented at this. its looking great

Are you still planning on some tweaks for Doom 3 and VSA 100 cards (Voodoo 4 & 5) ?

Gwhahaha... You surely proved those guys wrong that where convincing me that it was impossible to run this game on the V2. You OGLx 2.0 is improving.

yes,he proved me wrong..never using the word "impossible" again..

Doom, so you are the developer of oglX ?
can you tell us something more about this driver (some background/problems/ideas)?
btw, nice work man