News | Forum | People | FAQ | Links | Register | Log in
Fitzquake Mark V
I wasn't planning on doing this mini-project, it started as an effort to address some Fitzquake issues, fix them the right way up to Fitzquake standards (i.e. do it right, once and properly versus continual releases) and donate it back.

FitzQuake Mark V Download:

Short version: Eliminated most issues in FitzQuake thread, most issues I can even remember hearing of ever and marked every single one clearly with a very minimal implementation.

It may be the case that only metlslime and Quakespasm and engine coders may find this engine upgrade of interest.

Features: 5 button mouse support, single pass video mode, external mdl textures, alpha textures (like RMQ), record demo at any time, rotation support, video capture (bind "capturevideo toggle"), console to clipboard, screenshot to clipboard, entities to clipboard, tool_texturepointer, tool_inspector (change weapons to see different info), clock fix, contrast support, fov does not affect gun, gun displays onscreen, Quakespasm wrong content protection, external ent support, session-to-session history and .. (see readme).
gonna dig through this now. 
-sndspeed 44100 doesn't enable 44khz sound? 
Had A Look 
Digging the new water effect, set it as default :) the environment map & texture scrolling could be put to some good uses also, is it possible to have the environment map over a standard texture though? Looks kinda weird having only environment mapping with no base texture underneath.

The demo features are EXTREMELY welcome! Oh god you saved my life here :) 
Looks Very Interesting... 
I'll have to check it out when i get home.

Baker, does this engine make obsolete your previous "custom builds" of fitzquake? For example there was one a few years ago that had various fixes like the Intel adapter fix. 
Is there a full list of changes? The news post says "see readme" ... the readme says "see home page" ... 
going into fullscreen doesn't give me black screen anymore! :D

with the latest fitzquake i had to use a .bat with the windowed option for it to run, otherwise i had to tab out and then back in to see something. that was my only issue with fitzquake.

so far nothing wrong that i can see though [only played like 5mins though]. 
water ripple seems buggy though. lots of tearing and inconsistently sized faces on water brushes cause the ripple effect to be uneven. 
BSP2 Support? 
Or is that still RMQ engine only?

Lots of those fixes and features seem very useful. I like fov does not affect gun, although people that use extreme fovs in multiplayer kinda annoy me (especially in the 3rd person Rune, where you can see without being seen using an extreme fov). 
I Don't Think So... 
I didn't load your beta map ;) 
understandable ;)

vis is getting close to done, but every time it gets to 15 hours it goes back up to 25. lol. 
Random Note: 
r_waterripple looks better if you set "r_oldwater" to 1, because when r_oldwater is 0 it ignores the "gl_subdivide_size" setting. There are still subtle issues with it due to glquake's buggy subdivision (for example, it creates t-junctions.) 
The Real Problem Is 
Sine waves don't linearly interpolate. You cannot linearly interpolate a sine wave; the best you can do is increase tesselation so much that the problem becomes less visible - that's what r_oldwater 0 (in a sorta-kinda-roundabout way) or low values of gl_subdivide_size do, but at other costs elsewhere (fillrate, limiting texture size, extra vertex processing). 
Is there any way to stop monsters and pickups from being fullbright? 
Now my shitty laptop integrated gfx card can finally run maps with dynamic lighting without stuttering like Walter Jr in Breaking Bad.

But yeah, what Text_Fish said. 
See quakedef.h

I described the changes as best I could.

make obsolete your previous "custom builds" of fitzquake

Yes. My intention with this engine was so you (or the Quakespasm guys or any interested modder) could implement any fix or improvement you were interested it at will.

I know that over at Inside3D a lot of engine weaknesses have been uncovered [it is actually almost intimidating :( ] and rather than make it hard to absorb the solutions, I wanted to make it an easy process.

I've learned a great deal about the rendering process from FitzQuake's complete rework of it. This is my reciprocal work. :)

So far ... 
MH deserves all the credit for the frames per second increase. In the engine, this is marked as SUPPORTS_MH_DYNASPEED. It literally turns 11 fps dynamic light situations into 250 fps lighting situations. 
I do have a great liking for you demos. ;-)

I'm glad this made your day. 
Argh ... Quadruple Post ... 
@Tronyn ... no I haven't implemented BSP2 ... yet.

It you'd like everything BSP2 does, but in classic BSP, I do have your answer:

^^ BSP compiler with rotation and all BSP2 modification except it does classic BSP.

I didn't make that because I'm against BSP2 (I'm not) but because I have a conservative side that wants to understand individual changes one at a time. 
Is there any way to stop monsters and pickups from being fullbright?

Fixed. Thanks for pointing that out.

Please re-download. 
holy fuck the tool_inspector is awesome.
edict numbers, model index number, frame, target/targetname, absmin/maxs...
I won't be using this as a 'playing' engine (and it seems like that wasn't the intent anyway) but i will certainly use it for debugging stuff.
thank you! 
Cheers Baker. :) 
@daz, Necros 
is it possible to have the environment map over a standard texture though?

I agree, but I didn't want to introduce a hack into this. I'm not sure what a good mapping use of sphere maps are (except making metals look nice). That being said, you could use FitzQuake protocol 666 to place an alpha brush in front of another brush and use the environmental map texture on the alpha brush.

-sndspeed 44100 doesn't enable 44khz sound?

That isn't actually a FitzQuake 0.85 feature. 
Sorry, I've been using QS for so long now, I totally forgot about that. 
Well ... 
I've always liked the original Quake sounds as-is and one of the first times I gave a serious look at using DarkPlaces my first question was "The sounds in DarkPlaces are very 'crisp'" and I was told about the -sndspeed parameter which I set to 11025.

Maybe I'm in the minority.

I added -sndspeed command line param. 
Agree With Baker On -sndspeed 
With the sources at 11k and with the way Quake "upsamples" them by default, all it's really doing is pitch-shifting. The crispness may be there, but the bottom-end welly is all gone. 
don't really care about that myself. i've never noticed anything bad with the way it's done in quakespasm. that said, for whatever reason, the 11khz sounds seem uglier in DP for some reason.
Also, with my habit of using so many ambient sounds and random crap, i really can't do without 44khz. 
Is it implementation-time vs. level-of-interest prohibitive to add GLSL support for the sake of restoring software Quake's original per-pixel waterwarp on liquid surfaces and on the screen while underwater? If not it seems like a clear visual win over relying on subdivision and ST distortion, and I'm surprised we haven't seen it in more engines by now (MHQuake comes to mind).

GLSL isn't exactly new, and vertex based warp still exists as an elegant fallback. 
doing waterwarp on the surface with GLSL is fairly doable (though it is something I have never done.) It's probably cheap enough on any shader-capable card.

Doing the fullscreen warp when underwater involves touching a bit more of the renderer because you have to render the scene to a texture, then copy that texture to the screen using a warping shader. In terms of hardware requirements, I think anything that can run doom3 can handle it, but this is, again, based on zero personal experience. 
It's very cheap on any shader-capable card. The per-pixel sin is slightly expensive (although the shader compiler will typically optimize it to a single sincos instead of two sins) but that balances against a lower vertex submission cost due to no subdivision (and not to mention the ability to keep everything in a static VBO if you want to go that far).

Doing shader-based versions of both water and sky means that every single surf can go into a single static VBO, in fact, as no per-vertex data needs to be updated on the CPU at all (you'd use a cubemap for skyboxes in this setup - Doom 3 has some code for converting Q1/Q2 skybox layouts to alignments suitable for cubemaps and I've independently written the same conversion myself a few years ago so I'm reasonably certain that it can't be rocket science). Get some draw call batching in and you're suddenly running up to 5 times or more as fast in big, heavy scenes. That does require a higher GL_VERSION than Fitz aims for, as well as some massive surgery to the current codebase. Probably not reasonable to expect in any kind of short/medium timeframe, if ever.

The fullscreen warp has some complexities in how you handle the edges. You can use GL_CLAMP_TO_EDGE but it won't handle the bottom edge which juts against the sbar. There are solutions (I used a "control texture" that fades off the warp effect at the edges, another option is to just destroy and recreate the texture at the appropriate size if it needs to change, which generally doesn't happen at any performance-critical time).

Generally glCopyTexSubImage is going to be slower than using an FBO for this because it needs to shift more data around. Overall you can expect to lose maybe one third of your performance owing to increased fillrate even in the best case.

Another way to do it that doesn't need shaders (and will even work on GL1.1 hardware) is to use a grid of quads (much the same as what Fitz does for r_oldwater 0). That can give acceptable enough quality.

The third way is just to rotate the projection matrix a little based on time, which gives a reasonable enough effect at no performance cost. It's like Fitz's current stretch'n'squeeze effect but with some rotation added in too. You need to extract your frustum from the combined MVP rather than calculating it separately if you do this though. Easy enough (and a little more robust than calculating it separate).

Despite all this seeming complexity and multiple options it's probably cleaner and easier to integrate with any engine as it doesn't need to touch any code outside of it's own subsystem. So - detect if we're underwater (via r_viewleaf->contents) at the start of the scene, and either (a) just set a flag and/or (b) switch the render target. At the end of the scene, either capture the scene to a texture or put the old render target back, then draw using the appropriate method depending on what hardware capabilities are available.

For an engine like Fitz I'd recommend asm shaders rather than full GLSL. The main reason for that is that they're available on a much wider range of hardware, so they seem more in keeping with the Fitz philosophy. 
good news!
thanks, Baker. 
Alpha Animated Textures 
Would it be possible to do alpha animated textures?

Something like this:
I'll let Baker answer on his own behalf; this opnion is mine and mine alone.

Yes, it should be possible with the necessary code changes. However, by this point in time you're stacking up multiple "first character" hacks (alpha animated water with alternate anims anyone?) and things will begin to look a little delicate.

So some form of alternate system would be needed. Since Q3A shaders are out there, since we have a GPL working reference implementation (the Q3A engine), and since they don't require any format changes (just add a .shader file for anything you want different behaviour for), that would be my own preference. 
It might already be possible to do them:

Set r_texprefix_fence "+alpha" and load your level.

It should process all the textures that begin "+alpha" and likewise set a flag to mark that surface for alpha mask rendering.

I hadn't expected someone to want to use alpha textures like that, but I bet it works.

(Note: fullbright pixels in alpha textures are supported (except color 255 of course). Replacement textures replacing an alpha texture that has an alpha mask are also supported.) 
Baker this makes fitzquake look more like darkplaces, joequake, qrack e.t.c?

record demo is awesome... 
If by chance you are looking for something like JoeQuake, you might try Engine X. Engine X supports FitzQuake 666 protocol and looks like JoeQuake with the kind of very recent engine features one would expect (video mode change, etc). 
Obrigado Baker

I will see it ASAP!

Thanks for the reply!

Also, regarding the alpha textures, I think there is a bug with the way they are rendered, or it may be intended. The transparency textures bleed through the floor and you can see the void of the map.

Here is a picture showing what I mean:

Even if I paint the bottom of the glass brush with a solid texture, it still shows the void through the floor. 
Turn your alpha brushes into an entity like illusionary, door, func wall etc. Use a really good q3 fence texture, enable texture scroll and be amazed. 

Because of the way QBSP seals the world and chops off outside faces, putting this texture type on a brush that's not part of an entity will produce this result. It's expected behaviour and a result of normal QBSP operation, not really an engine bug (there's actually nothing that the engine can do to work around it as the data required isn't even there in the BSP to begin with). 
See above. I almost decided to enable alpha textures only for entities (func_wall, etc.).

But an experienced mapper knows all the rules and how the tools work and allowing it for the world is no different than, for instance, using the skip-remove tool.

Alpha textures should generally be limited to entities (func_wall, platforms, doors, etc). 
Random Black 
I have been testing my map with the mark V engine and for some reason all my models (map objects, items, weapons and monsters) randomly go black and monsters do it while patrolling.

I have checked the area the monsters patrol and my weapon does not go black. It is not a subtle change either, they are normal (full bright) one minute and then solid black the next.

Is there a special reason for this? (I know this is a counter productive thing to say but it does not happen in Fitz85) Is there a command line parameter I need to stop this? 
do they stay black with r_fullbright 1?

If yes, may be a texture problem.... if no, may be a lighting problem. (not a problem with your level, i mean a problem with the engine) 
I loaded the map, typed in r_fullbright 1 and I could see everything, no blackness. It looks like r_fullbright removes the light map from everything. It is very strange the blackness on certain objects, I thought it was specific locations where I have spawned stuff but it happens to wandering monsters.

I checked the original Q1 maps (played episode 1) and could not see any problems. I am using the latest compiler tools, hitting a couple of max limits but the engine still copes with it. 
It could be because I made the light check test against world submodels (plats, lifts).

I have a new revision to this with new features essentially done. I'll put a cvar in disable shadows/lighting from world submodels to see if that is the origin of the issue.

I also changed the lighting depth check (because MH did) from 8192(Fitz 0.85) to 2048 (original Quake) because MH had a comment about performance (8192 is a long, long distance).

The new version should be be available in 6-7 hours. 
Another Of Very Few Possibilities 
The code that obtains shadow surfaces in Quake is actually very imperfect and can fail to "hit" a downtrace for lighting. Prior to the trace, I may have it reset the result color to black (full darkness).

Either way this shouldn't be hard to solve. 
Awesome, thanks :D I will download it and test my map once you got a new link ready.

Another bug:
When I start the engine (windowed mode) the +mlook does not work (even if I have the window selected) The old Fitz engine when it started windowed would never give up the mlook but at least I could test my maps without have to go full screen all the time. (I usually have to exit Fitz to use another application because the mouse cursor is not available to any other windows apps).

Is this a windows issue? a problem with active window focus? Or is the application (mark V) not able to control the mouse look when windowed? 
I also changed the lighting depth check (because MH did) from 8192(Fitz 0.85) to 2048 (original Quake) because MH had a comment about performance (8192 is a long, long distance).

Note: the reason i extended this distance is because CZG had a really deep pit in one of his maps, and the scrags floating over that pit were black instead of taking the lighting from the floor. 
the light depth check could be tweaked via a command line parameter? Something to set before the engine fully loads? 
How much the increased depth check costs to make. Is it really worth reducing back to stock quake for a little extra performance? 
The lighting depth check should be cvar-ized. Having to restart the engine to change something like this is stupid.

2048 is probably a little too low, especially with the "run the test for static entities once only at startup" trick (which was where the main performance impact came from in tests - and mind you this was quite an extreme case too). It also fails to light models properly in Zerstorer when this low.

It's probably worth finding the max top-to-bottom extent of the world and using that value as well - that'll be guaranteed to catch anything. 
Yeah, That Works. 
end[2] = start[2] - (cl.worldmodel->maxs[2] - cl.worldmodel->mins[2]);

Why make the player do it when you can do you yourself? 
Continued ... 
@Necros: The lighting check is one of those super slow recursive world checks. I'll do as MH suggests and default it to the Fitz 0.85 --- I wasn't looking to make an changes in how Fitz 0.85 operates (I lacked the imagination of a situation where 8192 could actually be needed, like the CZG map metslime said that induced him to raise the distance check).

[I'll add in MH's idea of a world bounding box check .. and if set to 0 will check lighting from unlimited depth. These things are going to push the update version to tomorrow it seems. But getting things absolutely right is something worth taking the time to do.]

@Sock: Any chance you could zip your map plus save the game exactly at the point the view model (weapon) lighting is wrong? It would help me avoid investigating things that aren't actually the source of the problem. 
if you use the max level extents of the world, does that still save any performance? I assumed the cost of a traceline is related to the number of nodes it has to cross, and once the line is >= level extents, it's already the worst case, right? 
Or just end[2] = cl.worldmodel->mins[2] - better yet. 
@Sock Part 2 
Another bug: When I start the engine (windowed mode) the +mlook does not work (even if I have the window selected)

I didn't change any mouse operation, but I'll investigate and see that this gets resolved. 
The big advantage of basing it on the world extents is not so much in terms of performance but in terms of correctness. Using cl.worldmodel->mins[2] (I'd actually subtract another 10 or so just so that the end point is ouside the map, then check that start[2] actually is bigger than end[2] to cover for noclipping) means that you're always going to hit something during the downtrace - it's guaranteed because nothing in the world can be outside of that point.

The other method - pick a number and hope it's big enough - fails because eventually a map is going to appear for which it isn't big enough. True, 8192 matches protocol 15's default +/- 4096, bounds but it breaks on extended protocols that may increase those bounds.

Ultimately it comes down to a choice between a simple method that is guaranteed to always work versus just picking a number. 
Any chance you could zip your map

You certainly make it hard to be contacted, I tried the MarkV readme file, your account here and got no joy. Any chance you can drop me an email address? (my account here has my details) 
check your mail ;). 
New Version: 


