pouët.net

thank you everybody :) soundtrack will be made available shortly, just need to get some rest now.

to all those who say that this is "flash", by which i believe you mean "it could have been done in flash", i beg you to try. once you land in the pit of floating point degeneration despair, you will understand that such stuff looks much easier to do than it is (yes, i learned that the hard way, too ;).

more later :)

lemmus, the rgb-lines-from-center-thing actually works only on a quite high resolution... i think i picked it because of the weird moirée effects that build up when you keep staring at the center object for some time.

numtek: but it's not a guarantee for a well executed production. i remember that one wild entry taking place in a flower shop. forgot who made it though ;)

http://downloads.paniq.org/paniq-masagin.ogg

maybe i should tell a bit about the circumstances, so you guys understand better how it went.

we had only three months to do this thing. there was no werkkzeug involved. i took chaos' new altona subsystem (which is going to be open source one day) and added a new 2d engine on top. i extended the svg compiler i wrote for "die ewigkeit schmerzt" and wrote a script compiler (msgc) to be able to describe object chains/trees and transitions quickly. i wrote a deductive camera system. i solved the problem of infinite zooming once and for all. this already swallowed a lot of time.

regarding the motion blur i started off with nvidias shader based motion blur that i found in a paper, but found it to be worthless. instead i followed chaos' suggestion to just render the scene 16 times. that gave the best results, even if this would mean a massive fillrate sucker. we also got a FSAAx16 for free out of this (and you could also do blur and depth of field with it, but i found no good use for it yet.)

later on i got cp and tournesol to join me so we could get more content done. i had about 60% of the demo finished when i arrived at the party place. the demo wouldn't play through at all, but we had like 16 unfinished scenes which all followed the concept roughly. thursday to sunday we kept adding up and polishing the scenes until it became what you see now.

i am aware that there is a lot of stuff in it which could be done better. i apologize for the lack of time we had. you are all right, and we are going to try harder next time. i suppose i'm going to do this 2D stuff until nobody wants to see it anymore, and see how far i can push up the looks, and how many ideas i can stuff in in the future.

there are playback controls in the demo, btw. TAB turns on debug view, then you can use SPACE to halt the demo, and left/right arrow keys to skip forward/backwards (in pause mode it is slow motion). takes a little time for the player to react the first time because the track is being prepared for seeking.

i am going to release all SVG content in a few weeks, including the scripts and parts of the build system that i used.

emzic: the svgs are being translated to meshes in a preprocessing step, and those meshes are later being uploaded to the graphics card and rendered like that.

boyc: exactly :)

when will the first guy call it "boring 2d-flyby"? ;)

Seriously I'm really glad i could start my internship at neuro with this production. It was a massive experience! Thanks to paniq for asking me to join in! :)

wade: i'll think of you when i do my next production :)

aw crap i voted for myself that was stupid. i wish it was possible to just check "i am the creator and therefore do not wish to vote" on pouet :/

wade: i had nagging devils on my shoulder for this prod already, but yeah, thats the spirit ;)

tmb is back \o/

because you should listen to the voice in the music, not the one in your head. It clearly says "A monk asked Tozan". :)

which crowdpleaser exactly? perhaps it was more self-pleasing, who knows ;)

plonk420, actually i spent a lot of time tweaking the motion blur, and it is exactly the same you get as in regular cam recording.

contrary to intuition, an object passing the cam at a constant pace will be blurred equally on both sides. only when the object would be speeding up or down right in this frame, one trail would be longer than the other.

think about it: the camera shutter opens for a short period of time in which the object passes the lens very rapidly. in this case the position of the object distributes equally over the entire distance it moved, and while it appears to be translucent, its volume stretches. this equals to taking a lot of shots in a short amount of time and calculating the median cut of the frames recorded.



gargaj: exactly.

thanks ryg, that was the word. ;)

guess my knowledge of math terminologies is below any median cut :/

sonic: actually, this is sparta.

ferris: just looked up hugo elias motion blur, and i think that's the method i used. i did a supersampling of 16/8 images per frame (with a bit of overshooting because it looks better), which is adaptive to the framerate. each image is shifted to form a 60° 4x4 or 4x2 antialias kernel as well. when the image is not moving, the lines appear anti-aliased. there is another effect you can do with this, which was not used, which is blurring and depth of field.

so with supersampling images, you kill several birds with one (cpu heavy) stone: realistic motion blur, anti-aliasing, depth of field.

smash, I burned three different algorithms, just rendering the scene 16 times per frame simply looked the best. it's what render programs do, after all :)

Published the article on my blog as well:

http://blog.paniq.org/2008/11/how-masagin-was-born.html

"Masagin" in fucking HD resolution: http://tinyurl.com/9t3plh 5

without the 5, sorry ;) *verspackung

kaoD: it was in some way also a homage to Shpongle, yes :)

no scene.org award for my work? again? well, i should take it like a man: AAAAAAAAAAAAAAARRRRRRRRRRRRRRRGGGGGGGGGGGGGHHHHHHHHHHHHHHHHHH!!!!