QuoteOriginally posted by ps47

tested the 6.1.0.9 release candidate on my voodoo3..
hitman contracts: no change
oni: no change
hmm..

Indeed, the 0.9 rc fixes compressed textures, which means the changes have effect on Napalm only. I understood that ONI is greyish, right? that's because of linear fogging, which never worked correctly on Voodoos (although I'm not sure actually how is supposed to look ONI). But what about Hitman Contracts? What's wrong with it? Can you detail a bit? Thx.

PS: BTW, you just forgot to tell me that I need to be patient with Hitman Contracts. It really takes its time before starting up. That was my problem, after all... I'm a loose cannon when it comes to waiting and gave it the three-fingers-salute!

@bloodworm
Could you test NWN full game with rc3, please?

QuoteOriginally posted by dborca

Indeed, the 0.9 rc fixes compressed textures, which means the changes have effect on Napalm only. I understood that ONI is greyish, right? that's because of linear fogging, which never worked correctly on Voodoos (although I'm not sure actually how is supposed to look ONI). But what about Hitman Contracts? What's wrong with it? Can you detail a bit? Thx.

PS: BTW, you just forgot to tell me that I need to be patient with Hitman Contracts. It really takes its time before starting up. That was my problem, after all... I'm a loose cannon when it comes to waiting and gave it the three-fingers-salute!

ok,tested the 0.9 with oni on my voodoo5,and the game itself is fine now.I still have to use koolsmoky's glide3x to avoid problems with floor textures that are bit more distant (I have mentioned it before),but the game is not greyish anymore[8D].
sorry about hitman contracts,when you run it in opengl mode you will have to wait with black screen 'cause all intro videos are not displayed,but  they stil run so it takes some time to get to the main menu.mentioned it in the "how to" from voodoofiles,but I guess it was not clear enough..
and whats wrong with contracts?well on napalm the game is crashy,you cant even take a sreenshot without crashing to desktop (6.1.0.4 or newer).on voodoo3 the game is more stable,but only the 6.1.0.4 release works properly (with texus2 disabled).all newer releases act like the texus2 is on (and that causes garbage),looks like its ignoring the the fact that I have disabled it via the bat file..I have posted sreeens on the previous page of thes topic..

QuoteOriginally posted by ps47

I have posted sreeens on the previous page of thes topic..

Yea, but I can't figure what's wrong!

I did a very little bit of testing last night with Rc3, and all of the textures looked sweet to me.  I will do some more extensive testing tonight with different modules of the game!  the movies in NWN have never worked (comes up black and I have to spacebar my way through em) except when I set the desktop res the same as the game res, and then the game will come up black after the movies play (with music and mouse with  screen "clicks" when clicking the mouse).  this is a problem with the Bink video player in winblows and the screen res change thingy that dborca does not work on because it is a winblows thingy.  I think this is the same problem that contracts is having, but I don't own that game.

QuoteOriginally posted by bloodworm

I did a very little bit of testing last night with Rc3, and all of the textures looked sweet to me.  I will do some more extensive testing tonight with different modules of the game!  the movies in NWN have never worked (comes up black and I have to spacebar my way through em) except when I set the desktop res the same as the game res, and then the game will come up black after the movies play (with music and mouse with  screen "clicks" when clicking the mouse).  this is a problem with the Bink video player in winblows and the screen res change thingy that dborca does not work on because it is a winblows thingy.  I think this is the same problem that contracts is having, but I don't own that game.

Bloodword, are you using SFFT alpha driver?. If yes .. this is the problem. I've used the alpha 7 for testing and I have had the same problem (black screen) switching to AM3.0 no more problem and neverwinter night return to playing for me.

I have had some other strange problem using SFFT Alpha 7. In Call of Duty settings the resolution or changhing the detail freeze the pc wichever mesa release I use. Switching back to Amigamerlin 3.0 no one of this problem camed out. I'll inform SFFT about this.
Now ALL games that I 've tested run fairless in opengl.

Try and let me know

QuoteOriginally posted by ps47

QuoteOriginally posted by Amigamerlin

No problem for me with ONI and MesaFx 6.1.0.8. and voodoo5 5500. All looks ok and no problem with the menù.

I'll try hitman Contact !!

Bye

can you post a pic or two and your system configuration?and what glide3x are you using?

Glide3x .. is the one sitributed in the package (root Directory)

Image Insert:

51.26 KB



Image Insert:

80.87 KB

QuoteOriginally posted by dborca

QuoteOriginally posted by ps47

I have posted sreeens on the previous page of thes topic..

Yea, but I can't figure what's wrong!