Some features:

Game command supports -hipnotic, etc. Like type: game warpspasm -quoth

ALT-ENTER switches between fullscreen and windowed mode, "folder" command now opens the folder and highlights most recent file made (like a screenshot or demo).

Many bug-fixes, speed increases and Sock's lighting bug should be gone.

[Issue wasn't related to shadow downtrace for lighting, but I made that "infinite" now. r_lightpoint_depth 0 = infinite. You could set to 8192 or 2048 ... but I think I'll remove the cvar eventually. "infinite" is a Z endpoint of cl.worldmodel->mins[2] ... few objects.]

There are also major capture demo improvements to make things easy. See readme. If interested in demo capture, I recommend trying Google WebM (known as vp80) available at

WebM is the video codec Google wants to use as the HTML5 video standard, so it compresses video fast and the file size is small.

This engine revision will automatically detect that this codec is installed and use it.

[Video capture is simple in this engine.

Type capturedemo demo1 in console. Best to be in windowed mode so you can see demo progress. That's it.

You can also bind "capturevideo toggle" to a key] 
Another old Fitz bug, by the way:

Set host_maxfps to something stupidly high (10,000 or so) (I suggest adopting host_maxfps 0 = unbounded - Q3A did that and I had one player who was expecting the same behaviour from Quake).

Set scr_showfps to 1.

Look at the fps counter. Funny, isn't it? The tileclear isn't being refreshed every frame (which is a bad enough idea to begin with...) so the area where the counter lives just gets new figures drawn over it each time. 
I'll need to absorb your timing fixes first (plus add the server-side lerp movement for "monsters") and afterwards I'll make host_maxfps 0 function like as above. 
Please do not release updates using the same filename. Use the date as suffix or a version number. 
First release (R0):
Revision 1 (R1):
Revision 2 (R2):
Revision 5 (R5):

This meets my need of making someone doesn't download an old one for no reason, and should satisfy your desire to make sure no source codes/binaries get lost. 
"Title Demo" Support 
I forgot to mention the latest version has support for "title demos".

A "Title Demo" is a demo that plays with no HUD, no crosshair, fov 90, viewsize 120 (No status bar).

Usage: cl_titledemos_list "demo1.dem,demo2.dem,demo3.dem"

This allows usage of "startdemos demo1 demo2 demo3" to essentially play as a movie or an intro. This could be gameplay action or you could record of demo of you touring the map with no clip and no target (hopefully with a QuakeC progs that uses a null view model).

I more or less got this idea from how Warsow starts up showing game play action or how the original Unreal did a cool moving view of the castle. 
Add ... 
Kurok used a "title demo" as the start screen. It was a demo of a small map that was 70-90 seconds long (repeating) that showed a mountain and a block labelled "Kurok". For the longest time, I didn't realize the intro screen was a demo.

Demos, of course, are recordings of a map so they can have a soundtrack just like how a map can have a soundtrack key. 
Any chance to add widescreen Fov? Currently I have to put FOV 106 in the command line. 
Well ... 
That is a "no win" situation. Here is why ...

The field of view is the degrees of view showing. If I set to that to 90 degrees, I would hope that would be 90 degrees.

If I correct the FOV for widescreen to adjust to, say, a 4:3 aspect ratio (wide-screen correction) then it isn't really 90 degrees but some other number.

If I make it auto-correct, many people will not like it because it looks wrong because they are used to it looking a certain way in FitzQuake. So I would have to add a cvar to control it.

Which is one more setting for someone to mess with.

With how things are now, there is a setting to mess with (FOV) and everyone knows what it does. Versus add a new setting, which people would have to learn about. And other engines wouldn't save this new setting so it would get erased periodically. Not that FOV saves to config anyway.

Then there is the argument that 4:3 isn't the Quake aspect ratio to use for widescreen. That 8:5 is because original Quake loaded up to 320x200, not 640x480.

So ... I would add widescreen correction if a magic bullet answer exists. But I can't think of one.

The nicest thing about FitzQuake is that unlike some other engines that you can rely on it to be familiar versus some engines that do things that confuse you and you don't know how to change it or maybe it can't be changed. 
Agree with baker re:fov, but I would add that even in 320x200 mode, quake is intended to fill a 4:3 display, which means non-square pixels, but that is how monitors displayed that mode AFAIK.

(I sometimes look at the menu art and wonder if the letters are intentionally stretched to look correct in this mode.) 
Hey, when do you plan to release the version with mlook + windowed fixes? 
Boring engine technicality: MH explained a superior way of handling mouse input in the last day or two that is streamlined and efficient and very reliable and easy to manage.

So at the moment, I'm on a side quest since I don't want to put out two separate revisions that change the input code heavily back to back. Giving me something extra to do before I get this newest revision out and slowing me down a bit at the moment. 
I have to respectfully disagree with the rationale just given for not fixing up FOV. The reality is that hardware has moved on since 1996, and widescreen is now the norm. My own experience is that fixed-up FOV is a basic player expectation and not a fancy engine feature that's only of technical interest - I have a fairly large amount of positive feedback from people who specifically mention fixed-up FOV as a feature that they welcome.

Fixed-up FOV can be implemented without changing the defaults or other behaviour of the FOV cvar. FOV 90 will still give you the correct horizontal and vertical FOV for your chosen resolution and aspect, so everything can still work as expected.

320x200 resolution was not an aesthetic choice, it was a technical one. 320x200 was the old standard VGA mode 13h, meaning that it was the one display mode that was just guaranteed to work on everything. If that mode had been any other resolution, then that hypothetical other resolution would have been Quake's default. 
If widescreen really is the norm, just set FOV to default to 105 instead of 90. This gives correct behavior on a clean install, and doesn't override existing users configs that already have ~105 in their config.cfg or autoexec.cfg 
note that this probably means putting in a hack to ignore the default.cfg value for FOV, if there is one. But messiness under the hood may be worth it if the user experience is your highest goal. 
Why not just add a cvar to toggle between using absolute and aspect corrected fov, having absolute set as the default. 
the question is whether new users will have to change their configs, or whether existing users will have to change their configs. Any cvar like that would require one set of people to change their configs. 
The Problem Is... 
A large percentage of players aren't even aware that the FOV setting exists, or - even if they are - that it can be used to correct for widescreen (the same applies to +mlook). Those that are aware of it can always re-adjust. I suggest doing some research around the usual suspects such as the Steam forums, etc, for info on the specific problems that people have with Quake; these make great targets for fixing in any engine that aims at being accessible to players. Find what prevents people from getting into the game, fix it, and problems go away. This is the same philosophy behind removing the necessity for (but not the existence of) command-line options. Identify the barriers to entry, remove them, otherwise you're just developing for a captive audience who already know everything inside-out and are therefore not bothered by this stuff (and nor are they appropriate people to pass comment on how these things should be handled).

Regarding configs, the obvious solution is engine-specific configs. The old QuakeDev forums raised this as a point that was widely addressed in Q2 ports but all but ignored in Q1. It enables more peaceful engine cohabitation by ensuring that settings specific to one engine don't wreck another.

Again, it depends on who you're developing for. The same old group of people who will always use your engine no matter what, or are you trying to reach out to new players? 
engine-specific configs
oh my god, yes! or use /documents/mygames/engineName/modName/config.cfg 
documents / mygames / engineName / modName / config.cfg 
I Have To Admit, I Think MH Is Right 
I've seen his implementation of it, and it looks superior to anything else when it comes to the weapon being in the right place. Methinks. :E 
My Thoughts Were Incomplete 
MH is right as not having widescreen correction eats away at vertical FOV, narrowing the range of what is on-screen vertically. FOV was never intended to penalize vertical visibly, it was just that everyone used 4:3 resolution in the CRT era (640x480, 800x600, 1024x768, etc.)

This is a flaw. 
New Version: Revision 6 


Widescreen FOV correction, dynamic lights properly affect moved/rotated brush models, dynamic light bleed-through fix.

All entities are colormapped (colored dead bodies, etc. - like if in coop and you die or play against bots, etc.)

Demo rewind (PGDN) and fast forward (PGUP) of any demo the user plays via "playdemo"(and pause pressing pause key).

(The startup demo sequence is not user-initiated and that sequence is not meant to be paused or messed with as it is a game preview.

You must use the playdemo command like "playdemo demo1" to have demo pause/rewind/fast forward available.) 
Revision 7 
mp3 tracks support. And boring stuff you won't care about, although documented in the readme.


what about that infamous whiteroom bugfix

i assume thats still not fixed 
It's on the to-do list. I haven't worked through the potential solutions. I understand the underlying issue involved as szo and MH explained what causes the problem. please 
I followed the same naming pattern, I kinda of thought you'd know the URL but still ... 
Keeps Crashing/freezing My Computer 
Hi, loving the fov/gun/various other fixes in this, especially the clock fix so that the game runs at the proper speed, however as with your "Fitzquake Plus" I keep having an annoying issue - after playing for a while, the game freezes up completely, with the last sounds played looping over and over, then after a few seconds the screen turns a solid color and the sound a single tone. I can't ctrl+alt+del or do anything other than forcing a shutdown by holding down the power button. Previously this has only occured after playing for an hour or so, but today it happened after just a few minutes. I assume it has something to do with my computer having multiple cores, but I can't really pinpoint the problem. It's an ASUS G73JH laptop which I've had for two years, and I think it has only frozen up/crashed two-three times if I'm not taking these Fitzquake issues into account.

Here are my system specs:

Windows 7 Home Premium 64-bit
Intel Core i7 Q 720 @ 1.60GHz, 1600 Mhz, quad-core
6GB Installed RAM
ATI Radeon HD5870, 1GB VRAM

And my Fitzquake command-line parameters:

-width 1920 -height 1080 -bpp 32 -zonesize 2048 -heapsize 12800

I haven't played using Fitzquake 0.85 for long enough to see if it'll happen there as well, as I have the clock bug with it running too fast - that's why I've used Fitzquake Plus in the past, and now Mark V. Any input/advice on this is much appreciated. 
It's probably worth while to test using another engine (eg Quakespasm or FitzQuake0.85) to check that the problem is not one of bad hardware/overheating. 
If That Is REALLY Your Command Line 
Then you should be using:

-heapsize 12800

That means 12800 KB. Which is about 12 MB.

Although not a sure thing, this is likely why you are crashing. 
"Then you should be using: " = "Then you should NOT be using:" obviously ...

/Pays the price of not previewing post for 567th time. 
Seems like I managed to leave out a 0, it should indeed say 128000.

Seems like I paid the price even after proofreading! 
Also My Vocabulary Sucks 
Will give you a nice round 128 MB heap. 
I'd Give Quakespasm A Try Then 
The laptop I used when I was working on Fitz Mark V has virtually the same specs as your machine (graphics, Intel, Win 7 64, etc.)

I don't have any ideas on why you would have this issue, I will say that Fitz 0.85 should run on your machine if you do the "set affinity trick".

Go to Task Manager running Fitz 0.85 and select fitzquake085.exe and do Select Affinity and select "cpu 0" only. Then Fitz 0.85 will run ok without the clock issue.

The "clock fix" is just the standard deal that is used by engines like JoeQuake, ezQuake, etc. There isn't anything supernatural about it, it just uses a different Windows API call to get the time. I might have even used the code from DirectQ.

In fact, you might try DirectQ. Considering the quirky nature of the problem you have, it could be an OpenGL drivers kind of thing and DirectQ uses Direct3D: (Downloads on the right side of page) 
Was about to post that after changing my heapsize to 131072 I had played through several maps without crashing... and then everything froze as I quit the program. Joy.

I guess I could just use Quakespasm of course, but after having been away from singleplayer Quake for far too long, instead having played coop using EzQuake, I have become accustomed to how that engine looks and feels. I think Mark V captures this feel well with the widescreen fov and viewmodel corrections.

For comparison, here's how my screen looks using fov 130 with FitzQuake 0.85 and Mark V, and also r_viewmodelfov 130 for the latter.

Incredibly minor detail, and maybe I'm just imagining it, but movement feels much smoother with the corrections. 
Make that Quakespasm. Still, exactly the same as it would be with Fitz0.85.

Is Quakespasm your engine as well, Baker? 
So It Crashed When You Tried To Exit? 
Like when you tried to quit of Quake? Is this correct? I'm just trying to understand and get whatever info I can.

Quakespasm is a multiplatform FitzQuake: by szo, stevenaus and Sleepwalkr. 
Those 2 features you like (view model correction + widescreen correction). Those are both in DirectQ. 
Yes, froze up my entire system just as I quit the game. I've updated my graphics card drivers, hopefully that helps. 
There's a fundamental bug in FitzQuake and derivitaves (even the latest QS in the SVN has it) where the list of GL extensions and capabilities is retrieved once only, at startup, and then reused throughout mode changes. That can cause crashes as this list actually belongs to the current GL context; it's not global.

A potential crash case would be if you have a switchable graphics laptop and you're switched to the Intel GPU before the context goes down, but subsequent drawing uses an extension that the Intel doesn't have. Not certain how relevant that one is here, but it should be fixed.

A further bug is that it doesn't check extension names with a space at the end. This violates GL spec as the extensions string is specified to be space-delimited; it could falsely detect support for GL_ARB_do_something when the extension actually supported is GL_ARB_do_something_else (sidenote: Doom 3 has this bug too). I don't know of any extensions that this would trip up on though, but it is a potential crasher and correctness dictates that it should be fixed.

One other crasher that I'm aware of and that may be relevant here is that Quake Con_Printfs a "player left the map" message during shutdown if you exit while a map is running; if the context is down when this happens it can cause a crash.

The final one is during Host_ClearMemory; if you free this memory you can crash as the progs.dat code is still accessed until a disconnect fully completes. So if that's what's happening, just zero it instead (which is safe) and let the OS automatically reclaim it when the process terminates. 
@MH: Interesting ... 
See I never implemented string safety stuffs in Mark V because it would have torn a tornado-like path across the source code.

And my plan was to implement a ton of easy-to-understand upgrades like the QIP engine source code did to explain to whoever was interested how to do stuff.

[And changing all the sprintfs and strcpys would maul the source beyond recognition. Yeah techy enginey stuffs to the casuals ...]

One or more of the later part of your list could be culprits in this. 
Thanks for the bug pointers.

Regarding extensions being not per-context: see new commit:

Regarding Host_ClearMemory(): I think qs should be safe about it (same for "player left the map" like messages during shutdown), but I applied the following nonetheless: 
The extensions thing is not actually a matter of string-safety; it's a case of if you're using 'if (strstr (gl_extensions, "GL_ARB_do_domething"))' then you will also get a positive on "GL_ARB_do_domething_else". If your GL implementation supports the latter but not the former, then you've got a false positive.

There are already some extensions that follow this pattern, with GL_ARB_occlusion_query and GL_ARB_occlusion_query2 being one example that springs to mind. In practice and of this example any implementation that supports the second will always support the first anyway, but the pattern is there and it's not guaranteed that future extensions will get lucky like that.

However, since the GL_EXTENSIONS string is documented as being space-delimited (see - the page just describes GL4 where you can no longer glGetString (GL_EXTENSIONS)) the solution is simple.

Just use 'if (strstr (gl_extensions, "GL_ARB_do_domething "))' instead.

That's the bug that both Fitz and Doom 3 have. 
first, thanks for pointing out various bugs that i didn't know about :)


if (strstr (gl_extensions, "GL_ARB_do_domething "))

Won't this fail if the desired extension is the last one in the list? Or is there always a space as the last character of gl_extensions? 
Won't this fail if the desired extension is the last one in the list? Or is there always a space as the last character of gl_extensions?

I've honestly got no idea.

Reading between the lines I'd guess that this might be a reason why the new glGetStringi method was introduced (see but I really don't know.

One to check with various drivers I suppose. 
Re: Extensions Parsing 
Yeah, that would work.

I'd be more inclined to emulate the glGetStringi method by first parsing into a char** then just iterating through that, but that's academic - so long as it works it's fine.

Incidentally, just remembered to check for space-termination on the entire string, and yes - the string isn't space-terminated, so either of checking with or without a space at the end of the extension name is bugged. 
I think this engine is playing ambient sounds incorrectly.

