which is DirectQ 1.9.0 

I used fitzquake as a close second 

My name is ScampieSUXCOCK and I use Quakespasm. 

And I use FitzMkV, or RMQE 

I remember an earlier version I tried did not animate the sky textures correctly on func_walls, which was something I had done in Castle of Oblivion. So I stayed with GLQuake for a while, but I think with 081 I switched for good. 

for a long time i've been using aguirres enhanced engine

and now i use fitz85 (modified to prevent that infamous "whats that name of willem map" bug) 

Lately I have been using Fitz mark V with bsp2.
And Tyranns engine, as second engine. 

 

This would have been a great discussion thread!

Anyway I use Fitzquake latest SVN version (which is basically 0.85 with 2-3 half-baked new features) 

I vacillate between fitz .85 and the RMQ engine. 

I AM SCAMPIE I USE QUAKESPASM

Mostly because it's like Fitzquake, but also plays .ogg files from /music/ 

My name is Tronyn and I tend to use Jack Danieeaas I mean FitzQuake but with a strong secondary reliance on both DarkPlaces and RMQengine 

I am JPL and I have two reference engines (aforementioned)

I personally use both of them depending on the map. No need to say FitzQuake is the reference engine I (have been used to) map with. but I always give a try to aguirRe GLQuake, because it has a different look ingame (i.e light and fog density are not rendered the same)..

Well... Fitzquake is my preferred engine in anyway ;) 

Also, FitzQuake 0.85, because it comes with no bullshit and I haven't found a reason to use anything else yet. 

Some would say 'bloated'... 

and I used FitzQuake0.85 all of the time 

Is nice and rounded engine, but I can't use it to play my maps.

I use it when I record demos for others. 

http://www.youtube.com/watch?v=rWy6MNLuZLY 

Thanks for the great response guys, much appreciated!

Meanwhile I've spent a while trying to investigate the steam version of Quake, and it appears that the engines they supply have been slightly broken by the custom steam code they contain.

Winquake.exe is the less broken engine. Steam has some integration code, either to check you're still running steam in the background or to record your playing time for your profile. winquake must be a child process of steam.exe for the integration to work. If you launch winquake.exe from outside steam, it detects this, and signals steam to relaunch the process before shutting down.

This has two negative effects: 1) If you're watching for winquake to exit, you get signalled as soon as the first process closes, while the steam copy continues to run. Unusual problem, but I fell foul of it. 2) Much worse - when Steam relaunches winquake, it doesn't use any of the command line parameters from the original call. This means something as basic as
"e:\\steam\\ steamapps\\ common\\ quake\\ winquake.exe -game cass" does not work!

It's not impossible to run mods using the Steam version - you can add to the command line through the Steam interface, although it's cumbersome and persistant. But it's a barrier to making mods easy to run on Steam, as you can't supply a helpful batch file or external tool, users have to understand the command lines and manually action them.

I mentioned winquake was the better of the two engines - amazingly glquake is worse! It won't even run unless you launch it through Steam. My best guess as to how this happened is that some time in the past Steam integration changed. Since winquake is the primary engine for Steam's installation of Quake, it received a patch to make it compatible with the new version of Steam. Glquake got passed over for this, and so is nearly unplayable.

I doubt there's anything that can be done about all this, so I'm just venting/sharing. Fortunately you can just drop any custom engine into the directory and it works without any of these issues... 

http://i.imgur.com/cni4USL.jpg

Hope this helps. 

fyi that is NSFL gore shit and I don't get how Shambler is a mod here. 

unless you wanna see the inside of a mans scrotum 

it's safe 

But I post lots of links.

I am a member of the meta community.

Who's had a beer or two.