Haha ;)

Context, context, context ... 

but I agree, standards are important and if an engine implements something without a standard, that implementation can become a standard. It mostly depends on what content (maps/mods) actually use the feature.

I have tried to be cautious about adding crazy new features, and luckily most of the features I've added had a near-complete standard for how they worked (lit files, skybox, fog, external textures, .alpha, etc.)

When I do have to do my own thing (new protocol) I try to at least make it sane, and in the case of the protocol, I tried to add as much as possible in the first version to reduce the need to constantly make new protocol versions which only add one new feature.

Bumping limits is a stealthy way to set (or break) informal standards of course, and luckily aguirRe's engine has stabilized on which limits it bumps, and I was able to mostly bump all of those limits in a single release. 

hey, this is anon again..

don't know if this is a bug or just me being stupid BUT, upon completing all of the episodes/runes nothing happens. Specifically, I get back to "Introduction" and the last two episodes are locked (passed). The rest are open, even though I clearly remember them being locked upon completion. Also I only see 2 runes in the HUD.

Wazgoingon? 

You accidentally launched a new game after completing episode 2 and did not notice. 

You saved somewhere other than the start map. Which doesn't work too well... 

Old Mobility Radeon (gonna check the type later).
Driver: 6.14.10.6430

gl_clear 1 makes the game run ultra slow (think ~1 fps) in 32 bpp. In 16bpp it is slightly better (3-4fps I guess). 

No idea what type the chip is.
M6, 1002-4C59, 1028-00E3 (Dell Latitude something 610)

This is a new bug in 085. 080 works fine. 

The M6 Radeon is a mobile derivative of the Radeon 7000. Whatever the bug is, if it's on the Win32 driver side then it won't be fixed. I'd probably just keep gl_clear set to 0 until metlslime has had a chance to look at it. 

is this a bug specific to fitzquake 0.85 or do other fitzquakes (or glquake and derivatives) do it too? 

Fitzquake 085 only.

It seems related to how Fitzquake sets the resolution.

If I launch it with -width xxx -height xxx -bpp xx it works fine.
If I launch it normally, it does it's resolution change flicker and then runs so slow. I also noticed that the loading pentagram in the top right corner (always?) shows in funky colours then (like a normal map). Also a part on top of the display might flicker a bit.


PS: Setting a windowed mode with 16bpp when Windows is 32bpp is not fun. :P 

Testing large maps with FitzSDL-0.85beta on my desktop i'm getting quite a few crashes, sometimes every 5 minutes. And it just killed Xorg/Linux on my laptop while playing "timedemo demo1".

Hmmm... playing "-nosound" and have yet to get a crash. (Still.. negations can't prove a theory). 

I played multiplayer some days ago at office with FitzQuake0.85... it was running like a charm till it hang up, without any possibilities to unblock the game, except Ctrl+Alt+Del, and kill the process... and no error message at all... Maybe a network protocol issue, or something else, not sure...
Did you ever had heard about such issue before ? 

no, never heard of that. Can you tell me what map, what mod, and what you were doing at that moment? 

Hang up happened twice with 2 different mods: Reaper 0.80 and Killer 0.90.
The map was THF the first time, and DM3 the second time.
I was just running (bunny-hopping) and firing spikes with SNG on an another guy the first time, and the second I was ambushed with RL..
I am actually trying to educate my collegues at Quake DM at office :) 

kinda liked the laggy monster movement animation v0.8 provided more than smooh v0.85 one. any way to set the imprefect monster movement at v.085 pls? would really like to downgrade this feature. thanks 

r_lerpmodels 0
r_lerpmove 0 

the documentation states that they both default to 0, but it is wrong, they default to 1 :P 

i'm not certain, but i believe i've found some kind of odd bug to do with .blocked for doors.

this happens in fitzquake, but not in aguire's glquake, which leads me to believe it's a bug with the engine.

basically, you get crushed by a door when you're standing on top of it while it is traveling downwards. this shouldn't be able to happen since you can't block a door in that manner.

the instance where this was happening was originally in a map that was breaking many limits, but i've transplanted the bit of map into a seperate map and the problem still occurs...

any idea what this is? i can give you the bsp/map if you're interested. 

Have you increased your max FPS at all? At very high framerates glitches like that can start to appear, and it might be that aguirre's engine keeps a hard cap on server frames. If you can reproduce it at 72 fps then it isn't that. 

if you can upload the map somewhere and email me the URL, that would be useful. (or just mail it to me if that's easier for you.)

Also what Preach said. 

my host_maxfps was set at the default 72.
i set it to 10 and 60 and the bug didn't happen.
setting it to 71 (and 70, 69) makes it happen at a different spot, but setting it to 68 makes it go away, however, i get a single 'unstuck' message as the door hits the top of it's movement so i think it still has the potential to happen.

i'll send you the stuff in the mail. 

should have thought to test this sooner, but the bug also happens in normal glquake.

i'm pretty confused right now, because i've never had this problem before. i'm trying to figure out if i've built something different somehow, but as far as i can tell, it's the exact same combo of entities i've used many times before. o.o 

Yes, this happens at the start of Drew's speed map and at the start of White Room as well. Any kind of long distance door like that which you ride downwards has the potential to start hurting you for no apparent reason. It sucks. 

it's good to know it's not a bug i personally created. Still good to know about it, though. 

So I'm finally playing warpspasm on fitzquake .85 sdl mac beta, and it's lovely (the way it was meant to be played, no less), but I notice that the background music is directional; that is, I only fully hear it facing a certain direction.

I don't know if this is an issue with fitz or warp, but I confirmed that it doesn't happen playing warpspasm in Darkplaces.