...but DirectQ currently gets maybe 2000 downloads per month. I reckon it's got market penetration. ;) 

ok then. 

I maintain ProQuake but wouldn't recommend it for single player over FitzQuake any day of the week.

Anyway, yes we are in a time of a bit of engine flux due to a great many authentic baseline improvements being littered all over the place.

But as long as someone is able to play single player releases with some preferred and quality engine, there is no emergency ... and in time all this will sort itself out.

I myself would prefer to live in a world with a lot of general interest experimentation that "matters" going on. And regardless of preference or not, it is, in fact, exactly what is happening ;) 

did you guys really implement fog interpolation? or was that always there and i never knew?

cause it's pretty fucking cool. and also annoying because only a few weeks ago i wrote qc to handle fog interpolation with a complicated system to get ftos to output more than 1 decimal. :P 

it was always there :) 

queue "fuuuuuuu" on my part. :D 

Fog interpolation? I thought fog just kind of sat there statically. What is this fog interpolation? 

I believe it's that if fog changes colour it blends smoothly between the before and after colours over a period of time. 

Its only really decent when you control what the player is seeing and how they're moving. For example, sticking them inside a lift and blending it from a lot to none. 

little while ago, gb made a speed map and i mentioned being unable to load it in rmqengine. ("The application was unable to start correctly (0xc000007b). Click ok to close the application")
turns out, the SDL.dll included with 64bit quakespasm is what causes the error.

unfortunately, 64bit quakespasm can't run with the (i'm assuming?) 32bit SDL.dll that rmqengine uses.

just fyi, i guess. 

you can't mix a 32 bit app with a 64 bit library or vice versa 

sure, i mean, i guess that makes sense. the problem is there's no way to know since the file is named the same thing. 

try the InspectExe tool (http://www.silurian.com/inspect/index.htm) 

My sound is lagging hard in the new build,I was just wondering if anyone else is having an issue? 

After having gotten sick of some of the issues I had with Darkplaces (stuff not spawning properly, doors not working, items floating in mid air), I made the switch to Quakespasm and have been pretty happy.
Still having some issues, not sure whether it's due to my n00biness as someone that doesn't really understand Quake tech that well, or the engine itself.
Recently tried to play the map pack, Digs01 again, which worked fine on Darkplaces.
Water and teleporter graphics wont show up at all.
I know you can get around that problem in Travail with +r_oldwater 0 +r_waterquality 32, but I have no idea if there's any command line that will fix the issue I'm having with Digs01.
I fear this may effect some other map packs too, but I haven't tried much others yet.

Also, the NightJourney map pack (http://www.quaddicted.com/reviews/nightjourney_v2.html), just wont work once you try to start a new game. Minus some errors with stuff. Says something about missing Lava/md2 model (I think that's what it said, I ended up deleting Nightjourney in frustration because it wouldn't work anymore lol), which is odd because I never encountered that issue with Darkplaces 

hate to ask a question like this, but is r_wateralpha set to 0? that'd make it not show up. 

I just tried using +r_wateralpha 1 and it works fine, so indeed just n00biness on my part.
Odd that +r_oldwater and +r_wateralpha are the same thing, damn quake and interchangeable command lines :P
The +r_oldwater command line was the suggestion made on the Travail site which makes the alphas work properly. Why that is, I don't know, but it works for Travail.
Just calling it +r_wateralpha would have made more sense.

Anyway, thanks for the help, Necros (although the help was in a rather roundabout way lol) 

r_oldwater has nothing at all to do with alpha.
r_oldwater 1 uses the original method of making the water texture warp. turning the option off uses a more expensive, but much nicer looking warping effect.
r_waterquality controls how good the warp looks, when using r_oldwater 0. 

r_oldwater 0 fixes up bad texture alignment for liquid brush seams. And too much water alpha may make a teleporter disappear. 

The problem is that sine waves don't linearly interpolate. r_oldwater 0 doesn't actually fix it correctly: what it does do is reduce the problem to an extent that it's not really as noticeable, but the tradeoff is that it imposes limits on the maximum size you can use for external textures. Doing the warp per-pixel in a shader is the only real way to definitively fix it in the general case. 

I guess there might be a situation that r_oldwater 0 makes it not as noticeable, but I've seen only perfect results so far. No complaints. 

same here. it looks fantastic and very authentic. 

It would be awesome if we could get a cmd/cvar to change the weapon models position on screen back to the vanilla placement instead of the "Darkplaces style". I think the engine is great and this is my only complaint. 

Version 0.85.5 of QuakeSpasm is released.

Merry Christmas and a happy new year to all. 

>deathmatch and coop cvar "fix" of Quakespasm 0.85.5

Although for sure that does not change the behavior of id1 progs.dat nor Quoth nor any other single player mod I know of, I am somewhat certain that change breaks the idea of cvar guided behavior in QuakeC. Cvar behavior is decided by QuakeC.

Since aguirRe is no longer around, well, his primary goal was mod compatibility and had deep knowledge of even obscure mods. Which I don't have. It may be possible that this change breaks some obscure or even not so non-obscure mods ... like ones with a lot of settings.

Then again maybe not.

DarkPlaces style weapons vs. Quake style

I conducted a deep and thorough investigation of this issue during the summer for Engine X. Engine X has an almost entirely unrestricted ability to resize the Quake window in real time like any other windows application.

I discovered some severe liabilities with DarkPlaces/FitzQuake style gun placement being hopelessly flawed with certain aspect ratios.

At the moment some of the work in DirectQ has the best current solution which has an FOV-immune gun placement possibly inspired by Qrack (which seems to have got it from possibly a Phoenix or QER tutorial).

I say best current solution because there is an additional factor involving FOV y, that is generally not a source of concern if you correct for a 4:3 aspect ratio, which for sure Qrack does (but the code is slightly less clean than applying it to FitzQuake, which simplified the FOV calculations).

At the risk of making this too wordy, the 4:3 aspect ratio is not always correct because some mods have side-mounted weapons (not center of screen) which may or may not have been designed with a 4:3 aspect ratio in mind and without taking in account the proper aspect ratio for the appearance of side mounted weapons they can disappear off-screen when not also incorporating the intended mod aspect ratio (!!).

Too much information, perhaps. But a complete and accurate description of factors into the presentation of the view weapon model.