Example: Run Contract Revoked and load the start map, and then stand in the pentagram in the middle. You can hear the sound cue from the Nightmare selection hall clearly and loudly, which is not the intended behavior at all. 
To Clarify 
The hall is right beneath the pentagram, but shouldn't be heard. It's as if Fitz Mark 5 does something to the attenuation... 
Woukdn't Be The First Port To Do That 
DirectQ changes this as well, I think, and DP even more. Sometimes you can even hear the spike shooters from logic gates if they are too close... 
I hate that DP did that, but at least it provides a console command to fix it. 
What is the reasoning in the first place?? 
in DP's case, I believe it was something along the lines of 'I like it better this way'. :\ 
Re: Sound 
Interesting ...

The sound cut-off distance was brought on par with a couple of other engines. Unaware of the above.

Back in the day, ProQuake raised the sound cut-off distance "to match DOS Quake" to keep fairness against a DOS client in multiplayer (i.e. not fair if DOS client can hear sounds a bit further away) -- although some recent discussion @ Inside3D explores this in more detail. This change found its way into DarkPlaces maybe 5 years when it was noticed DarkPlaces could hear sounds other clients could, and of course found its way into DirectQ (these aren't only clients).

Wasn't looking to alter the intended designs of any single player maps ... and I thought this change was innocent enough but seems not. 
It's easy to just cvar-ize this value (I use "snd_clipdist").

My own use of it dates back to days when it came up originally, and where (as I recall) evidence was presented that this was the original value but had been subsequently changed in a patch. Unfortunately is long dead and it's not possible to provide links, but that's where things stand so far as my recollection is concerned.

It opens an interesting question so far as the topic of "fixing up Quake" is concerned, and I believe that it's similar to the question posed by supporting fullbrights and overbrights - to what extent do you draw the line between "this is the way things are supposed to be" on one hand versus "this is the way mappers/other content creators prefer it" on the other? We're all aware that content exists where using fullbrights and overbrights causes problems with the original design (e.g. using palette entries from the fullbright range for textures which never caused problems in GLQuake), but should this be treated the same or is it something that it's better to keep away from? 
Resurrecting FOV 
I've been hacking some on the Doom 3 BFG code, and was interested to note that it uses the same method as mine for widescreen FOV: first calculate fov_y based on an ideal aspect (16:9 for D3, 4:3 for mine, although I adjust height for sb_lines too), then calculate fov_x based on the true aspect. 
It opens an interesting question so far as the topic of "fixing up Quake" is concerned

For myself, as far as sound attenuation is concerned, as long as there is a cvar to revert it to default values, then engines can default to whatever they want. Like I said, DP has that option and now I know your engines do so it's a simple matter of including them in config files that run before a mod is loaded.
It's more problematic if you aren't making a mod, but at least the option is there to fix it.

In fact, providing a cvar offers interesting new possibilities for messing with sounds such as fading them out gradually for dramatic effect. 
Next Time An Update Happens ... 
I'll just use the original sound distance if the single player scoreboard is showing (single player + coop) and if the deathmatch scoreboard is showing I'll use the other value.

Not looking at the source, I'm not 100% sure if the value is client (likely) or server (doesn't seem likely, but I'm not looking @ the source).

I don't like cvars and settings (except for features that help developers tune stuff). 
There's a bug in my map that has a unique component only in Fitzquake. The first room has a pretty large bsp model for some pesky vertex saving. It seems that only RMQ actually allows collision with the model (DP/DirectQ/Fitz don't collide with it at all so I guess this bit is definitely my fault).

However in fitzquake if you move to the far side of the room away from the model it disappears, which no other engine does:

Model rendering properly

Taking a step backward 
fyi the model entity is positioned just to the left of the healthpacks near the middle of the screen, so is definitely inside the room. 
1. ALL engines should handle external bsp collision. Unless you rotated it.

2. You can't fix this unless you can find a way to change the size of the entity's bbox to be smaller. :( 
bleh. '2' is referring to the disappearing bmodel.
This is due to the bmodel's bbox being linked to too many visiblility 'areas'. the problem is that the engine has a limited number of links to visible areas and when that list fills up, it just starts removing other links and replacing them. 
Ah, hopefully won't be a problem with a full vis then? :/ 
I noticed that dropout in the beta but didn't think anything of it specifically because lots of the bmodels in my map did that and yes it got better after fullvis. 
In my experience, it tends to get worse with a full vis, but you won't know for sure until it's done. 
BSP Models Suck 
As well as the problem with it's size (which would affect any brush model type) try this:

gl_flashblend 0
Fire a rocket at it.

Ugly, isn't it? 
Luma ? 
Does Mark V support luma on skin textures? 
Model replacement textures use the DarkPlaces external texture naming convention (so replacement textures for models go in the progs folder).

You can call them _glow or _luma (_glow is what Quake 3 uses.) 
Luma And V 
After trial and error I got _luma to work. The thing is the _luma texture need to be sized to the original model skin NOT the replacement texture. So dropping in a replacement skin pack doesn't work out. 
+1 To Future To-do List 
I can't remember all the details, but it was really hard to add external texture support for .mdl for FitzQuake while sticking by the strengths of FitzQuake.

I can't remember what texture set I used to test the feature, but I wanted to keep with FitzQuake way of doing things which in this particular case involved some contortions.

FitzQuake, unlike other engines, doesn't stretch skins to accommodate OpenGL baseline compatibility and instead pads it. This made adding external texture support for .mdl difficult while still retaining the feature (which is good and avoid stretching). As far as I know, the replacement texture and the luma/glow texture being the same size should always work, but you seem to be saying it doesn't.

I'm not sure when I'll be back to doing a revision #8 of the engine, but clearly this will be checked out , rectified and documented in the readme. 
I'd Recommend 
Checking for and using GL_ARB_texture_non_power_of_two as an optional path instead of using skin padding.

Also - and this is available in GL1.1 as well so it may appeal to you more - instead of recalculating the skin texcoords based on the padded size, just scale the texture matrix instead. You can keep the original skin texcoords and have different sized skins this way. 
The Non_power_of_two 
Extension would be extremely useful in FitzQuake, ultimately. Because the padding stuff --- and that code was ingenious --- but it really increases the overhead.

Something fun about non_power_of_two --> the texture you download is the one you uploaded ;-) so in theory, one might even be able to super-optimize the Fitz texture manager to not even need to store raw pixels source location (* I am aware of the exceptions here and there).

re: Texture matrix scaling, may I trouble you for a really simple example (which I would normally do at I3D except it is rather broken)?

I've never done anything with the texture matrix, but a simple example and I'm sure I could take it from there with ease ... 
Texture Matrix Scaling 
Something like this should work:

void GL_PadAliasSkin (aliashdr_t *hdr, gltexture_t *tex)
glMatrixMode (GL_TEXTURE);
glLoadIdentity ();
glScalef ((float) hdr->skinwidth / (float) tex->width, (float) hdr->skinheight / (float) tex->height, 1.0f);
glMatrixMode (GL_MODELVIEW);

void GL_UnpadAliasSkin (void)
glMatrixMode (GL_TEXTURE);
glLoadIdentity ();
glMatrixMode (GL_MODELVIEW);
Thanks ... 
MH adds Baker XP +1 for the Nth time, where N is getting to be a sizable number ... 
You can also translate and rotate, or even do wacky crap like load perspective onto it. Very handy stuff, and a far more elegant solution to many problems than trying to brute-force it in C code. 
Entity Lighting 
Would it be possible to have a map key to set light level on static entities? 
Static Ents 
I remember asking when working on statics in my last map
and I thought it was not possible.
So the only way out was resetting the gammalevel of their skinfiles. 
It should be possible but would need a protocol change as statics are sent from the server to the client during connection time. You'd also need to define how it works with coloured light and whether or not they should be affected by dynamic lights too. 
Basedir Option For Paths With Spaces 
I'm trying to use the -basedir command-line option and something is off. (This is on Windows 7.)

If the path doesn't have any spaces in it, all is fine. Let's say the folder containing id1 is named "foobar" at the root of the C drive:

fitzquake_mark_5.exe -basedir C:\foobar

That works. But if the folder name is "foo bar" I'm out of luck. This doesn't work:

fitzquake_mark_5.exe -basedir "C:\foo bar"

Using the "shortname" (barf) of the path-with-spaces does work:

fitzquake_mark_5.exe -basedir C:\FOOBAR~1

This isn't an emergency at all and I'm likely just making some stupid mistake, but FYI. (I ran across this while trying to write up some info on how to use different Quake engines.)

FWIW, QuakeSpasm does handle the path with spaces OK. 
Engine Update 
@Baker, Is there any plans for another update soon? 
I got your private message. I'll respond in thread @ I3D. 
Is This Some Sort Of ARG? 
Magical Mystery Tour 
I am not sure what you mean by ARG, but this is me trying to contact Baker. I am planning to tie up loose ends on the development of my MOD and I want to modify the MarkV engine so I can distribute it in my final zip file. I tried emails, private messages and finally this place, hence the weird reply.

Baker is a very tricky person to contact! :) 
Just Meant It Seemed 
A roundabout way.

Or, possibly, if we chased up the link to I3d we'd find some hidden ITS release... :) 
Maybe ... 
This MOD by SOC is not an ARG, FYI 
Moody arc figs modify cargos. Crag modify so cigars my food. 
I have a tiny issue with mark v. My soundtrack mp3 files won't play. I'm sure I have installed the files in the right place, since this is logged:

Current music track: music/track04.mp3

But I'm not hearing it. Either there's another volume adjuster I'm not finding (I tried the CD music volume slider), or perhaps this has something to do with it:

CDAudio_Init: MCI_OPEN failed (266)

I don't have a physical CD player present on this machine, perhaps some virtual ones though. Or is this codec related? 
Ignore That 
DirectQ used to work but now it's giving the same error message. Has to be something with my system. Never mind. 
Stuff ... 
@Mandel: A sincere thanks. Makes me think the world is a better place when seeing high investigations like that.

Anyways, I told Sock I'd do an update for Mark V and once is coming shortly (24 hours or less is the estimate. Maybe with something of interest to Mandel.) 
Revision 8 
1. tool_menu command. A conceptual experiment.
2. follow/chase/race your ghost player (type "ghostdemo demo1" in console to follow John Romero around e1m3). A ghost will not pass out-of-sight and will wait for you.
3. community.lmp support (sock wanted this and is a quality solution).
4. Sound limit reverted to GLQuake/WinQuake/FitzQuake 0.85 level instead of the "DOS Quake level" per comments above.


Readme: Zip:

For reference: community.lmp (This is an alternative to pop.lmp registered Quake check for a total conversion to indicate that Quake should act as if the registered version is being run). 
@Baker, thanks for the community file, it works a treat. :) There is one more thing I would love to add, the current -heapsize is crazy small, is there a way to make the default 64000 instead?

Would this cause problems with anyone else wanting a lower heapsize? 
Ok what about this idea instead :-
(taken from the source files - common.c)

The file "parms.txt" will be read out of the game directory and appended to the current command line arguments to allow different games to initialize startup parms differently. This could be used to add a "-sspeed 22050" for the high quality sound edition. Because they are added at the end, they will not override an explicit setting on the original command line.

I searched the source files and could not find this implemented but if it was, it would be perfect. I could then create a command line for my MOD. I am trying to make this as easy as possible for new people wanting to play the game and avoid modifying shortcuts.

Also I checked for the map model bug where some were black and everything looks exactly like the original Fitz. 
The default heapsize in Mark V always was 64MB or the equivalent of -heapsize 65536

Do you mean 640MB like 10 times the allocation?
If so, I can understand that because you use a ton of media.

[ #1 - YES really 640 MB -heapsize 640,000]
[ #2 - NO I meant 64 MB. -heapsize 64,000]

If #2, that's in there now. If #1, sure I can do that but I thought you meant 64MB. 
Re: Lighting 
"Also I checked for the map model bug where some were black and everything looks exactly like the original Fitz. "

Glad to hear that.

I spent several hours carefully planning the lighting optimizations back at the time and checked each step many times over, precisely to avoid that kind of issue. Although the lighting code is complex, I've always been disappointed that issue slipped through. 
@Baker, ignore my previous post, the memory is indeed set to 128Mb, I thought it was a memory problem because when I changed resolution I was getting the following error:

SetPixelFormat failed:

I assume this is the fault of my video driver because eventually I can get past this error and the engine works fine. I was trying to set video settings of 1680x1050x32

Thank you for all the help with this release. I know you have been crazy busy lately, thanks for finding the time. :) 
Re: 22050 
SetPixelFormat: Engine requests to operating system (Windows) "I want 24 bpp and stencil buffer". It wouldn't be the amount of memory allocated to Quake. Your guess about the video card is as good as my guess, seems likely.

I made community.lmp cause sound to default to 22050. ;-)

Can mp3 be used to replace .wav files in maps yet? Would love some nice HQ ambiance. 
Screensaver Issue 
Another tiny issue, not sure if it is unique to Fitzquake Mark V - I was watching a longer demo when suddenly the screensaver activated (or at least the monitors turned black). I moved the mouse to wake up the monitors (the pause demo playback feature is great btw) but when the picture came back, the gamma and contrast had reset. 
mp3 is just a compressed .wav file [more or less].

mp3 is lossy compression of a sound file like JPEG (.jpg) is lossy compression of a graphics file.

mp3 is to .wav as ...
jpg is to .tga or .bmp or raw.

Use [or another tool] to convert your mp3 to wav. 
@Mandel Re: Screensaver 
I'm not sure when the next update will be (late summer?) but I'll address that.

I hope you found PGUP/PGDN keys too when you play a demo [fast forward/rewind]. 
I think mechtech meant using mp3 files for single sounds in a map. 
@Spirit Mp3 Instead Of .wav 
What I was trying to illustrate: why?

FitzQuake doesn't support jpeg [lossy image compression]. You use tga.

Why do you need to use mp3 [lossy sound compression]? Convert the mp3 to wav.

mp3 engine code is super-ugly and you don't really want the engine to do it, you want the operating system to do it. This is more of an Inside3D discussion, but you know how H264 is often supported by hardware? You want hardware doing the mp3 decoding ideally just like you want hardware doing video decoding H264.

Short version: mp3 is messy to support and that's ok for a soundtrack, but the idea of using mp3 instead of .wav is a really bad one for some sort of the same reasons as why png is slow, pk3 is slow and video encoding is slow even with hardware support. 
I'd Like To Have... 
A compressed sound format. .wav is a huge waste of space. MP3 or ogg even flac. If I was to use say a 15 minute background loop wav is too fat.

if sound file decompression is too much overhead I get it. 
An Attempt To Descibe As Best I Can ... 
It chews up a ton of CPU (lessen some by hardware support). Quake supports at least 8 simultaneous sounds, 9 if you count sound track.

One mp3 playing via operating system API (Mark V) = no big deal.

You don't realize the unreasonableness of your idea in regards to performance.

Which is ok, I get that. A few years ago, I would have grilled engine authors with the same thing.

Your idea on the surface seems totally reasonable. mp3 = common = why not lots of them. I know the engine side and I first ran into this with PSPQuake which had both a software version (mad.cpp) and a hardware emulation option.

mp3 playback is resource intensive.

Unfortunately, I don't have an MH/Spike/LordHavoc or Divverent here to better translate this to "layman's terms" of the world of suck that goes on with mp3 decompression.

It's ok for a single "stream".

If I have done a "communication fail" here, I'm to blame. But watch Quakespasm's CPU utilization when playing MP3 or imagine why Quake 3 or DarkPlaces don't support what you propose and realize that my poor attempt to phrase the problem in an easily digestible way is a bad reflection on me but the actual problem is real. 
Are we talking about mp3 music or mp3 sound fxs?
Ogg support would be nice for ambient sound though. 
The above is a discussion about using .mp3 instead .wav files.

(ogg has all the same issues as mp3, as ogg is the lossy compression of a sound file that requires the cpu to continually decompress it adding "stress" and a potential new "lag factor" into the mix [i.e. several mp3 sounds at same time].) 
I understand now your explanation was fine. 9 decompressions happening at once=BAD Idea 
Baker thank you for your dedication to Quake 
so how do modern games do it then? D3 had it, for example, and it's not even that new anymore.

