[Warzone-dev] [Warzone 2100 Trac] #834: Translation update: Russian
#834: Translation update: Russian -+-- Reporter: Maxim raptor9...@… |Type: enhancement Status: new |Priority: major Milestone: 2.2.2 | Component: Data: Translation Version: 2.2.1 |Keywords: Operating_system: Microsoft Windows | Blockedby: Blocking:| -+-- This is last Russian translation update for Warzone versions 2.2.x. Many-Many mistakes were corrected here. Translated: 100% Fuzzy translated: 0 -- Ticket URL: http://developer.wz2100.net/ticket/834 Warzone 2100 Trac http://developer.wz2100.net/ The Warzone 2100 Resurrection Project ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] [Warzone 2100 Trac] #340: Sensors and Jammers
#340: Sensors and Jammers ---+ Reporter: Per| Owner: Per Type: enhancement| Status: accepted Priority: major | Milestone: 2.3 Component: Engine: other |Version: svn/trunk Keywords: ecm sensor | Operating_system: All/Non-Specific Blockedby: | Blocking: ---+ Comment(by elio): the radar detector works like a cb-tower, it attacks radar turrets with its assigned units or bunkers (mortar/artillery) -- Ticket URL: http://developer.wz2100.net/ticket/340#comment:11 Warzone 2100 Trac http://developer.wz2100.net/ The Warzone 2100 Resurrection Project ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] [Warzone 2100 Trac] #756: Crash if map preview during map download
#756: Crash if map preview during map download +--- Reporter: Per | Owner: Type: defect | Status: new Priority: minor | Milestone: 2.2.2 Component: Engine: Networking |Version: 2.2.1 Keywords: map preview | Operating_system: All/Non-Specific Blockedby: | Blocking: +--- Comment(by anonymous): The idea behind the patch is that the last file chunk (recv function returns true) will turn the button on again. We should test it before committing. -- Ticket URL: http://developer.wz2100.net/ticket/756#comment:2 Warzone 2100 Trac http://developer.wz2100.net/ The Warzone 2100 Resurrection Project ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] [Warzone 2100 Trac] #340: Sensors and Jammers
#340: Sensors and Jammers ---+ Reporter: Per| Owner: Per Type: enhancement| Status: accepted Priority: major | Milestone: 2.3 Component: Engine: other |Version: svn/trunk Keywords: ecm sensor | Operating_system: All/Non-Specific Blockedby: | Blocking: ---+ Comment(by Zarel): In addition, it detects radar turrets nearby, which can be useful to find where exactly the sensor bombarding you with artillery is. Oh, and, this really belongs in the forums, not in a bug ticket. -- Ticket URL: http://developer.wz2100.net/ticket/340#comment:12 Warzone 2100 Trac http://developer.wz2100.net/ The Warzone 2100 Resurrection Project ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] Making trac friendlier?
On Sat, Aug 22, 2009 at 8:50 AM, Christian Ohmchr@gmx.net wrote: And if View Tickets brought up the list of open tickets, newest first instead of the current list of mostly useless reports, it might actually be useful. Is there a way to modify this report list? It always just distracted me with its pretence of usefulness, and I made a custom bookmark to get a simple bug list without being bothered by it. Well, Timeline is a mostly useful list of the latest tickets, and it's only one click. That's what I use a lot of the time. :P Otherwise, I generally do View Tickets, click the first report, and click ticket number twice (to sort descending). So it's not _completely_ useless. Oh, and to go completely off-topic, our wiki is currently listed under development, but also contains user stuff. It would be very nice to have the user side more visible, maybe then people read it and start adding info to it. We have user stuff in the wiki? Any user stuff that's in the wiki should also be in the Guide... -Zarel ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] SF svn repo upgrade to 1.6.4?
On Fri, Aug 21, 2009 at 07:06:59PM -0400, bugs buggy wrote: *After* the 2.2.2 release, I was thinking we should upgrade our SVN repo( svnadmin upgrade) to svn version 1.6.4. Any objections to this? It makes quite a few things easier on us (merges), see the release notes here: Looks worthwhile. Let's do it! -- Stephen Swaney sswa...@centurytel.net ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] [Warzone 2100 Trac] #340: Sensors and Jammers
#340: Sensors and Jammers ---+ Reporter: Per| Owner: Per Type: enhancement| Status: accepted Priority: major | Milestone: 2.3 Component: Engine: other |Version: svn/trunk Keywords: ecm sensor | Operating_system: All/Non-Specific Blockedby: | Blocking: ---+ Comment(by anonymous): well, going back to bug thing, units assigned to a mobile radar should not move if the radar is just moving, since all your arty units will try to follow, which moves all the long range units outside of any safe zone you might have for them. And so it kills the usefulness of mobile arty units assigned to mobile sensor since all move together, its better to send a constructor to build a sensor tower then, since your arty wont move out. Another thing curious I've come to notice is the following: You have a sensor tower near enemy base... and you build a sensor mobile unit and its sitting at your base. Then you have lots of arty units assigned to your mobile sensor, if you target with you mobile sensor something in range of the sensor tower, the mobile unit wont even move, it targets the enemy, and the arty assigned to the mobile sensor fires like if it where assigned to the sensor tower in range. Is this normal? And another final thing, how come the radar detector only comes in crappy wooden tower? where is the hardened radar detector tower? -- Ticket URL: http://developer.wz2100.net/ticket/340#comment:13 Warzone 2100 Trac http://developer.wz2100.net/ The Warzone 2100 Resurrection Project ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
[Warzone-dev] [Warzone 2100 Trac] #835: WZ compilation using MinGW [patch]
#835: WZ compilation using MinGW [patch] --+- Reporter: i-NoD |Type: defect Status: new|Priority: major Milestone: unspecified| Component: Build system Version: svn/trunk |Keywords: Operating_system: Microsoft Windows | Blockedby: Blocking: | --+- Challenges and iniparser for MinGW. Look [http://forums.wz2100.net/viewtopic.php?f=6t=3602 here]. -- Ticket URL: http://developer.wz2100.net/ticket/835 Warzone 2100 Trac http://developer.wz2100.net/ The Warzone 2100 Resurrection Project ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] Making trac friendlier?
Am Samstag, 22. August 2009 14:50:46 schrieb Christian Ohm: On Friday, 21 August 2009 at 23:11, Zarel wrote: On Fri, Aug 21, 2009 at 9:16 PM, Stephen Swaney sswa...@centurytel.net wrote: Right now, we overload 'enhancement' to mean both patches and feature requests. Ideally, we want to be able to separate the bugs and patches from feature requests which are often useless. The last time I brought this up, the reply was to add [patch] to the subject line. [...] Seems to work well enough like that. Except that filtering for that is harder. A direct trac type would be nice. Basically if we want non-bugs in trac, we need an easy way to get a list of outstanding issues without the noise (and the contrary things to waste time on when bored list). That was my intention when I suggested making needinfo a priority (maybe not the best solution, but easy to do without plugins), you can just filter it out while keeping the bug open (autoclosing with the pending plugin might be nice, though). I think Trac allows tagging with custom keywords. If we allow only devs to do that, we could use it for this purpose, too. (See my last mail on the subject.) signature.asc Description: This is a digitally signed message part. ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
[Warzone-dev] [Warzone 2100 Trac] #836: beta11 crashes after mission success summary - savegames also
#836: beta11 crashes after mission success summary - savegames also +--- Reporter: dch |Type: defect Status: new |Priority: major Milestone: unspecified | Component: other Version: 2.2.1|Keywords: Operating_system: Mac OS | Blockedby: Blocking: | +--- i have a bunch of saved waypoints during this mission. all of them end up crashing @ end of mission. will retest with 2.2.2 release and update ticket. -- Ticket URL: http://developer.wz2100.net/ticket/836 Warzone 2100 Trac http://developer.wz2100.net/ The Warzone 2100 Resurrection Project ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
[Warzone-dev] 2.2.2 is now released!
The developer staff brings you the release of Warzone 2100 2.2.2. The most noticeable fix in this release is that people should have significantly fewer crashes, as well as less problems with sounds and numerous other fixes in this release as well. For a complete list see the Changelog. NOTE to builders, we need Fedora Mac builds please. :) ChangeLog: 2009-08-23: Version 2.2.2 * General: * Change: Add the ability of allied players to share sensors (ticket:636, r7900) * Change: Stop rotation when Continue is pressed after winning a multiplayer/skirmish game (r7887) * Change: Show when a game was saved in a tooltip on the loading screen. (r7864, ticket:682) * Fix: Cannot display more than one game from lobby. Also fix a lobby display issue. (r7839, ticket:691) * Fix: Various checks and workarounds to make game run more stable (r7836, r7894, r7889, r7883, r7881, r7851, r7847, r7842, r7822, r7910 / ticket:759) * Fix: Crash due to path length overflow (r7916, ticket:738, ticket:765) * Fix: Bug that caused some keyboard shortcuts to be unusable in multiplayer since they were considered cheats (r7856) * Fix: Verify that our target is still around before doing fire support with it. (r7910, ticket:759) * Fix: Fix crash length overflow by capping path lengths to max 255 nodes. (r7916, ticket:738) * Fix: Fix a typo, we wanted to display ??? when ping is =2000 (r7922) * Fix: Fix camera bug in warcam code. Patch by i-NoD (r7924, ticket:757) * Fix: General order/action code cleanup (r7926) * Fix: Fix segfault when trying to read target of droid with no target in aiUpdateStructure (r7928) * Fix: Use _NSIG in the exceptionhandler if available for *BSD compatibility. (r7972, ticket:818) * Fix: Add correct linker flags for openbsd to configure. (r7974, ticket:819) * Fix: Disable locales without translation. (r7969, ticket:813) * Fix: NTW updated to 1.8.7 (r7998 - r8009) * Fix: When babas are burning, we always play the scream now. (r8025, ticket:830) * Fix: Make sure we have a valid color choice for our SP game, when we are coming from a MP game. (r8032) * Translations: * Fix: Commit Portuguese translation. (r7943, ticket:783) * Fix: Updated translations (r7880, r7877, r7875, r7871, r7868, r7863, r7861) * Graphics: * Fix: Increase video buffer size from 4K to 256K. This fixes playback of videos with a bitrate larger than ~2000kbps. (r7981) * Change: Add a north pointer for the rotating radar. (r8013, ticket:769) * Sound: * Fix: Fixes the removal of unused (sound) sources. (r8012, r8026, ticket:770) ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
