Monday, November 16, 2009

FitzQuake Protocol Is Done

...ish. Current position is that I can successfully play a demo recorded in FitzQuake using sv_protocol 666, FitzQuake can successfully play a demo recorded in DirectQ using sv_protocol 666, and DirectQ can connect to itself using protocol 666. I have yet to test a network connection from each engine to the other.

There are some parts of the FitzQuake protocol I've chosen not to fully implement yet. What this means is that my server won't set the flags or send the messages, and my client just tests for the flags and blindly gobbles up the messages. These are parts that rely on code changes elsewhere, such as alpha support and support for > 8192 entities.

If I want to make protocol 666 my new default I'm going to need to implement alpha fully on the server at least; I don't think support for > 8192 ents is that important (not even Warpspasm needs it).

In other news I've cleaned my monitor and it's been eye-opening in more ways that one. There was 4 years (!!!) of accumulated gunge on it which I had just gotten used to and hence never really noticed. The brightness from it now is pretty extreme, and actually HURTS to look at. I've had to turn down the brightness a little as a result. Ouuufff.

2 comments:

gnounc said...

I was just thinking about cleaning my monitor! Thx you talked me out of it.

mhquake said...

Heh heh heh.