Re: [warzone2100-dev] 2.2.3 release?

2009-09-12 Thread buginator
Christian Ohm wrote: > On Saturday, 12 September 2009 at 15:51, Per Inge Mathisen wrote: >> I'm quite sure that not all bugs are fixed, but the amount of bug >> fixes in 2.2.3 is large enough to warrant a new release, unless anyone >> is actively working on an important fix that we should add first

Re: [warzone2100-dev] 2.2.3 release?

2009-09-12 Thread buginator
Per Inge Mathisen wrote: > On Sat, Sep 12, 2009 at 4:11 PM, i-...@yandex.com wrote: >>>* Fix: Some sounds were missing for super cyborgs (ticket:830, r8102) >> Per, are you sure it's not a #919? IFAIK Ticket #830 is for baba >> screams, not weapon sounds. > > Possibly. I just tried to reconst

Re: [warzone2100-dev] [Warzone2100-commits] SF.net SVN: warzone2100:[8906] branches/2.3

2010-01-29 Thread buginator
On 1/1/10, Per Inge Mathisen wrote: > On Fri, Jan 1, 2010 at 5:14 PM, Dennis Schridde wrote: > > Am Freitag, 1. Januar 2010 17:01:58 schrieb ...@users.sourceforge.net: > >> Revision: 8906 > >> Property Changed: > >> > >> branches/2.3/ > >> branches/2.3/data/mods

Re: [warzone2100-dev] A question of wikis

2010-01-29 Thread buginator
On 1/2/10, NoName wrote: > Am 02.01.2010 19:03, schrieb Dennis Schridde: > > > Hello! > > > > Am Samstag, 2. Januar 2010 18:07:36 schrieb Daniel Kliman: > > Kamaze likes to maintain a server and provide us with hosting. (At least > > last > > time I talked to him.) > > > I still do, but i'm a

Re: [warzone2100-dev] Splitting out original campaign

