are done (sorry if this steps on your toes with the view.c merge Deek) and
I'm almost positive flymode will now work. Even though view offset is
done, it won't.
The reason for this is that cl.stats[STAT_FLYMODE] is pretty much going to
ALWAYS be 0 on a standard server. Since 0 tells us that we're not flying,
this is fine. cl.stats[STAT_VIEWHEIGHT] is also going to be 0, but it
should be 22 for normal views. I could always assume this value is an
offset from 22, but that just seems lame to me. I'll either do it anyway
or we'll have to find a good opportunity in the connect cycle to set the
cl.qfserver qboolean to true.
I'm thinking about using an info key value for this, but we'd be better
served I think by coordinating with QSG to up the protocol version across
all engines.
code for scr_consize a bit. I also made it work in software targets. If
you set scr_consize outside the range of .2 to .9 it now assumes you're
an idiot and ignores your setting, using the appropriate boundary value.
A note about gl_conalpha for GL targets. It now works up to a consize of
.9 rather than working just upto 2/3 of the screen. Works just as it did
before. The only reason it matters is that the boundary for scr_consize
does not apply to the decision of whether or not to use alpha--only to
how big to make the console.
That means if you set scr_consize to .91 or something it won't be bigger
but you'll lose alpha. Don't even try to report that as a bug---I will
tell you simply Don't Do That(TM).
look sane now however. Other projects which wish to keep the ability
to render in software better check out the changes - you won't find them
in a tutorial. ;>
If you try to load a 30-version'd BSP (ie, one with colored lighting) you
are gonna find that software renderering looks like shit. I know what
the problem is.
looked kinda silly IMO. Turn off the stupid bubbles, we have real colored
dlight now!
I may put up some of the "outtake" screenshots of the broken lightmap code
as I was writing the support. Some of them look cool. =>