fitz0.85 is opengl right?

still dont understand what fitzquake have that joequake,qrack,glquake e.t.c dont have because with my ATI X850 in the only that dont screw my image...

:( but i whould love to know what it is :| need joequake to record speedruns demos :( 

gl_ztrick 0 

Mr Fribbles are you joking or serious?

I dont understand nothing about those things... if true i will try when i get home

thanks!

if joequake have this command... 

gl_ztrick i google it, and i guess you are right... zomggg will be the first thing I will do when I get home... 

I think fitz sets ztrick to 0 by default. 

there is no such command in fitzquake0.85 

finaly got home and try!

FUCKING YEEEEEEEEEEEEEEEEEE

is working

/me kisses Mr Fribbles 

I removed ztrick long ago. It was basically a hack to avoid clearing the z-buffer between frames, at the cost of half the z-buffer precision. It didn't play well with my sky rendering code, plus it's not needed any any card newer than the voodoo1. 

I'm using the fitzquake085_mp3 build supplied in Baker's mp3 support tutorial but I can't get it to actually play any mp3 files. :(

I have no idea what could be possibly wrong. My soundtrack is in id1\music (or travail\music for that matter), and not within a .pak either. The playback related console messages appear for me, and I can use the mp3 commands just fine (without any errors that is). Nothing plays, still.

Is it as simple as turning it on with a cvar, or something? 

You have to use these mp3s due to the file names:

http://www.quake-1.com/files/modfiles/travail_soundtrack_mp3_easy.zip

They go in id1\music or travail\music folder. 

I have already renamed the mp3's myself beforehand. I also have the original Quake soundtrack in id1\music, also named track##.mp3. 

If it says ...

"track name is 03"
"playing track03.mp3"

Then check the volume control in Windows.

If it is just saying ...

"track name is 03"
and doesn't say "playing track03.mp3"

Then you don't have track03.mp3

If you aren't using -nocdaudio and aren't getting either of the above messages, something else is wrong. 

It says:

Track name is 03
playing track03.mp3

It's not my sound being disabled from within Windows, either, I can listen to anything else just fine. 

Have you tried renaming any old map and replacing one? 

After testing several maps from several gamedirs, I can safely say it's not a mapside problem ;) 

If it says playing, you can rule out everything the user is doing as a problem. It isn't the map or anything else.

It's either the engine, DirectX drivers or possibly Windows settings somehow.

In the future, I'll get broader testing of the change to get wider feedback. This modification hasn't had broad testing at this point. 

These are some features I think any Quake engine should have these days:

1. connect blah:port working well (this is the game that introduced online multiplayer after all)

2. NAT fix

3. Ping in scoreboard (it's just useful)

4. Support for fake CD tracks from ogg or mp3 files

The reason for having the basic multiplayer functions is that some people test their multiplayer-capable mods in Fitzquake because they're doing singleplayer maps as well.

The reason for the ogg/mp3 support (ogg is fine) is that finding and swapping and maintaining and storing CDs is a nightmare, especially since Quake CDs are getting older and rarer, and the Steam version doesn't come with the CD. 

My stupid test suggestion was made stupider. I meant to say 'mp3' not 'map'. 

An SP engine feature request / question.

Could we have global sounds play genuinely globally, and not only when in the player's LOS? 

Yeah, that should go into QSB 1.0.

Sorry for thread hijacking :-P 

Unlike other ports, Fitzquake freezes for a couple of seconds when using the edicts command in conjunction with -condebug. 

 

That actually sounds normal enough. The edicts command spews a *lot* of text to the console, all of which is written to the HD using unbuffered IO when -condebug is enabled. I'd be surprised if an engine does anything other than freeze for a short while, in fact. 

the solution is to buffer that stuff, but the negative of buffering is if you crash before you flush the buffer, you end up not logging whatever was buffered.

I guess it depends on what the primary use case of -condebug is. If it's diagnosing a crash, vs. just a convenient reference for later use. 

Well, it works flawlessly in GLquake and Ezquake for example. Winquake freezes, too.
The delay varies depending on the OS. On XP, it takes roughly 40 seconds for E1M1, on Win7 almost 100 seconds (and I even had to close it from the task manager afterwards). GL seems to handle the buffering differently then?