irclog2html for #bzflag on 20041130

00:02.08*** join/#bzflag sgk284 (~sgk284@ACAB88FD.ipt.aol.com)
00:05.36*** join/#bzflag Mikkel (~Mikkel@h000d93444438.ne.client2.attbi.com)
00:06.19*** join/#bzflag BZFlag6798 (www-data@69.28.129.166)
00:06.51*** join/#bzflag Nemisis-1 (www-data@69.28.129.166)
00:08.06Nemisis-1does anyone know if they have a new version of bzflag up yet?
00:08.33blast007the latest non-dev version is 1.10.8
00:08.50Nemisis-1ok
00:08.52Nemisis-1nvm then
00:09.00blast007there is however, and 1.11.24 copy on bzbb
00:09.09blast007s/and/a/
00:09.27Nemisis-1i tried going to bzbb but its down for some reason
00:09.30blast0071.11 is the current development version
00:10.01blast007ah, yes...think pat is working on something
00:10.07Nemisis-1ok
00:10.15Nemisis-1do you know when itll be back up?
00:10.20blast007they had to transfer it to a different server
00:10.24blast007nope, not sure
00:10.28Nemisis-1ok
00:10.34Nemisis-1thanx
00:25.51Patlabor221I'll move the bzbb version to a public folder soon
00:29.04*** join/#bzflag wizart (~wizart@dsl-084-057-095-102.arcor-ip.net)
00:29.08blast007k
00:29.46*** join/#bzflag nullified (~shess@138.9.200.8)
00:54.52*** join/#bzflag nullified (~shess@138.9.200.8)
01:07.51Patlabor221http://my.bzflag.org/builds/1.11/ <------- for those that need em
01:08.16creeperz1.11 the new cvs?
01:08.16*** topic/#bzflag by Patlabor221 -> http://BZFlag.org/ || http://bzbb.bzflag.org/ || http://stats.bzflag.org/ || http://cia.navi.cx/stats/project/BZFlag || Universidad de los Andes, Colombia http://agamenon.uniandes.edu.co/~pfiguero/CG/ || BZFlag went SF Platinum on/near November 26th! || 1.11.x builds http://my.bzflag.org/builds/1.11/
01:08.24Patlabor2211.11.24
01:08.30creeperzi see
01:11.44blast007I can't remember...is 1.11 becoming 1.12, or 2.0?
01:13.56amathis1.12
01:14.07blast007k
01:14.41blast007I remember some discussion of calling it 2.0, but couldn't recall what decision was made  ;)
01:17.40*** join/#bzflag macaddict89 (www-data@69.28.129.166)
01:19.14macaddict89~bzfquery macaddictslair.homeip.net:5154
01:19.27*** part/#bzflag macaddict89 (www-data@69.28.129.166)
01:20.36nullifiedwe have 2.0 scheduled for release?
01:21.09amathishmm
01:21.11amathisam I wrong?
01:21.16amathisI was under the impression it was 1.12
01:21.28amathisPatlabor221: learner, *ping*
01:21.33nullifieddunno...  i thought 1.12 was scheduled...
01:21.49blast007I know it was 1.12 in the beginning...not sure now
01:21.54amathisthat is what I thought.
01:22.36nullifiedoh ok :)
01:22.50nullifiedhe got my hopes up for a min :)
01:24.15blast007sigh...I'm seeing reference to "1.12" _and_ "2.0" in my logs  >.<
01:26.14*** join/#bzflag Pimpinella (~frank@p5082073C.dip0.t-ipconnect.de)
01:33.56*** join/#bzflag MeBigFatGuy (dave@balt-209-150-117-143.dynamic-dial.qis.net)
01:57.08*** join/#bzflag nullified (~nullified@138.9.200.8)
02:07.21*** join/#bzflag nullified (~nullified@138.9.200.8)
02:07.40*** part/#bzflag nullified (~nullified@138.9.200.8)
02:12.03*** join/#bzflag [dmp]_ (~dennis@port151.ds1-aboes.adsl.cybercity.dk)
02:12.14MeBigFatGuy...if only...
02:13.27Patlabor221bzbb is back up
02:13.37blast007Patlabor221: cool  :)
02:54.30CIA-3opencombat: 03jeffm2501 * 10SGL/ (9 files in 4 dirs): make font manager read text based fmt files for those "other" endian fellows.
03:11.03*** join/#bzflag Mikkel (~Mikkel@h000d93444438.ne.client2.attbi.com)
03:14.27*** join/#bzflag nullified (~shess@138.9.200.8)
03:16.42*** join/#bzflag bryjen (~bryjen@2002:45a6:8672:0:0:0:0:1)
03:23.05CIA-3opencombat: 03jeffm2501 * 10SGL/ (4 files in 2 dirs):
03:23.05CIA-3opencombat: fix font drawing ( need full texture path )
03:23.07CIA-3opencombat: hook up some text drawing in sample
03:23.09CIA-3opencombat: hook up some mouse input in sample
03:44.32*** join/#bzflag shorty114 (~shorty114@shorty114.user)
03:51.54*** join/#bzflag bouncingtank (~shess@138.9.200.8)
03:57.48*** join/#bzflag mmu_man (revol@ALyon-112-1-11-235.w80-14.abo.wanadoo.fr)
04:08.33*** join/#bzflag patlabor221 (~jeffm@Patlabor221.active.supporter.pdpc)
04:08.33*** mode/#bzflag [+o patlabor221] by ChanServ
04:14.49*** join/#bzflag Aribeth (~Aribeth@dsl081-067-057.sfo1.dsl.speakeasy.net)
04:21.05CIA-3opencombat: 03jeffm2501 * 10SGL/sample/Test.cpp: create temp class for silly GCC
05:04.43*** join/#bzflag sgk284 (~sgk284@ACAB88FD.ipt.aol.com)
05:24.28*** join/#bzflag amathis (~amathis@amathis.linuxfordummies)
05:26.05*** join/#bzflag amathis (~amathis@amathis.linuxfordummies)
05:42.45learneramathis: pong
05:42.56amathislearner: it is 1.12 not 2.0 right?
05:43.00amathisthe next release
05:43.42learnerI'd prefer to call the next release 2.0 for a variety of reasons, but that's not been settled (and probably won't be until release day)
05:43.50amathisok
05:44.34learnermakes sense to mark the slew of major features (many that were never slated for 1.12)
05:44.54learnerplus the 1.X line has been around forever
05:45.02learnerand 2.0 marks a nice new beginning
05:45.18learnergoes well marketing-wise with going platinum too
05:46.26learnerbut most importantly -- the features.. lots of big and small changes overall -- the changelog is enormous compared to previous releases
05:47.01learnerso I'd say 2.0 .. and then let 3.0 be the next major jump that uses a new engine, new graphics/physics etc
05:52.50amathisok
05:52.52amathisI agree.
05:58.53sgk284how far along is that python port of the bzflag client?
05:59.44*** join/#bzflag m0nkey_poo (~creeperz@70-57-235-119.sxfl.qwest.net)
05:59.47learnerthe python port hasn't moved in over a year
06:00.07learnerbut it was a fairly functional proof-of-concept in 1.7 days
06:00.34learnerit would have to be updated to the current protocol -- not horrible, but it'd be some work to update it
06:03.34*** join/#bzflag SilverFox (SilverFox@68-116-47-254.or.charter.com)
06:14.38Pimpinellalearner: is the phyton port still of any value for sombody?
06:14.44learnersure
06:15.09learnerif the person knows python, they should be able to update it in an evening or two to the updated protocol
06:15.37learnerthere were a handful of toys in that module of value
06:15.49learnerlike the 2d observer map
06:16.00Pimpinellaic
06:16.11Pimpinellashould try it some day
06:18.22Pimpinelladid manu talk to you about the possibility to send messenges and commands with another plyers identity?
06:18.58learnernope
06:19.23Pimpinellawell, anyways, i think he's wrong about that anyways
06:19.27learnerdid you see the bug report about a couple invalid kick scenarios on the new cheat detection code running there? :)
06:20.00Pimpinellarunning where?
06:20.13learneryour server
06:20.33Pimpinellanot yet, on sf?
06:21.14learnerit was, I closed the report since it didn't apply to commited code yet
06:21.43learnerbasically lots of invalid speed kicks
06:22.01learnera really easy one to reproduce: turn on roger and get killed
06:22.24Pimpinellahm, i'll try
06:23.21Pimpinellaalso the speedcheat detection sometimes kills innocent players
06:23.34Pimpinellas/kills/kicks
06:23.47sgk284is that from manu's patches?
06:23.52Pimpinellayep
06:24.21learnerthe changes are "okay" .. the problems really are probably other things that should not be happening and somehow are
06:24.53learnerlike mac users with accelerated input devices on slow computers somehow overaccelerating
06:24.54Pimpinellayeah
06:25.20learnersdl port may fix that, but it may just be masking the real problem
06:25.49learnerlikewise with that roger kick .. i'd bet it's because roger respawns immediately and begins playing
06:26.20learnerand the kick code suddenly has this massive position jump without taking the kill into account or something
06:26.32learneror roger keeps (erroneously) sending updates when he's dead
06:26.49learnerdunno.. needs debugging
06:26.54Pimpinellayep
06:27.09Pimpinellasome good hints at least :)
06:28.00Pimpinellai had a server crash yesterday, the first in this whole year
06:28.01learnermanu's made a lot of assumptions about packet transport ordering, unfortunately, and I've not made any progress explaining that 1/10000th of the time it may be wrong .. and that will definately be noticed over a day's time
06:29.54Pimpinellanot sure what you mean, but no more time at the moment :(
06:30.04Pimpinellamaybe yu can explain later?
06:30.12learnersure
06:30.16Pimpinella:)
06:30.28Pimpinellawell, cu later than