#bitfighter IRC Log

IRC Log for 2012-12-01

Timestamps are in GMT/BST.

00:00:03 raptor wow peoples are here
00:00:41 bobdaduck That's what I said this morning!
00:08:52 bobdaduck Also a bunch of people online in game.
00:15:19 Watusimoto probably from another chatroom where I've been discussing the game?
00:15:38 raptor footloose and little_apple..
00:16:00 Watusimoto and two others
00:22:05 raptor ok, heading home
00:22:15 raptor later!
00:22:56 raptor Quit ()
00:51:33 heyub Quit (Ping timeout: 245 seconds)
01:00:50 raptor has joined
01:00:51 ChanServ sets mode +o raptor
01:04:40 bobdaduck Quit (Quit: Page closed)
01:40:50 Watusimoto ok, checking in energy edits
01:41:06 Watusimoto I;ll test more tomorrow, but this basically works the way I think it will work best
01:41:19 Watusimoto open to any bugs/criticisms
01:41:25 Watusimoto please read the checkin notes
01:41:44 BFLogBot Commit: e3a3f6be04ea | Author: watusimoto | Message: Illustrate energy problems 
01:41:45 BFLogBot Commit: 306099d9a026 | Author: watusimoto | Message: Energy mostly sorted, I think.  Note that this checkin enables SHOW_SERVER_SITUATION, which you may want to disable as it can cause crashes if not properly used.  Theoretically, the flickery sheild issue is still present, though I wasn;t able to reproduce it after my last edits.  Will review further tomorrow. 
02:18:17 raptor hi
02:18:21 raptor ok
02:19:21 Watusimoto Quit (Ping timeout: 260 seconds)
03:29:15 BFLogBot Commit: a0d9b6b7db19 | Author: buckyballreaction | Message: Fix preprocesser error warning 
03:51:20 koda Quit (Quit: k thx bai)
03:51:42 raptor Quit ()
04:11:19 Wuzzy Quit (Remote host closed the connection)
08:42:00 Watusimoto has joined
11:01:40 LordDVG has joined
13:02:20 LordDVG Quit (Remote host closed the connection)
13:02:52 LordDVG has joined
13:37:57 BFLogBot Commit: 621aeaea54dd | Author: watusimoto | Message: Crash protection 
13:37:58 BFLogBot Commit: 89814875f01d | Author: watusimoto | Message: Comments 
13:38:00 BFLogBot Commit: 687d62a45afb | Author: watusimoto | Message: Remove unnecessary s2c --> found a nicer way using existing functionality.  Also adds some debugging code; makes a beep when the client thinks it is shooting.  This highlights a problem with repeat burst firing that in turn causes energy levels to vary widely btwn client and server. 
13:38:01 BFLogBot Commit: 7dcba9433231 | Author: watusimoto | Message: Merge 
15:02:03 raptor has joined
15:02:03 ChanServ sets mode +o raptor
15:02:47 raptor good morning
15:08:36 BFLogBot Commit: 3bcdc527e37c | Author: watusimoto | Message: Remove pointless functions, improved energy, fixed rapid-fire burst bug. Needs testing, but most of the energy quirks have been fixed. 
15:09:11 Watusimoto hey there
15:09:23 Watusimoto this energy issue uncovered other strange bugs
15:09:34 raptor yes
15:09:39 raptor really strange
15:09:55 Watusimoto when you are firing bursts, you can hold teh fire button and the client thinks you fire like 20 times while the server thinks you only fired twice
15:10:07 Watusimoto I think that is now fixed
15:10:11 raptor huh - i didn't notice that...
15:10:16 Watusimoto you wouldn't
15:10:32 raptor client-side energy was all messed up...
15:10:36 Watusimoto it only becomes apparent when you look
15:10:47 Watusimoto I think it's working quite well, actually
15:10:59 Watusimoto try your favorite energy busting level with my latest checkin
15:11:01 raptor must finish compiling
15:11:07 Watusimoto I think you'll find it works pretty well
15:11:09 raptor ok
15:11:26 Watusimoto I haven;t tested that level, but I have been playing with energy items
15:11:27 raptor uhhh
15:11:42 raptor shielding doesn't use client-side energy
15:11:48 raptor and the shield is green
15:11:51 Watusimoto what?
15:11:55 Watusimoto it does for me!
15:12:36 Watusimoto ian -- does energy go down when I start shielding?
15:12:43 raptor there's this inner green circle when i shield
15:12:49 Watusimoto yes
15:12:53 Watusimoto I have a wittness!
15:13:10 raptor ok there, i switched teams, now energy goes down..
15:13:12 Watusimoto the green shield shows when the server thinks your shield is on
15:13:34 Watusimoto you should see it lag by about half of whatever /lag is set to
15:15:59 Watusimoto and you
15:16:11 Watusimoto 'll hear a new chirp -- that is when the client thinks you've fired
15:16:20 raptor hmm
15:17:27 Watusimoto helps in understanding who is thinking what
15:17:58 raptor http://sam6.25u.com/upload/3screenshot_11.png
15:18:27 raptor this only happens when i first join the level - client doesn't register any energy is being used
15:18:44 raptor fixes itself when i switch teams or die
15:19:01 raptor that was zero lag
15:22:54 Watusimoto so how did you get it.  just join and apply sheidls?
15:23:18 raptor launch game -> host -> change level to NASCAR - shield
15:24:53 Watusimoto confirmed
15:25:08 Watusimoto bizarre
15:25:40 Watusimoto only seems to happen on nascar
15:25:44 Watusimoto other levels, no
15:27:08 raptor maybe level needs energyitem?
15:27:41 raptor sam686 and i actually hit his bug before on one of our test levels when we were creating Seeker
15:27:51 raptor but only once or twice, and it went away
15:29:53 Watusimoto it doesn't happen on my test level, which has energy items
15:30:05 Watusimoto gametype doesn;t seem to matter
15:30:21 raptor huh
15:34:29 raptor where are all these bugs coming from??
15:34:54 raptor i bet it was the energy refactor at the start..
15:36:34 Watusimoto oh, I see interesting
15:36:42 Watusimoto shield itself isn't working
15:36:46 raptor found somethign?
15:36:55 Watusimoto noticed a more obvious symptom
15:37:04 Watusimoto I'll find it... no question about that
16:03:58 raptor ok weird
16:04:06 raptor WallSegmentManager:229
16:04:15 raptor is that code not needed?
16:06:56 Watusimoto ok, I see the problem, but do not understand it
16:07:07 Watusimoto ship's clientInfo is null
16:07:33 Watusimoto computeBufferForBotZone?
16:07:42 raptor heh
16:07:53 raptor that makes it so bots don't skirt corners
16:08:02 Watusimoto right
16:08:07 raptor or run into turrets
16:08:14 Watusimoto and don't squeeze through too-tight things
16:08:20 Watusimoto so yes, I think it is needed
16:08:26 Watusimoto unless there is reasoon to not think so
16:08:31 raptor are you responding to my question?
16:08:41 raptor because that is a different 229 than i have...
16:08:48 Watusimoto what do you have?
16:08:58 raptor if(wall->getObjectTypeNumber() == PolyWallTypeNumber)
16:08:59 raptor       WallSegment *newSegment = new WallSegment(mWallSegmentDatabase, *wall->getOutline(), wall->getSerialNumber());
16:09:12 raptor WallSegmentManager.cpp:229
16:09:17 Watusimoto sorry, my bad
16:09:54 Watusimoto I think so
16:10:14 raptor because the variable newSegment isn't used anywhere
16:10:29 Watusimoto oh
16:10:44 Watusimoto ah but it is needed
16:10:52 Watusimoto maybe not the variable
16:10:57 raptor is that because the construction is doing stuff
16:11:01 raptor ah, ok
16:11:02 Watusimoto but the mere act of creating a segment adds it ot the database
16:11:08 raptor ok ok
16:11:11 Watusimoto hence this: // The WallSegment constructor will add it to the specified database.
16:11:13 Watusimoto :-)
16:11:21 Watusimoto I added that comment because of similar confusion
16:11:30 raptor pssh - comments...  who reads those...
16:11:35 Watusimoto that's why I explicitly added edges to the database
16:11:52 Watusimoto we _could_ do that for segments too, might make things clearer, but will result in dupe code
16:12:10 raptor ok, i'll just remove the variable (i'm cleaning up compiler warnings)
16:12:12 Watusimoto but you can remove the var assignment if you think it would clarify
16:12:14 Watusimoto ok, good
16:12:21 raptor thanks
16:12:28 Watusimoto back shortly
16:14:18 LordDVG Quit (Ping timeout: 250 seconds)
16:23:26 raptor when you get back
16:24:26 raptor ship.cpp:1317  xmFireTimer isn't used - can i remove that or was the code that used it commented out temporarily?
16:25:40 raptor LuaScriptRunner.cpp:857   lots of old commented out code; can be removed?
16:26:37 raptor LineItem.cpp:269   more commented code can be removed?
17:26:42 Watusimoto For the moment leave it -- when we're all satisified that things are working, we can remove it
17:27:05 raptor hi
17:27:08 Watusimoto hi again
17:27:08 raptor in response to which?
17:27:18 Watusimoto oh, sorry
17:27:24 Watusimoto all that for 1317
17:27:30 raptor ok
17:28:21 Watusimoto if the bots are more or less working you can delete 857
17:28:29 raptor they've been working!
17:28:57 Watusimoto delete 269
17:29:25 raptor and is the backslash needed for the newline?
17:29:55 Watusimoto where?
17:30:03 raptor 268
17:30:11 raptor is the backslash  needed at th eend of that?
17:30:34 Watusimoto probably not
17:32:58 BFLogBot Commit: 6b897f953e30 | Author: buckyballreaction | Message: Fix several compiler warnings 
17:35:31 Watusimoto I fixed that stupid energy bug
17:35:39 Watusimoto with a very stupid hack
17:35:41 raptor the shield one?
17:36:05 Watusimoto yes
17:36:12 raptor oh good
17:36:19 Watusimoto I don;t like it
17:36:25 Watusimoto it just pastes over the real problem
17:36:36 raptor i wonder how much of our code does that...
17:36:46 Watusimoto I changed if(!mCooldownNeeded && getClientInfo() && !getClientInfo()->isShipSystemsDisabled())
17:36:47 Watusimoto to
17:36:55 Watusimoto if(!mCooldownNeeded && (!getClientInfo() || (getClientInfo() && !getClientInfo()->isShipSystemsDisabled())))
17:37:07 Watusimoto because getClientInfo returns null on that level for some reason
17:37:25 Watusimoto on the other hand... it fixes the problem!
17:38:55 raptor huh
17:40:48 raptor that's... odd....
17:41:02 Watusimoto I'll check it in so you can see how the enregy works for you
17:41:10 raptor ok
17:41:17 raptor do we have some sort of out-of-order problem with sending clientinfo
17:41:27 Watusimoto i think we should spend NO time on making lag > 500 work nicely
17:41:33 Watusimoto that's my mental cutoff
17:41:34 raptor yes
17:41:38 raptor i agree
17:41:53 raptor and actually, the threshold for a lot of games is 100/150
17:42:03 raptor after that they say you're on your own...
17:42:13 BFLogBot Commit: bf2c67e58133 | Author: watusimoto | Message: Hide client-side firing sound behind #ifdef SHOW_SERVER_SITUATION 
17:42:15 BFLogBot Commit: 04603daf90fb | Author: watusimoto | Message: Remove unused assert 
17:42:16 BFLogBot Commit: 6ac5a128b9d2 | Author: watusimoto | Message: Paper over an annoying bug 
17:42:18 BFLogBot Commit: eaceeb490dc2 | Author: watusimoto | Message: Clearer code 
17:42:19 BFLogBot Commit: 15e1376adaae | Author: watusimoto | Message: Formatting 
17:42:21 BFLogBot Commit: 1e534a486292 | Author: watusimoto | Message: Merge 
17:42:28 Watusimoto but there shouldn;t be any gross bugs, but yes
17:42:33 Watusimoto I actually won't play at 200
17:42:39 Watusimoto I think it's almost unplayable
17:42:57 raptor it is for almost any game..
17:43:11 Watusimoto at least that means it isn't just us being lame
17:43:20 raptor so i think, maybe our focus should be on reducing network?
17:44:33 Watusimoto reducing network?
17:44:40 raptor sorry, bandwidth
17:45:10 Watusimoto yes, though I think we are pretty good
17:45:15 Watusimoto btw, see http://code.google.com/opensource/gci/2012/index.html
17:45:23 Watusimoto specifically the task categories
17:45:39 Watusimoto particularly the Outreach/Research section
17:45:57 raptor i don't see that on that page
17:46:06 Watusimoto maybe we can add a task for publicizing the game
17:46:27 Watusimoto you don;t see "The tasks are grouped into the following categories:"
17:46:39 raptor oh, yes - i thought you meant to show specifics
17:46:40 Watusimoto "Outreach/Research: Tasks related to community management, outreach/marketing, or studying problems and recommending solutions"
17:46:47 raptor marketing!
17:46:51 Watusimoto yes!
17:47:56 raptor shield fixed on that map
17:50:07 Watusimoto though I am not really sure where our stuff stands
17:50:17 Watusimoto i.e. have our tasks been added to the list?
17:51:29 Watusimoto ok, need to go work on dinner ... will try to track down the underlying cause of the clientinfo bug later.  Could that be related to the badge bug?
17:54:54 Watusimoto_ has joined
17:56:36 raptor the badge bug is entirely separate
17:56:57 raptor and we can defer it
17:57:07 raptor the idle bugs are bad, though
17:57:47 Watusimoto Quit (Ping timeout: 265 seconds)
18:00:48 raptor ok, i'm off to do errands.  i'll be back later, too
18:34:48 CrazyLinuxNerd Quit (Remote host closed the connection)
18:38:57 CrazyLinuxNerd has joined
18:43:13 Watusimoto_ Quit (Ping timeout: 265 seconds)
18:43:43 koda has joined
18:54:54 LordDVG has joined
19:04:22 Watusimoto has joined
19:28:13 raptor back
19:28:29 raptor with 4 more lbs of butter!
19:53:20 Watusimoto Quit (Ping timeout: 264 seconds)
20:30:34 Fordcars has joined
20:30:38 Fordcars hello
20:30:43 raptor hi
20:31:18 Fordcars It was quite funny there were 2 servers with passwords and I guessed both passwords: 123 and 1234
20:33:40 Fordcars so the server got hacked, huh. Was that this week at one moment it was down
20:34:03 raptor i discovered it about 2 weeks ago
20:34:11 Fordcars ah ok
20:34:53 Fordcars anyway going to idleville for around 30 minutes
20:35:06 raptor bye
20:58:41 Watusimoto has joined
21:08:26 Watusimoto java.  sigh
21:08:29 Watusimoto http://developers.slashdot.org/story/12/12/01/1847244/how-does-a-single-line-of-basic-make-an-intricate-maze
21:08:39 Watusimoto not a great set of comments
21:08:50 Watusimoto but it;s a bout a very overhyped 1 line basic program
21:09:02 Watusimoto about 2/3 of the way down is a java equivalent
21:09:07 Watusimoto so sad.  so true.
21:22:56 LordDVG Quit (Remote host closed the connection)
21:44:56 raptor Quit (Ping timeout: 250 seconds)
21:51:56 Watusimoto found something... events happen in a different order on nascar for some reason
21:52:11 Watusimoto players join at a different phase in the level loading
21:52:31 Watusimoto resulting in a null playerinfo at a critical juncture
21:52:36 Watusimoto but why?
21:59:52 raptor has joined
21:59:52 ChanServ sets mode +o raptor
22:13:34 Watusimoto mysteries abound
22:17:20 Watusimoto maybe its level size that's the problem
22:17:35 Watusimoto except geowar is even larger
22:17:42 Watusimoto and doesn;t have the problem
22:17:47 Watusimoto but nascar is big
22:34:19 raptor Quit (Ping timeout: 246 seconds)
22:46:30 raptor has joined
22:46:30 ChanServ sets mode +o raptor
22:46:33 raptor Hi
22:46:37 raptor I'm really here now
22:46:50 raptor until my router dies again...
22:47:09 raptor out-of-order on Nacsar
22:47:13 raptor i thought so...
22:48:01 Fordcars I am back after freezing my butt for the past 2hours putting christmas lights
22:48:33 raptor brrrr
22:48:41 Fordcars yeah
22:49:15 raptor Watusimoto: maybe it has something to do with the item count?  there are loads of energyitems..
22:51:25 Fordcars or slippery zones
22:52:58 raptor 296 energyitems on tha tmap..
22:55:36 raptor also don't knock java enterprise...  it pays my bills - although i cannot deny the truth; that example was spot on in many things i've seen
22:56:07 raptor :)
22:57:40 Watusimoto I think thie issue is that a buffer gets full and gets sent sooner on that level than antoher, and somwehere a paket needs to be marked order guaranteed that is not
23:02:59 raptor what s2c sends the energyitems - that'd be my first guess
23:04:05 Watusimoto it's not a s2c -- it's part of the TNL replication process
23:04:16 raptor what process is that?
23:17:13 Watusimoto uh.... just TNL, I think
23:17:44 Watusimoto walls are unuisual in how they are replicated.  other objects are duplicated by TNL
23:22:02 Watusimoto sorry - I know that's a crap answer
23:29:12 raptor i'm having a hard time starting the idle bugs - i'm not in a very good debugging mood..
23:30:21 Watusimoto I understand!
23:30:25 Watusimoto take a break
23:30:39 raptor i would, but i haven't even started!
23:35:05 raptor sometimes i think we need a flowchart for each of these systems
23:52:55 raptor another segfault!:  http://pastie.org/5464539
23:53:11 raptor host a game, open another client, join the game
23:53:15 raptor crash!
23:58:18 Watusimoto you'll need to disable that compile directive
23:58:28 Watusimoto looking for name...
23:58:42 Watusimoto SHOW_SERVER_SITUATION
23:58:50 Watusimoto that will cause crashes with other clients
23:58:53 raptor oh, that one...
23:58:57 raptor ok
23:58:57 Watusimoto it could be made safer
23:59:06 Watusimoto perhaps should be made safer

