Comments on: Software vs GLQuake: Fullbrights

By: Custom textures in MP Quake - QuakeOne - Quake 1 Resurrection

Custom textures in MP Quake - QuakeOne - Quake 1 Resurrection — Wed, 08 Sep 2010 17:53:41 +0000

[...] you're converting textures, make sure that you have a good read of this before releasing anything: Software vs GLQuake: Fullbrights (Although I assume that Baker's tool handles the necessary palette mangling automatically). [...]

By: dreadlorde

dreadlorde — Wed, 09 Dec 2009 16:18:42 +0000

We need more articles like this. Maybe we can place a bounty on these kinds of articles? They’re very useful to new engine programmers; such as myself, in that they provide an in depth look at how things work in Quake without the reader having to dive straight into source code.

Hell, if Spirit can’t place a bounty on articles like this, I would be willing to negotiate with someone a price so that they could provide us with them, and maybe some more detail on what source files implement what is being described.

By: Irritant

Irritant — Mon, 23 Nov 2009 18:23:09 +0000

Of course by now, this is all usually handled by use of a shader system rather than relying on a pallette to provide fullbright colors on map textures.

By: mh

mh — Sat, 21 Nov 2009 22:51:13 +0000

Thanks for this one, it’s very important. Getting overbrights wrong is at worst merely unpleasant, getting fullbrights wrong can completely destroy the hard work of the mapper and texture artist in creating an atmosphere.

It needs to be realised beyond doubt that both are deliberate intended features of the Quake engine, and making the point about the colormap reinforces this. It is after all trivially easy to generate a colormap that has neither.