Timestamps are in GMT/BST.
| 00:13:56 | | Hugo has joined |
| 00:14:04 | Hugo | Hello |
| 00:14:22 | | Hugo is now known as Guest11147 |
| 00:14:45 | Guest11147 | Hello? |
| 00:14:47 | Guest11147 | Im Hugo |
| 00:14:51 | Guest11147 | Is anyone here? |
| 00:15:29 | | Guest11147 Quit (Client Quit) |
| 00:25:03 | Watusimoto | karamazovapy: just a numbering issue; 017 will be next version released, will probably include core changes |
| 00:25:30 | karamazovapy | ...well it's not just a numbering issue if we're breaking compatibility, is it? |
| 00:46:55 | sam686 | the problem with core changes is, older client can't really handle the core changes, and the core changes will brobably be on 017 |
| 01:01:26 | | raptor has joined |
| 01:01:26 | | ChanServ sets mode +o raptor |
| 01:02:25 | raptor | howdy folks |
| 01:31:43 | | Watusimoto Quit (Ping timeout: 248 seconds) |
| 01:35:29 | | raptor Quit (Ping timeout: 240 seconds) |
| 02:06:59 | karamazovapy | damn, watusimoto's gone |
| 02:07:08 | karamazovapy | hey sam686 or Zoomber ? |
| 02:07:20 | karamazovapy | is the master responding slowly for either/both of you? |
| 02:07:48 | karamazovapy | I noticed a real drag when I was sending the mass e-mail yesterday, and posting and retrieving forum messages seems to be dragging a lot for me tonight |
| 02:18:32 | sam686 | i sometimes seen bitfighter.org take a very long time for pages to load |
| 02:32:55 | | raptor has joined |
| 02:32:56 | | ChanServ sets mode +o raptor |
| 02:34:10 | raptor | yes, i've noticed that our new master seems to aggressively throttle CPU sometimes... |
| 02:36:25 | sam686 | to me, it kind of looks like a very slow / buzy vps hard disk... |
| 02:37:06 | sam686 | i have seen wiki's user preference takes a long time to load, but other pages loads fast |
| 02:38:16 | raptor | maybe that's it - maybe the harddisk keeps going to sleep |
| 02:39:09 | sam686 | or maybe, there is multiple vps on one machine, and the hard disk is buzy with reading stuff from some other vps server in the same machine |
| 02:39:23 | raptor | that too... |
| 02:41:14 | sam686 | a real server computer won't have that problem as everything is on it's own machine, including hard disk, and even allowing swap to be enabled if needed.. (but more expensive) |
| 03:19:17 | raptor | found a bug |
| 03:20:48 | raptor | i don't think -rootdatadir is working properly... |
| 03:24:41 | raptor | sam686: is cacheDir used much anymore? |
| 03:24:58 | raptor | it doesn't look like it is |
| 03:29:58 | sam686 | it might have been the old way of catching bot zones, when bot generating might have been slow |
| 03:30:22 | raptor | can i remove it? |
| 03:32:07 | sam686 | you probably can, i guess |
| 03:33:21 | sam686 | i remembered that watusimoto written the first way of catched zone, which is simply writing "BotNavMeshZone" text, after generated by bot zone lua i wrote |
| 03:34:00 | sam686 | then i wrote a binary mode cache which was a much faster way to cache to write and read bot zones |
| 03:34:32 | sam686 | then, i guess its been removed my watusimoto, maybe because of new bot zone generation |
| 03:34:44 | raptor | yeah |
| 03:48:01 | | BFLogBot - Commit d8fe07816ad6 | Author: buckyballreaction | Log: Make scripts/ and editor_plugins/ default to rootdatadir |
| 03:48:02 | | BFLogBot - Commit 5daee2a5f95b | Author: buckyballreaction | Log: Remove cacheDir, it isn't used anymore since we auto-generate botzones |
| 03:54:50 | raptor | I should probably re-release the mac packages... |
| 03:55:00 | raptor | bots don't work |
| 04:15:07 | raptor | ok i re-posted mac/linux packages |
| 04:23:35 | raptor | heading to bed early |
| 04:23:39 | raptor | good night |
| 04:29:09 | | raptor Quit (Remote host closed the connection) |
| 04:34:44 | | sam686 Quit (Read error: Connection reset by peer) |
| 04:38:32 | | sam686 has joined |
| 04:38:32 | | ChanServ sets mode +v sam686 |
| 08:58:44 | | watusimoto has joined |
| 08:58:45 | | ChanServ sets mode +o watusimoto |
| 09:00:34 | | sam686 Quit (Ping timeout: 245 seconds) |
| 09:01:20 | | sam686 has joined |
| 09:01:20 | | ChanServ sets mode +v sam686 |
| 09:23:29 | | sam686 Quit (Read error: Connection reset by peer) |
| 09:26:42 | | sam686 has joined |
| 09:26:42 | | ChanServ sets mode +v sam686 |
| 10:23:04 | | sam686 Quit (Read error: Connection reset by peer) |
| 10:26:39 | | sam686 has joined |
| 10:26:39 | | ChanServ sets mode +v sam686 |
| 11:15:48 | | Watusimoto_ has joined |
| 11:24:58 | | Zoomber Quit (Ping timeout: 245 seconds) |
| 11:31:40 | | Zoomber has joined |
| 11:31:41 | | ChanServ sets mode +v Zoomber |
| 11:50:55 | | koda has joined |
| 12:10:42 | | LordDVG has joined |
| 12:53:25 | | watusimoto Quit (Remote host closed the connection) |
| 14:00:09 | | Watusimoto_ Quit (Ping timeout: 240 seconds) |
| 14:23:31 | | raptor has joined |
| 14:23:32 | | ChanServ sets mode +o raptor |
| 15:52:35 | | LoneWolfy has joined |
| 15:52:45 | LoneWolfy | Msg nickserv identify Yoshi95 |
| 15:52:48 | LoneWolfy | Oops |
| 16:05:15 | | raptor Quit (Ping timeout: 252 seconds) |
| 17:00:18 | | raptor has joined |
| 17:00:18 | | ChanServ sets mode +o raptor |
| 17:59:03 | | Watusimoto has joined |
| 17:59:53 | | sam686 Quit (Read error: Connection reset by peer) |
| 18:03:51 | | sam686 has joined |
| 18:03:51 | | ChanServ sets mode +v sam686 |
| 18:23:43 | raptor | hello |
| 18:37:10 | | Watusimoto Quit (Ping timeout: 248 seconds) |
| 18:38:02 | | raptor Quit (Read error: Operation timed out) |
| 18:40:47 | | sam686 Quit (Read error: Connection reset by peer) |
| 19:22:16 | | LoneWolfy Quit (Remote host closed the connection) |
| 19:33:31 | | raptor has joined |
| 19:33:31 | | ChanServ sets mode +o raptor |
| 19:45:59 | | Zoomber Quit (Ping timeout: 252 seconds) |
| 19:48:35 | | raptor Quit (Remote host closed the connection) |
| 19:59:45 | | Watusimoto has joined |
| 20:05:31 | Watusimoto | hello |
| 20:57:40 | | raptor has joined |
| 20:57:41 | | ChanServ sets mode +o raptor |
| 20:57:44 | raptor | hello |
| 21:09:39 | | raptor Quit (Remote host closed the connection) |
| 22:24:35 | | sam686 has joined |
| 22:24:36 | | ChanServ sets mode +v sam686 |
| 22:36:50 | karamazovapy | hello |
| 22:36:55 | karamazovapy | (my turn, right?) |
| 22:39:28 | sam686 | hello |
| 22:47:39 | Watusimoto | hi |
| 22:49:27 | | raptor has joined |
| 22:49:27 | | ChanServ sets mode +o raptor |
| 22:49:33 | raptor | hi |
| 22:51:29 | raptor | so should we not autodetect the joystick upon start-up? |
| 22:51:29 | raptor | unless the option is saved in the INI, of course |
| 22:56:34 | | LordDVG Quit (Remote host closed the connection) |
| 23:03:27 | raptor | we don't actually save the input mode in the INI... |
| 23:03:42 | raptor | i guess we should always start up with default keyboard? |
| 23:07:21 | sam686 | i think it always does keyboard mode with no joystick available anyway, and joystick mode when joystick is available.. |
| 23:07:52 | sam686 | it is not possible to play in joystick mode when having no joystick game pad plugged in |
| 23:08:11 | raptor | yes, i'm speaking with this as context: http://bitfighter.org/forums/viewtopic.php?f=28&p=11258#p11258 |
| 23:09:41 | sam686 | i think that problem existed on 015? not sure, as it always does joystick mode on 015 too (with joystick plugged on) |
| 23:10:56 | sam686 | maybe, a user want it to save input mode to "keyboard" and keep it that way, even when there is joystick available.. |
| 23:11:40 | raptor | yes - we don't currently save input mode |
| 23:17:38 | raptor | ok, i'm committing a change to not force the joystick on people.. |
| 23:20:02 | | BFLogBot - Commit 899f7c101980 | Author: buckyballreaction | Log: Don't force joystick on people, default to keyboard on start-up |
| 23:21:40 | raptor | ok, back to the rolling bug list... |