Index Search ←Prev date Next date→

These logs were automatically created by BFLogBot on irc.freenode.net.

00:00:03	raptor	wow peoples are here
00:00:41	bobdaduck	That's what I said this morning!
00:08:52	bobdaduck	Also a bunch of people online in game.
00:15:19	Watusimoto	probably from another chatroom where I've been discussing the game?
00:15:38	raptor	footloose and little_apple..
00:16:00	Watusimoto	and two others
00:22:05	raptor	ok, heading home
00:22:15	raptor	later!
00:22:56		raptor Quit ()
00:51:33		heyub Quit (Ping timeout: 245 seconds)
01:00:50		raptor has joined
01:00:51		ChanServ sets mode +o raptor
01:04:40		bobdaduck Quit (Quit: Page closed)
01:40:50	Watusimoto	ok, checking in energy edits
01:41:06	Watusimoto	I;ll test more tomorrow, but this basically works the way I think it will work best
01:41:19	Watusimoto	open to any bugs/criticisms
01:41:25	Watusimoto	please read the checkin notes
01:41:44		BFLogBot Commit: e3a3f6be04ea \| Author: watusimoto \| Message: Illustrate energy problems
01:41:45		BFLogBot Commit: 306099d9a026 \| Author: watusimoto \| Message: Energy mostly sorted, I think. Note that this checkin enables SHOW_SERVER_SITUATION, which you may want to disable as it can cause crashes if not properly used. Theoretically, the flickery sheild issue is still present, though I wasn;t able to reproduce it after my last edits. Will review further tomorrow.
02:18:17	raptor	hi
02:18:21	raptor	ok
02:19:21		Watusimoto Quit (Ping timeout: 260 seconds)
03:29:15		BFLogBot Commit: a0d9b6b7db19 \| Author: buckyballreaction \| Message: Fix preprocesser error warning
03:51:20		koda Quit (Quit: k thx bai)
03:51:42		raptor Quit ()
04:11:19		Wuzzy Quit (Remote host closed the connection)
08:42:00		Watusimoto has joined
11:01:40		LordDVG has joined
13:02:20		LordDVG Quit (Remote host closed the connection)
13:02:52		LordDVG has joined
13:37:57		BFLogBot Commit: 621aeaea54dd \| Author: watusimoto \| Message: Crash protection
13:37:58		BFLogBot Commit: 89814875f01d \| Author: watusimoto \| Message: Comments
13:38:00		BFLogBot Commit: 687d62a45afb \| Author: watusimoto \| Message: Remove unnecessary s2c --> found a nicer way using existing functionality. Also adds some debugging code; makes a beep when the client thinks it is shooting. This highlights a problem with repeat burst firing that in turn causes energy levels to vary widely btwn client and server.
13:38:01		BFLogBot Commit: 7dcba9433231 \| Author: watusimoto \| Message: Merge
15:02:03		raptor has joined
15:02:03		ChanServ sets mode +o raptor
15:02:47	raptor	good morning
15:08:36		BFLogBot Commit: 3bcdc527e37c \| Author: watusimoto \| Message: Remove pointless functions, improved energy, fixed rapid-fire burst bug. Needs testing, but most of the energy quirks have been fixed.
15:09:11	Watusimoto	hey there
15:09:23	Watusimoto	this energy issue uncovered other strange bugs
15:09:34	raptor	yes
15:09:39	raptor	really strange
15:09:55	Watusimoto	when you are firing bursts, you can hold teh fire button and the client thinks you fire like 20 times while the server thinks you only fired twice
15:10:07	Watusimoto	I think that is now fixed
15:10:11	raptor	huh - i didn't notice that...
15:10:16	Watusimoto	you wouldn't
15:10:32	raptor	client-side energy was all messed up...
15:10:36	Watusimoto	it only becomes apparent when you look
15:10:47	Watusimoto	I think it's working quite well, actually
15:10:59	Watusimoto	try your favorite energy busting level with my latest checkin
15:11:01		raptor must finish compiling
15:11:07	Watusimoto	I think you'll find it works pretty well
15:11:09	raptor	ok
15:11:26	Watusimoto	I haven;t tested that level, but I have been playing with energy items
15:11:27	raptor	uhhh
15:11:42	raptor	shielding doesn't use client-side energy
15:11:48	raptor	and the shield is green
15:11:51	Watusimoto	what?
15:11:55	Watusimoto	it does for me!
15:12:36	Watusimoto	ian -- does energy go down when I start shielding?
15:12:43	raptor	there's this inner green circle when i shield
15:12:49	Watusimoto	yes
15:12:53	Watusimoto	I have a wittness!
15:13:10	raptor	ok there, i switched teams, now energy goes down..
15:13:12	Watusimoto	the green shield shows when the server thinks your shield is on
15:13:34	Watusimoto	you should see it lag by about half of whatever /lag is set to
15:15:59	Watusimoto	and you
15:16:11	Watusimoto	'll hear a new chirp -- that is when the client thinks you've fired
15:16:20	raptor	hmm
15:17:27	Watusimoto	helps in understanding who is thinking what
15:17:58	raptor	http://sam6.25u.com/upload/3screenshot_11.png
15:18:27	raptor	this only happens when i first join the level - client doesn't register any energy is being used
15:18:44	raptor	fixes itself when i switch teams or die
15:19:01	raptor	that was zero lag
15:22:54	Watusimoto	so how did you get it. just join and apply sheidls?
15:23:18	raptor	launch game -> host -> change level to NASCAR - shield
15:24:53	Watusimoto	confirmed
15:25:08	Watusimoto	bizarre
15:25:40	Watusimoto	only seems to happen on nascar
15:25:44	Watusimoto	other levels, no
15:27:08	raptor	maybe level needs energyitem?
15:27:41	raptor	sam686 and i actually hit his bug before on one of our test levels when we were creating Seeker
15:27:51	raptor	but only once or twice, and it went away
15:29:53	Watusimoto	it doesn't happen on my test level, which has energy items
15:30:05	Watusimoto	gametype doesn;t seem to matter
15:30:21	raptor	huh
15:34:29	raptor	where are all these bugs coming from??
15:34:54	raptor	i bet it was the energy refactor at the start..
15:36:34	Watusimoto	oh, I see interesting
15:36:42	Watusimoto	shield itself isn't working
15:36:46	raptor	found somethign?
15:36:55	Watusimoto	noticed a more obvious symptom
15:37:04	Watusimoto	I'll find it... no question about that
16:03:58	raptor	ok weird
16:04:06	raptor	WallSegmentManager:229
16:04:15	raptor	is that code not needed?
16:06:56	Watusimoto	ok, I see the problem, but do not understand it
16:07:07	Watusimoto	ship's clientInfo is null
16:07:33	Watusimoto	computeBufferForBotZone?
16:07:42	raptor	heh
16:07:53	raptor	that makes it so bots don't skirt corners
16:08:02	Watusimoto	right
16:08:07	raptor	or run into turrets
16:08:14	Watusimoto	and don't squeeze through too-tight things
16:08:20	Watusimoto	so yes, I think it is needed
16:08:26	Watusimoto	unless there is reasoon to not think so
16:08:31	raptor	are you responding to my question?
16:08:41	raptor	because that is a different 229 than i have...
16:08:48	Watusimoto	what do you have?
16:08:58	raptor	if(wall->getObjectTypeNumber() == PolyWallTypeNumber)
16:08:59	raptor	WallSegment newSegment = new WallSegment(mWallSegmentDatabase, wall->getOutline(), wall->getSerialNumber());
16:09:12	raptor	WallSegmentManager.cpp:229
16:09:17	Watusimoto	sorry, my bad
16:09:54	Watusimoto	I think so
16:10:14	raptor	because the variable newSegment isn't used anywhere
16:10:29	Watusimoto	oh
16:10:44	Watusimoto	ah but it is needed
16:10:52	Watusimoto	maybe not the variable
16:10:57	raptor	is that because the construction is doing stuff
16:11:01	raptor	ah, ok
16:11:02	Watusimoto	but the mere act of creating a segment adds it ot the database
16:11:08	raptor	ok ok
16:11:11	Watusimoto	hence this: // The WallSegment constructor will add it to the specified database.
16:11:13	Watusimoto	:-)
16:11:21	Watusimoto	I added that comment because of similar confusion
16:11:30	raptor	pssh - comments... who reads those...
16:11:35	Watusimoto	that's why I explicitly added edges to the database
16:11:52	Watusimoto	we _could_ do that for segments too, might make things clearer, but will result in dupe code
16:12:10	raptor	ok, i'll just remove the variable (i'm cleaning up compiler warnings)
16:12:12	Watusimoto	but you can remove the var assignment if you think it would clarify
16:12:14	Watusimoto	ok, good
16:12:21	raptor	thanks
16:12:28	Watusimoto	back shortly
16:14:18		LordDVG Quit (Ping timeout: 250 seconds)
16:23:26	raptor	when you get back
16:24:26	raptor	ship.cpp:1317 xmFireTimer isn't used - can i remove that or was the code that used it commented out temporarily?
16:25:40	raptor	LuaScriptRunner.cpp:857 lots of old commented out code; can be removed?
16:26:37	raptor	LineItem.cpp:269 more commented code can be removed?
17:26:42	Watusimoto	For the moment leave it -- when we're all satisified that things are working, we can remove it
17:27:05	raptor	hi
17:27:08	Watusimoto	hi again
17:27:08	raptor	in response to which?
17:27:18	Watusimoto	oh, sorry
17:27:24	Watusimoto	all that for 1317
17:27:30	raptor	ok
17:28:21	Watusimoto	if the bots are more or less working you can delete 857
17:28:29	raptor	they've been working!
17:28:57	Watusimoto	delete 269
17:29:25	raptor	and is the backslash needed for the newline?
17:29:55	Watusimoto	where?
17:30:03	raptor	268
17:30:11	raptor	is the backslash needed at th eend of that?
17:30:34	Watusimoto	probably not
17:32:58		BFLogBot Commit: 6b897f953e30 \| Author: buckyballreaction \| Message: Fix several compiler warnings
17:35:31	Watusimoto	I fixed that stupid energy bug
17:35:39	Watusimoto	with a very stupid hack
17:35:41	raptor	the shield one?
17:36:05	Watusimoto	yes
17:36:12	raptor	oh good
17:36:19	Watusimoto	I don;t like it
17:36:25	Watusimoto	it just pastes over the real problem
17:36:36	raptor	i wonder how much of our code does that...
17:36:46	Watusimoto	I changed if(!mCooldownNeeded && getClientInfo() && !getClientInfo()->isShipSystemsDisabled())
17:36:47	Watusimoto	to
17:36:55	Watusimoto	if(!mCooldownNeeded && (!getClientInfo() \|\| (getClientInfo() && !getClientInfo()->isShipSystemsDisabled())))
17:37:07	Watusimoto	because getClientInfo returns null on that level for some reason
17:37:25	Watusimoto	on the other hand... it fixes the problem!
17:38:55	raptor	huh
17:40:48	raptor	that's... odd....
17:41:02	Watusimoto	I'll check it in so you can see how the enregy works for you
17:41:10	raptor	ok
17:41:17	raptor	do we have some sort of out-of-order problem with sending clientinfo
17:41:27	Watusimoto	i think we should spend NO time on making lag > 500 work nicely
17:41:33	Watusimoto	that's my mental cutoff
17:41:34	raptor	yes
17:41:38	raptor	i agree
17:41:53	raptor	and actually, the threshold for a lot of games is 100/150
17:42:03	raptor	after that they say you're on your own...
17:42:13		BFLogBot Commit: bf2c67e58133 \| Author: watusimoto \| Message: Hide client-side firing sound behind #ifdef SHOW_SERVER_SITUATION
17:42:15		BFLogBot Commit: 04603daf90fb \| Author: watusimoto \| Message: Remove unused assert
17:42:16		BFLogBot Commit: 6ac5a128b9d2 \| Author: watusimoto \| Message: Paper over an annoying bug
17:42:18		BFLogBot Commit: eaceeb490dc2 \| Author: watusimoto \| Message: Clearer code
17:42:19		BFLogBot Commit: 15e1376adaae \| Author: watusimoto \| Message: Formatting
17:42:21		BFLogBot Commit: 1e534a486292 \| Author: watusimoto \| Message: Merge
17:42:28	Watusimoto	but there shouldn;t be any gross bugs, but yes
17:42:33	Watusimoto	I actually won't play at 200
17:42:39	Watusimoto	I think it's almost unplayable
17:42:57	raptor	it is for almost any game..
17:43:11	Watusimoto	at least that means it isn't just us being lame
17:43:20	raptor	so i think, maybe our focus should be on reducing network?
17:44:33	Watusimoto	reducing network?
17:44:40	raptor	sorry, bandwidth
17:45:10	Watusimoto	yes, though I think we are pretty good
17:45:15	Watusimoto	btw, see http://code.google.com/opensource/gci/2012/index.html
17:45:23	Watusimoto	specifically the task categories
17:45:39	Watusimoto	particularly the Outreach/Research section
17:45:57	raptor	i don't see that on that page
17:46:06	Watusimoto	maybe we can add a task for publicizing the game
17:46:27	Watusimoto	you don;t see "The tasks are grouped into the following categories:"
17:46:39	raptor	oh, yes - i thought you meant to show specifics
17:46:40	Watusimoto	"Outreach/Research: Tasks related to community management, outreach/marketing, or studying problems and recommending solutions"
17:46:47	raptor	marketing!
17:46:51	Watusimoto	yes!
17:47:56	raptor	shield fixed on that map
17:50:07	Watusimoto	though I am not really sure where our stuff stands
17:50:17	Watusimoto	i.e. have our tasks been added to the list?
17:51:29	Watusimoto	ok, need to go work on dinner ... will try to track down the underlying cause of the clientinfo bug later. Could that be related to the badge bug?
17:54:54		Watusimoto_ has joined
17:56:36	raptor	the badge bug is entirely separate
17:56:57	raptor	and we can defer it
17:57:07	raptor	the idle bugs are bad, though
17:57:47		Watusimoto Quit (Ping timeout: 265 seconds)
18:00:48	raptor	ok, i'm off to do errands. i'll be back later, too
18:34:48		CrazyLinuxNerd Quit (Remote host closed the connection)
18:38:57		CrazyLinuxNerd has joined
18:43:13		Watusimoto_ Quit (Ping timeout: 265 seconds)
18:43:43		koda has joined
18:54:54		LordDVG has joined
19:04:22		Watusimoto has joined
19:28:13	raptor	back
19:28:29	raptor	with 4 more lbs of butter!
19:53:20		Watusimoto Quit (Ping timeout: 264 seconds)
20:30:34		Fordcars has joined
20:30:38	Fordcars	hello
20:30:43	raptor	hi
20:31:18	Fordcars	It was quite funny there were 2 servers with passwords and I guessed both passwords: 123 and 1234
20:33:40	Fordcars	so the server got hacked, huh. Was that this week at one moment it was down
20:34:03	raptor	i discovered it about 2 weeks ago
20:34:11	Fordcars	ah ok
20:34:53	Fordcars	anyway going to idleville for around 30 minutes
20:35:06	raptor	bye
20:58:41		Watusimoto has joined
21:08:26	Watusimoto	java. sigh
21:08:29	Watusimoto	http://developers.slashdot.org/story/12/12/01/1847244/how-does-a-single-line-of-basic-make-an-intricate-maze
21:08:39	Watusimoto	not a great set of comments
21:08:50	Watusimoto	but it;s a bout a very overhyped 1 line basic program
21:09:02	Watusimoto	about 2/3 of the way down is a java equivalent
21:09:07	Watusimoto	so sad. so true.
21:22:56		LordDVG Quit (Remote host closed the connection)
21:44:56		raptor Quit (Ping timeout: 250 seconds)
21:51:56	Watusimoto	found something... events happen in a different order on nascar for some reason
21:52:11	Watusimoto	players join at a different phase in the level loading
21:52:31	Watusimoto	resulting in a null playerinfo at a critical juncture
21:52:36	Watusimoto	but why?
21:59:52		raptor has joined
21:59:52		ChanServ sets mode +o raptor
22:13:34	Watusimoto	mysteries abound
22:17:20	Watusimoto	maybe its level size that's the problem
22:17:35	Watusimoto	except geowar is even larger
22:17:42	Watusimoto	and doesn;t have the problem
22:17:47	Watusimoto	but nascar is big
22:34:19		raptor Quit (Ping timeout: 246 seconds)
22:46:30		raptor has joined
22:46:30		ChanServ sets mode +o raptor
22:46:33	raptor	Hi
22:46:37	raptor	I'm really here now
22:46:50	raptor	until my router dies again...
22:47:09	raptor	out-of-order on Nacsar
22:47:13	raptor	i thought so...
22:48:01	Fordcars	I am back after freezing my butt for the past 2hours putting christmas lights
22:48:33	raptor	brrrr
22:48:41	Fordcars	yeah
22:49:15	raptor	Watusimoto: maybe it has something to do with the item count? there are loads of energyitems..
22:51:25	Fordcars	or slippery zones
22:52:58	raptor	296 energyitems on tha tmap..
22:55:36	raptor	also don't knock java enterprise... it pays my bills - although i cannot deny the truth; that example was spot on in many things i've seen
22:56:07	raptor	:)
22:57:40	Watusimoto	I think thie issue is that a buffer gets full and gets sent sooner on that level than antoher, and somwehere a paket needs to be marked order guaranteed that is not
23:02:59	raptor	what s2c sends the energyitems - that'd be my first guess
23:04:05	Watusimoto	it's not a s2c -- it's part of the TNL replication process
23:04:16	raptor	what process is that?
23:17:13	Watusimoto	uh.... just TNL, I think
23:17:44	Watusimoto	walls are unuisual in how they are replicated. other objects are duplicated by TNL
23:22:02	Watusimoto	sorry - I know that's a crap answer
23:29:12	raptor	i'm having a hard time starting the idle bugs - i'm not in a very good debugging mood..
23:30:21	Watusimoto	I understand!
23:30:25	Watusimoto	take a break
23:30:39	raptor	i would, but i haven't even started!
23:35:05	raptor	sometimes i think we need a flowchart for each of these systems
23:52:55	raptor	another segfault!: http://pastie.org/5464539
23:53:11	raptor	host a game, open another client, join the game
23:53:15	raptor	crash!
23:58:18	Watusimoto	you'll need to disable that compile directive
23:58:28	Watusimoto	looking for name...
23:58:42	Watusimoto	SHOW_SERVER_SITUATION
23:58:50	Watusimoto	that will cause crashes with other clients
23:58:53	raptor	oh, that one...
23:58:57	raptor	ok
23:58:57	Watusimoto	it could be made safer
23:59:06	Watusimoto	perhaps should be made safer