On 2/17/10, Guangcong Luo <za...@wz2100.net> wrote: > On Wed, Feb 17, 2010 at 6:18 AM, Per Inge Mathisen > <per.mathi...@gmail.com> 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 to blocker? >
This only happens on 'ramps' right? > > >> My fix for #1268, as well. > > > > http://developer.wz2100.net/ticket/1268 (sync issues) > > > > There is no fix there. It sounds like a general problem. > > > Nah, I know the specific cause and how to fix it. No big deal either > way; I'll probably fix it before the 21st. > OK... > > > http://developer.wz2100.net/ticket/1039 WSS bug. I thought there was a > > working work-around for this already? I see no new fix there. > > > No, we only committed the part of the work-around where we removed a > feature. The other parts of the workaround were never committed (or > coded, for that matter). > Never looked at this... > > > http://developer.wz2100.net/ticket/1589 has to be fixed (oil derricks > > disappearing). > > > Agreed > *If* this is the result of a player(s) leaving, then it was fixed. If this is the result of something else, then, I dunno. The ticket doesn't give enough info. > >> I have some movement-code fixes for #760, but although they're > >> theoretically better, they practically seem to have as many problems > >> as the old code. > > > > Each time we touch this code, it gets worse. > > I do have a few leads now, though. > All the movement code is very hard to debug, I rather just leave it as is, and put you 'fix' in the next beta releases. > >> We should really look at fixing #1066. > > > > http://developer.wz2100.net/ticket/1066 (can't use non-ascii chars > > with physfs2) - why is this important? > > > Because it prevents people whose usernames contain non-ASCII chars > from playing Warzone with default settings. > This is only a problem on linux, if they are using physfs 2.0 On mac & windows, we don't use that. I rather not mess with the code more, and possibly having more bugs in a RC isn't a good idea. > > >> #1236 should also have something done about it. > > > > http://developer.wz2100.net/ticket/1236 (limits) - this has been > > semi-broken for years, why do we need to start fixing right before > > release? It should be working for all players now... for the AI, well, again, I rather not introduce things in this release that could make things worse. > > http://developer.wz2100.net/ticket/1340 (mouse cursor trapped in some > > cases) - not important > > > Quite important, for Windows users. Being able to alt+tab out of > Warzone is a pretty important feature. This is a SDL windows bug. I upgrade to 1.2.14, and saw the issue. Fell back to 1.2.13, and the issue wasn't there. > > http://developer.wz2100.net/ticket/1581 (power jumps to max) - we have > > no leads as to cause, and iirc only reported once > > > I have a few ideas (UDWORD underflow...) > I tried the savegames, and didn't notice this bug. > > http://developer.wz2100.net/ticket/1469 (power upgrade is downgrade) > > this is campaign only? maybe should be fixed first. > > > No, I've definitely reproduced it in skirmish. > How? > > http://developer.wz2100.net/ticket/1536 (saving/loading with > > multi-lassat mod) that is simply not supported > > > It's an easy fix, anyway. > Yes, and not really needed. > > http://developer.wz2100.net/ticket/1472 (double click truck) feature > > > Arguably a bugfix. :P It's minor enough not to cause too may problems, > and it modernizes the game. > save the 'bugfix' for 2.3.1 > > > http://developer.wz2100.net/ticket/1531 (rail darts do not behave > > correctly) should probably be fixed > > Agreed. > Projectile code? _______________________________________________ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
