00:00:00 --- log: started forth/09.01.30 01:19:09 --- join: H4ns1 (n=Hans@p57BBA4E2.dip0.t-ipconnect.de) joined #forth 01:19:19 --- quit: nighty__ (Client Quit) 01:19:21 --- quit: H4ns (Nick collision from services.) 01:19:23 --- nick: H4ns1 -> H4ns 01:20:12 --- join: H4ns1 (n=hans@p57A0CC61.dip.t-dialin.net) joined #forth 01:38:04 --- quit: impomatic ("programming @ http://tr.im/xey") 01:56:20 --- quit: proteusguy ("Leaving") 04:04:21 --- join: edrx (i=edrx@189.25.61.107) joined #forth 04:45:08 --- join: tathi (n=josh@dsl-216-227-91-166.fairpoint.net) joined #forth 04:45:09 --- mode: ChanServ set +o tathi 06:10:27 --- join: aguaithefreak (n=aguai@122-116-183-8.HINET-IP.hinet.net) joined #forth 06:26:55 --- quit: edrx (Remote closed the connection) 06:27:18 --- join: edrx (i=edrx@189.25.61.107) joined #forth 06:32:05 --- quit: nighty^ (Remote closed the connection) 07:11:54 --- join: nighty^ (n=nighty@x122091.ppp.asahi-net.or.jp) joined #forth 07:25:05 --- quit: workthrick (Read error: 110 (Connection timed out)) 07:31:28 --- quit: nighty^ (Excess Flood) 07:32:13 --- join: nighty^ (n=nighty@x122091.ppp.asahi-net.or.jp) joined #forth 07:54:03 --- join: H4ns2 (n=hans@p57A0CA54.dip.t-dialin.net) joined #forth 08:01:52 --- part: edrx left #forth 08:09:27 --- join: JasonWoof (n=jasonwoo@unaffiliated/herkamire) joined #forth 08:09:27 --- mode: ChanServ set +o JasonWoof 08:12:03 --- quit: H4ns1 (Read error: 110 (Connection timed out)) 08:54:41 --- join: GeDaMo (n=gedamo@dyn-62-56-77-42.dslaccess.co.uk) joined #forth 09:04:28 --- quit: H4ns ("Leaving.") 09:45:16 --- nick: H4ns2 -> H4ns 10:01:17 awesome, I get 61fps in vor on fedora 10:01:52 higher frame rate is really nice 10:01:59 I broke 5 minutes on my second game 10:02:14 whats vor? 10:02:16 (I was getting something like 36 on ubuntu, same machine 10:02:20 jasonwoof.com/vor 10:02:28 i get about 30 fps in wow running it in wine :/ 10:02:29 2d action game 10:02:43 vor is 2d SDL game 10:03:10 but i have an insanely large window and ive set all the comnfigs to MAX lol 10:03:25 max distance, max detail etc etc 10:03:25 you've brought it on yourself! 10:03:30 lol 10:03:33 wow is pretty that way 10:03:48 I like smotheness though 10:04:03 especially in vor where split-second timing is crucial 10:04:23 well when gentoo updates virtualbox to the 2.1.2 ill be able to move it from wine to virtual box 10:04:56 the trouble with vor at 61-62fps is that every second or two there's two frames while the actual monitor only updates once 10:05:06 this is visible as a little lurch 10:05:32 why would you want it in virtualbox? 10:05:42 might run faster than under wine 10:05:48 isn't it faster in wine? 10:05:54 dont know 10:06:24 you'll find out I guess :) 10:06:31 not able to run it in vbox yet because gentoo is behind the curve :P 10:06:39 yup 10:07:23 i already have xp and (ugh) vista running in virtualbox vm's and im installing a 32 bit gentoo right NOW because my main system is 64 bit. not ported isforth to 64 bit yet 10:07:28 if ever 10:23:17 would be very cool to have a way to slow vor down if it's going faster than the refresh rate, so it stays in sync 10:23:36 is this possible with SDL? 10:23:40 will it be with SDL v2? 10:23:53 --- quit: erider ("Ex-Chat") 10:24:39 There is something to constrain the frame rate 10:28:14 The thing I was remembering was in Pygame 10:28:26 http://www.pygame.org/docs/ref/time.html#Clock.tick 10:29:48 oh, it's trivial for me to limit the frame rate 10:30:05 what I'm looking for is a way to stay in sync with the frame rate of the actual monitor 10:30:22 eg I can limit it to 60fps, but if you're monitor is going at 70fps, that would suck 10:30:39 also, in actual practice, it would probably suck at 60fps too 10:30:56 Are you using flip? 10:31:02 think so 10:31:15 yeah 10:31:39 It says that on hardware which supports it, it waits for a vertical retrace 10:31:51 oh, cool 10:32:57 --- join: Quartus` (n=Quartus`@207.245.250.55) joined #forth 10:33:14 http://www.libsdl.org/cgi/docwiki.cgi/SDL_Flip 10:33:39 well, some year I'll have a decent graphics card with good drivers 10:34:14 It seems to depend on what parameters you pass to set video mode 10:34:37 ahh ok. that's cool, it iliminates tearing 10:34:45 but it doesn't stop me from calling flip twice in one frame 10:38:57 I need some way of knowing when the next VBT will be 10:40:33 doesn't have to be extremely accurate, eg if I just find out when they were, I can predict close enough 10:41:01 eg would be very cool to get sdl events that say "VBT happened at " 10:41:32 once I get a few of those, I can make a pretty good guess when the next one will be 10:41:44 and I can keep statistics on how long it takes to render a frame 10:41:58 I don't see anything like that in SDL 10:42:15 and after that have a pretty good idea how long it takes to do a frame 10:43:27 then if I'm able to go faster than the refresh rate, then I wait for events, until I'm, say before the next VBT 10:44:40 yeah, I'm fairly sure it's not in SDL 1.2 or Xlib 10:44:55 if it's in SDL 1.2 it's gotta be in the opengl stuff 10:58:47 --- join: ygrek (i=user@gateway/tor/x-73d8ebfdb7b5077b) joined #forth 10:59:57 --- quit: aguaithefreak (Remote closed the connection) 11:00:02 --- join: aguaithefreak (n=aguai@122-116-183-8.HINET-IP.hinet.net) joined #forth 11:05:35 --- quit: aguaithefreak (Read error: 104 (Connection reset by peer)) 11:13:23 ooh, I found something that says "swapbuffers" will wait to return if the buffer from the previous "swapbuffers()" hasn't hit the screen yet. I presume that they are talking about opengl. 11:13:46 I can't seem to find any documentation (except for the function prototype) on the opengl function swapbuffers() 11:15:26 ahh, there it is: http://www.glprogramming.com/blue/ch07.html#id5568454 11:15:33 I looked in the wrong book. red vs blue 11:16:16 here's the interesting bit: "Subsequent OpenGL commands can be issued immediately after calling glXSwapBuffers, but are not executed until the buffer exchange is completed." 11:17:08 oh, and this is before that quote: "The update typically takes place during the vertical retrace of the monitor, rather than immediately after glXSwapBuffers is called." 11:40:13 time: 5:48 11:40:17 average fps: 61.8 11:40:46 dunno if that's fast enough that limiting it would make any sense 11:41:07 I've had testers report FPS of 500 11:41:23 which is just plain wasting electricity 11:51:09 and i dont think they can accurately measure that 12:46:25 --- quit: ygrek (Remote closed the connection) 12:49:03 --- join: ygrek (i=user@gateway/tor/x-1806f4e179814254) joined #forth 12:50:06 --- quit: JasonWoof (Read error: 113 (No route to host)) 13:04:42 --- quit: GeDaMo ("Leaving.") 13:19:23 --- join: JasonWoof (n=jasonwoo@unaffiliated/herkamire) joined #forth 13:19:23 --- mode: ChanServ set +o JasonWoof 14:06:53 --- quit: nighty^ (brown.freenode.net irc.freenode.net) 14:06:53 --- quit: warpzero (brown.freenode.net irc.freenode.net) 14:06:53 --- quit: preflex (brown.freenode.net irc.freenode.net) 14:06:53 --- quit: uiu_ (brown.freenode.net irc.freenode.net) 14:06:59 --- join: nighty^ (n=nighty@x122091.ppp.asahi-net.or.jp) joined #forth 14:06:59 --- join: warpzero (n=warpzero@75-175-228-234.hlna.qwest.net) joined #forth 14:06:59 --- join: preflex (i=mauke@rm-f.net) joined #forth 14:06:59 --- join: uiu_ (n=ian@schihei.net) joined #forth 15:36:27 --- quit: ygrek (Remote closed the connection) 16:47:12 --- quit: qFox (Read error: 54 (Connection reset by peer)) 16:55:52 --- join: edrx (i=edrx@189.25.95.134) joined #forth 17:13:02 --- quit: nxt (Remote closed the connection) 17:21:24 --- join: nxt (n=nxt@77.207.25.109) joined #forth 17:43:26 --- quit: tathi ("leaving") 19:15:03 --- quit: I440r (Remote closed the connection) 20:26:37 --- quit: JasonWoof ("Leaving.") 20:47:09 --- part: X-Scale left #forth 22:59:53 --- quit: edrx (Remote closed the connection) 23:59:59 --- log: ended forth/09.01.30