I'm not actually asking for this, but I'm not really understanding what the big deal is. I understand that it takes time to decompress the audio files, but surely it's not so bad as to impact engine performance? 
I think that goes outside the scope of this thread.

But would be good material for another thread to discuss this in further detail (Does Saurbraten do this? Did they think about doing it and rule it in or out and what reasons did they have? What does szo + co. think about this idea? As I understand it, DarkPlaces does not do this ... did LordHavoc rule this out? Did Remake Quake try to talk MH into this? Did MH reject this idea? Etc. etc.)

But these thoughts exceed the scope of FitzQuake Mark V and my knowledge almost entirely ...

[And it is so out-of-scope I'd like to not have it in the Mark V thread, since I can't even be a knowledgeable participant in the discussion ... if you see what I mean ...] 
The time you spend decoding an mp3 is time you don't spend waiting for the disk to read a much larger wav.
If you're worried about decoding time, you can always offload it to another core before initiating playback.
You really won't notice it unless its done in bulk, but that's the same as everything else done during load time.

The real problem with mp3 is that its patented and thus the only way a gpl program can legitimately decode one is to make use of an operating system feature that does the magic for you, resulting in portability issues. ogg vorbis is thus a better choice on account of third-party libraries being legal in the usa and stuff.

In fte, its 200 lines to load+decode mp3 (using the win32-os-based decoder), and 400 lines to load+decode ogg (using libvorbisfile).
Sure, the sound code needs a slight tweak too, of course, but while you're doing that you get bonus points for running the audio mixer on another thread (if your mixer is on a different thread, your on-demand decoding will be too, and yes, I got a not insignificant fps increase from that). 
16-bit Models 
So, following that quake character re-modelling thread (see General Abuse) - I learned that the QuakeForge engine supports an .mdl format that simply uses 16-bit vertex accuracy, rather than the standard 8-bit vertex accuracy.

What's more, the guy doing the new monster models is using blender, using an .mdl exporter that has the option of writing to this 16-bit .mdl format.

My question is this:

Does support for the 16-bit .mdl format sound like something that's easy enough and worthwhile enough to be worth considering? 
Please Don't ;-) 
Because then there's another incompatibility between engines. 
if it was implemented in a way so it's only used to replace existing 8-bit models, in the same way that external texture support only works by replacing existing quake textures...

No worse than external texture support then, right? 
if you want to mess with the format, i would highly advocate MD2 format because the grid's granularity is calculated per frame instead of per model. that right there would give a huge boost to fidelity. 
Or the inter-quake model format is already supported by a handful of Quake engines.

And yeah, works in exactly the same way as external texture support. 
That sounds like a good compromise. And +1 for IQM. 
I'm only suggesting this because it looks like that capnbubs guy is making some absolutely nop-notch and faithful remakes of the character models, which even an old fuddy-duddy such as myself thinks are cool.

So it got me thinking that it's a shame to have to be stuck with 8-bit vertex accuracy on those models if it's easy for capnbubs to export versions of those models in a better format...

Just tentatively dipping my toes into the water here really... 
There used to be an "extended-BSP" format which allowed you to bundle high-res textures etc with a bsp file - the extra data was zipped in a lump attached to the end of the file. Because existing quake engines were happy to ignore any junk appended to the end of a file, they would load in any engine.

You could do something similar with an extended .mdl format. It would be a bit fiddly to add the extended coordinates there. The way to do it with no duplicated data would be to split the 16 bit coordinates into a high and low byte, store the high byte in the regular mdl coordinate data and the low bit (offering the extra precision) in the extended data lump.

Care might have to be taken that this method didn't parse models which already have a lump of extra data on the end. Which models have that? Any saved by QME 3.0 - the extra data is things like skinnames and model groupw which the editor wants to preserve (3.1 has its own file format instead) 
Necros/Mechtech Re:ogg 
Spike basically said "already doing this in FTEQW, if you run sound in separate thread is not problem".

I have the next 2 versions of Mark V planned out, but don't expect to be working on those until late summer.

There is a chance that the "ogg instead of wav" could be in the 2nd future revision.

Meanwhile, in two separate projects goldenboy and Dr. Shadowborg are targeting FTEQW which does Fitz 666 protocol and bsp2. DarkPlaces does bsp2 and IQM.

There is ample opportunity to play around with those features even now in other engines. 
I just wanted to know why decompressing oggs or mp3s is such a problem for quake. 
24 hours ago I had only considered "what might go wrong" or how someone might abuse the feature (turn every .wav into an 11 MB .ogg or .mp3 and then blame the engine and demand "you must fix").

Then it occurred to me that you can make a laggy map with bad r_speeds in a map editor. I had already changed my mind prior to Spike's post, but I had the idea of pre-emptively decompressing to .wav on gamedir change.

Spike's method is far better than that.

Not the first time someone thought "this feature would be bad" and later changing mind.

I actually look forward to playing around with this. 
Mouse Acceleration? 
How to get rid of mouse acceleration completely? It's switched off in the system and I use -dinput and m_filter 0
, couldn't find anything else in readme.
But still get inaccurate mouse input like with a bit of acceleration - depending on the speed I move my mouse with, not just distance.

It is specific fitzQuake problem, I don't have this in DP or FTE or other quake games. 

or all 3.

Both WinQuake and GLQuake have this issue, FitzQuake isn't unique. And the code causing the issue you refer to is "not well liked" by hardly anyone. But it is in WinQuake/GLQuake so like +mlook, the behavior is destined to remain in this engine so that keeps with the original Quake behavior [whatever they could have been thinking ... ??? ]. 
it seems more and more that fitzquake gets called out for behaving in some ways the same as glquake.

At the time i thought it made sense because the target user is someone who is switching from glquake to fitzquake, so their configs should continue to work (i.e. i didn't change the defaults of any pre-existing cvars.)

Many years later i guess people install fitzquake before any other engine, or they are switching from more radically different engines like darkplaces, which have very different default behaviors.

So i should probably change all the default settings in the next version to "good settings." 
There are plenty of settings that should be default without having to change the config; mlook on, mouse wheel up/down changes weapon, console speed higher (terrible with large screens) and console/sbar text changes size to match screen resolution. 
@sock ... Quake.rc + Default.cfg 
There is sadly annoying stuff in default.cfg hiding in pak0.pak too:

* F11 key zoom alias that changes sensitivity and default.cfg
* Keys could be improved to default to WASD with Q and E for swim up/down
* "Reset to defaults" in the engine has unpredictable behavior because Quake didn't reset cvars, so re-running default.cfg does not fully default.
* The +/- sizeup and sizedown keys confuse if accidentally pressed and these are in default.cfg living in pak0.pak

Also the original QuakeC source didn't support both impulse 10/impulse 12 weapon switching, some single player mods like Castle of Koohoo or Duke of Ontranto (and far more) impulse 12 does not do anything.

[Avoiding mentioning too much how in original Quake (or Travail or Marcher or ...) in coop if one player grabs silver key and dies, key is gone and map is effectively broke as no further progress is possible ... relevant to exact topic ... I suppose not]. 
In coop, the keys always stay just like the weapons (but unlike them, they fire their targets correctly). 
I hope you found PGUP/PGDN keys too when you play a demo [fast forward/rewind].
No way... Nice feature :) 
+1 Awesome Feature 
@Baker, there is certainly plenty of stuff that is wrong with the defaults and it is nightmare for anyone coming back to Quake wanting to play the game. I hope you still keep tinkering with this engine, I certainly appreciate all your effort.

+1 also for PGUP/PGDN, freakin awesome feature. I can't believe it is not a standard feature for Quake engines. 
Ogg Stuff 
I converted pak0 and pak1 sounds to ogg 128bit. I ran DP 20130304. Works well IMO.

Nice converter at 
Revision 9: Automatic Gamedir Switch In Coop 
Revision 9: If you setup a coop game running, say, Marcher or Warpspasm, when a Mark V client connects it will automatically switch to the right game dir.

Mark V Server tells client: I'm running "game marcher" or "game warpspasm -quoth" or "game hipnotic -hipnotic".

Mark V Client will switch.

Non Mark V clients won't even notice the message, it is fully backwards compatible and transparent to other clients.

1. When recording a demo, it will print what gamedir is running so someone receiving your demo can figure out what mod they need installed to view it.
2. Fixed a multiplayer coop demo bug.

Special thanks to Spike for how to achieve the gamedir switching in a way that didn't require yet another protocol --- like we need more of those.

Although I didn't plan on do another Mark V update for a while, there may be one more coming in a few days. If so, this one will solely be due to some fun information from Spike. 
As I said before, please version code your zip files. 
From now on, I'll post versioned zip link to make your life easy like:

Revision 9: 
Don't Play Marcher In Coop 
the progs is horribly broken in coop :} 
Don't Do Bastion Either 
Spirit, Negke and I learnt this the hard way. 
Truth Is ... 
I've discovered a ton of maps fail the coop test.

Whether the progress stopping barrier that never raises (the fix is to make a button that can open it not accessible in the inside, obviously) ...

Or lack of ammo ...

Or insufficient # health boxes ...

[I added sv_cheats 0 to Mark V to prevent cheating in coop like god, notarget, noclip but it doesn't block "give h 999" or "give 7" or "give s 500" ... ] 
Yeah Bastion's Buggered Too 
I tried to get clever with the QC and of course didn't get round to testing properly in coop mode. 
So, Er, Hpw Do I Get The External Textures For Models Working? 
Can't get it working, and I can't find any instructions.....

Please help Baker. I need you. 
Tga Skins 
My little 82 meg experiment. Has skins working in Fitz V
Similar to Dark Places format
soldier.mdl_0.tga that kind of thing 
Big help :) 
Nice Assist Mechtech 
Yeah, Mark V uses the DarkPlaces naming convention for replacement model textures like soldier.mdl_0.tga where the texture should be in the progs folder. 
So Are They Enabled By Default? 
Does anyone have a working set for the standard Quake bad guys? Proving harder than I thought.... 
Yes Because I Don't Believe In Options/settings 
Download a DarkPlaces texture pack and look at the texture names if needed like

Naming convention is simple:

Model name: player.mdl
Replacement name: [model name.mdl] _ [skin #].tga
Result:[model = player.mdl]_[skin = 0].tga
Result: [player.mdl]_[0].tga
Result: player.mdl_0.tga 
I'm Not Interested In Bumping The Thread For This 
[But don't want to risk making Spirit upset.]

Revision 10

Incremental refinements but the source changes are large and includes a Visual Studio 2012 project file now.

Main real changes:
give ks - give yourself silver key
give kg - give yourself gold key
give q1 - give yourself rune #1 [r and s aren't avail]
give q4 - give yourself rune #4

"give" command with no parameters gives you minimal info on give command.

Reworked video mode shutdown in a way that might fix the crash one user was experiencing that I don't get [or may not]. 
Good To See 
this being worked on. Go on with the good job. Cheers. 
To Anyone Interested ... 
Within the next week, there will be another upgrade to Mark V. It won't include the mp3 request due to running out of time.

On the plus side, I think it completes the idea of getting the codebase entirely straight.

Keep in mind that the emphasis of this was to give back code clean-ups to the FitzQuake codebase to tune-up the 100 oddball bugs discovered at Inside3D without burdening, say, metlslime without having to read all that.

Exciting? Well ... that is subject to intepretation.

I do want to fix any bugs discovered, but other than that, it will be the final Mark V. 
Bsp2 Support 
It's the future!!!

By the way my faveourite thing about this engine is the demo handling. Supports multiple (most) protocols :) 
Looking Forward To It 
Well ... 
It will be a very boring release. At least from the angle of exciting and interesting features goes.

From the other possible angles like the "boring and uninteresting" releases angle, it might barely fit itself in to mildly underwhelm.

And these are the kind of expectations I hope I can almost meet.

But from the more serious side ... it will be available in many preference flavors such as .exe, .zip, .rar, .7z and the classic and irritating .dzip/.dz format.

It will be a very worthy final chapter to this engine and I have to among other things type up a credits.txt to accidentally not include in the final .dz archive.

Kidding aside, it has quite a number of things that I owe significant credits to others. For 5 days I've been tempted to release this intermittently in pieces, but no ... I want to do it all at once. 
Final Chapter?! 
... I hope you WERE kidding ;) 
I Wasn't Kidding 
This will be the final chapter of Mark V. I'm doing some final testing and want to give a day or 2.

I'm not fond of "pre-release talk" (it's hated here, which I like because I hate it too) but I wanted to see if anyone had something to say I wasn't aware of that I needed to take into consideration.

If ever the words "radical" and "conservative" fit a description, it my hope this last one achieves this. It is my desire to draw this to a close with a very wide range of conservative fixes, some of which don't seem reasonable.

Thursday release. Final answer. Unless Thursday final turning requires an expansion of the definition of "Thursday" to include Hawaii or one of Jupiter's moons to meet a slight procrastination.

[But yeah, I really love FitzQuake ... what a marvelous engine.] 
Hello Baker, 
I don't know if it is too late to submit a feature request, but if not, could you add external ent support and multiple gamedir support to Mark V? I have been using these two features extensively with darkplaces, and found them to be extremely convenient and useful. Thanks. 
Doomer, Sound Like You Want "happy Ending" 
Don't worry, maybe you don't get what you think you want, but maybe you get more than you bargained for ... and then some ... 
Thank You Baker! 
Wait with excitement. 
Is it possible to set fog parameters before the map is loaded? Then the fog parameters could be specified in the quake.rc file.

Can you add a fog distance command? Like at say 1024 units the fog does not affect surfaces? Then really tall ceilings could be black instead of the colour of the fog. Also make this a new fog command like 'fogdist' or something, don't add this feature to the existing fog command, it will cause problems with mods that use the fog command already. 
Masked Textures 
Can we get masked textures (like grates, chainlink fences) to have a value key in a similar way to how the "alpha" key works? This would be much better than having the texture start with a curly brace "{"

(which pissed off SleepwalkR to no end) 
Yikes, Talk About Last Minute Requests ... 
@sock ... I think it would need fade or something otherwise surface at 1023 looks strikingly different than surface at 1024 distance.

FitzQuake expects the fog to be in the worldspawn and resets it on level load and I think new cvars are almost always bad. Better would be backwards compatible way to allow one more fog parameter in the worldspawn keys.

I also think it would require more tuning and testing to make sure it looks rights than I can do in the next few hours, but I'll think about while I'm trying to get the engine out. The Kurok mod (also an engine modification of FitzQuake)used an alternate fog formula, but I haven't been thinking about fog much lately so ...

I'll see if I can integrate the Kurok fogging for you to look with the engine release.

@elephant ... you mean like a worldspawn key to put into bsp to indicate alpha texture prefix? The idea isn't bad, but would be better if the mapping elite got to together and planned out things like that ...

I think me just putting something in that hasn't been discussed and argued about is how "really ugly hacks" happen. 
Final Version: Beta 1 
Download | Read Me

@sock: type fogex 300 12000 50 60 76 to enable distance fog <z-near> <z-far> <red 0-100> <green> <blue> ... worldspawn key is "beta_fogex"

@Ricky ... see readme. 
Where the new FitzQuake at... metl, give me a fix! 
@Baker, I downloaded the new beta and I like noclip, notriggers :) good for testing. I LOVE the command auto-complete, my god about time! It even does map names within gamedir folders :)

What is r_stains? I saw it mentioned in the readme file but could not see any difference and the readme does not say what to do with it.

I had a play with the new fog and it feels back to front to me. I want original fog up close and then fade to specific colour at distance. Maybe I am not getting the parameters right but I tried for a while and could only get black at distance and no fog up close or white fog up close and glowing at distance.

Say for example I have fog 0.05 0.1 0.1 0.1 defined which is a nice wispy fog. On surfaces at distance (1024+) this gets brighter instead of darker regardless of light, I want to have a fog up close and then fade to nothing. I assume the distance fog would have a different colour to the foreground fog. Ultimately I want fog in a room but when looking up at a high ceiling 1024+ units it is black because there is no light, does that make sense?

One possible idea for alpha textures is to link the process to the texture. If the mapper specifies external textures and they have an alpha mask defined (tga/png format) then load and use it. This does not require fancy name changes or lots of effort by mappers just an external texture directory with alpha textures. 
Not Worldspawn 
Just have it as a brush entity key. 
External .vis support. No more vispatching maps.
what? so it just loads .vis files generated by vis.exe now? 
Alpha Mask Textures... 
Ok, let me clarify a little more.

