Timestamps are in GMT/BST.
| 00:02:02 | | Watusimoto Quit (Ping timeout: 252 seconds) |
| 00:10:01 | | raptor Quit () |
| 03:23:12 | | raptor has joined |
| 03:23:13 | | ChanServ sets mode +o raptor |
| 03:27:12 | raptor | good evening |
| 03:30:26 | sam686 | hi |
| 03:31:35 | | BFLogBot - Commit 990e6e562f96 | Author: sam8641 | Log: Some small TNL changes for better handling of receiving out of order or duplicate packets. |
| 03:31:58 | raptor | just curious - do your TNL changes add any extra network overhead? |
| 03:32:58 | sam686 | no, just make it so it properly drops the packet instead of trying to read and process the packet when that would cause severe corruption with connection.. |
| 03:33:19 | raptor | ok |
| 03:33:47 | sam686 | as I was running into a corrupted connection when using "/lag 500 20" |
| 03:34:00 | sam686 | my latest fix seem to have now fixed that |
| 03:36:54 | sam686 | Most of my TNL changes doesn't break NetConnection and EventConnection compatibility, needed for master and older clients. |
| 03:37:03 | raptor | oh good |
| 03:39:09 | sam686 | The only change I made that broke NetConnection compatibility is adding GuaranteedOrderedBigData, but that also when moving Bitfighter master to new vps.. |
| 03:39:25 | raptor | yeah that was a while ago |
| 03:39:42 | sam686 | more like, i think, a year ago.. |
| 04:35:12 | raptor | heading to bed again - i find that i'm having a hard time coming up with things to code |
| 04:35:17 | raptor | i think we need to release soon... |
| 04:35:30 | sam686 | ok.. |
| 04:36:04 | sam686 | fix bugs is one thing to do... |
| 04:36:14 | sam686 | if you look at latest code changes |
| 04:36:19 | raptor | yes - but not very exciting :) |
| 04:36:20 | sam686 | latest bug list \ |
| 04:36:56 | sam686 | doing number 37 bug list, which is kindof easy.. |
| 04:47:16 | raptor | is #38 really a bug? |
| 04:52:17 | raptor | well, good night |
| 04:54:04 | sam686 | ok, fixed it |
| 04:54:34 | sam686 | the problem is, if you do /settime 0.2 and then bring up engineer menu |
| 04:55:02 | sam686 | engineer was still up when it should not when level changes |
| 04:55:14 | raptor | ah |
| 04:55:26 | raptor | ok, falling asleep |
| 04:55:27 | raptor | night! |
| 04:55:31 | | raptor Quit () |
| 04:55:32 | sam686 | night |
| 05:36:47 | | BFLogBot - Commit 346d01b6c63f | Author: sam8641 | Log: Engineer menu go away on level change, Fix TNL from repeated disconnect from master. |
| 06:05:01 | | sam686 Quit (Ping timeout: 245 seconds) |
| 07:43:12 | | watusimoto has joined |
| 07:43:12 | | ChanServ sets mode +o watusimoto |
| 07:51:36 | | kodaws has joined |
| 08:22:16 | | LordDVG has joined |
| 08:28:32 | | LordDVG Quit (Remote host closed the connection) |
| 10:50:30 | | KETEK has joined |
| 10:50:32 | KETEK | hola! |
| 10:50:37 | KETEK | hola |
| 10:50:46 | KETEK | Me bajao el juego pa linux en la ofi |
| 10:50:50 | KETEK | alguien juega? |
| 10:50:54 | KETEK | some one to play? |
| 10:51:07 | | KETEK Quit (Client Quit) |
| 15:09:09 | | raptor has joined |
| 15:09:09 | | ChanServ sets mode +o raptor |
| 15:09:25 | raptor | hi watusimoto |
| 15:10:01 | raptor | do you really think the screenshot issue is a bug? I remember explicitly coding it so it would take a screenshot at whatever the windows size was |
| 15:10:24 | raptor | i don't remember why that was chosen, though |
| 16:46:29 | | kodaws Quit (Ping timeout: 246 seconds) |
| 16:58:10 | | watusimoto Quit (Ping timeout: 260 seconds) |
| 17:38:11 | | Watusimoto has joined |
| 17:57:08 | raptor | !bug |
| 17:57:08 | BFLogBot | To enter a bug, please make sure it is reproducible and then go to http://code.google.com/p/bitfighter/issues/list | Also, see current running bug list: http://bitfighter.org/wiki/index.php/Running_Bug_List |
| 18:04:34 | raptor | man wikis can be slow... |
| 18:18:24 | raptor | Watusimoto: did you add bug #38 on the running list? |
| 18:25:41 | Watusimoto | hi |
| 18:25:45 | raptor | hello |
| 18:26:09 | Watusimoto | #38? is that screen shot size? |
| 18:26:32 | raptor | yes |
| 18:26:55 | raptor | i remember explicitely shoosing to code it to do the window size, but i don't remember why |
| 18:27:00 | raptor | *choosing |
| 18:27:50 | Watusimoto | so the idea when I originally coded the screen shots was that all shots would come out a standard size and look, to make posting to our screenshot section easier\ |
| 18:28:28 | Watusimoto | one thing I haven't tried is manually resizing to 800x600 and seeing how they look |
| 18:28:44 | raptor | well, they'll look worse |
| 18:28:47 | Watusimoto | but if your window is smaller, scaling up will not work so well |
| 18:29:03 | Watusimoto | if you are at 1600x1200, they should look good |
| 18:29:10 | Watusimoto | or 1200x900 |
| 18:29:10 | raptor | due to the nature of vector graphics -> raster -> resize |
| 18:29:41 | raptor | because the vector graphics have the same line width regardless of window size |
| 18:29:41 | Watusimoto | well, that's my reasoning -- all screenshots should be 800x600 to make them easier to use |
| 18:29:51 | raptor | ok, i can probably due that... |
| 18:30:00 | Watusimoto | it did work that way at one point |
| 18:30:17 | raptor | screenshots never worked for me until I coded in libpng |
| 18:30:26 | Watusimoto | I had to manually resize the window temporarily for one frame; it was a rather disjointed experience, though |
| 18:30:35 | raptor | ah |
| 18:30:46 | Watusimoto | so I did some playtesting with the heat seekers |
| 18:30:59 | raptor | oh good! with Invisible and Zemmer? |
| 18:31:04 | Watusimoto | overall, I think you guys really nailed them |
| 18:31:07 | Watusimoto | they work great |
| 18:31:26 | Watusimoto | I have a whole page of comments, but only one directly related to seekers |
| 18:31:33 | Watusimoto | well, maybe a couple |
| 18:31:35 | raptor | ok |
| 18:31:47 | Watusimoto | so I think we should definitely include them in 018 |
| 18:31:55 | raptor | yay! |
| 18:31:59 | Watusimoto | thoguh they will really change the nature of the game, I think |
| 18:32:16 | raptor | so will the energy regen |
| 18:32:22 | Watusimoto | I also think we should include the energy regen |
| 18:32:27 | raptor | :) |
| 18:32:32 | Watusimoto | also well received |
| 18:32:41 | Watusimoto | I like that it is very clear what is happening |
| 18:32:55 | Watusimoto | the previous round of energy changes were subtle, and no one knew they were there |
| 18:33:01 | raptor | yes - i was suprised at how balanced it seems |
| 18:33:01 | Watusimoto | games should have lots of exaggerated stuff |
| 18:33:24 | Watusimoto | I also noted that the teleporter engineering looks very slick |
| 18:33:33 | Watusimoto | so I think we have 3 major changes, all positive |
| 18:33:44 | Watusimoto | overall, I thought the game looks better than ever |
| 18:33:48 | Watusimoto | so I am very pleased |
| 18:34:02 | Watusimoto | so a couple of questions |
| 18:34:05 | raptor | you say that like your an observer instead of a player :) |
| 18:34:12 | raptor | err... developer |
| 18:34:16 | Watusimoto | true... |
| 18:34:19 | Watusimoto | why is the outside of the core white? |
| 18:34:24 | Watusimoto | is that an intentional change? |
| 18:34:39 | raptor | oh, that was intentional, but made a long time ago |
| 18:34:56 | Watusimoto | I seem to recall; the kids asked about it, I noted it |
| 18:35:04 | raptor | looking up the reason - it had to do with not seeing the cores very well depending on the colors |
| 18:35:11 | Watusimoto | ok |
| 18:35:17 | Watusimoto | I'll cross it off the list |
| 18:36:09 | Watusimoto | though maybe after you kill a panel, the light pane line should be red (or blue or whatever). what do you think about that? |
| 18:36:12 | raptor | i can change it back.. |
| 18:36:57 | Watusimoto | I think seekers should leave some sort of trail |
| 18:37:22 | raptor | i remember when i changed teh Core panels, the colors looked disjointed to have all the debris be the core color |
| 18:37:32 | raptor | oh wait, different question... |
| 18:37:41 | raptor | yes... i think that might be good |
| 18:37:56 | | raptor wonders where his reading comprehension went |
| 18:37:58 | Watusimoto | I'll play with that for a bit and see if I come up with |
| 18:38:30 | Watusimoto | debris should be white, but the faint line after panel is gone should (maybe) be original colr we used (faint team color) |
| 18:38:53 | raptor | yes, i think i like that |
| 18:38:57 | Watusimoto | ok good |
| 18:39:05 | Watusimoto | it will help reinforce the teamishness of the panel |
| 18:39:08 | Watusimoto | rather core |
| 18:39:09 | Watusimoto | ok |
| 18:39:17 | Watusimoto | 2. seeker trail -- I'll try some things |
| 18:39:43 | Watusimoto | the kids were dismayed that seekers sought cloaked players. |
| 18:39:49 | raptor | haha |
| 18:40:01 | Watusimoto | I am less so, but it got me thinking that maybe there should be a module to avoid seekers |
| 18:40:16 | Watusimoto | maybe sensor, or some underused module |
| 18:40:37 | Watusimoto | I really like the seekers bouncing off shields, btw |
| 18:40:43 | Watusimoto | I didn't think I would, but it is great |
| 18:40:45 | raptor | hmm interesting idea with sensor... |
| 18:40:57 | raptor | haha, yeah - it creates a bit of mayhem |
| 18:41:09 | Watusimoto | think about the module question |
| 18:41:25 | Watusimoto | it could be an existing or new module |
| 18:41:29 | Watusimoto | it could be active or passive |
| 18:41:41 | Watusimoto | it could merely hide you or actively repulse the seekers |
| 18:41:44 | raptor | so if cloak + sensor could make you immune to heat-seekers |
| 18:41:58 | Watusimoto | that might be an incentive not to use shield! |
| 18:42:04 | raptor | yep! |
| 18:42:12 | Watusimoto | what if there were a mdoule to turn the seekers back on the attacker? |
| 18:42:22 | Watusimoto | a reprogramming module? |
| 18:42:38 | raptor | hmmm |
| 18:42:46 | Watusimoto | well, let that stew a bit |
| 18:43:05 | raptor | maybe a passive area effect that makes all projectiles deadly to anyone? |
| 18:43:10 | Watusimoto | I think when you are engineering a teleporter, you should see your big green lump in the cmdrs window |
| 18:43:32 | Watusimoto | and maybe be able to do all your placement there if you so wish |
| 18:43:48 | raptor | thats seems fine |
| 18:43:49 | Watusimoto | it offers no real advantage, but makes the experience less disjointed |
| 18:43:58 | Watusimoto | I'll add that to the bug list |
| 18:44:04 | raptor | ok |
| 18:44:23 | Watusimoto | I think we should make mines and sbs a little less visible |
| 18:44:33 | Watusimoto | I know we're going to redo them, but they seem so obvious currently |
| 18:44:34 | raptor | sbs? |
| 18:44:37 | raptor | oh spybugs |
| 18:44:37 | Watusimoto | spybugs |
| 18:44:48 | Watusimoto | I'll do that too if you agree |
| 18:44:59 | raptor | well, i've had positive feedback about the passive detect |
| 18:45:05 | raptor | so maybe reduce the radius for those? |
| 18:45:07 | Watusimoto | I'm thinking of knocking them down by 10% or so |
| 18:45:18 | Watusimoto | there is already a reduced radious, no? |
| 18:45:24 | raptor | yes, about half screen |
| 18:45:29 | raptor | but so are cloaked ships |
| 18:45:32 | Watusimoto | ok, that looked like a bug |
| 18:45:50 | raptor | cloaked ships, spybugs, mines all detected at about half screen - done on purpose |
| 18:45:54 | Watusimoto | to make it look like not a bug, I think they should be partially transparent near the edges of detection |
| 18:46:10 | Watusimoto | so they fade on and off as you fly by, rather than blinking on and off suddenly |
| 18:46:38 | Watusimoto | so after some radius, we set the alpha based on distance beyond that radius |
| 18:46:43 | raptor | yeah, i coded it very simple |
| 18:46:47 | Watusimoto | until alpha hits 0 and they are invisible |
| 18:46:54 | raptor | that sounds fine |
| 18:46:58 | Watusimoto | it would be easy to upgrade as well, and would look much more polished |
| 18:47:11 | raptor | yes, good idea |
| 18:47:13 | Watusimoto | I think we should rename heat seeker to just seeker |
| 18:47:19 | Watusimoto | shorter and more accurate |
| 18:47:28 | raptor | so are you thinking different radius for mines/spybugs than ships? |
| 18:47:31 | Watusimoto | or some other name altogether |
| 18:47:46 | Watusimoto | we can keep the radius -- I am not offering an opinion on the radius detection |
| 18:47:58 | raptor | ok |
| 18:48:12 | Watusimoto | maybe the last 10% if the current radius can be the semi-transparent radius |
| 18:48:25 | Watusimoto | that would have the effect of slightly contracting the effective range |
| 18:49:03 | Watusimoto | So do you like "seeker"? |
| 18:49:25 | raptor | sure |
| 18:49:27 | Watusimoto | And should seekers seek the shooter (not sure if they do or not) |
| 18:49:41 | raptor | they target opposing players |
| 18:49:46 | Watusimoto | I like that with bouncers and mines you need to be somewhat careful where you use them |
| 18:49:55 | Watusimoto | maybe seekers should target opposing players + shooter |
| 18:50:11 | raptor | well, we could have the seeker target anyone after it bounces on the shield? |
| 18:50:11 | Watusimoto | that would make bouncing off shields more dangerous |
| 18:50:20 | raptor | that might be interesting.. |
| 18:50:30 | Watusimoto | maybe, but no one likes friendly fire |
| 18:50:30 | raptor | simultaneous idea.. |
| 18:50:58 | raptor | bouncers do that, right? opposing player + shooter |
| 18:51:01 | raptor | oh wait |
| 18:51:03 | raptor | no |
| 18:51:03 | Watusimoto | yes |
| 18:51:16 | raptor | no <- i mean, seeker does hurt shooter already |
| 18:51:17 | Watusimoto | mines are the only thing you can use to damage your teammates |
| 18:51:32 | Watusimoto | but will the seeker target the shooter? |
| 18:51:53 | raptor | no |
| 18:51:59 | Watusimoto | I'm suggesting they should |
| 18:52:14 | Watusimoto | 95% of the time this will have no impact |
| 18:53:12 | raptor | that makes shield more of a requirement, doesn't it? |
| 18:54:08 | Watusimoto | not sure |
| 18:54:24 | Watusimoto | it make seekers a tad more dangerous |
| 18:54:31 | Watusimoto | I think they really will be the weapon of choice |
| 18:54:45 | raptor | really? |
| 18:54:47 | Watusimoto | and I think there shoudl be risk involved when using them |
| 18:54:49 | Watusimoto | yes |
| 18:54:53 | Watusimoto | they aer super powerful |
| 18:55:01 | Watusimoto | I think |
| 18:55:08 | raptor | yeah, four shots to kill |
| 18:55:18 | Watusimoto | I think phasers + seekers + shield + xxx will be the new combo of choice |
| 18:55:39 | Watusimoto | but we'll see |
| 18:56:16 | Watusimoto | seekers seeking the shooter is kind of like shooting a bottlrocket off in a small room |
| 18:56:57 | raptor | haha |
| 18:57:03 | Watusimoto | Invisible had no badges on the scoreboard |
| 18:57:07 | Watusimoto | he was expecting two |
| 18:57:16 | raptor | oh? |
| 18:57:17 | Watusimoto | and Zemmer also had none, but was expecting one |
| 18:57:22 | raptor | which one? |
| 18:57:25 | Watusimoto | I'll test again now |
| 18:57:29 | Watusimoto | Zemmer = participation |
| 18:57:34 | raptor | i haven't given the BBB ones out yet... |
| 18:57:42 | Watusimoto | Invisible = part + 2nd place |
| 18:57:44 | Watusimoto | ah, ok |
| 18:57:48 | raptor | ok - so we do want a participation one? |
| 18:57:48 | Watusimoto | then no worries |
| 18:57:52 | Watusimoto | I'll cross that off my list |
| 18:57:58 | raptor | 'part' ? |
| 18:58:05 | Watusimoto | participation |
| 18:58:13 | Watusimoto | these badges are a big deal in this household |
| 18:58:16 | raptor | oh |
| 18:58:16 | raptor | ok |
| 18:58:16 | raptor | question |
| 18:58:23 | Watusimoto | ok, then one more bug |
| 18:58:37 | raptor | do we want participation + gold + silver + bronze to all be acquireable? |
| 18:58:50 | Watusimoto | what does that mean? |
| 18:58:55 | raptor | i think i butchered that last word... |
| 18:59:07 | Watusimoto | I knwo the word, just not what you mean |
| 18:59:08 | raptor | or the opposite: mutually exclusive |
| 18:59:14 | Watusimoto | ah, I see |
| 18:59:17 | raptor | so you can only have 1 |
| 18:59:18 | raptor | of the set |
| 18:59:23 | Watusimoto | good question; yes |
| 18:59:40 | Watusimoto | because we don't want an incentive to go for third if you have already finished first and 2nd |
| 18:59:47 | raptor | hahaha |
| 18:59:52 | Watusimoto | seriously |
| 18:59:52 | raptor | that would be interesting... |
| 19:00:07 | raptor | that might invite griefing |
| 19:00:10 | Watusimoto | Thomas suggested having participation badges for each BBB -- they would be numbered |
| 19:00:34 | Watusimoto | That might be too many, but it would encourage continued particiation |
| 19:00:43 | raptor | we have only 32bit mask... |
| 19:03:14 | Watusimoto | that's 256 -- if we have 4 bbbs a year... |
| 19:03:36 | raptor | ? |
| 19:03:45 | raptor | i mean, 32 bits for 32 badges |
| 19:03:50 | Watusimoto | anyway, we don't need to decide now. everyone who gets a bbb can be upgraded to a bbb9 if we decide to go that route in the future |
| 19:03:51 | raptor | total is what we send |
| 19:03:56 | Watusimoto | oh, sorry |
| 19:03:59 | Watusimoto | misunderstood |
| 19:04:15 | Watusimoto | i thought we could have 256 badges, but you are right, only 32... |
| 19:04:31 | Watusimoto | maybe we could revoke participation badges before each bbb |
| 19:04:40 | Watusimoto | so you have to keep playing to remain current |
| 19:04:53 | raptor | haha |
| 19:06:42 | Watusimoto | and then there was a bug where Ian was hosting and T was a levelchanger |
| 19:06:56 | raptor | ask sam about that - he made some TNL changes recently |
| 19:06:59 | Watusimoto | on T's window, he had a + next to his name |
| 19:07:09 | raptor | level changer? |
| 19:07:14 | Watusimoto | and on I's window, T did not have a + |
| 19:07:20 | raptor | ugh |
| 19:07:23 | Watusimoto | level change permissions |
| 19:07:26 | Watusimoto | ugh is right |
| 19:07:39 | raptor | i've fixed that (I thought) at least twice now... |
| 19:07:41 | Watusimoto | that was exactly my reaction |
| 19:07:51 | Watusimoto | well, it's still a problem |
| 19:08:05 | raptor | and you tested with latest 018? |
| 19:08:08 | Watusimoto | yes |
| 19:08:10 | raptor | rats |
| 19:08:13 | Watusimoto | current as of last night |
| 19:08:24 | Watusimoto | so that's my new list of issues |
| 19:08:31 | Watusimoto | I'll fix some, and add the rest to the list |
| 19:08:55 | raptor | ok |
| 19:09:06 | raptor | i'm working on the screenshot one |
| 19:09:28 | Watusimoto | ok |
| 19:10:01 | raptor | ugh, i have to resize the window... |
| 19:10:44 | Watusimoto | I think the Au + Ag + (Sn + Cu) badge exclusivity could be handled at the presentation level |
| 19:11:16 | raptor | yeah? code in a supersede order? |
| 19:11:22 | Watusimoto | yes |
| 19:11:25 | raptor | Tin? |
| 19:11:33 | Watusimoto | Tin + copper = bronze |
| 19:11:37 | Watusimoto | I think |
| 19:11:37 | raptor | oh duh |
| 19:11:55 | raptor | yep |
| 19:12:27 | Watusimoto | but it would be easier to code that way, I think, and we could just assign the badge without worrying who already had what |
| 19:12:38 | raptor | yes, i agree |
| 19:13:55 | Watusimoto | well, that was a good list of fixes, I think |
| 19:14:02 | Watusimoto | nothing too hard |
| 19:14:17 | Watusimoto | but long enough to make it look like I paid attention |
| 19:14:48 | raptor | :) |
| 19:25:19 | raptor | ok, everyone has participation badges now |
| 19:26:35 | raptor | an now Invisible has his silver |
| 19:27:17 | Watusimoto | wonderbar! |
| 19:43:17 | raptor | blast - i guess i can't just change the canvas, i have to actually reshape the opengl window... |
| 19:45:42 | raptor | Watusimoto: how do you want screenshots of the editor handled? |
| 19:46:03 | Watusimoto | ah.... |
| 19:46:18 | raptor | this is getting more complicated by the minute... |
| 19:46:20 | Watusimoto | in that case, I think just use the current window size |
| 19:46:26 | Watusimoto | i.e. no change from current behaviour |
| 19:46:37 | raptor | otherwise the default size? |
| 19:46:52 | Watusimoto | otherwise => not in editor? |
| 19:46:59 | Watusimoto | default => 800x600> |
| 19:47:03 | raptor | yes, like in menus/etc |
| 19:47:03 | Watusimoto | ? |
| 19:47:05 | raptor | or game |
| 19:47:09 | raptor | lobby |
| 19:47:11 | Watusimoto | I think so |
| 19:47:27 | Watusimoto | none of those screens show more than 800x600 pixels of info |
| 19:47:35 | raptor | ok |
| 20:11:16 | | koda has joined |
| 20:38:35 | | BFLogBot - Commit c82504f08ff4 | Author: watusim...@bitfighter.org | Log: Upgrade documentation tool to include c sourcecode; put documentation for lua- vec into lua-vec c files; change "vec" to "point" at the c level for consistency and understandability (will break any scripts that use vec) |
| 20:38:36 | | BFLogBot - Commit 2e9d132f058f | Author: watusim...@bitfighter.org | Log: Update Point shortcut to use point instead of vec, add deprecation warning |
| 20:38:38 | | BFLogBot - Commit a95f04c36997 | Author: watusim...@bitfighter.org | Log: Added note about when we started warning folks |
| 20:38:40 | | BFLogBot - Commit 0a5bc9b39c7c | Author: watusim...@bitfighter.org | Log: Updated documentation |
| 20:38:42 | | BFLogBot - Commit e3dfce6fb38d | Author: watusim...@bitfighter.org | Log: Make mines a tad less visible. |
| 20:38:43 | | BFLogBot - Commit d2df4f07d880 | Author: watusim...@bitfighter.org | Log: I think this is clearer, though a tad more verbose |
| 20:38:45 | | BFLogBot - Commit 9a914351e551 | Author: watusim...@bitfighter.org | Log: Merge |
| 20:44:31 | raptor | I'm trying to figure out how to resize the opengl surface without touching the window... |
| 20:44:49 | raptor | otherwise screenshots will be very annoying |
| 20:52:50 | Watusimoto | I resized the window when I did it; and it was annoying |
| 20:53:07 | raptor | there must be a better way... |
| 20:53:35 | Watusimoto | here's a thought -- if seekers are as popular as I think, maybe having shield module (activated or not) should attract seekers more as a penalty for having shield |
| 20:53:49 | | BFLogBot - Commit 1c83785ca36e | Author: watusim...@bitfighter.org | Log: Start changing HeatSeeker to Seeker, some formatting along the way |
| 20:53:50 | | BFLogBot - Commit 6156d837a87d | Author: watusim...@bitfighter.org | Log: Kill a magic number, restore seeker color |
| 20:54:19 | raptor | you foudn my magic number |
| 20:54:38 | raptor | so if a seeker is within a certain proximity of a shield, it targets that instead? |
| 20:57:42 | Watusimoto | of someone who has shields... perhaps |
| 20:58:19 | raptor | not sure if that will change dynamic too much... |
| 20:58:28 | Watusimoto | no, maybe not |
| 20:58:39 | Watusimoto | that's what I concluded about the heat portion of heatseeker |
| 20:58:45 | Watusimoto | and why I stopped pushing it |
| 20:59:07 | Watusimoto | but maybe it cuold make a sharper turn towards a shiedl player |
| 20:59:41 | raptor | well, that would require adjustments to the targeting logic: right now, once it has a target it's locked |
| 21:07:05 | raptor | getting into opengl a little deeper than i wanted... |
| 21:09:23 | raptor | Watusimoto: I think i've got openGL to resize itself without resizing the window and I'm doing it before I call the pixel capture function; however, the pixel capture function grabs the previous screen before resize |
| 21:09:31 | raptor | have you run into something like that before? |
| 21:09:39 | Watusimoto | I never got that far |
| 21:10:02 | Watusimoto | When you are rendering 100 fps, being off by one frame is no big deal |
| 21:10:31 | raptor | but the previous frame ends up being the old size... |
| 21:10:37 | raptor | which is my problem.. |
| 21:11:49 | raptor | maybe i'll try swapping buffers a bunch |
| 21:14:13 | Watusimoto | ah |
| 21:14:30 | raptor | that doesn't do anything - maybe i'm missing something more fundamental |
| 21:15:53 | Watusimoto | could you try capturing the *next* frame, which might be the right size? |
| 21:18:54 | | BFLogBot - Commit 3efca05a5327 | Author: watusim...@bitfighter.org | Log: Fix sensor help |
| 21:18:56 | | BFLogBot - Commit ceef0a49f8ba | Author: watusim...@bitfighter.org | Log: Add flickering flame effect to seekers |
| 21:18:57 | | BFLogBot - Commit 4028ed712b63 | Author: watusim...@bitfighter.org | Log: Self documenting code! |
| 21:18:59 | | BFLogBot - Commit 60f1ae48f285 | Author: watusim...@bitfighter.org | Log: Dial down the flames a bit in the help |
| 21:26:27 | raptor | if this works i'm an idiot |
| 21:29:46 | raptor | heh, i'm an idiot |
| 21:30:38 | raptor | i just needed to call render() on the UI once and swap the buffers twice |
| 21:37:34 | Watusimoto | heh |
| 21:41:09 | raptor | ha! it works! |
| 21:44:05 | | BFLogBot - Commit d0cd5c9397ec | Author: watusim...@bitfighter.org | Log: Add trails to seekers |
| 21:44:06 | | BFLogBot - Commit 916cc062a595 | Author: watusim...@bitfighter.org | Log: Formatting |
| 21:44:32 | Watusimoto | so... when you get a chance, take a look at seekers now |
| 21:44:41 | raptor | ok, one moment... |
| 21:44:55 | Watusimoto | I want to dial down the effect a little, but I wanted to see if you hated it before I go too much further |
| 21:46:57 | raptor | i kind of like it, but the streak needs to be toned down |
| 21:47:17 | raptor | like half of what it is when traveling at normal speed |
| 21:47:27 | raptor | comparable to the ship |
| 21:49:30 | Watusimoto | I want it fainter and smaller |
| 21:49:57 | raptor | maybe that's it - it needs to be fainter |
| 21:53:21 | raptor | well, it's correctly taking screenshots without resizing the window, but there is a flicker |
| 21:53:34 | raptor | i wonder if i can do buffer magic... |
| 22:07:37 | raptor | ok Watusimoto, i pushed my screenshot changes |
| 22:07:52 | raptor | tell me if it works on windows (there is a slight flicker of 2 frames) |
| 22:09:12 | | BFLogBot - Commit 2cf37d3895fe | Author: buckyballreaction | Log: Screenshots are now always taken at the default canvas size (800x600) unless in the editor |
| 22:09:19 | raptor | i wonder if i can draw off screen somehow... |
| 22:09:32 | Watusimoto | I looked into that |
| 22:09:37 | Watusimoto | a long while back |
| 22:09:40 | Watusimoto | no luck |
| 22:09:43 | Watusimoto | then |
| 22:12:02 | raptor | looks like i have to create another window? |
| 22:12:10 | raptor | looks messy |
| 22:20:27 | raptor | yuk |
| 22:20:35 | | raptor goes off to do something else |
| 23:18:34 | | sam686 has joined |
| 23:18:34 | | ChanServ sets mode +v sam686 |
| 23:23:33 | raptor | all right, going home |
| 23:23:36 | raptor | later! |
| 23:23:43 | | raptor Quit () |
| 23:47:26 | Watusimoto | heading to bed myself... I implemented the seeker trails. see what you think. give me feedback tomorrow. feel free to alter the params. they are in the seeker profile in void FXTrail::render() |
| 23:47:55 | Watusimoto | you can control the color and the rate of fade (and hence the length) by futzing with the params there |
| 23:47:57 | Watusimoto | good night! |
| 23:49:22 | | BFLogBot - Commit c6131e643f11 | Author: watusim...@bitfighter.org | Log: More keys to ignore |
| 23:49:24 | | BFLogBot - Commit dab2efb45a4f | Author: watusim...@bitfighter.org | Log: Fix lua crash |
| 23:49:25 | | BFLogBot - Commit 8fbab2e46a45 | Author: watusim...@bitfighter.org | Log: Vastly simplify seeker trails |
| 23:49:27 | | BFLogBot - Commit ba3316dd9f74 | Author: watusim...@bitfighter.org | Log: Variable case |
| 23:49:28 | | BFLogBot - Commit 704d2625449d | Author: watusim...@bitfighter.org | Log: Formatting |
| 23:49:30 | | BFLogBot - Commit 83f3742a81a7 | Author: watusim...@bitfighter.org | Log: Formatting |
| 23:49:31 | | BFLogBot - Commit d36a06e43e19 | Author: watusim...@bitfighter.org | Log: Fix compile error |
| 23:49:34 | | BFLogBot - Commit 4d40bea3a99d | Author: watusim...@bitfighter.org | Log: Formatting |
| 23:49:36 | | BFLogBot - Commit 6fd00e8a33a7 | Author: watusim...@bitfighter.org | Log: Start conversion of FxTrail to a "profiles" model |
| 23:49:37 | | BFLogBot - Commit 8d3793e66490 | Author: watusim...@bitfighter.org | Log: Spark manager works on a system of profiles now; implemented a seeker profile |
| 23:49:39 | | BFLogBot - Commit 75ac3fc4589e | Author: watusim...@bitfighter.org | Log: Merge |
| 23:53:15 | | Watusimoto Quit (Ping timeout: 252 seconds) |