[warzone2100-dev] Replace 3 Warzone txt files with DyDo ones
Hello Actually DyDo uses some templates which is not included in the standard ones. Therefore I have to modify following files: stats/templates.txt, stats/assignweapons.txt and messages/strings/names.txt what I have done is just adding some rows to the standard files. I have not removed any rows. I was wondering if we could replace the warzone files with the ones I use for DyDo. This would allow to play with DyDo and other mods which uses such templates (obviously the other modders should updated their files). Another advantage is that by doing this I do not have to care anymore about any new update of such files like it happened recently. ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] Replace 3 Warzone txt files with DyDo ones
On Fri, Feb 26, 2010 at 11:46 AM, DylanDog d...@obooma.net wrote: Actually DyDo uses some templates which is not included in the standard ones. Therefore I have to modify following files: stats/templates.txt, stats/assignweapons.txt and messages/strings/names.txt what I have done is just adding some rows to the standard files. I have not removed any rows. I was wondering if we could replace the warzone files with the ones I use for DyDo. That is a good idea. - Per ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
[warzone2100-dev] Clang analysis results for 2.3
A build with the Clang static analyzer (scan-build ./configure scan-build make) gave the following output: http://the_cybersphinx.users.sourceforge.net/warzone-2.3-r10022/ A lot of the results are false positives because of the... creative... use of pointers, but a lot of valid stuff as well (for example, the deltaX stuff can still divide by 0). Sourceforge says they have no quotas for their web space, let's hope that includes 200 MB of formatted source... ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] Clang analysis results for 2.3
On Feb 26, 2010, at 2:57 PM, Christian Ohm wrote: A build with the Clang static analyzer (scan-build ./configure scan-build make) gave the following output: http://the_cybersphinx.users.sourceforge.net/warzone-2.3-r10022/ A lot of the results are false positives because of the... creative... use of pointers, but a lot of valid stuff as well (for example, the deltaX stuff can still divide by 0). Sourceforge says they have no quotas for their web space, let's hope that includes 200 MB of formatted source... ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev I did something similar for trunk a while back: http://dak180.users.sourceforge.net/throwfiles/m6afd7c17.txt (somewhere between 9784 and 9795 or thereabouts) Note though, that the Clang static analyzer cannot yet parse c++ code so anything that depends on a cpp file is likely a false positive. -- My Web Sites: http://dak180.users.sourceforge.net/ smime.p7s Description: S/MIME cryptographic signature ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
[warzone2100-dev] [Warzone 2100 Trac] #1639: AI allies steal oil derricks
#1639: AI allies steal oil derricks --+- Reporter: jdie...@… |Type: bug Status: new|Priority: minor Milestone: unspecified| Component: Engine: Scripting / AI Version: unspecified|Keywords: Operating_system: All/Non-Specific | Blockedby: Blocking: | --+- When the enemy destroys your oil derricks, allied AI players will attempt to steal them once they stop burning. This is extremely frustrating when you are unable to capture enemy derricks and continually losing your own to your supposed allies. It might make more sense to have allied AI *not* build on oil resources that were once owned by its allies, at least for a respectable amount of time (say five minutes) after the resources have stopped burning. -- Ticket URL: http://developer.wz2100.net/ticket/1639 Warzone 2100 Trac http://developer.wz2100.net/ The Warzone 2100 Project ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] [Warzone2100-commits] SF.net SVN: warzone2100:[10028] trunk
On Friday, 26 February 2010 at 21:50, the_cybersph...@users.sourceforge.net wrote: Revision: 10028 http://warzone2100.svn.sourceforge.net/warzone2100/?rev=10028view=rev Author: the_cybersphinx Date: 2010-02-26 21:50:37 + (Fri, 26 Feb 2010) Log Message: --- Use the system's version of GLee, if available. Require at least 5.4, since that's what we have included. If not detected, we use the integrated copy as before. Modified Paths: -- trunk/configure.ac trunk/lib/ivis_opengl/Makefile.am trunk/lib/ivis_opengl/pieblitfunc.c trunk/lib/ivis_opengl/piedraw.c trunk/lib/ivis_opengl/piefunc.c trunk/lib/ivis_opengl/piematrix.c trunk/lib/ivis_opengl/piemode.c trunk/lib/ivis_opengl/piestate.c trunk/lib/ivis_opengl/screen.c trunk/lib/ivis_opengl/tex.c trunk/lib/ivis_opengl/textdraw.c trunk/lib/sequence/Makefile.am trunk/lib/sequence/sequence.c trunk/src/Makefile.am trunk/src/multiint.c trunk/src/texture.c Oh, I've changed the includes for GLee.h to GLee.h, so I guess the other build systems have to be fixed now. For lib/sequence/ and src/, add lib/ivis_opengl/ to the include dirs. I also intend to commit this to 2.3 soon, after the broken stuff is fixed. ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
[warzone2100-dev] Exception Handler write permission problem
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 directory, when the game crashes. We should be using CSIDL_PERSONAL for crash dumps, since this one is : User-specific game files that are read and modified and can be manipulated outside of the game context. Therefore, if no objections, I will be making this change to our crash handler, so it dumps everything in: C:\Users\user name\Documents\Warzone2100 Will that be OK with everyone? ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] Exception Handler write permission problem (revised)
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 directory, when the game crashes. We should be using CSIDL_PERSONAL for crash dumps, since this one is : User-specific game files that are read and modified and can be manipulated outside of the game context. Therefore, if no objections, I will be making this change to our crash handler, so it dumps everything in: C:\Users\user name\Documents\Warzone2100 This is where they talk about this stuff: http://msdn.microsoft.com/en-us/library/ee419001%28VS.85%29.aspx Will that be OK with everyone? ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