- It would be a brush entity key.
- It would use palette number 255 (the pink one)
- It would be a normal texture. (no tga/png needed!)

Why a brush entity key? Well we have this support with alpha, why not just set the key to something like "alphamask"? You could even have it as "alphamask 1" or "alphamask (insert palette number here)" and specify which colour of the palette can be the alpha texture, this way you could still make a texture look nice in both ordinary quake engines that do not support alpha masks and ones that do!

I like shipping .bsp files only, I really hate cluttering up my quake directory for the sake of one or two maps in a .pak file or any of that kind of nonsense. My quake dir is in enough of a mess!

What do you think? 
exe. doesnt start at all for me. just getting the usual "starting quake" window, then it just flushes out, no warning nothing.
running xp sp3 on intel Chip ati video 
@mfx Hmmm. Does a previous version work ok? And flushes out = it exits or crash? I added multisample support that abuses that window, but seems your graphics card no like. I'll see what I can do to resolve that.

@necros --- no external .vis means that instead of vispatching your stock Quake maps for transparent water, you just use .vis you toss in the maps folder. I'm on a low bandwidth connection at the moment, in a few days when I'm back I'll upload something and show you what I mean.

@fifth -- You lost me. I can make a BSP with a texture named "{alphatexture" and it works. Why do you need external files? Am I missing something here? Or is something not working right about the engine and external textures? 
Shoot the wall several times in the same place.

Or use lightning gun. 
I didn't initially get that but Fribbles made a fish. 
Yeah the curly brace standard is actually one of the dumbest decisions I can think of. I'm saying the standard should be changed to a key tied to an entity brush instead.

(FYI, the curly brace conflicts with the .map standard formatting...)

Like I said, it really pissed off SleepwalkR and I can fully understand why (open up a .map file in notepad and realise why this was a terrible decision) 
previous ver. works fine.
this one it just doesnt Do anything than
just showing the starting window, no crash msg or sth. just disappearing from ram. 
no external .vis means that instead of vispatching your stock Quake maps for transparent water, you just use .vis you toss in the maps folder.

oh ok, i see what you mean about that. :)
changelog has some interesting things in it, thanks for doing this, baker. 
@fifth ... 
Why a brush entity key? Well we have this support with alpha, why not just set the key to something like "alphamask"?

I can relate to what your dislike of the curly braces.

I'm a decent Quake engine coder, but I know my place and I'm the wrong person to code anything that could be interpreted as a standard.

I named the experimental fog for Sock to look with an unlikeable name "beta_fogex" so it couldn't accidentally be interpreted as a standard, and likewise some of the experimental things I did with texture prefixes are console variables.

I'm not the right guy to make those kind of decisions. If I have any credibility with the 10-year engine devs (self-deprecating humor), it is that they know I'd wouldn't think of that doing anything like that.

Shorter version: Maybe ask people like metlslime, tyrann, preach and necros and such?

I'm just not the right guy. Seriously. 
@necros ... .vis Files 
Extract to quake/id1/maps folder

Then the original Quake maps are vispatched (unless you set "external_vis 0") to work with r_wateralpha.

It isn't that I think r_wateralpha is that great of a feature, but more that the vispatch process is extraordinarily painful since the original utilities will not work on Win64 even with DOSBox so someone looking to try that out can do it. 
@sock ... Triple Post Time ... 
If the mapper specifies external textures and they have an alpha mask defined (tga/png format) then load and use it. This does not require fancy name changes or lots of effort by mappers just an external texture directory with alpha textures.

QW and Q1DM players would be very upset because someone (a cheater) would use replacement textures with alpha to make walls "see through" that shouldn't be. 
people do that for a 17 year old game? 

{ prefix is compatibility with halflife, but also distingushes between alpha-blended alphas, and alpha-tested alphas. Which is especially useful if you have both active on an entity at once.
In the case of internal textures, palette 255 is a valid palette. While unlikely, its possible that this particular palette index could be used on other textures not intended to be transparent upon the same brush entity. Additionally the image loader will likely need to replace this palette index with an average of its still-visible neighbours in order to avoid colour leakage (yay! HALOS!), which is not something that can easily be done without walking through the ent file and checking each model in a really slow and hacky way on a per-surface basis (with multiple copies of the texture - things get even more fun if the qbsp reused the surface in two separate inline models). Which is why a flag on the entity is a stupid way to do it.

That's why we use a { prefix for alpha tested surfaces. 
but it's incompatible with the .map format because curly braces are clearly already used for a different purpose (which appears to be containing sets of information together). This makes certain map editors (namely Trench) take a huge shit when the open curly braces aren't closed properly. :P

I'll leave it up to you coder types to sort out this mess, but I wouldn't mind having alpha mask textures for some of my upcoming maps (I have some nice ideas for them that I haven't seen yet). 
It's Not Such A Huge Problem 
but it's annoying, and I wonder why you guys haven't chosen another character that doesn't have a semantics in the context of map files. 
You Can Solve The Immediate Problem ... 
In console

] r_texprefix_fence
"r_texprefix_fence" is "{"

] r_texprefix_fence "!"

Name mask textures !myfence

] r_texprefix_fence "fence_"

Name mask textures fence_1

You will be able to map with TrenchBroom and view the maps you make in Mark V with alpha masked (fence-ish) textures.

And maybe somehow this problem will come to a conclusion by time you have polished map. 
then fix Trench to parse by tokens like qbsp does, or to write texture names in quotes so that it doesn't trip over its own output.

If I read the code right, it looks like a texture name with a comma in it will break it too, with an infinite loop, but its written in c++ and the code flows all over the place, so I've no certainty over that. 
@sock Re: Super-auto-complete Of Everything 
@Baker, I downloaded the new beta and I like noclip, notriggers :) good for testing. I LOVE the command auto-complete, my god about time! It even does map names within gamedir folders :)

I had to rewrite a large chain-reaction of things to implement proper auto-completion of everything.

It wasn't fun at all, but I was getting really tired of not having autocomplete and asked myself "Ok ... you engine code right? Are you going to kill this once and for all or just keep being aggravated".

I thought since this was the last Mark V, the choice was "regrets" or "no regrets" and I didn't want to look back on it with regret.

I had a play with the new fog and it feels back to front to me. I want original fog up close and then fade to specific colour at distance.

I tested the "alternate fog" on Masque of Red Death to see how surfaces look at a very far distances and they don't fade out to full gray with the settings I suggested.

The OpenGL 1.x fog options are pretty thin. There is linear fog, and whatever GL_EXP and GL_EXP2 do (which clearly involve exponents probably using distance).

I don't know if much better fog could be done in OpenGL 1.x using glFog (I somehow doubt it) and I think it would require someone with a particle effects shader mindset --- which is something I don't have.

[I haven't forgotten about mfx. Not sure when I'll have the chance to put out beta 2). 
Re: Bsp2 
Heh - I'm definitely no engine coder, I'm totally glad you're even considering supporting it! I really like this engine a lot BTW. Massive props :) 
Couple Of Things... 
The silver key door in e1m2 was non-solid for some reason. I had the SK but didn't need it to open the door as I just passed through. The released fiend was also able to pass through the closed door.

When using the engine to play DMSP2 I've notived that some enemy become somewhat impervious to fire. One grunt took almost 120 nails to drop. 
What Map Had Issue With Dmsp2 
Will help me track down bug, I have a few suspects in mind. 
Several Maps 
Here's demo of me making no impression...

That one's on atlantis.bsp, but it's also happened on naughty2.bsp and the Travail DM maps as well. Sometimes there's no effect; sometimes one in ten or so shots hit. 
I think I need to double check changes I made when adding external .vis support. I'm able to reproduce the issue reliable. Thanks for the bug report. 
This is probably a dumb question but: what does "Automatic wide-screen FOV correction" in the readme file mean?

I thought this might be something like QuakeSpasm or Fodquake's FOV adjustment. Despite the discussion in the thread above. :-) But nope it doesn't seem to be doing that (in revision 9).

So is that readme line just talking about protecting the weapon viewmodel from FOV changes, then? Or is it something else? 
Widescreen FOV Means 
1) Adjusting the field of view calculations to be equivalent of a 4:3 aspect ratio.

The Mark V vs. Quakespasm FOV correction is the same calculation [although I don't know that the Quakespasm guys know this ;) ]

2) The viewmodel FOV "fix" is entirely separate from the above, but what it does is backs out the FOV calculation when rendering the weapon (viewmodel) so that the weapon does not get distorted if using, say, fov 110.

Note: I expect beta2 to be out later this week correcting the distrans discovery (grrr) and hopefully the issue preventing it running with mfx's video card. 
...I have a bug named after me *blushes* 
Well how 'bout them apples, yeah it really is doing the adjustment ... missed it last time I checked. 
Some Requests 
Hey Baker, not sure if you gonna work on it more, but...

Would it be possible to have support for foreign keyboard layouts?

Could you make the console fade-in faster? (maybe make it relative to vertical res)

Have the End key jump to the bottom of console log? (rather than having to hold page down for 30 secs) 
Console Fade 
is a command, "conspeed" I think it is. 
I've run out of time to do anything except light touch-ups to correct bugs and I had to cut international keyboard support from my to-do list (along with many other things, sadly).

I wanted to get one final update out and actually moved that forward rather than late summer.

My time is up, and they'll send zombies and nazis --- and maybe even nazi zombies --- after me if I don't focus on my real world objectives. Go figure. 
Regardless, thanks for the great update :) 
Windows Key Disabled? What Gives 
Is there another way of minimizing it then? 
Yes the windows key is disabled when Mark V runs.

Fullscreen, you definitely want it disabled. Windowed mode, harder to say.

For windowed mode, I made the decision like this:

1) Mappers are really smart, know how to install engines, know how to use more than one.

2) Casual players are afraid of that stuff. And are way less likely to be pressing the Windows key for functionality when running the game because they probably are just "playing the game".

So I decided to err on the side of a casual player who just wants the game to work.

An uber intelligent mapper such as yourself could use Quakespasm or DirectQ or such if you are developing a map or mod and need that.

[Although, I'm betting Quakespasm likely disables that as well ... but I know Fitz 0.85 doesn't ...] 
Can't You Just Alt-tab? 
Or Press ALT-ENTER Toggle Fullscreen 
Quakespasm also supports this.

Mark V's video code rewrite makes ALT-ENTER a very fast operation. 
Hitting Enemies 
There is something weird going on with the latest release
Fitz: 0.92 exe: 02:43:35 May 24 2013
(using version command)

After a while the enemies cannot take any more damage from the player. It is like their bounding box has moved/changed. If I quicksave and quickload the problem goes away and then gradually comes back. I have only encountered this problem with my latest map. 
Super Enemies 
I did some more investigating and it is not the bounding boxes, I can see them with the r_showbbox command. It is a time based event where enemies no longer take/receive damage. After a while I can just walk through them. I can't produce a save file to show what is happening because quick save/load fixes the problem (temporarily) 
Can you capture it in a demo? 
are they still damageable (blood particles vs grey puffs)?

can you get the edict # and check what the fields look like? (maybe make a tiny hack mod where the axe does an eprint of whatever it hits) 
Use Quakespasm Or Previous Mark V 
I have no time and sadly will have no time for amount of time that I can't determine right now.

I have about 15 minutes of "real" free-time and this isn't going to be changing soon.

I'm sorry about the bug --- real-life prevents me from having any meaningful amount of time to address this and I will continue to have no time for the future as far as I can see it --- and this is beyond my control.

Someday, I will fix --- I was trying to "go out in style with a delicious technical masterpiece" that could be feature ripped into Quakespasm easily --- I went all out, I thought I was practicing some awesome quality control and this slipped by me --- but I locked-in, I have no time and I'm not going to have any time.

And I'm sorry. I really was shooting for the moon to please to go out with a really fun bang with some incredible engine performance and flexibility.

Now I am beyond the event horizon, all paths available to me lead only towards real-life and I am far beyond the point of return to be able to work on this.

Believe me, I wasn't looking to let anyone down --- but I am no longer able to do anything about this.


The Sadly Uber-Time-Restricted-Baker

i mean seriously... 
Barking At The Moon Again ;-) 
Feature Request 
Something to add to a wish list ...

* Be able to freeze a demo and then fly around the world to inspect / look at things. It would be very helpful for debug reasons to see what is happening with a demo. I don't mean change or move stuff around, just fly around and see where things (monsters/items) are. 
From what I know (unless I mix up things) Quake demos only include the entities in the PVS so a feature like that would require a whole different protocol. 
As the demo progresses the engine is updating entities with new locations, states (moving, alive, dead etc) and when the map is frozen I just want to fly around and see where all the entities are and what state they are in. Even the current PVS would be better than nothing. 
Qrack does this today and is the only engine I know of that allows this. I don't have any experience personally using the feature recently, I'm just pointing you to what can satisfy this desire today.

