1) Clock fix
2) Session to session command line history via the up arrow
3) Half-Life .bsp support
4) Rotating brush model support and extra chase camera options

Source included, of course, and has 2 project files: MS VC++ Express and Code::Blocks

http://quake-1.com/files/engine-sources/fitzquake_plus.zip

Mostly made to satisfy someone who wanted Half Life map support in FitzQuake. 

5) 5 button mouse support

^^ Add. Forgot to mention. 

Session to session command line history via the up arrow

i noticed this in quakespasm and i thought i was going insane for a while before i realized what was going on.

5 button mouse support

you are a quake hero for a week and three days. 

Is the next Fitzquake going to have Nehahra support? 

I've considered it before, but it was never a high priority. I still need to generate a list of necessary features (e.g. spr32, special protocol for the demos, fake cvars so the fog works, alpha (already done), not sure what else...) 

Nehahra support is quite tricksy and it doesn't sit too well with more modern engine features. Aside from anything else it does evil things like changing the protocol without defining a new PROTOCOL_VERSION; obviously a relic of earlier times. 

i can't quite figure out exactly what causes this, but as i am building a map, once the map reaches a certain point in size, weapons stop interpolating their animations.

yeah. wtf indeed. :P

is there maybe like a certain number of slots that fill up for models to interpolate? i haven't seen monsters being affected by this though.

this happens in quakespasm and rmqengine as well as fitzquake085. 

weird. I can't even think about how that's possible :| 

can you send me a map that causes this bug? Or is there an already-released map out there that does? (if it's due to size, maybe warpspasm or something?) 

That's wacky. Must be a protocol thing then as RMQ's MDL renderer is significantly different. 

i did actually notice that on an unvised e2m4rq (which is massive) in rmqengine a few months back. seemed to disappear once everything was vised though 

Rubicon 2 looks flashy ;>
But regards the demo crash, is there a reason "Model not found" doesn't throw a Host_Error ?

cl_parse.c:
- Con_Printf("Model %s not found\n", model_precache[i]);
+ Host_Error("Model %s not found\n", model_precache[i]); 

can fitz play nehahra? 

it's on the wishlist though. 

I couldnt find it in the readme. Would be a good feature IMHO. Aguire/Nehquake engine doesnt appear to be widescreen friendly. 

and Directq doesn't support the neh Fog, so we are waiting for a "perfect engine" lol 

It this possible by some toggle or console command I'm missing somewhere? Would be very handy. 

there's no way to keep track of the last save spot (aside from quicksave) in the qc, and it's the qc that handles what happens when you die. (for button presses and reloading the map).
if the engine had some extended builtin function 'getLastSave' then it'd be a simple matter to hook it into the qc. 

That's a shame :( Thanks for the response. 

or for a mod?

if you implement an autosave system, you can hook that in easily enough so that pressing fire when dead loads the last autosave.

also, if you coopt the quicksave key and redirect it to an impulse, you can assign a function to quicksave as normal, but then you can mark a variable somewhere to remember that the player has quicksaved and to load that save when dead. 

Late reply - As a player only. It's simply for convenience since Duke/Doom/HL do it, I've wondered if it were possible in Q1. 

as an engine patch on Quakespasm (but it could be applied to any engine.) It's really nice; keeps the gameplay pace high when you die - just shoot and you're back in the game :D.

The patch also autosaves every so often, based on a heuristic (picking up health = probably a good time to autosave)

Here is a windows binary:
https://github.com/downloads/ericwa/Quakespasm/quakespasm-ericw-autosave-02-28-2010.zip
and the source:
https://github.com/ericwa/Quakespasm/tree/autosave 

I just did it in DirectQ as a restart2 command; it tracks the name of the last save you make and just reloads it if something valid was in there. Probably not very robust (what if the load fails?) but hey! - it's a hack anyway. 

if you're gonna add it, you should really make it controllable via qc instead. :(

should be a 'getLastSave' command that outputs a text string or something.

restart2 works i guess, though. you just call that in qc instead of restart. 

Probably not very robust

Make sure the save is from same map that the player died on maybe :)