Updated patch.
I've moved texture creation from video_write() into seq_Play(), where it makes
more sense, and added a check for the video size. I've also removed the radar
warning message, and added a check for the YUV420 format (though those should
be committed separately).
On Wed, Apr 08, 2009 at 02:19:08PM +0200, Christian Ohm wrote:
On Wednesday, 8 April 2009 at 11:46, Per Inge Mathisen wrote:
But I'm not sure if the actual problem is in Mesa, or if Warzone is doing
something strange with the VBOs. If someone knows some simple example programs
using VBOs
On Wed, Apr 8, 2009 at 9:46 AM, Florian Schanda
flor...@elysiumlarp.org.uk wrote:
Will you support the open source ATI drivers -- as they currently don't work
for trunk/.
Have you made a bug report about it? Note that it may be hard to fix,
since I don't think anyone of us have those
Hi,
On 8 Apr 2009, at 08:46, Florian Schanda wrote:
On Wednesday 08 April 2009 01:56:13 bugs buggy wrote:
And by low end, I mean systems that
have crappy openGL drivers, I think we require openGL 1.3 maximum for
this release?
Will you support the open source ATI drivers -- as they
On Wednesday, 8 April 2009 at 11:46, Per Inge Mathisen wrote:
On Wed, Apr 8, 2009 at 9:46 AM, Florian Schanda
flor...@elysiumlarp.org.uk wrote:
Will you support the open source ATI drivers -- as they currently don't work
for trunk/.
Have you made a bug report about it? Note that it may
On Wed, Apr 8, 2009 at 2:56 AM, bugs buggy buginato...@gmail.com wrote:
On 4/7/09, Per Inge Mathisen perxx...@gmail.com wrote:
I don't think adding version checking code to 2.2 is a good idea.
Let's not do a lot of changes to it, so that it can be released.
Um, I think your wrong on this, it
On Wednesday 08 April 2009 01:56:13 bugs buggy wrote:
And by low end, I mean systems that
have crappy openGL drivers, I think we require openGL 1.3 maximum for
this release?
Will you support the open source ATI drivers -- as they currently don't work
for trunk/.
It might be painful, but I
Speak now before we do these changes. They must be done all at once!
In short, game server port is now 2100
Master server port is now 9998
config dir is now Warzone 2100 2.2 (for mac/windows) and .warzone2100-2.2
The bot will need updating.
Anything else?
http://developer.wz2100.net/ticket/370
On 4/7/09, Elio Gubser elio.o...@gmail.com wrote:
Am Dienstag, den 07.04.2009, 15:49 -0400 schrieb bugs buggy:
Speak now before we do these changes. They must be done all at once!
In short, game server port is now 2100
Master server port is now 9998
config dir is now Warzone 2100
I don't think adding version checking code to 2.2 is a good idea.
Let's not do a lot of changes to it, so that it can be released.
Instead, I suggest that for trunk we use port 2100 for game, port 9990
(or something else) for master; for 2.2 we use port 2100 for master,
and port 9990 (or
2009/4/7 bugs buggy buginato...@gmail.com:
We also may want to change GAMESTRUCT, so the master server can take
care of games that have a password, and other stuff we want to check
for?
YES.
The master server should also save the version number, and any mods
loaded. I'm sick and tired of
On 4/7/09, Per Inge Mathisen perxx...@gmail.com wrote:
I don't think adding version checking code to 2.2 is a good idea.
Let's not do a lot of changes to it, so that it can be released.
Um, I think your wrong on this, it isn't *that* much that has been
changed/modified.
The lifespan of 2.2 is
On 4/7/09, Zarel zarelx...@gmail.com wrote:
2009/4/7 bugs buggy buginatorx...@gmail.com:
We also may want to change GAMESTRUCT, so the master server can take
care of games that have a password, and other stuff we want to check
for?
YES.
First, let me explain a bit.
typedef struct
{
13 matches
Mail list logo