[I still have no time to work on Mark V and don't see this changing in the known future ... but I still care ... ] 
Daz's recent CG video revealed another Mark5 bug: playing back a demo of sock's map, many models were displayed pitch black, sometimes flashing depending on the view angle. I haven't tested it, but I could imagine the clipping and lighting issue also ccurs on other over-limit maps. 
Hey no worries on your time, I just wanted to post here some ideas if you come back to MarkV development in the future. 
quakeworld servers can record Multi-View Demos that support that (cl_demospeed 0 to freeze them or whatever it is, attack to toggle free-cam, jump to switch players).
With FTE, you can start a map and issue the 'easyrecord' command and it'll just start recording some randomly named mvd demo.
(sv_voip_record and it'll also include any voice chat too, for extra playback privacy invasions *cough*). 
Feature Request 
Something to add to a wish list ...

* Excluding entities from being recorded in a demo. For example detecting a new key on an entity "nodemo" "1".
* Excluding entities from casting shadows (r_shadows). For example detecting a new key on an entity "noshadow" "1"
* R_shadows always casts shadows from 360 angle, being able to change this via worldspawn. For example a new key "r_shadowangle" "90" 
Feature Request 
More stuff ...

* Adding external texture support for model skins (24bit TGA) with use of the alpha channel so that the skin can faded gradually. The external skin could be specified with an extra key on the entity. Like for example "ext_skin" "textures/hiknight1.tga" 
Small Note Regarding Alpha: 
Drawing alpha-blended models correctly requires sorting every alpha object (if convex) or triangle (of a concave object) in the scene and drawing them back to front. I don't know of any engine that does this (perhaps darkplaces.) But fitzquake certainly doesn't.

People probably haven't complained about the cheap method used in fitzquake and other engines, probably because most mappers use the feature sparingly, and only on simple convex brush-models, and not on many models in the same scene so that you see them overlapping incorrectly.

I only mention this because as a perfectionist like me, you will probably notice this problem once you start relying heavily on the feature, on many objects in the same scene, and on objects with convex, organic shapes.

The safest way to use alpha given this, is to only put it on convex shapes and make it hard for the player to have a line of sight that passes through multiple layers of alpha objects. 
Ah Yes 
I remember now...last time I checked darkplaces doesn't handle this within a model - if you have multiple layers of fur in the model you do get graphical glitches occur where they overlap. 
even if you do depth-sort, large objects can still cut through and overlap in screenspace even if the actual brushes don't (or for instance a transparent player standing waist-high in water).
mostly a .alpha set to 0.99 will result in the entity using the alpha channel of 32bit replacement textures (blended).

ext_skin with nice long strings would be far too painful. just use .skin if you really need that sort of thing (in combination with shaders as needed). 
Engine Question 
Would a QC controllable sound mixer be a good feature? Adding reverd echo and other dsp stuff. I remember good ol duke3d had a few option with sector effectors. Setting an effect to match a rooms size would be cool. 
don't care too much about that, although it would be interesting to use every once in a while.

what I want is moving sound sources and doppler effect! 
also, while i'm dreaming, sound that travels through leafs/portals would be totally bad ass with volume attenuated by distance traveled instead of just radius. 
halflife had various triggers that can apply various eax environment settings.
the forwards-thinking audio api to use is presumably openal, which would give environmental effects as well as doppler effects.
but hey, if you want to write your own reverb library and plug it in to a quake engine, be my guest. :P
incidentilly, a couple of engines already have rate modifiers, just not editably so... doppler would theoretically be easy enough to add, but as quake traditionally never moved sounds (and with invisible entities generating sounds and thus there not always being velocity information) I'm not sure how much it would break. 
Sizedown In DirectQ Engine 
Greetings everybody,

a few hours ago I decided to install DirectQ engine for Quake 1 and find it to be brilliant.

The only (MAJOR) problem with it so far is the fact that "sizedown" command won't work.
It's properly binded to "-" but it has no effect.
Writing the command in console does nothing too.

"Sizeup" works just fine.

I run a 1920*1200 resolution on a 24 inches monitor and the fact that I can't "sizedown" the window makes the engine a bit...useless in the end.

Can anyone please aid me on this ?

Thank you in advance for your help. 
What does sizedown do? 
viewsize cvar. set it to 30 for a tiny view (not always supported nowadays), 100 for default sbar+ibar, 110 for sbar-only, and 120 for not even an sbar.
note that not all engines support a value less than 100. I've no idea what directq is meant to support, but if in doubt specify the viewsize cvar value directly and see what you get. 
Outside Chance ... 
That in the next 3 weeks I'll release a fix-up Mark V final release. I only have effectively one day off a week and not much free time in that one day off, really --- but I worked on Mark V in a 115 different mini-revisions and I know the first one of these with "the issue".

The bad news is I so radically changed the code base that even one "mini-revision" is a heap of changes.

But the good news is that if I spend 30 minutes a day for a week or 2, I should be able to repair it.

If I'm not way too tired to do so each day ... 
Best Way To Get Something Done to give it to someone who's busy...

<mumble> bsp2 </mumble> 
I don't have answers, I only have questions. Sometimes I think that Metslime, MH, Spike, the Quakespasm guys (szo, stevenaus, SleepWalker ... in no particular order) and myself should team up to make "The Answer To Everything Classic Quake Engine 42 = 6 x 7" engine.

Which is a pipe dream --- except I don't actually believe that. Such a thing almost seems like it was always meant to happen ... like it was part of the Universe's master plan and maybe the only the reason the Universe was made from this incredibly narrow and very Quake-centric point of view ...


[End Stereotypical Baker post ;-) Hey I gotta be me ... ] 
Diversity Is Good, A Little Competition Is Good 
We'll See ... 
Lately I've been spending most spare moments of thought on how to get an update out with virtually no "true" free time.

I'm rather determined to get an update out --- I'm just trying to figure out "the how".

Some of the great stuff in "Final Mark V" is irresistibly fun --- and I'm still quite irritated about the collision bug.

I hope you are doing well, SleepWalkR. Admittedly, my finite time I haven't had much time to read up on your massive contribution to Quake mapping in TrenchBroom. :( 
Fixed Version 
Read me:


Weight: 448k (the engine)
Speed: Yes
Features: Some
Code: Better
Map Editor Used: Notepad.exe
Is Bug Free: Should be (cross fingers)
QuakeC Version: Depends on gamedir

Recap of features: Faster, auto-completes about everything including key names, brightness only affects window, skill level recorded in demo, optional multisample capability. Borrowed some of Quakespasm's finesse and tried to largely sync with entirety of Quakespasm's codebase. See read me. External .vis support.

Short version: Light, fast, quick, better.

You won't likely notice any of the changes because they were implemented very softly and subtly, in FitzQuake style.

Last version of Mark V. 
Doesn't Work 
on my surface pro...

Seriously I have no idea what's up with this thing. It only runs DirectQ. 
fifth? what's the problem? spazzes out spining wildly?
that happens when the operating system ignores calls to set the mouse cursor position.
you can avoid such calls with a the -dinput argument to most engines (often alternatively settable with in_dinput 1;in_restart).
If your engine supports rawinput, that can also be used instead, fixing the issue in the same way.
In FTE, _windowed_mouse 0 will enable the touchscreen mode that I hacked together for android - other engines that retain that cvar will simply disable the mouse entirely instead.

DirectQ presumably uses dinput by default, hence why its the one that works out of the box - pretty much every other engine can use dinput too, they just don't by default. 
Some Good Advice There Spike 
but it fails to load, just crashes when you click on it. And windows 8 doesn't give any explanation to why it wont load.

I reckon it's probably driver related to be honest. As per usual. 
I don't claim to have any working knowledge of a Surface Pro, but you could type "nomouse 1" in the console or add that to your config.

On an iPad, I know how it would interpret mouse events and if I had any free time would consider an enhanced merge of FitzQuake Mark V + Quakespasm + iPhone Quake and peek at FTEQW's Android stuff.

I really was trying to complete merge Quakespasm and Mark V back in the spring -- but ran out of time before I could get it ready for a Mac OS X build. :(

/End Dreams ... 
On The Plus Side ... 
I was glad I was able to use a sizable chunk of the ideas that Spike and MH suggested to streamline the code. And something invaluable that Reckless provided.

Spike supplied a treasure trove of great info --- and many of these things are implemented like skill level and gamedir is recorded to demo (as one example) --- but he gave me tips on how to do some really awesome stuff.

Alas. I ran out of time. 
fitzquake 085
heapsize 512000
game quoth
map dis_sp6
die alot

fitzquake mark5 final
heapsize 512000
game quoth
map dis_sp6
hunc alloc failure 
Gosh Darn It 
I had the idea of disappearing forever with the earlier post being the last trace of "Baker" ever on any noticeable forum.

And distrans, you ruined it all!

Thanks for the bug report, I suppose I have only myself to blame.

/Will investigate, solve and all that. Rats!@!@!@ 
Better Than Ragequitting 
I suppose... 
Not As Good As This 
Haha, Awesome 
Yes - thats a classic. But a womyn !?

.. So all we have to do to keep this project ticking is find bug reports for Baker :) 
LOL @ Blitz 
Lest we forget...he took a lot of risks to become part of an industry he loved. 
Hey Baker... 
...some would say that's not a bug i.e. more favourable than actually playing dis_sp6 :) 
Copy Pasta From TB Thread 
"Got it to work (dunno how long for), using driver version from 05/12/2012.

This was from going to settings and "refreshing" the system, not a complete reformat.

There's definitely some driver issues with the surface pro. "

Again, this does work on certain driver versions. 
Distrans Bug Fixed 


ragequitting + jokes

Well, I never thought of it like that. I'm just tired and worn out and at times I wonder if I have anything positive to contribute or have been some sort of Quake villain -- which was never my intent.

SA: So all we have to do to keep this project ticking is find bug reports for Baker :)

Haha, maybe first good laugh I've had in a while.

Either way, I guess I'll keep the door ajar a bit ... 
Ta Baker 
I'll d/l tomorrow and let you know about the next one :) 
I Really Wish 
the MarkV engine would support 'sv_freezeonclients' from the DarkPlaces engine. It is perfect for taking screenshots and checking out what AI are doing without affecting the player or console speed. 
and checking out what AI are doing

it would've been a total cheating? 
By That Logic ... 
it would've been a total cheating?
you should also ban god, notarget, noclip and impulse commmands! ;) 
No They're Classic Commands 
krimzon_sv_parseclientcommand can be used to block them if you really want that. they're already blocked in deathmatch. 
"freezeall" command is what you seek.

I made it a command rather than a cvar for some technical reasons that are rather tedious to explain.

freezeall is a toggle and is supported in Mark V in the server too as a recognized command. 
"sv_cheats 0" will stop god, noclip, freezeall, fly in Mark V.

A Mark V server will also tell Mark V clients what gamedir is running and automatically switch them.

For instance, if the Mark V server is running "-game warp -quoth" it will instruct Mark V clients to do the same upon connecting.

[Which is a Spikeism ... thanks Spike!] 
Any Chance 
Of supporting bsp2? 
@ijed, Why Do People Like This Engine? 
Mark V has almost no features that anyone ever asked for. Ever.

And yet people like the hell out of it?

I guess what I saying here, why should anyone use this over Quakespasm, Fitz 0.85 or DarkPlaces?

Yet, serious single player or coop people love this engine.

Despite the fact it doesn't implement ANY features that anyone ever actually wanted or asked for?

I implemented stuff that I thought the average player would really like to make things fun, user-friendly and easy.

I guess I'm saying, bsp2 is just going to ruin single player entirely. You probably can't even properly coop any of those maps.

Is the master plan here to create impossibly large levels that can never be cooped and bust all sanity in even things like recording demos?

Of what use are maps that cannot be cooped in the bigger picture?

I personally don't see super-giant for the sake of super-giant as a positive direction --- many Fitz 666 maps are only barely coopable over LAN.

What makes Quake isn't multiplayer --- QuakeLive or other things can do that --- and it isn't literal single player because you can find this in other games.

But coop is where Quake reigns supreme -- how does BSP2 further this great strength of Quake? Or are we just breaking engine limits these days without considering the consequences of where the path is leading?

Let's just break every limit --- creating a cascade that challenges rendering and the network protocols and even advanced predictive protocols is just "wrong" to me.

If you think about it, almost everything in Mark V has been done to support coop and demo sharing. BSP2 teaches map authors to not really consider map design constraints for maximum "utility" and just be lazy. There are many incredibly big protocol 15 maps --- Fitz 666 raises that to beyond absurdity --- and now lazy map design isn't satisfied by that?

Sheesh --- some of the Travail levels --- like the one with the lift that teleported --- worked around that. Just as a base example.

The short version: bsp2 end result maps aren't usually coopable --- coop is a design strength of Quake --- perhaps maps that don't fit in the design strengths of Quake should only be playable by outside the mainstream engines.

/Good judgment almost kept my from clicking submit --- then again, I don't have much of that. Submit it is! 
What about sex before marriage? 
Baker, If you're actually serious about coop, you'd go implement support for RFC 5245 somehow. :P

Also, its probably worth rewriting the network protocol anyway, *especially* for coop. Coop can easily get more spammy than deathmatch. 
Bug Again

It's on an ATI 3670 with 11.12 drivers. 
Coop Is The Only Reason To Play Quake? 
And big maps are lazily made?

Each to their own then.

I get the point of wanting a simple engine though. 
Quake Does Not Equal Coop 
I've played coop quake maybe once or twice in my entire life.

I thought the whole point of these huge super giant bsp2 maps was to make an epic singleplayer romp? And these super maps are very few and far between.

I really don't see the reason for this rant, most people like Fitz for its stability, simplicity and faithfulness as a quake engine.
I personally prefer DirectQ because it is slightly more feature-rich, but it's mostly unsupported these days. 
I take exception to the comment about lazy maps too.

The features I like about FitzV:

Runs fast
Supports loads of demos
Cool demo features
Perspective correction on weapon models in widescreen

Though I would like it if I could play my big map on your engine. As we move forwards in time, some people are going to want to make huge maps. TBH it's been a fantasy of mine since I started mapping, the only reason for not doing it was the engine limits.

9 out of 10 people have hardware that can run huge maps. r_speeds is not really an issue any more (though I still full-vis my maps).

I mean it would be nice if there was an active Fitz branch engine that supported BSP2. Tyrann's new compiler is quite possibly the best qbsp compiler we have ever had, AguirReMHLight is IMO the best light tool. Everything is in place, we even have engines, but it would be nice if an active (and very cool) engine supported everything. Then I would ONLY use FitzV for EVERYTHING. And more than likely, the majority of other folks would too...

Supported Coop but my new one won't at all. In theory I could try and include it, but there's a tonne of dependencies in the AI and core game mechanics that mean it wouldn't make sense to try it coop unless I completely changed the game mode...

Which could be valid I suppose, will give it some thought.

It's also a very big map. 
"freezeall" command is what you seek.
Wow thank you, the command is perfect! :D

Mark V has almost no features that anyone ever asked for. Ever. And yet people like the hell out of it?
I like this engine because it is simple and not over the top. There are no fancy extra graphical features or SP fixes, it just works, really well.

+1 for wanting bsp2 support, it would be nice to play future large maps with my favourite engine. 
Lets Make Things More Interesting... 
one quick hack later: voila, markv with bsp2 support:
Completely unsupported, use at own risk, etc.

Baker, be sure to read the readme in there. I mean it. Really. 
Will test later..... 
I'm laid up for a week with sciatica and won't be near a PC :[ 

[I owe Spike so many thanks at this point, I think he flipped the universe's digit counter with that one.]


I'm not reading your replies right now.

Here is why --- and perhaps I can make Barnak really happy here ---

All of the spare time I don't have --- 100% of it --- I am building Fruitz of Dojo native OS X Mark V with 100% feature set (well maybe 99% --- Mark V AVI capture on OS X isn't something I can add conveniently).

[Will still have a very Quakespasmy codebase.] 
Thanks Spike!

Got the level plugged in and running now. There's a couple of graphics glitches - the standard id sky doesn't render properly and the HUD sometimes gets stuck on white, but a lot of the other stuff that I was missing like coloured light and fullbrights is now working properly. 
sky+hud bugs don't relate to the code changes I made. Could be down to compiler differences or due to simply being based off an old version (baker still hasn't released the source to match his latest exe).
Coloured lights and fullbrights are not my work either. 
Fair Enough 
I'm building with Tyrann's latest tools, though I doubt they're the cause in this instance. 
I Meant C Compiler. 
Looks Like 
I'm provoking the white HUD with bad qc. 
quake one is the best game in all time 
Gray Borders 
There are thin (1-2 pixels wide) gray borders along the right and bottom edge of the screen in Fitz MkV, at any resolution. Any way to remove them? Graphics are Intel HD Graphics 2000. Also, is it normal that dynamic lights break through walls?á 
Dynamic lights break through walls because because computing occlusion dynamically was too big an issue in 1996 (english: shadows are expensive). Nowadays we use shadowmaps or shadow volumes for that stuff. So you can use something like Darkplaces or FTE if you want those kind of features. 
And about the gray lines? A graphics driver issue perhaps? 
I have no idea, that one sounds more like some engine or driver edge case. You'll have to ask someone qualified. I've read that Intel's openGL drivers can be a bit buggy tho. 
I Can Confirm This... 
I have the 4000 version in my surface and I am constantly having to dick around with different drivers.

I haven't had a lot of problems since I updated from windows 8 to 8.1 though. 
Been away from the internet for 3 months and just now trying the newest Mark 5 from post 314. I got the same hud bug posted by Yhe1 (post327). Next day I used Metl's original 0.85 to check an Unforgiven map for something. Then later, went back to Mark 5 for some other testing. Hud is now fine... hehe.

Is it something to do with the config.cfg? Everytime I'm switching engines I sometimes need to delete the config.cfg from the Id1 and Quoth folder to clear up some issues with various info_command and trigger_command entities.

Engine is really fast now with lots of my alpha_masked trees, leaves, bushes, ferns etc (as .bsp mapobjects). It's like Pyramid of the Magician.

Dynamic lights usually pass through func_wall and door entities but world brushes do block them. I checked at some examples while in Mark 5 and it was working correctly. 
One Last Thing - Weapons Moving Up/Down 
Only one more thing - is there a way to prevent weapon moving up/down while looking up/down, like it's implemented in QuakeSpasm? Double-Barreled Shotgun completely disappears when you look straight down. 
White Hud Bug 
Hi all. I've tried this little nice engine for a minute. Looks like this type of bug:

happens when your gamma cvar is set to ANYTHING but 1 IF your scr_sbaralpha cvar is set to 1 (scr_sbaralpha 0.9 or 0 will fix the problem). 
Trying To Play With Fitz Features. 
And I have found a bunch of stuff that I cannot get to work,

texture pointer, ghostdemo, r_mirroralpha... it's weird because things like gl_greyscale and r_stains work.

Also, no m_filter??? 
And How 
do I get external textures working for models and such? It says the engine supports it but what are the files that it supports? What are the naming conventions? What directory do they need to be in? 
External Textures For Models 
if it follows the standard method, then external model textures go into /progs/
the filename should be [modelFileName].mdl_[skinNum] 
Figured It Out... 
Save the files as .tga files using your naming convention you just mentioned.

The files I had were as .png files. 
Some Ramblings 
On some monitor resolutions I've noticed the gun stock shrink more than others, but it never disappears. Could be a res bug.
Its a good feature for changing gun perspective looking down from roof tops.

other stuff...

tool_texturepointer 1 - does work for me

r_mirroralpha - does not look like it is

The Mark5 from post #61 loads .bsp mapobjects correctly on start-up. The final version though, needs a map restart (just once) so that alpha masked textures are rendered right.

Most everything else is good though. 
Just move to Linux and give Baker some peace :) 
Unknown command "max_edicts"

Why the fuck would anyone do this? I can't finish ne_ruins because it keeps running out of edicts. 
The command has changed, use:

