Quake 3 on Classic

[Cowcat]

I use lightmap, not vertex.

If you also use dynamic lights, we have one.

Thing is that the use of altivec could be beneficial on "expensive" effects, like dynamic lights (as the light ball that follow a missile for example) but those are small cases.

On other Q3 engines the use of SSE is on more general functions and that could be interesting to tackle in the future if someone mimic those in altivec.

Then minigl, c functions like memcpy-memset, etc, etc.

[Cowcat]

Test,test,test...

[grelbfarlk]

Yes, it works again! Great!

Now fix Ifusion to work too.

After testing a bit... GL_Nearest must be the default, GL_Linear does actually smooth some effect like the explosions and blood haze are not blocky any more, walls and floors still seem pretty pixelated. There is a performance decrease but it's only a couple frames and textures on characters are noticeably less blocky.

GL_LINEAR_MIPMAP_LINEAR and GL_NEAREST_MIPMAP_NEAREST I guess are the only other two filters available to Warp3d, if you're really really bored could you try to add them? GL_NEAREST_MIPMAP_NEAREST looks about the same as GL_NEAREST, so that's probably not worthwhile.

I guess Quake3 normally uses GL_Linear_mipmap_nearest is default on PC, I guess the other option is you could just write new Warp3D drivers for us.

[Cowcat]

Yes, it works again! Great!

WTF dude: I cannot understand what made this work again without changing a thing discussed in Sonnet thread.

There will be a r2 version due some problems with demo recording, etc.

Some stuff is added like "sys_nostdout" and besides a whole bunch of internal updates, mirror visuals are fixed.

Still working with dll creation: Works with 68k version but warpos have problems. Anyway dll's cannot be used for online playing (it switches to bytecode), but for single playing it is considerably faster in 68k.

Some of those textures settings are supossedly supported by warp3d but don't remember if old minigl has code for it.

[Hedeon]

Isn't CVar_Validate related to the config file? Seeing it is comparing strings and all?

[Cowcat]

Isn't CVar_Validate related to the config file?

Could be, but cvar functions are used all over the place and probably Validate is not only used on config file. Maybe some cvar function call has been updated lately or some string check here and there this months: Been doing that as soon a particular fix is done on official ioquake3, spearmint or Quake3e.

[grelbfarlk]

Originally Posted by Cowcat

Yes, it works again! Great!

Some of those textures settings are supossedly supported by warp3d but don't remember if old minigl has code for it.

Don't know if this all actually works but I see in MiniGL:

ULONG tex_GLFilter2W3D(GLenum filter)
{
    switch(filter)
    {
        case GL_NEAREST:                return W3D_NEAREST;
        case GL_LINEAR:                 return W3D_LINEAR;
        case GL_NEAREST_MIPMAP_NEAREST: return W3D_NEAREST_MIP_NEAREST;
        case GL_LINEAR_MIPMAP_NEAREST:  return W3D_LINEAR_MIP_NEAREST;
        case GL_NEAREST_MIPMAP_LINEAR:  return W3D_NEAREST_MIP_LINEAR;
        case GL_LINEAR_MIPMAP_LINEAR:   return W3D_LINEAR_MIP_LINEAR;
    }
     return 0;

Then in Warp3D:

#define W3D_NEAREST             1       /* no mipmapping, no filtering */
#define W3D_LINEAR              2       /* no mipmapping, bilinear filtering */
#define W3D_NEAREST_MIP_NEAREST 3       /* mipmapping, no filtering */
#define W3D_NEAREST_MIP_LINEAR  4       /* mipmapping, bilinear filtering */
#define W3D_LINEAR_MIP_NEAREST  5       /* filtered mipmapping, no filtering */
#define W3D_LINEAR_MIP_LINEAR   6       /* mipmapping, trilinear filtering */

[Cowcat]

Checked today this subject:

Both old & newer hyperion minigl call

W3D_SetFilter(context->w3dContext, tex, minf, magf);

to do the mipmapping & this work is left to the warp3d drivers. Sucess depends on gfx card and the updated W3D. Seems to me we are stuck in year 2001.

[BULI]

Originally Posted by Cowcat

Test,test,test...

Downloaded and will be test soon Thanx

[grelbfarlk]

Originally Posted by Cowcat

Checked today this subject:

Both old & newer hyperion minigl call

W3D_SetFilter(context->w3dContext, tex, minf, magf);

to do the mipmapping & this work is left to the warp3d drivers. Sucess depends on gfx card and the updated W3D. Seems to me we are stuck in year 2001.

I don't know what's going on, I started the game with GL_Linear_mipmap_nearest and the settings in the menu were for Bilinear, started a demo and switched to GL_Linear, after the demo was completed it's now set to Trilinear in the menus and it looks pretty good. Floors are reasonably smoothed and characters, weapons don't look blocky, so that's good enough for me!

GL_LINEAR_MIPMAP_NEAREST I guess is the default based on what's in Wrangler's cfg, this looks like it sets it to GL_Nearest which is the fastest and worst looking setting. At least when I set it like that it looks like GL_Nearest.

So for people who want to test this for themselves, set r_texturemode=GL_LINEAR , you can do this while the game is running, even when in a map. It's a little slower but looks much better, fair tradeoff to me.

[Cowcat]

Funny is some (old) "trilinear" check is done against Voodoo cards just to make sure never gets enabled. I assume is pretty old stuff done against some ancient window drivers, but I believe non of it gets disabled: The string checkin for gfx cards don't match what minigl gives, so didn't try to update this part of the game.

Still Q3beta5 OK?: Read that problems still remain for some Sonnet user(s).

[grelbfarlk]

Originally Posted by Cowcat

Funny is some (old) "trilinear" check is done against Voodoo cards just to make sure never gets enabled. I assume is pretty old stuff done against some ancient window drivers, but I believe non of it gets disabled: The string checkin for gfx cards don't match what minigl gives, so didn't try to update this part of the game.

Still Q3beta5 OK?: Read that problems still remain for some Sonnet user(s).

I have had it throw an exception once when I set some video options and screen was messed up, so I quit and that's the point that it threw the exception. Otherwise I have not played it that much other than to run demos, but that's the only one I've seen.

[trixster]

Originally Posted by Cowcat

Still Q3beta5 OK?: Read that problems still remain for some Sonnet user(s).

beta5 workig ok for me. not sure what my crash was but all working fine now, it hasnt happened again.

[Cowcat]

Originally Posted by trixster

beta5 workig ok for me.

Glad to read that.

[grelbfarlk]

Working ok for me too.

[BULI]

Originally Posted by grelbfarlk

Working ok for me too.

For me too.

A have exactly the same result in demo four- 25.7FPS (same file q3config.cfg) as before version with JIT.

[Cowcat]

have exactly the same result in demo four

Although some code is updated, not much has changed JIT-wise. Beta5 was released just to see if worked OK with newer Sonnet library.

[grelbfarlk]

The crash on exit after changing video settings and "blindly" exiting is actually a bit of a bear, when this happens it doesn't save the q3config.cfg. I was going to turn on Lightmap, what's the config file setting for that? Does anyone know offhand?

[Cowcat]

"blindly" exiting is actually a bit of a bear, when this happens it doesn't save the q3config.cfg

I thought it did. Anyways, launch q3 from shell with +set r_vertexlight 0 ...but you know that already.

[BULI]

Originally Posted by trixster

beta5 workig ok for me. not sure what my crash was but all working fine now, it hasnt happened again.

In my config, I had few crash in new Q3 (freeze screen and looping samples), in earlier versions, especially without JIT, I hadn't it, was more stabille.


Maybe I should something change in my Q3config (I have sound on via 8 bit DMA and dynamic light).

Or, I have not enought memory 192 MB in my Sonnet?