ok.I think the hitman contracts problem looks like this:
6.1.0.4->I can disable texus2->everything is fine.
6.1.0.5 or newer->I cant disable texus2->graphic issues.

looks like turning texus2 off with bat file DOES NOTHING..

QuoteOriginally posted by ps47

ok.I think the hitman contracts problem looks like this:
6.1.0.4->I can disable texus2->everything is fine.
6.1.0.5 or newer->I cant disable texus2->graphic issues.

Dude, what issues? I don't even know how it's supposed to look like.

hmm,my english is probably worse that I thought[xx(]
I will try to put it as simple as I can.
I'm running hitman contracts demo on my voodoo3 3500tv.
I use opengl and mesafx.
mesafx6.1.0.4 works fine,you must ENABLE SW rescaling to fix white textures,and DISABLE TEXUS2.if you do this,the game runs and looks the way it should.

if you leave texus2 on,all textures are just a black mess.

with mesafx6.1.0.5 or newer I have disabled texus2,but the textures remained black (posted pictures,page 25 of this topic)

it looks like I cant disable texus2 with 6.1.0.5 or newer..

QuoteOriginally posted by ps47

all textures are just a black mess.

That's what I wanted to know!

QuoteOriginally posted by ps47

with mesafx6.1.0.5 or newer I have disabled texus2,but the textures remained black

Do you mean the intro screen always looks like this?
http://www.3dfxzone.it/enboard/topic.asp?TOPIC_ID=1107
I'm not sure they are supposed to look like that all of the time. I mean there are some flashing effects, but the overall screen should remain blackish.

you are right,the main menu looks that way only during that flashing effect (lightning strikes outside;)).the main menu should look like this most of the time:
Image Insert:

73.59 KB
as you can see,there is no graphic corruption,the room is a bit darker but still good visible..(just for the record,vodooo3 3500tv,with mesafx6.1.0.4.,sw rescalling on,texus2 off;))

QuoteOriginally posted by ps47

as you can see,there is no graphic corruption,the room is a bit darker but still good visible..(just for the record,with mesafx6.1.0.4.,sw rescalling on,texus2 off;))

Hmmm... it seems that Hitman Contracts pumps precompressed S3TC textures into OpenGL, based only on the faint assumption of GL_EXT_texture_compression.

OpenGL spec does not bind GL_EXT_texture_compression to any specific format whatsoever, so this technique is really disgusting. That is, GL_EXT_texture_compression might exist, but the renderer might choose to provide FXT1 only, for example.

Bad OpenGL coding exists everywhere, and is unfortunate that we, driver developers have to deal with such things...

Other examples:
BloodRayne demo: does check for WGL_ARB_render_texture/WGL_ARB_pbuffer, but right after the test (and regardless of its result) it jumps into WGL_ARB_pbuffer routines. Hmmm... Also tries to use 4 TMUs, regardless of the OpenGL limits.
ONI demo: by some magic (and contrary to any OpenGL techniques) it fetches the function pointers of BlendColor and assumes GL_EXT_blend_color is present.
Savage2 demo: well, it blindly assumes GL_EXT_vertex_buffer_object, GL_EXT_texture_compression and GL_S3_s3tc.
UT2004 demo: issues some cube_map commands, even if cube mapping is not available.

I'll try to think of a workaround for Hitman Contracts. I still don't know how it's crashy on Napalm. What's the drill with screenshot?

cant help you much with napalm.the game is unstable,I cant even make a screenshot (using hypersnap,it works fine on the voodoo3),because the game crashes instantly.usually crashes when I try to change the graphic setings as well..

QuoteOriginally posted by ps47

cant help you much with napalm.the game is unstable,I cant even make a screenshot (using hypersnap,it works fine on the voodoo3),because the game crashes instantly.usually crashes when I try to change the graphic setings as well..

Whether it crashes when you try to take a HyperSnap screenshot is not a criterion. It did not crash on my Napalm. Ever. Try to use other Glide3x libraries to see where theproblem is.

ATTN everybody on this thread:
It's a general rule of thumb that people always bitch about Mesa, even when other software is faulty (either be it directx part of the driver, or third party software). Well, it works the other way, too: maybe Mesa is doing things right and the others don't. I'm not paid to accomplish full compatibility with every d@mn piece of software in the world. I'm not paid at all. However, I WILL continue MesaFX support, just for fun. I don't say that MesaFX is bugfree. Au contraire... But, before making assertions about buggy MesaFX, /PLEASE/ try everything that's possible to eliminate other sources of errors. I might be able to workaround conflicts with certain software, but I need something more than: "omigosh! it crashed".