2010-01-29 Thread buginator
On 1/4/10, Kreuvf wrote: > Per Inge Mathisen wrote: > > So here is my suggestion: We pick one branch as the final campaign > > release tree, and at some point branch it to become an "original > > campaign only" branch, removing anything other than campaign from it > > (ie no skirmish, multipla

Re: [warzone2100-dev] Planning to commit unicode, raytrace, retarget -> 2.3, and pointtree -> trunk

2010-01-29 Thread buginator
On 1/16/10, C yp wrote: > Hi, I was told big commits should go on this mailing list before being > committed. And apparently a quick rewrite of a few files is considered a big > commit. Sounds good, but just a slight note, since we are still using svn for our VCS, all patches should be in svn-dif

[warzone2100-dev] Fwd: [Openal-devel] OpenAL Soft 1.11.753 released!

2010-01-29 Thread buginator
This was sitting in my inbox, and I thought it could help our userbase with their PulseAudio issues. -- Forwarded message -- From: Chris Robinson Date: Jan 17, 2010 10:25 PM Subject: [Openal-devel] OpenAL Soft 1.11.753 released! To: ope...@opensource.creative.com Cc: openal-de...@

Re: [warzone2100-dev] Replacing Aivolution with DyDo-AI

2010-01-29 Thread buginator
On 1/25/10, wp1004671-obooma wrote: > > First of all, hello everybody in the mailing list. > I am not going, for now, to commit to anything else but DyDo, for the > future let`s see but my programmer skills are not that good...and here to > the second point, I have no idea how this all works ->

Re: [warzone2100-dev] [Warzone2100-commits] SF.net SVN: warzone2100:[9038] trunk

2010-01-29 Thread buginator
On 1/7/10, Per Inge Mathisen wrote: > On Thu, Jan 7, 2010 at 4:01 AM, wrote: > > PNG optimization, also known as 'Crush them all!'. > > Again? > > Did you measure any significant savings from doing this? It is kinda > annoying to have to download every image anew for every working copy, > y

Re: [warzone2100-dev] [Warzone2100-commits] SF.net SVN: warzone2100:[9538] branches/2.3

2010-01-29 Thread buginator
On 1/28/10, Per Inge Mathisen wrote: > On Thu, Jan 28, 2010 at 10:34 AM, wrote: > > Revision: 9538 > > > http://warzone2100.svn.sourceforge.net/warzone2100/?rev=9538&view=rev > > Author: zarelsl > > Date: 2010-01-28 09:34:18 + (Thu, 28 Jan 2010) > > > > Log Message: >

Re: [warzone2100-dev] Mod List Patch

2010-01-29 Thread buginator
On 1/16/10, dak180 wrote: > Because Zarel is currently unable to post to the list he asked me to pass > this on; http://developer.wz2100.net/ticket/1415 > > Yeah, I know this is obviously too late now, and I don't see any replies here on the ML, but I assume that the replies about this patch was r

Re: [warzone2100-dev] Multi-turrets

2010-01-29 Thread buginator
On 1/29/10, Guangcong Luo wrote: > On Fri, Jan 29, 2010 at 7:36 AM, Per Inge Mathisen > > wrote: > > > I highly doubt that forum users are in any way statistically > > representative of ordinary users, nor in my experience are they good > > representatives of the interests of ordinary users. We

Re: [warzone2100-dev] Merging the Qt branch

2010-01-29 Thread buginator
On 1/28/10, Per Inge Mathisen wrote: > Hello, > > The Qt port branch has come a long way recently, and now runs entirely > without SDL and QuesoGLC (and all its dependencies). I would like to > merge it into trunk soon, so I would encourage everyone to take the > branch for a test run, and see

[warzone2100-dev] VCS / DCS changes?

2010-01-29 Thread buginator
Greetings all. Talking with sourceforge, they said if we are still having issues with svn being slow, we can open a ticket with them, and they can migrate us over to their BETA svn server which would need svn:// access instead of https:// access that we have now. Buginator: Submit a ticket

[warzone2100-dev] Freeze! Please read this about 2.3

2010-01-29 Thread buginator
As was previously mentioned a long time ago, Debian will be freezing in March. ok, so the latest release team mail says "we propose freezing in March 2010." to transition to testing/squeeze, wz needs 10 days in unstable, but IIRC as long as it is uploaded before the freeze the release team will

[warzone2100-dev] Revision: 9250, Revision: 9257

2010-02-02 Thread buginator
Revision: 9250 Author: zarelsl Date: 11:52:01 PM, Friday, January 15, 2010 Message: An assert to figure out why time travel is occurring. Revision: 9257 Author: zarelsl Date: 5:26:45 PM, Saturday, January 16, 2010 Message: Some hacks to paper over the time travel bug. Just what is the

Re: [warzone2100-dev] Revision: 9459/9460 disabling -Werror?

2010-02-02 Thread buginator
Revision: 9459/9460 Author: dak180 Date: 12:19:43 AM, Sunday, January 24, 2010 Message: Turn -Werror off to keep Zarel sane. AFAIK, there is a very good reason to keep -Werror *ON*, and that is, we will see less commits that will break linux builds. I advise to revert this and change it ba

[warzone2100-dev] Revision: 9544

2010-02-02 Thread buginator
Revision: 9544 Author: cypr Date: 9:55:50 AM, Thursday, January 28, 2010 Message: visibility: Make object-object visibility less weird and less inefficient. What is your definition of 'weird' ? ___ Warzone-dev mailing list Warzone-dev@gna.org https

[warzone2100-dev] Don't commit 'devpkg' files to svn

2010-02-02 Thread buginator
This is very annoying, all dev packages should belong where we have all the rest of the dev packages. Namely, here: http://download.gna.org/warzone/development/devpkg/ There is no reason why there should be an exception for mac dev packages. Revision: 9218 Author: dak180 Added : /branc

[warzone2100-dev] Proposed Beta 10 release date

2010-02-02 Thread buginator
I was thinking this weekend (2/6/10) will be a good time to release Beta 10. Anyone got any show stopping bugs that need to be looked at, please list them, (hey wait, don't list them, fix them! ;)) and I can take a look when I get back. ___ Warzone-dev

[warzone2100-dev] Rework directories for mods

2010-02-05 Thread buginator
I thought everyone knew this, but I guess not... In physFS, we have only one "write" directory. That directory is the one where we have permission to write whatever we want. That directory is the one the game __should__ look for for anything and everything that is user game related. The only exce

[warzone2100-dev] *If* we move to a new SVN server, then these restrictions apply

2010-02-05 Thread buginator
= Note that this new environment has the following up-front limitations: * No integration with the trac hosted app * No stats tracking -- changes that occur while this is in test stage may not ever get reflected in the site stats. * L

Re: [warzone2100-dev] Rework directories for mods

2010-02-05 Thread buginator
On 2/5/10, Guangcong Luo wrote: > On Fri, Feb 5, 2010 at 7:27 PM, buginator wrote: > > We should make a 'mods' directory in the config directory, and deal > > will all mods there. > > I'm fine with that. > > > > Before the release of Beta

[warzone2100-dev] Beta 10 is now out

2010-02-07 Thread buginator
Today we bring you Beta 10. More bugs were squashed, multiplayer sync improvements and for more information, see the changelog. :) Note, when playing multiplayer games, you will see some "info" log lines, these are NOT errors or warnings, it is to help us track down issues that were reported in t

[warzone2100-dev] Welcome aboard Safety0ff!

2010-02-09 Thread buginator
Another day, another new member has joined the project. Welcome Safety0ff! ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev

[warzone2100-dev] Revision control systems & a test server(?)

2010-02-11 Thread buginator
For those of you not keeping score, so far, from the input I have been getting about which (D)VCS, we should use, this is the breakdown so far. svn: As I already posted, we could migrate to the new beta servers, but we would have those restrictions that was already mentioned. git: still unfriendl

Re: [warzone2100-dev] Rail Guns are Misnamed

2010-02-11 Thread buginator
On 2/11/10, dak180 wrote: > Rail Guns as described and as depicted in the in-game modules are actually > Coil Guns. > > We should probably rename them to reflect this, as that would be easer than > redoing the descriptions and modules. > I have no objections.

Re: [warzone2100-dev] [Warzone2100-commits] SF.net SVN: warzone2100:[9800] trunk/src

2010-02-14 Thread buginator
On 2/14/10, Per Inge Mathisen wrote: > On Sun, Feb 14, 2010 at 7:02 AM, wrote: > > Revision: 9800 > > > http://warzone2100.svn.sourceforge.net/warzone2100/?rev=9800&view=rev > > Author: buginator > > Date: 2010-02-14 06:02:27 + (Sun,

Re: [warzone2100-dev] PC controllers

2010-02-16 Thread buginator
On 2/16/10, Guangcong Luo wrote: > On Mon, Feb 15, 2010 at 10:11 AM, mike varner wrote: > > is it possible to make warzone 2100 use a dual action PC controller for > > the games > > i been trying to fine the keys for but it not there > > > Hello, Mike. > > warzone-dev is a mailing list for th

Re: [warzone2100-dev] [Warzone2100-commits] SF.net SVN: warzone2100:[9690] branches/2.3/src/game.c

2010-02-16 Thread buginator
On 2/6/10, wrote: > Revision: 9690 > > http://warzone2100.svn.sourceforge.net/warzone2100/?rev=9690&view=rev > Author: sendai > Date: 2010-02-06 20:20:06 + (Sat, 06 Feb 2010) > > Log Message: > --- > Allow loading broken maps that have duplicate buildings when as

[warzone2100-dev] Another release is planned on Feb 21st

2010-02-16 Thread buginator
I was thinking it was time we do another release on the 21st. I don't think we have any blocker bugs left for a 2.3 RC 2 (?) release. We do have a build issue for the cross-compiler. It has the same issue as described here: http://developer.wz2100.net/ticket/1590 We could add --disable-dependen

Re: [warzone2100-dev] Another release is planned on Feb 21st

2010-02-17 Thread buginator
On 2/17/10, Guangcong Luo wrote: > On Wed, Feb 17, 2010 at 6:18 AM, Per Inge Mathisen > wrote: > > http://developer.wz2100.net/ticket/702 > > > > Rearm pads. Not necessary. > > > Not being able to see your rearm pad is a pretty big issue... weren't > you the one who set that one's priority t

Re: [warzone2100-dev] Another release is planned on Feb 21st

2010-02-17 Thread buginator
On 2/17/10, Guangcong Luo wrote: > On Wed, Feb 17, 2010 at 11:24 AM, Christian Ohm wrote: > >> Can anyone think of anything else that needs to be looked at before we > >> do a 2.3 RC 2 (?) release? > > > > But to get to the important questions, why not rc1.5? > > > How's about RC 1a? > RC 1b

[warzone2100-dev] Displaying time / level name on release builds?

2010-02-17 Thread buginator
You know how in debug builds, we show the level name and time? I want to turn this on for release builds as well, so people can be much more specific on what level they really are on, (especially for mac people, since they don't have good crash dumps or logs, and it seems accessing the terminal or

Re: [warzone2100-dev] Remove armour hit sides

2010-02-19 Thread buginator
On 2/18/10, Per Inge Mathisen wrote: > Hello, > > In my effort to clean up the basic engine definitions, I would like > remove the armour hit sides. This was added a while ago by Watermelon, > and to my best knowledge it has never been used for anything useful or > interesting, nor do players

Re: [warzone2100-dev] [Warzone2100-commits] SF.net SVN: warzone2100:[9641] branches/2.3/win32/__BUILD_SCRIPT

2010-02-19 Thread buginator
On 2/19/10, Giel van Schijndel wrote: > > None of these ^^ commits are necessary. > > Using another HOST_TRIPLET than mingw32 can be achieved by specifiying > "HOST_TRIPLET=${whatever_you_want}" as command line argument to > __BUILD_SCRIPT. Well, while not 100% necessary, it didn't really make

[warzone2100-dev] Adding -fstack-protector-all to all builds?

2010-02-19 Thread buginator
For all future builds, starting with 2.3 rc* (insert whatever, 1a/1b/2...) I think we should enable the compiler flag -fstack-protector-all, to help us with stack corruption issues. This would be enabled for both release & debug builds, on all platforms except mac, since it looks like 10.4 doesn't

[warzone2100-dev] 2.3 RC1a postponed. Beta 11 delayed / canceled...

2010-02-21 Thread buginator
This wasn't a good week to release anything it seems. Those last minute patches that we thought would be good, turned out to be not so good. In #warzone2100-games, as soon as people started to get beta 11, they had issues, from crashes to connections problems to not being able to start a game. Th

Re: [warzone2100-dev] 2.3 RC1a postponed. Beta 11 delayed / canceled...

2010-02-22 Thread buginator
On 2/22/10, Guangcong Luo wrote: > On Sun, Feb 21, 2010 at 8:26 PM, buginator wrote: > > Those last minute patches that we thought would be good, turned out to > > be not so good. > > > This statement seems to imply that it was the last-minute patches that > we

Re: [warzone2100-dev] 2.3 RC1a postponed. Beta 11 delayed / canceled...

2010-02-22 Thread buginator
On 2/23/10, buginator wrote: > On 2/22/10, Guangcong Luo wrote: > > > On Sun, Feb 21, 2010 at 8:26 PM, buginator wrote: > > > Those last minute patches that we thought would be good, turned out to > > > be not so good. > > > > > > This stat

[warzone2100-dev] Pre build for Wed. night, and Beta 11a to be tagged on the weekend?

2010-02-23 Thread buginator
A little update, after a few more fixes, and 1 8p game that everyone entered OK, it seems to be working better. My first thought was to make a tag on Wed. night, and then have some testing results (hopefully people would make bug tickets), but I am not sure that is the best course of action. I am

[warzone2100-dev] Beta 11a to be released this Friday night

2010-02-25 Thread buginator
OK, the new plan is to release Beta 11a this Friday night. This should allow more people to play this version over the weekend. The only question I have is, should we force --debug net on or not? ___ Warzone-dev mailing list Warzone-dev@gna.org https:/

[warzone2100-dev] Exception Handler write permission problem

2010-02-26 Thread buginator
We are apparently writing our crash dumps to a access controlled area, and that is CSIDL_PROGRAM_FILES. (or in other words, that is the normal install path of our game). Needless to say, that is bad, and that is also why we have people say they don't see a warzone2100.rpt file in their install di

Re: [warzone2100-dev] Exception Handler write permission problem (revised)

2010-02-26 Thread buginator
We are apparently writing our crash dumps to a access controlled area, and that is CSIDL_PROGRAM_FILES. (or in other words, that is the normal install path of our game). Needless to say, that is bad, and that is also why we have people say they don't see a warzone2100.rpt file in their install di

[warzone2100-dev] Merging shaders into trunk

2010-03-06 Thread buginator
In case people haven't noticed, in this ticket, http://developer.wz2100.net/ticket/851 i-NoD thinks it is ready for the shaders branch to die off, and merge it into trunk. I have no objections to the merging. Anyone else care to comment? ___ Warzone-de

[warzone2100-dev] Implement IdeaTorrent & another 2.3 release ?

2010-03-07 Thread buginator
Since we have a ton of feature requests in trac, I thought it might be nice to start up a IdeaTorrent on our SF site. "IdeaTorrent is what can be defined as an "open innovation software": it lets people submit their ideas, brainstorm them, and vote on them." And for the next 2.3 release, I am thi

Re: [warzone2100-dev] Implement IdeaTorrent & another 2.3 release ?

2010-03-09 Thread buginator
On 3/8/10, Gilles J. Seguin wrote: > On Mon, 2010-03-08 at 01:00 -0500, buginator wrote: > > And for the next 2.3 release, I am thinking we should add more logging > > calls to the template code (hey, it worked for the net code), and even > > a specific console comman

[warzone2100-dev] About include cleanup + mem leaks + a 2.3 release ?

2010-03-13 Thread buginator
Correct me if I am wrong, but shouldn't all our .c / .cpp files have these two includes: #include "lib/framework/wzglobal.h" #include "lib/framework/frame.h" The first one we use to set platform specific defines & compiler options. The second one we use for platform specific overrides. Since tha

[warzone2100-dev] Warzone's direction for 2.3 series

2010-04-04 Thread buginator
Before I left, I was told there was going to be some balance changes, and I haven't seen any for the beta 12 release, besides the penetration fix for the cannons. Is this still going to happen? The autoload of mods. This is still causing issues, as can be seen by trac tickets where people forget

[warzone2100-dev] Warzone's direction for 2.2.4

2010-04-04 Thread buginator
Hey all, just wanted to update a few things about the project. First off, 2.2.4 should be dead. Really. It serves no useful purpose for us at all. The codebase has changed too much, so any bug reports we get on this version is pretty much meaningless in the vast majority of the cases. We should u

[warzone2100-dev] Warzone's direction for Qt branch

2010-04-04 Thread buginator
In case anyone is following, this is the Qt trac ticket: http://developer.wz2100.net/ticket/1549 It does build on all systems now (except for the cross-compiled builds--I haven't had a chance to test that yet). The main problems with Qt is, we have some serious Qt <->openGL issues on all platform

[warzone2100-dev] Warzone's direction for newnet branch

2010-04-04 Thread buginator
This branch is where Cyp has been doing sync fixes to the netcode. It looks like it is working only on 64bit platforms. It fails in 32 bit MSVC builds, and cross-compiled builds. All known compiler flags have been tried, but we can't get it to connect without tons of sync errors. Once those iss

[warzone2100-dev] Always on logs for all platforms

2010-04-04 Thread buginator
As you may/may not know, on windows, we have UAC restrictions on vista / win7, so we (or SDL) can't write to the default path where we install the game into. On macs, it is pretty hidden on how to access the stdout/stderr logs as well. I suggest we always turn on --debugfile with a file called wz

Re: [warzone2100-dev] Warzone's direction for 2.3 series

2010-04-04 Thread buginator
On 4/4/10, Guangcong Luo wrote: > Looks like the ML is back up. Better late then never... > Man, we had a long IRC debate over this. Yeah, this mail was before that conversation. > When Buginator removed the autoload feature in the 2.2 betas, I was > under the impression that

Re: [warzone2100-dev] [Warzone2100-commits] SF.net SVN: warzone2100:[10489] branches/2.3/src/multijoin.c

2010-04-05 Thread buginator
On 4/5/10, Per Inge Mathisen wrote: > On Mon, Apr 5, 2010 at 5:24 AM, wrote: > > Revision: 10489 > > > http://warzone2100.svn.sourceforge.net/warzone2100/?rev=10489&view=rev > > Author: buginator > > Date: 2010-04-05 03:24:05 + (Mon,

Re: [warzone2100-dev] Warzone's direction for 2.2.4

2010-04-05 Thread buginator
On 4/5/10, Kreuvf wrote: > Guangcong Luo wrote: > > I don't think any other software company has done that, ever, which > > should be the first clue that perhaps it's a bad idea. > > We are not a software company. And we do not produce commercial games, so > please > don't compare us with the

Re: [warzone2100-dev] Warzone's direction for 2.3 series

2010-04-05 Thread buginator
On 4/5/10, C yp wrote: > On Mon, Apr 5, 2010 at 2:52 AM, Guangcong Luo wrote: > > Looks like the ML is back up. > > On Sat, Apr 3, 2010 at 2:27 PM, buginator wrote: > > >> ... > >... > > >> The network code, AFAICT, we do not have any network rel

Re: [warzone2100-dev] [Warzone2100-commits] SF.net SVN: warzone2100:[10523] branches/2.3/data/mods/multiplay

2010-04-09 Thread buginator
On 4/9/10, dydo...@users.sourceforge.net wrote: > Revision: 10523 > > http://warzone2100.svn.sourceforge.net/warzone2100/?rev=10523&view=rev > Author: dydo-ai > Date: 2010-04-09 20:04:37 + (Fri, 09 Apr 2010) > > Log Message: > --- > to be replaced with new ones to

Re: [warzone2100-dev] [Warzone2100-commits] SF.net SVN: warzone2100:[10509] trunk/data/mods/multiplay/ntw/stats/body. txt

2010-04-09 Thread buginator
On 4/8/10, delphi...@users.sourceforge.net wrote: > Revision: 10509 > > http://warzone2100.svn.sourceforge.net/warzone2100/?rev=10509&view=rev > Author: Delphinio > Date: 2010-04-08 21:30:12 + (Thu, 08 Apr 2010) > > Log Message: > --- > > > Modified Paths: >

Re: [warzone2100-dev] A really awesome way to use git...

2010-04-09 Thread buginator
On 4/6/10, Per Inge Mathisen wrote: > Apparently, this is _not_ an April's fool: > > http://github.com/blog/626-announcing-svn-support > > They are working on full write support. That should take care of the > I-must-use-a-GUI issue with GIT. So if anyone know a way to ensure we > do not get l

Re: [warzone2100-dev] Warzone's direction for 2.3 series

2010-04-09 Thread buginator
On 4/7/10, Safety0ff wrote: > For fire effects (not only oil well fires,) the _killEffect_ function > retrieves the tile from the position (Vector3f,) and clears the fire bit > of that tile. Effect times seem to use integers. > If you don't believe me then look at the _killEffect_ function, it

Re: [warzone2100-dev] Branching 2.3.1

2010-04-09 Thread buginator
On 4/7/10, Guangcong Luo wrote: > Hey, guys. > > There's been a lot of drama surrounding what should and shouldn't be > committed to 2.3-branch. The things we are postponing to 2.3.1 are > things that deserve testing, and I believe the sooner we get them > tested, the better. > > I think there

Re: [warzone2100-dev] Bugs for next beta

2010-04-09 Thread buginator
On 4/5/10, Per Inge Mathisen wrote: > I did some testing on Windows this Easter, and the crash report > dialog when running in fullscreen is worse than useless, it freezes > the entire game, giving a black screen. This needs to be fixed, or the > dialog can just as well be removed altogether.

Re: [warzone2100-dev] Ticket #1746

2010-04-09 Thread buginator
On 4/7/10, Guangcong Luo wrote: > This whole exercise is moot, though, since Per's preferred solution is > to commit the savegame changes, but just don't do anything with the > new saved data in 2.3.0. > Um... so where does disabling 'autoload' stand? If your patch is *not* committed, then auto

Re: [warzone2100-dev] Beta 13

2010-04-10 Thread buginator
On 4/10/10, Per Inge Mathisen wrote: > I think we should try to push out a beta 13 this weekend. Unless I > hear any objections, I will be tagging tonight. > Huh? What? Wait! Define tonight? Just need to commit http://developer.wz2100.net/ticket/1759, then we should be set.

[warzone2100-dev] Project status after 2.3 release

2010-04-11 Thread buginator
It is getting very close to the release of 2.3, so I figure we should sort a few things out before we hit the launch button. Trac tickets basically boil down into tickets that are: a) useless. (can't replicate, no good info in said ticket) b) general corruption. (can't replicate) c) other corrup

Re: [warzone2100-dev] Warzone's direction for 2.3 series

2010-04-12 Thread buginator
On 4/4/10, Guangcong Luo wrote: > I think the bMultiMessages change I committed may have made the sync > worse, so I guess it should be reverted once again. This is really > frustrating, because it really does fix seven different bugs relating > to bMultiPlayer having an unexpected value. > >

Re: [warzone2100-dev] Warzone's direction for 2.3 series

2010-04-12 Thread buginator
On 4/12/10, Guangcong Luo wrote: > On Mon, Apr 12, 2010 at 8:21 PM, buginator wrote: > > This hasn't been reverted yet any reason why not? > > If you don't have time, then specify which revisions need to be > > reverted, and I can do it. > > >

[warzone2100-dev] 2.3 RC 1a to tag on 4/16 or 4/17

2010-04-13 Thread buginator
Barring any other showstopping bugs, or objections, I think we should tag 2.3 RC1a late Friday night or early Saturday morning to get this out to as many of our current testers as possible before they start their weekend gaming sessions. All mod authors, please make whatever changes you need to ma

[warzone2100-dev] version strings

2010-04-14 Thread buginator
I was adding a version check to the lobby, to inform users that a new client is available. The question I have is, currently we (ab)use the version string to include mod information. ie: "2.3 svn" becomes "2.3 svn, mod:blah blah blah" (1)If we still want to go with what is currently done, then it

Re: [warzone2100-dev] Project status after 2.3 release

2010-04-14 Thread buginator
On 4/11/10, Guangcong Luo wrote: > Anyway, w.r.t. to our future, I have a new idea: We branch 2.4 right > before merging in Qt and newnet. Trunk is reasonably stable, and the > last time we branched trunk was over a year ago. Getting current trunk > to stable should be a reasonably fast proces

Re: [warzone2100-dev] 2.3 RC 1a to tag on 4/16 or 4/17

2010-04-14 Thread buginator
On 4/14/10, Christian Ohm wrote: > I've got the Playstation music track now (in its original 37800 Hz), and could > add the Vorbis version (upsampled to 44100 Hz of course) to the music folder. > Any objections? I personally have no objections, but the PSX stuff is all in that gray area of lega

Re: [warzone2100-dev] 2.3 RC 1a to tag on 4/16 or 4/17

2010-04-14 Thread buginator
On 4/14/10, Christian Ohm wrote: > http://developer.wz2100.net/ticket/251 > > If we can find a nice way to test if we're loading a game (game time if that > works, or something else), this should be included I tink. > Anyone got some good savegames we can test this patch with?

[warzone2100-dev] 2.3 code freeze until 2.3.0 branch, 2.3.0 release target date 4/24/10

2010-04-17 Thread buginator
Let's try this again, 2.3 is in a code freeze, and ONLY show stopping bugs will be fixed. It was suggested that we branch 2.3.0 from svn head, once we know the status of the Dydo changes. If the Dydo changes can't be rectified, then we will do what we did the the 2.3_rc1a tag. The 2.3.0 release

[warzone2100-dev] Getting the word out about 2.3.0 ?

2010-04-17 Thread buginator
Once 2.3.0 has been released, we need to get the word out to all the sites that we hit before, and all the others that link to the 2.2.x series. For now, all old links have been broken, except for these: http://download.gna.org/warzone/releases/ http://download.gna.org/warzone/snapshots/ Whoever

Re: [warzone2100-dev] 2.3 code freeze until 2.3.0 branch, 2.3.0 release target date 4/24/10

2010-04-17 Thread buginator
On 4/17/10, Christian Ohm wrote: > On Saturday, 17 April 2010 at 15:45, buginator wrote: > > Let's try this again, 2.3 is in a code freeze, and ONLY show stopping > > bugs will be fixed. > > > > It was suggested that we branch 2.3.0 from svn head, once we

[warzone2100-dev] branch/2.3 now unfrozen, tags/2.3.0 has been created

2010-04-18 Thread buginator
Ok, branch/2.3 has been unfrozen with the creation of tag/2.3.0. ** DO NOT COMMIT into tags/2.3.0 without ML or IRC approval *** ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev

Re: [warzone2100-dev] [Warzone2100-commits] SF.net SVN: warzone2100:[10523] branches/2.3/data/mods/multiplay

2010-04-19 Thread buginator
On 4/12/10, Dylan Dog wrote: > ok, sorry but I have very low knowledge about svn. > > I had downloaded the two mentioned files, modified them locally then when I > tried to "commit" them TortoiseSVN always gave me an error back ("file > already exists" ??) which avoided the update on the branch. Th

Re: [warzone2100-dev] getting user art in the game

2010-04-20 Thread buginator
On 4/20/10, Per Inge Mathisen wrote: > On Tue, Apr 20, 2010 at 11:36 PM, Stephen Swaney wrote: > > An idea worth stealing? > > Indeed. > > Note that such images should not have the logo written into the image > itself, as we draw it over the image anyway. Nor we need to pretend > Pumpkin Stud

Re: [warzone2100-dev] getting user art in the game

2010-04-20 Thread buginator
On 4/20/10, Guangcong Luo wrote: > As I've mentioned several times, there are ways of gesturing "thanks" > that don't mislead users into thinking Pumpkin Studios made 2.3 (and > since they're defunct, Warzone must be a dead game). I mean, there is > something wrong if "Pumpkin Studios" gets mor

Re: [warzone2100-dev] Proposed patches for tags/2.3.0

2010-04-22 Thread buginator
On 4/22/10, Christian Ohm wrote: > On Sunday, 18 April 2010 at 13:21, buginator wrote: > > ** DO NOT COMMIT into tags/2.3.0 without ML or IRC approval *** > > Things we might possibly want to include in 2.3.0: > > http://developer.wz2100.net/changeset/10659 - fix com

Re: [warzone2100-dev] [Warzone2100-commits] SF.net SVN: warzone2100:[10689] trunk/macosx/Resources

2010-04-23 Thread buginator
On 4/23/10, dak...@users.sourceforge.net wrote: > Revision: 10689 > > http://warzone2100.svn.sourceforge.net/warzone2100/?rev=10689&view=rev > Author: dak180 > Date: 2010-04-23 04:12:19 + (Fri, 23 Apr 2010) > > Log Message: > --- > Distinguish between different typ

[warzone2100-dev] Disable mutli-turrets (again) for 2.3.0 ?

2010-04-23 Thread buginator
Since we still have issues with multi-turrets, that have never been fixed, I think we should disable them once again for 2.3.0. Main issues, it still can look like crap, and the range issue for the turrets, and I am sure there are some other issues hiding. Objections ? ___

Re: [warzone2100-dev] Disable mutli-turrets (again) for 2.3.0 ?

2010-04-23 Thread buginator
On 4/23/10, Guangcong Luo wrote: > On Fri, Apr 23, 2010 at 7:21 PM, buginator wrote: > > Since we still have issues with multi-turrets, that have never been > > fixed, I think we should disable them once again for 2.3.0. > > Main issues, it still can look like crap, and th

[warzone2100-dev] 2.3.0 has been released

2010-04-24 Thread buginator
2.3.0 has been released, windows & source tarball have been completed, and the mac builds are pending. Thanks for all the hard work you all have done in getting 2.3.0 out the door. We now move on to better things. :) Here is a full changelog for 2.3.0 (you can thank me later!) 2010-04-24: Ver

[warzone2100-dev] Pruning a unnecessary directory

2010-04-24 Thread buginator
If no objections, since we don't use it, we should kill \pkg\dpkg. Any objections? Looks like it was used when we made debian builds, but all the files in that directory are pretty much old / unnecessary. ___ Warzone-dev mailing list Warzone-dev@gna.or

[warzone2100-dev] lack of syncs for newnet / lua / Qt

2010-04-24 Thread buginator
Since the sync bot is MIA again, (and it looks like it was skipping patches as well) would it be ok to start doing mass syncs to those branches, or will that hose up the history when we merge things back to trunk ? Is there a better way to handle syncs ? __

Re: [warzone2100-dev] Rename .img files to .csv?

2010-04-26 Thread buginator
On 4/26/10, Zarel wrote: > On Mon, Apr 26, 2010 at 4:19 PM, Per Inge Mathisen > wrote: > > It will break mods... - Per > And if one does, well, my recent cursor additions (not to mention your > new icons for ECM stuff - at least, I think they're yours) will break > it anyway. :P > > It's s

[warzone2100-dev] Qt branch issues

2010-04-27 Thread buginator
Because of the way some of the merges were done in this branch, it is very difficult to find out what the exact change was that broke some stuff in qt. I think it would be much easier for us to rebase qt from trunk, and apply the qt specific patches to a new branch. I count around 74 patches, wit

Re: [warzone2100-dev] 2.3.0 has been released

2010-04-27 Thread buginator
On 4/27/10, Dylan Dog wrote: > Hello > > Sorry for the late response to you PM on the forum. > Yes, please help me to close the current DyDo thread, I`ll then open a new > one. I do not know how to close the actual thread but it seems I do not have > the rights... Done. > Which folder on svn I

Re: [warzone2100-dev] Let's git going

2010-04-28 Thread buginator
On 4/28/10, dak180 wrote: > On Apr 28, 2010, at 2:58 AM, Per Inge Mathisen wrote: > > > That leaves only > > the question of whether git is good/user-friendly enough on > > Windows/Mac. > > For a number of reasons I would prefer mercurial, of which I think the most > important is that the mac g

Re: [warzone2100-dev] Let's git going

2010-04-29 Thread buginator
On 4/29/10, Christian Ohm wrote: > On Wednesday, 28 April 2010 at 18:34, NoName wrote: > > I do still vote for Mercurial. > > > How about accessing a git repo with hg? > > http://candidcode.com/2010/01/12/a-guide-to-converting-from-mercurial-hg-to-git-on-a-windows-client/ > I belive you can do

[warzone2100-dev] More on fixing the Qt branch

2010-04-29 Thread buginator
After some more tinkering with the code, I finally found the issue that MSVC was having. In short, a bool in c is a int, and in c++ a bool !=int. It was always returning 256 on false, and -858993663 on true. For those that don't see what that is, here: false = 0x0100, true = 0xcc01 ma

Re: [warzone2100-dev] More on fixing the Qt branch

2010-04-30 Thread buginator
On 4/30/10, Christian Ohm wrote: > On Thursday, 29 April 2010 at 22:45, buginator wrote: > > After some more tinkering with the code, I finally found the issue > > that MSVC was having. In short, a bool in c is a int, and in c++ a > > bool !=int. It was always return

Re: [warzone2100-dev] git test repo active (also for hg/bzr users)

2010-05-04 Thread buginator
On 5/3/10, Gilles J. Seguin wrote: > what is missing from > git://gitorious.org/warzone2100/mainline.git > ? > what is problematic ? > who is lost ? the administrators or the users > Are you asking if we are using that? Officially, not really. We are still using SVN. _

Re: [warzone2100-dev] git test repo active (also for hg/bzr users)

2010-05-04 Thread buginator
On 5/3/10, Christian Ohm wrote: > > Since there seems to be no winner in the RCS discussion, we have basically > two > choices: 1. stay with SVN, 2. Decide on one of them (as backend at least). > From > what I've read, it seems it is easily possible to access a git repository > with > both

Re: [warzone2100-dev] [Warzone 2100 Trac] #1270: Random freezes happens in some games.

2010-05-05 Thread buginator
On 5/5/10, james wrote: > It happening with me in a single player skirmish mode with > sk-cocktate. and they are getting longer the longer the game goes on. > its at 6:20 hours but I have saved and rebooted several times and it > just keeps getting worse. the mouse still moves around the screen

Re: [warzone2100-dev] [Warzone 2100 Trac] #1270: Random freezes happens in some games.

2010-05-07 Thread buginator
On 5/7/10, Kronos wrote: > while i didn't wanted to extend this discussion here, the same problem > happens here, and worse, it was happening at multi-play. Last time it > happened, the game completely froze off, and the only way to exit the game > was rebooting my machine. > > Seriously, I don't b

Re: [warzone2100-dev] More on fixing the Qt branch

2010-05-08 Thread buginator
On 4/30/10, buginator wrote: > On 4/30/10, Christian Ohm wrote: > > On Thursday, 29 April 2010 at 22:45, buginator wrote: > > > After some more tinkering with the code, I finally found the issue > > > that MSVC was having. In short, a bool in c is a int, and

[warzone2100-dev] hg (mercurial) test repo is up and running @ SourceForge, bzr is up and running @ LaunchPad

2010-05-08 Thread buginator
We have a hg test repo of the Qt branch up and running here: ssh://usern...@warzone2100.hg.sourceforge.net/hgroot/warzone2100/qt_test Have at it. :) If you never used if before, then this is a good tutorial: http://hginit.com/ (everyone says this is the best one) If you rather watch a video fro

  1   2   3   >