If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

For example we're likely first, or at least one of the very first open source engine projects to bring modern-day engine stuff to the open source engines, like hardware rendered models (classic Quake 2/3 engine forks do this in the CPU, being very inefficient in model rendering).

Several open 3d engines have been doing that for a long time (ogre, cs, irrlicht...). Perhaps you mean to open id engines, etc?

I wanna clear one thing up: Warsow is the Qfusion and Qfusion is far from dead 1.0 engine changes are ernomous, making the engine pretty darn modern in many aspects: Hardware rendered skeletal animations, incredibly high map performance with VBO's, octagon hitboxes, nice e-sport features like r_drawflat etc. You can read more about our new engine stuff here.

I guess I would have personally just preferred the game and engine to have been kept separate.

Originally Posted by crizis

Secondly we do have our reasons for keeping semi-closed* repository. The engine projects we have are always pretty gigantic, multi-month projects which need big commitment from the guys who do them. For example we're likely first, or at least one of the very first open source engine projects to bring modern-day engine stuff to the open source engines, like hardware rendered models (classic Quake 2/3 engine forks do this in the CPU, being very inefficient in model rendering).

I call BS on this one outright. If you're properly using revision control, that should be in a branch. Honestly, especially if you're not using something terribly like CVS or SVN and using something that isn't brain-dead like Git, Mercurial, or another distributed SCM, you could technically even keep the branch private until you're ready to merge the changes. So, I reject your argument outright on this one.

Originally Posted by crizis

*) We're actually very open to contributors who actually commit on these projects. But on the other hand having open repository would somehow imply that we're interested in merging every random idea that anyone comes up with. This is not the case - we have our vision what the game should be, and people usually just get mad when we decline their code/features which does not fit in our vision of the game.

First, this puts a bit of a burden on anyone accepting patches since the patches have to be against a source drop and can't be brought up-to-date before submitting them. As for the second part, I can't really comment but some kind of documentation on how patches are accepted (including what's acceptable) could be written and included in the engine. That way, there's no confusion as to what's acceptable to ask to be accepted and what's not.

Originally Posted by crizis

For players everything is and will always remain free however. So hopefully you enjoy our release

I usually try every release, but I don't have hours of free time for games. And just to be clear, I really do appreciate the work that goes into the game and engine, and my gripes are really quite minor (even if I make them sound like they're not.)

Originally Posted by crizis

Yes, I mean these ones which actual games use.

That seems like quite the statement to make. I'm sure the dev's at PlaneShift (which IIRC had their first release three years prior to Warsow's first release) might argue to the contrary. Just saying.

It doesn't look like there's a package for warsow in Precise, but there was one for Oneiric: packages.ubuntu.com/oneiric/warsow It looks like the dependencies there should be mostly what you'll want (the -dev versions too, but you knew that already.) libjpeg62 will likely be libjpeg-dev instead. Of course, this is just my best guess since I don't have a Precise chroot.