statement from a coder in quite needed :)

category: general [glöplog]
i'm working on fixing kkapture bugs and problems again; last year i couldn't get "hypnoise, part 1" to kkapture nicely for the scene.org awards, and had to settle with using the "automatic frameskip" liberally. i didn't have time to look into it back then, but it bothered me :). yesterday i discovered a similar problem with "atmta", and it seems to occur with "yes we can" too.

what's happening is that the demo seems to busy-wait, spinning and calling "waveOutGetPosition" in a loop until a certain amount of time is elapsed (seems to be pretty close to 50ms with "yes we can", didn't try with the other ones). in effect that means i can't capture the demo with more than 20fps no matter what i do. is this intentional? if yes, what's the point? i can see why you'd want it with a feedback-heavy demo like hypnoise, but there's no reason that i can see to do this in "yes we can".

anyway, i'm now adding code that detects this behavior and automatically advances frames if necessary to kkapture, but i'm still curious why it's written this way.

i would've used mail, but there's no email addreses in your nfo-files and no website :)
added on the 2010-03-04 00:13:11 by ryg ryg
I was also wondering why hypnoise, part 1 is running with only ~21fps... at least that's what fraps is telling and i think it's correct.
would love to see one of my fav intros of all time running at 60fps!
added on the 2010-03-04 00:57:37 by RufUsul RufUsul
feedback effects are dependent on framerate.. you either lock the framerate to something, or it looks different on each machine. And if you're locking it, you lock it to something low or a lot of machines can't render it fast enough and the effects no longer look right again...
added on the 2010-03-04 01:15:57 by psonice psonice
ryg: code recycling is a bitch :). I am sure they just used the same base for the two intros, considering hypnonoise has been released earlier.
added on the 2010-03-04 04:20:01 by decipher decipher
same code - maybe, but ofcourse i also see no reason locking fps in yes we can
lets see what ized can say about it:)
added on the 2010-03-04 05:48:24 by unc unc
Old codebase from feedback prods. I'll release multiresolution universal titan pack kkrunchy-friendly "yes we can" version in few days.
added on the 2010-03-04 11:22:24 by Ized Ized
kkrunchy-friendly? don't you mean kkapture-friendly? :)
added on the 2010-03-04 11:25:11 by kusma kusma
oh yeah. I'm asleep now, so... I did it just for lulz
added on the 2010-03-04 11:26:50 by Ized Ized