gonna dig through this now. 

-sndspeed 44100 doesn't enable 44khz sound? 

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 :) 

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. 

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 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. 

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.) 

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. 

@Tronyn ... no I haven't implemented BSP2 ... yet.

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

http://quake-1.com/docs/utils/txqbspbjp_rotate_skip.zip

^^ 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!