the default is 0 which is automatic (GL default 1024) 
Mouselook Wont Work 
how do I fix this? 
I'm So Stupid... 
I set lookstrafe on by accident. fixed it now. 
On My Withlist... 
... for the next FQ release would be two things involving music support:

1) MP3 playback from within PAK files (like in Quakespasm).
2) Ability to use custom music packs without having to copy them into mod subdir (by supporting at least 2 gamedirs, e.g. -game epiquake -game rubicon2 to play Rubicon 2 with Epiquake pack). As far as I can see from the readme, something like this might be planned already, so I hope this is going to happen. ^^

Other than that, this beats pretty much any port out there which attempts maintaining the "classic" visuals. Darkplaces & Co. might offer eye-candy, but FQ Mk V delivers what I prefer: Quake the way it's supposed to look with a few visual touches here and there. Two thumbs up for keeping this alive, and looking forward to more updates in 2014! 
Totally digging this (late for the party, I know), but yeah -- I'm getting the whited-out HUD thing, too. Any sort of workaround or anything? 
White Hud 
does post #350 help? 
It did. Thanks ;D 
FMV Is Indeed A Very Good Engine 
Especially if you are not into all those HD eyecandy and prefer a more-faithful-to-vanilla approach. 
why does fitzquake mark 5 care what its own filename is?

fitzquake_mark_v_final.exe - no hunk alloc failure

copy fitzquake_mark_v_final.exe, rename to fitzquake_mark_5.exe - hunk alloc failure

copy fitzquake_mark_v_final.exe, rename to blitzisawomyn.exe - hunk alloc failure

delete fitzquake_mark_v_final.exe, rename blitzisawomyn.exe to fitzquake_mark_v_final.exe - no hunk alloc failure

I have it named as fitzquake5.exe and it runs fine. 
Lun did you maybe create a profile for fitzquake_mark_v_final.exe in your driver settings? 
Just unzipped it.

I'll have to assemble a test case for Baker if he still checks the thread. There is something final about the word 'final' though. 
Shrak Freezes 
Can anybody else confirm that the "Shrak" TC (v2.0) freezes with FQ Mk V randomly? Unfortunately I don't even get any error message, so I cannot give any details about what might be the problem... 
Shrak not loading is a benefit. 
Check Yourself Before You Shrak Yourself 
wasn't that one of those eye-gougingly bad "unofficial!!!" commercial shovelware mods from 1997? 
Commercial Addons 
It was, but there were worse ones, e.g. "Aftershock", "Q!Zone" or "Dark Hour". Anyway, most of the time I can bypass these crashes by not attacking enemies, which kinda sucks. Especially the shotgun seems to cause trouble. On the other hand, "Malice" works without any problems - almost. In "Staying Alive", killing Vasquez and her helpers more than once (after they respawn) would result in a crash, too. But that's rather minor. I am just wondering if it's a problem with the addon or possibly FQ. Good news is that pretty much all the other good (custom) addons out there are working, e.g. Prodigy, Zerst÷rer or Travail. Maybe "Shrak" is just unworthy of running with this polished port? :D 
1. @Lunaran

I can't imagine how the executable name could make a difference. Maybe if you have an insanely long path that is 240+ characters long?

@ Spike re: source code

I just changed the optimization to /O1, I didn't actually change any source code -- the source code is current. I mention this in the readme, although yeah I didn't re-upload the VC6 project with an updated .dsp reflecting the /O1 instead of /O2

@ onetruepurple "Unknown command "max_edicts"

I renamed it because I changed the default value to 0 and FitzQuake 0.85 saved it config. 0 is automatic size. ne_ruins is the only map I know of that breaks automatic sizing (because it counts the edicts in the .bsp on map load and adds a ton of padding, but ne_ruins manages to bust this).

@1path0gen1 "White HUD bug"

That's disappointing, at least in your post #350 you figured out a workaround. Never experienced that problem myself. :(

@NightFright re: Shrak

I'm glad you like the engine, but since I don't warez I'll never play Shrak. But everyone has always said Shrak is crap, so ...

@roblot re: r_mirroralpha

It is broke. I wanted to finish the implementation, but ran out of time. The issue has to do with FitzQuake drawing the sky in an unusual way. Somewhere I had pages of notes on how to do r_mirroralpha really, really right. And "security cameras" too like Duke Nukem. And had ideas of teleporters that showed the destination point-of-view. But ran out-of-time and I can't imagine ever having the time to do this now.

@FifthElephant re:ghostdemo

I removed it.

@FifthElephant re:m_filter

I simplified the mouse code beyond imagination. The mouse code in Mark V is hilariously short and amazingly precise. Like a work of art. m_filter just averaged movement. Maybe in days where someone got 22 frames per second this might be helpful. Anyways, I removed plenty of hardly ever used cvars like modem and serial port stuff and the 80 weird mouse settings. I think I removed joystick support too (or maybe I didn't).

@ NightFright "Next release"

I don't know if one will ever happen. Then again life is unpredictable.

@ NightFright "Double gamedir support"

Typing "game masque -hipnotic" works. Substitute -quoth or -rogue. I should have made "-anything" work ... but I decided not to for reasons I can't remember.

On the plus side, Mark V does pack hints in a demo so it knows what gamedir options were set and playing the demo will automatic switch to the correct gamedir. It also knows what skill level was set. 
"But Ran Out-of-time And I Can't Imagine Ever Having The Time To Do T" 
Did you get a kid or something? 
the progs in ne_ruins spawns several hundreds of new entities as part of the pathing system. It's too bad you changed the variable name as there is a line in one of the config files in the mod that sets max_edicts "8192" to prevent any problems when running in fitzquake variants. 
clearly should have been left in.

Also, I noticed there is a variable to set mirrored surfaces (different to r_mirror I think)... I thought maybe you had changed it.

It's a shame you stopped working on it. The different features in each engine is why the community is divided (and why people are still using widely hated engines like RMQ).
I just thought it would be nice to put mirrors and alpha fences (actually I was working on a haunted house style map that had neato spiderwebs and stuff using a combo of masked and alpha'd textures, but the implementation made it a son of a bitch to finish) 
I'm finding this late, but I love this!
This is very close to my ideal Quake client.

I just started trying to set up Quake after some years of not really messing with it, and wanted to use Fitzquake, but of course no NAT fix in 085, so that didn't work for running a server over my wifi router for an internet friend to connect to... Then I stumble onto THIS post with a NAT fixed Fitzquake plus lots of other fixes. Nice! Thanks Baker.

But when I play with a new toy, I really pound the heck out of it (ok, that sounded bad :P ), so I'm finding bugs... which I will report in hopes of them being fixed some day, if Baker ever works on this again.

Bug(?) List:

"Kind of" NAT Fixed?
FitzquakeV connects to Proquake Server fine.
But I Can't get anything to connect to a Fitzquake server running either protocol 15 or 666.

Skin Crash!
Assigning a skin to a projectile crashes the client if the skin # is invalid (if the player doesn't have the model with multiple skins). Standard behavior is to either show the default skin or a skinless model. FitzQuake085 did not have this problem.... I know-- I shouldn't assign an invalid skin, but if the server is running a mod that uses more skins on the projectiles (like a laser model with more colors), a client can still play on the server without having the custom model with extra skins -- he just won't see the extra skins. Well, that's how it should work.... FitzquakeV crashes.

"Always Run" = Bad.
This is not a good setting to default ON. It's weird. It doesn't actually do what you'd think (make it like you're holding down the +speed run button) -- it just messes with your normal "walking" forward and back speed, but not your sidestepping speed, exactly. So you end up being able to run forward fast, BUT when doing so you sidestep slowly... EVEN AFTER you press the run button or use +speed in the console. Always Run must be switched off to get proper sidestep speed when running, even when using the +speed option (unless you make other settings, I guess?). Please default it back to off. A better fix would be to change the "Always Run" menu option to actually lock +speed on instead of whatever weird thing it currently does.

An Easy One:
progs/bolt.mdl should be in the r_noshadow_list

What Am I Chasing?
With chase_active 1 and your back against a wall, toggling chase_mode off and on will cause the camera to jump up to the ceiling and stick there.

I wish fog settings would save across maps... and I kinda wish I could set a skybox permanently on for every map too.

Oh, I can't seem to get replacement sprite textures to work. Replacement textures for models seem fine, but like, I can't get progss_bubble.spr_0.tga to appear in the game. Placing it in a "textures" folder doesn't help either.

And finally, I feel like the blends (especially the ring blend) are way too... slight. I can barely tell it's happening with the ringblend. Though in Fitzquake085 I thought the blends were way overdone. There must be a happy middle.

And finally finally, gl_overbright_models seems overdone; when a player (especially wearing white colors) is standing in a bright area he's practically glowing and really washed-out. Not a pretty effect (run around with chase_active 1 and color 0 to see). Maybe there's a way to set a max brightness value to not exceed? I like the way it looks in dark areas though....

Well, hopefully more work will be done on Fitzquake at some point int he future. Thanks for what you've done so far, Baker! 
Ok, the more I mess with Mark V, the more I love it. This is now definitely my favorite Quake client ever. Small, FAST, and not crammed full of altered default settings and eyecandy that changes the way Quake does things, but with extra features to play with and tweak as you want, plus all the little enhancements that SHOULD be default, like correct interpolation and bug fixes.

Continued report of issues in hopes they may be fixed sometime in the future.

Legitimate Bugs:

MP3 soundtrack doesn't play IF you don't have a CD drive! On my netbook, I noticed at startup it would give the error "cdaudio_init: mci_open failed (266)" so I wondered if my lack of a CD drive was disabling the MP3 music too, so I tried running it on my older laptop with a built-in DVD drive and the MP3 tracks worked perfectly. So then I plugged my external USB DVD drive into my netbook and tested again... and heard no MP3 music... UNTIL I adjusted the volume slider for CD music (it wasn't too low, it's just that the music is silent until you change the volume in any direction). I also found that ALT-TABing away from the window and coming back will cause the MP3 tracks to kick in (they are playing from the start -- just silently). As a workaround, I found I can get the MP3 tracks playing correctly from the start (ONLY if I have my DVD drive attached) by including in the autoexec.cfg "bgmvolume 0; wait; bgmvolume 1"

If you try to load a skybox made of JPG files, it will CRASH because they aren't TGAs. That's kind of bad behavior.

Centerprint messages seem to be cut off at 19 lines. In Qrack and other clients you can see more than that (I tried the old arcade mods Paqman and Tetris which use a few more than 19 lines of centerprint to draw the games). Also, it would be nice if the centerprint didn't necessarily appear right in the center of the screen. If there's room near the top, let it appear up there so it doesn't block the view so much. Is there a variable to adjust where it appears?

r_skyalpha doesn't seem to work for me. It just makes the sky look... weird and inverted or something.

Multiple gamedirs... how does this work? I can't get it to work. I thought since I can't toggle Colored Lights off (mentioned below), I'd just place the LIT files in a separate gamedir and then when I wanted to use them I could do something like "-game fvf -game lights," or from the console "game fvf lights" but it doesn't seem to work.

"Kind-Of" Bugs:

All the old methods of stopping Demos from playing at start up no longer work (-map none, for example). This is probably a result of fixing bugs where Quake would just stop if it got an invalid command like that, heh. But now I can't do anything to stop the demos from playing at start!

Not Exactly Bugs (but things that should be included for the added features):

Colored lights can hypnotize. Sparkle someone else's eyes. But there's no way to toggle them off & on like for textures or skyboxes.

When you do "game fvf" from the console, it should exec the autoexec.cfg file located in the new game directory.

I wanted a button to cycle fog off and on, but the "cycle" command doesn't work with "fog" (i.e, bind F4 "cycle fog 0 0.03" would be handy). "variable fog not found."

I would also like a button to turn off skyboxes, but you can't bind a key to "sky "" " because of the quotes needed in that command. It would be great if there was a bindable command to disable skyboxes, like, "sky default" or "sky 0" or something. (Workaround: make skyoff.cfg which contains the command 'sky "" ' and bind a key to "exec skyoff.cfg".)

Also, it would be great to support something like Qrack's skybox.cfg file where you can specify a skybox to load for each level automatically. Failing that, what about just having a certain skybox load instead of Quake's default sky based on the skybox name (kind of like a replacement texture). There are only like 2 skys in Quake, aren't there? Purple and blue.... So if you have like default_blue_ skybox it will automatically load in any level that uses the blue sky, and a purple one for the purple sky.

As for automatically activating fog across maps... a cheap hack would be to have the engine look for a file like "eachmap_exec.cfg" and exec it at the start of each map. Then the user could put whatever fog setting (or other settings they need to repeat each map, like skyboxes too) in that file....

scr_crosshairscale should also scale down (0.5, 0.4...). I really just need a tiny dot in the middle of my screen. Why would anyone want to make it BIGGER? heh.

New Feature Wishlist:

Proquake RCON

Custom Crosshair graphic

Actually, this whole post is a "wishlist" because I wish someone would continue work on this engine :D 
Mark V Issues 
I can confirm centered messages being cut off prematurely. Also, it seems that sometimes an MP3 track from the previous level keeps playing after entering the next level. This way, several tracks are being played at the same time which kind of sucks.

Also, I would really like to know how to get ne_ruins running with Mk V. For me, it always crashes when exiting the intro map. So far I haven't found any way to make it work - and it also doesn't work with Quakespasm, btw. 
Small(er) Report Update 
Ok, I found the "external_lits" console variable that lets me deactivate the colored lights. I guess that's something that needs a map reload to alter though, but at least the option is there.

About the MP3 music tracks, I wish there was a way to disable/enable them from loading. There is a pretty long delay when the MP3 tracks are loading before each map starts, EVEN WHEN the MP3s aren't actually being played. For example, -nocdaudio on the command line does indeed stop the MP3 tracks from playing... in exactly the same way that having no CD drive stops them from playing... i.e., they are still loaded into memory, and the messages at the start of each map says "current music track: musicblah.mp3" but it is "playing silently" or something and there's no way to actually hear it. A way to truly disable/enable the MP3 loading (other than renaming the music folder) would be great.

By the way, I found a nice workaround for those of us who don't have built-in CD drives but still want to be able to use MP3 soundtracks: download Microsoft's nice little Virtual CD Control Panel ( ) and you can easily set up a virtual CD drive that Quake will recognize and so allow the background music to play without having to adjust the volume to make it start....

And I found something else that looks like a major bug. On levels E1M2 and E2M3 (and only those levels -- I checked them all), the game will crash if you toggle the value of external_textures. EVEN if you don't actually have any external textures in your textures folder.... My external textures do work on these levels IF they are enabled when the map starts. In that case the game crashes when I try to disable them.....

Further thoughts on some of my earlier suggestions:

I think the quad, pent, and biosuit blends are probably fine. The lava blend is pretty dark, but that should be expected if you're swimming in lava.... It's just the ring and water blends are a bit too weak by default.

What about "water_fog" effects? It would be a fog setting that only shows up when you're underwater (that would look better than the blends anyway). It could be a bluish or yellowish fog for the waters, greenish for slime, and redish for lava.

And about saving fog and skybox settings across maps by possibly having the engine execute a re-exec.cfg at the start of each map -- it works petty well (heh, I did it by QuakeC), and in conjunction with some clever aliases it can even cycle through each of your skyboxes automatically on each map change.

It might be more "self-contained" (no external files) to just have the engine activate an alias: "re-exec" for each client at every new map... then the player could set up that alias to do the things they want, like if it was just as simple as 'alias re-exec "fog 0.03; sky blah" ' or if they still want to use a cfg file, 'alias re-exec "exec whatever.cfg" '

Anyway, this is just a cheap, simple hack I thought of, which might be easier to implement rather than saving actual console variables.... 
with colored lights, altnertaively you could not install the .lit file in the map directory in the first place. It only contaisn colored light info I believe so you dont losing anythign else by not installing it. 
Colored Lights 
@ nitin

Yeah, I may not have been clear in what I was saying. I actually do like the colored lights -- I just wanted a way to toggle them off and on in the game so I could compare what it looked like with and without them. I eventually found the external_lits command briefly mentioned in the documentation, but it's a setting that requires a map restart to kick in.

@ NightFright

Hey, I just found a post on Quakeone where you are working with colored lights and lit files. Could you do me a favor and come and post on my forum? No registration is required to post (just like here! I hate registering for forums, haha). I'd like to see if you can make some lit files for me -- I'm having varying and non-ideal results depending on which tool I try on the Iikka and Terra maps.... 
Encountered A Bug 
I was playing through a episode (deathmatch classics volume 2) and upon switching maps i got a "not enough handles" error and quake crashed

(happened once in many tries)

realy rare to me, hardly ever notice bugs with fitz :) 
Thanks for all the bug reports, I hate bug but like to know what they are too.

