Quake Video Code Rant

[Baker]

[mh]

[Baker]

I'm hoping I can unwind all that spaghetti, by tomorrow morning.

What I would like to do is have some flexibility to define viewports at will and get a true framework going with the 2D graphics. [And the menu and the sbar].

With ProQuake I had to stick with expectations, maintain builds, ensure backwards compatibility. With Engine X, I can do whatever makes sense.

I noticed from day 1 things relating to both the "canvas management" and the menu.

[Off-topic, but speaking of nasty stuff I read the whole . Many things I didn't know ... that skybox/savegame thing. Well, those were the early days.]

If I can truly get a handle on the disgusting redundancy of the window definition cvars, I'll should have some major speed gains in accelerating some of the things I want to wrap up.

[mh]

[Baker]

[Spike]

[TimeServ]

Well really FTE doesn't have a software renderer because I woke up one day and decided to remove the entire software renderer code because I was sick of looking at that and then committed that change in. So really I'm the one to blame for that. Spike just didn't feel like getting into a commit war and reverting the changes I guess.

[Baker]

Software renderers are fun, but I think to some extent they really are a novelty for the most part. It is fun to learn how they work, the pixel buffers and all that.

But maintaining a novelty build of FTEQW with so much capability that software just isn't going to have is a hell of a lot of maintenance overhead.

[And it's not like the SW build source isn't out there for prior builds.]

[mh]

[Spike]

[Irritant]

[mh]

[Baker]

[Chip]

[leileilol]