point-size entities will behave correctly, since a rotated point is still point-sized. It's hull1 and hull2 which are built around box-shaped entities which will exhibit inaccurate collision when the hull is rotated. 

I believe for legacy maps, and people who simply want to keep using them, hiprotate will not go away... Quoth supports it nicely, RMQ will keep supporting it as part of its backwards compatibility effort etc...

For those of us who would like to do it in a more sane way in the future, the avelocity based rotation will be a gift of the gods.

Meaning, with RMQ and other forwards-compatible mods, you'll be able to have what you prefer. 

what does it mean:

it's from a console log
-------------
]quit
VID_Gamma_Restore: failed on SetDeviceGammaRamp
------------- 

ATI sucks. 

i got nvidia 

Well, I think it says something about not being able to restore the original gamma (of the OS versus the one ingame). 

it means restoring your desktop gamma setting didn't work, but i'm not sure why -- windows doesn't give any useful error messages when that happens. 

That's what it means.

A piece of shit geared towards your needs, the users needs.

I can't be arsed - but imagine I'd just gone on for a while about how magical a piece of shit can be, but at the end of the day is still something that won't fuck off no matter how many times you flush. 

also, after talking to somebody by email (baker, jpl, or spirit, or maybe someone else)... that person told me he was getting the message even int cases where the gamma change actually worked! So sometimes the "failure" isn't actually a failure, from that one user's report. 

Post failed! 

They fall true the map.
In all the other engines they hang on the wall, but in Fitz ver .85 they either appear normal, throwing meat at you, or they fall true the map.
I don't get it.
If I start the start.bsp map, they are all hanging nicely on the wall, but in my own (nearly done) map, they don't. 

Can't delete my previous post.
There was something wrong, but it was because I was using an alternative pack.

Sorry ... 

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.