Like a ghost, I'm not really here. And the final Mark V is what it is (hint: final).

But I dream too. Maybe Mark V will influence ideas in the remaining active engines like Quakespasm or whatever the next FitzQuake has to offer.

Or both. Or neither.

Or "Hey look, a nickle!".

/Baker tricked you and scrambles away while you look for the nickle. If you are British, pretend nickle is a "quid", whatever the fuck that is. 
No excuses for shoddy workmanship!!!

If think it's called 'sustainable currency'. 
A US nickle is worth 0.02998 quid (apparently). Baker is trying to short-change us! 
Gamma, Contrast, And Blends 
I found that my lava and pain blends are way too powerful because of my gamma setting. I use the brightest gamma setting that works -- "gamma 0" -- and that makes my screen the correct brightness. Anything else is too dark. But when gamma goes lower than 0.5 the lava and pain blends become so intense they pretty much blind you (especially at gamma 0).

I can't find any way to make adjustments (other than turning off the blends, which I don't want) to alter this.

Like, there is supposed to be a "contrast" adjustment, but "contrast" in the console returns "unknown command."

And none of these settings seem to work right: r_lavacolor, r_watercolor, r_slimecolor. They do nothing if I set them from 0-9, and anything 10 or over just causes the blend to completely go away (just like gl_polyblend 0), and they won't come back until I restart Fitzquake.

Anyone know ways of adjusting the lava/pain blends, or other ways to tweak brightness/contrast in Fitzquake? 
Those are undocumented variables that can alter the water or lava or slime appearance.

The default is Quake normal: r_watercolor "130 80 50 128" (<red 0-255> <green 0-255> <blue 0-255> <percent 0-255>)

But typing r_watercolor "0 0 255 64" would be a blue hue in water as an example.

You weren't really supposed to notice any of those existed, they expect 4 parameters and doing any less than 4 defaults the percent to 0 which means none ... 
Gunter Notices Eeeeeverything ;) 
I am a power tweaker (not that kind!), and I monkey around with every setting I can find to see what I can adjust/improve.

Thanks for providing a little documentation for those undocumented commands.

Excellent, it works like a charm to adjust the lava color so that it's not so blinding with my gamma setting.

I notice that the default Quake numbers you provided for watercolor are not the default for Fitzquake Mark V. Can you provide the default values for Fitzquake (and standard Quake -- or point me in the right direction to find them) for each of these blends so I'll have a base to start with for tweaking them? My lava ends up looking like cherry jello since I'm not sure what the right color for lava is supposed to be -- I mainly just want to adjust the intensity and leave the color alone.

And I don't suppose there are any other undocumented variables that will control ring, pent, quad, and (especially) pain blends similarly?

Much thanks, Baker. 
Ah, I found the default values for liquids in the Quake code:

cshift_water = { {130,80,50}, 128 };
cshift_slime = { {0,25,5}, 150 };
cshift_lava = { {255,80,0}, 150 };

Setting the lava intensity to 128 seems to work well.

And by my eye it looks like the water intensity is the only changed default in Fitzquake, and it seems to have been changed to a value of 50? That must be why I thought it looked so slight... I think I'm ok with Quake's default value of 128 for that. 
Look! In The Sky! It's Gamma-ra! 
r_skyalpha and r_skyfog only work right if I have "gamma 1" but any other gamma setting causes them to do weird things.

Ya know, I see that solid white "scr_sbaralpha" thing someone else mentioned, but only on my old laptop. I don't see it happen on my netbook where I'm getting the weird sky issues with gamma != 1.

As I mentioned before, Fitzquake Mark V is really insistent upon playing the demos (and there's no way to stop it); so much that it seems to prevent Qview from connecting to a server. When I try to use Fitzquake through Qview, it starts up and I see the message that I'm connecting through Qview, and then the demo starts playing and I don't connect to the server :/ But then I can just type "exec qview.cfg" to get connected, but still.... Fitzquake is gonna play those demos NO MATTER WHAT! 
Resolution Issues 
Gee, it sounds like I'm really complaining a lot with all my bug/issue reports... but here are some more!

Widescreen resolutions seem to cause the weapon model to be much more hidden "under" the bottom of the screen. Like at 800x600 the weapon model sticks up a lot (like in proquake), but at 1024x600 the weapon model doesn't stick up very much (like in standard quake).

In some windowed resolutions, the top of the screen is hidden so that you can't see all the lines of text. Like, in 800x600 (windowed) you never see the first line of text (and maybe half of the second line too) at the top of the screen. So if you start typing a message, you never see what you're typing. Setting my windowed resolution to something weird like 750x550 on the command lines causes the problem to go away.

The names in the scoreboard when you press Tab are "bronze." I don't like that; it's usually harder to read on top of Quake's mostly-brown world. The names should be the proper color (white) unless the person used bronze characters to make their name.
OH... if I actually make my name with bronze characters, then it appears white in the scoreboard! It seems backwards....

The r_noshadow list should also include k_spike.mdl and lavaball.mdl (glowing things shouldn't really cast shadows). And I mentioned before that bolt.mdl should be in there, but I'll clarify that "bolt1.mdl" should be renamed to "bolt.mdl" since there is no bolt1.mdl in (standard) Quake. For other people who wanna fix this, you just need this altered list in your autoexec.cfg file:

r_noshadow_list "progs/flame.mdl,progs/flame2.mdl,progs/bolt.mdl,progs/bolt2.mdl,progs/bolt3.mdl,progs/laser.mdl,progs/k_spike.mdl,progs/lavaball.mdl"

I guess I'll mention that trying to make shadows for bolt.mdl (if it's kind of long) causes a major slowdown for an instant, but this behavior didn't happen in standard Fitzquake 0.85

Hm, I think I have to mention a niggle I have with the r_nolerp list: it contains models that are not a part of standard Quake. I don't think you should be catering to all the different mods out there by adding their modiels to the default settings in "standard" Fitzquake. That's something that each mod author (or possibly player) should have to configure themselves, with a custom r_nolerplist, and not expect the engine author to account for all their custom models.... If you start accounting for all the possible custom mods out there, the list is going to become really bloated (hey, I've got a few models from FvF you could add to that list ;).

Not that it matters, since it is how it is and probably isn't going to change; that's just my thought on the matter.

I'm really not just trying to complain with all these bug reports.... It just shows that I'm playing the heck out of Fitzquake! And the only little annoying issue that I can't work around is the centerprints and scoreboard appearing right in the middle of the screen and blocking the view. I really wish they behaved like in proquake and appeared near the top of the screen....

Hmm, and here's something I've seen several times: Fitzquake V doesn't always honor the -window command on the command line (from my batch file). Like I just ran standard Fitzquake without any parameters (so it ran full screen), and then after I closed that and ran Fitzquake V -window -width 750 -height 550 (batch file) it started up full-screen.... Then when I hit ALT+ENTER it switched to the proper-size window. 
Widescreen resolutions seem to cause the weapon model to be much more hidden "under" the bottom of the screen. Like at 800x600 the weapon model sticks up a lot (like in proquake), but at 1024x600 the weapon model doesn't stick up very much (like in standard quake).

isn't this desired behaviour? it retains the look of the weapon regardless of fov or aspect ratio. older engines would make the weapon look weird at wide screen or high fov. 
Weapons Hiding 
Having a tiny weapon is annoying. However I play my game with these variables to make the weapon look "chunky".

r_viewmodelfov 110
v_gunangle 2

Give it a try? 
Always Play -windowed 
never had any trouble, but i dont use a batch file just exec my command line 
Having a tiny weapon is annoying. However I play my game with these variables to make the weapon look "chunky".

r_viewmodelfov 110
v_gunangle 2

Give it a try?

If I "view" a "model" at the right "angle", when I "play my game", my "weapon" also goes from "tiny" to "chunky"... 
It took me way longer than I will admit to to understand what you were getting at there Kinn...

Perv! ;) 
I Do Not Have A Tiny Weapon!! 
Yes, having a tiny weapon is annoying :p Everyone laughs at you. So I've heard....

The desired effect is that your weapon looks the same (sticks up the same amount) no matter what resolution or FOV you are in.

@ FifthElephant

r_viewmodelfov 110 does the trick to make the weapon model look the same in wide-screen modes as it does normally in non-widescreen modes. Too bad that's not automatic, but it's good to know there's a way to adjust it. Thanks.

v_gunangle seems to be an unknown command though. 
v_gunangle might be for another engine to be honest. Maybe directq. 
Bad MP3 Issue! 
One bug I've noticed is that when you complete a level, the music doesn't stop playing and will continue to play over the song in the next level. I am using mp3 files in the music folder by the way. Everything else works great though!

One work-around is to save your game, quit, and reload your save. Another is to simply turn off the music, but that's a bit drastic... 
Try using ogg files instead 
OGG files aren't supported in Fitzquake ;)

Ok, I investigated the music glitch....
Here's where the problem occurs:

Upon touching the exit there's is a noticeable pause while the mp3 track loads and you see in the console: "current music track: music/track03.mp3" -- that's the Quake intermission track. However, it never stops the current music track from playing at that point, like it should.

And then both (I think) the current background track and the intermission track enter "the phantom zone" and you will hear those tracks playing in the background, EVEN if you alt-tab away from the Quake window! Meanwhile, the new music track for the new level you enter will be playing in Quake (and you will only hear that track when the Quake window has focus -- you always hear the phantom tracks). Additionally, the phantom tracks will not respond to bgmvolume commands in Quake, but the active track will.

It looks like if you just keep exiting levels, eventually you have like ALL the quake music tracks playing at once in the phantom zone....

Note: you do not get the phantom track effect when using the changelevel command as opposed to touching the exit, since Changelevel never tries to run the "end of level" code that should stop the current track from playing then load the intermission music.

If you use "cd off" and then "cd on" right before exiting, it will then play the intermission music and will not continue playing it when you switch to the next map. However, after doing this, any music playing in Quake will no longer respond to bgmvolume commands, and it will still be playing even if you alt-tab away from Quake....

The Correct Workaround:

If you issue "cd stop" just before exiting a level, you're golden. The intermission music will play and not keep playing on the next level, and the music tracks will continue to respond to bgmvolume commands....

Crud. it looks like the "phantom track" is impossible to kill (short of closing Quake) once it starts. So the "cd stop" command MUST be issued BEFORE you touch the exit.... I'll have to fiddle with my QuakeC to see if there's any way possible to issue a "cd stop" command AS SOON as the exit it touched, before any of the glitches can kick in....

Annnnd another issue I have.... Looks like setting "mouslook" to default "on" in the menu is not such a good thing either :/

Two reasons why: It overrides any alias settings I have to temporarily disable mouselook, and more egregiously, if I turn it off in the menu, it turns itself back on the next time I start Fitzquake....

Here's an example of something I set up in a cfg file:

alias +nolook "-mlook"
alias -nolook "+mlook"
bind z +nolook

So +mlook is on , but when I hold down the Z button, mouselook will temporarily be OFF so that I can, for example, move a few "inches" forward very slowly using the mouse (to get the perfect view or position for a screenshot or something).

But as mentioned above, the menu setting overrides mouselook ever being off, so I have to turn it off to use this stuff. But the menu setting keeps turning itself back on.... 
Tiny Update 
Yep, issuing a "cd stop" command via QuakeC stuffcmd to each of the players as soon as the level exit is triggered -- that totally fixes the glitch.

Also, "cd off" was the command I was looking for to completely prevent the MP3 tracks from loading. Though oddly, if I put "cd off" in my autoexec, I will then need to do "cd on" followed by "cd reset" to get the tracks to play again (level change alone won't do it).

If I just issue "cd off" inside of quake (and not in autoexec), then all it takes to get the tracks playing again is "cd on" (and a level change, as usual). 
I Find That Shaving Makes My Weapon Look Bigger 
It's just an ilusion thoough.... 
Annnd, I'm Back. 
The "mouse look" menu option doesn't bother me anymore; +strafe is the command I was looking for to temporarily disable it and allow moving with the mouse.

But unfortunately "cd off" command only works if you actually have a CD drive. So as I mentioned upthread, there's no way to disable the loading of MP3s -- or to make them play -- if you have no CD drive (so I'll have to create a virtual CD drive before playing Quake even if I'm not going to use MP3s, just to prevent the considerable delay as it loads them into memory).

As I mentioned before, E1M2 and E2M3 will crash if you try to toggle external_textures on or off. I noticed that when these levels load, there is an error: "mod_loadtexinfo: 1 texture(s) missing from bsp file." And Fitzquake V does not handle missing textures very well (crashing). I know there's that one weird untextured button on E2M23 in DM mode. tool_texturepointer says it's "notexture."

New issues:

You can't use % in normal chat messages.... For example, I tried to say, "we need to kill 100% monsters" and it comes out "we need to kill 100(invalid macro ' ')monsters"

In Proquake, you get the little color boxes with scores (representing the top two players) in the HUD, to the right of your Cells ammo. Proquake will show no more than 2 of them, because if it were to show 3 or more there, they would block the clock. Fitzquake V blocks the clock with 3 ore more of them....

And more issues with centerprint: When you die, the scoreboard appeared right in the middle of the screen, the same as with the centerprints, so that if there are 3 or so names in the scoreboard, it will block the centerprint. For example, when you die in FvF there is a centerprint message "Press 2 to Observe" but you can't read it because names in the scoreboard will hide it. Proquake keeps the scoreboard at the top of the screen and avoids this issue. 
Hm, This One Is Possibly Semi-critial.... 
Was playing today on END map. Me and another player were using Fitzquake Mark V (server was proquake). He got disconnected and could not reconnect, because Fitzquake was giving him the error:

"host_error: Colors slots full."

I didn't encounter this, but he couldn't reconnect until we were at the next map. I know that has to do with the colormaps for the dead bodies, right? But why would it prevent him from connecting to the server at all?

Not so critical continued reports:

Toggling high-quality textures on or off in a game causes the player skin to go completely white. Other players will look solid white after you do this. But rarely it doesn't happen.... It seems to require restarting Fitzquake to fix it.

Oh, and you can use the PAUSE button even in Deathmatch on a server that has Pause disabled. It won't pause the server -- it will just pause YOU and your view of the action will be completely frozen until you unpause yourself.... Of course, you'll probably be dead by then....

And... I have a modified DM6 map with a few small extra areas. It seems to no longer be recognized by Fitzquake as far as applying high-quality textures to the walls. The wall texture names are still all the same, but Fitz won't apply them to my modified DM6. High-quality item textures still work fine. 
Gunter, hats off that you have singlehandedly brute-force revealed weaknesses in the engine.

And this is the kind of gauntlet of testing that almost any engine author could only dream to have --- in the thoroughness and the rigor.

I'm replying out of this admiration.

In a perfect world, I could correct these and the other bugs that others have graciously found -- and this level of bug-testing is frankly incredible compared to what I can recall seeing in maybe anything except maybe Quakespasm and ezQuake (I got really high levels of feedback for "modern" ProQuake, and the detail and testing in this thread seems to vastly exceed even that).

Mark V Final was apparently not as bug-free as I hoped when given a wide-array of testing in different environments and the kinds of uses that normal FitzQuake didn't even typically encounter (like as a client to a multiplayer server, as an example. I'm sure it got drilled and grilled in SP and coop not only up/down but left/right and forward/backwards).

I wish there were 2 of me. The one of me that exists isn't likely to ever have the time to revisit Mark V. :(

On the plus side, it is open source. And I don't see much posted that wouldn't be somewhat easy to remedy by an experienced engine coder.

Ultimately, attention is probably better served by people contributing to or whole-heartedly endorsing Quakespasm. Mark V doesn't contain too much that couldn't be ported to that engine to achieve a singular "old school" classic engine ... 
You have to admire his resilience in finding all these bugs...

It's a shame you don't have time to revisit the engine (in particular my biggest peeve being the distorted texture scaling issues).

I have always envied people who can code, I tried to learn how to code for best part of a year when I was unemployed and I just don't have the mindset for it. 
Post A Reply:
Website copyright © 2002-2014 John Fitzgibbons. All posts are copyright their respective authors.