|
Making Good Progress by Fizzer
[nfo]
|
||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
|||||||||||||
|
popularity : 60% |
|||||||||||||
alltime top: #5083 |
|
|||||||||||||
|
||||||||||||||
added on the 2021-04-04 16:32:03 by fizzer  |
||||||||||||||
popularity helper
comments
wow
rulez added on the 2021-04-04 16:33:05 by wrighter 
it was amazing, and then I realized you had to render each photograph, and then it was incredible
"play baalll~"
Still cuteness overload =)
Quote:
- thisit was amazing, and then I realized you had to render each photograph, and then it was incredible
Thumb up for the photos alone! Super solid prod. Love it!
Nice and funny picture and great workstage idea
The motion blur is a really nice touch. I'm wondering if the scene has been rendered multiple times to achieve it.
Just thinking about the amount of work it must have been to give every single brick a plausible velocity vector...
nice
Amazing!
wow
For the little details alone
The more I look at, and think about this, the more awesome it gets. Did you manually hardcode the positions/motion? did you simulate the collision externally and pack the data? did you *run* a simulation in the exe??
So many little details to enjoy in the rendering too.
So many little details to enjoy in the rendering too.
Fizzzzzrrrrrrr
I guess I'll make a more detailed write-up later, but since some people are asking already:
The positions, orientations, and motion data were all generated offline and stored in the executable with a delta-encoding scheme. The placements of the blocks you see in the photos at the back (the built 'tower') is procedural, but the deltas for the foreground positioning and motion are stored as data.
I in fact ran a full rigid body simulation of the blocks being hit by a sphere. To do this I used the opensource ODE library so I can do some hacks and easily access the simulation state directly with C++ code. Yes, this required the same procedural tower-building code to exist in both C++ and GLSL.
The photos are not rendered separately: They act as 'portals' so that any rays hitting them are teleported back to a camera position and some global variables are tweaked so that the lighting setup is different and the tower of blocks is at a different stage.
There is only one rendering pass, although it is split into tiles to avoid driver timeouts. In any case each pixel is calculated only once, and by one pixelshader.
I hope that clears a few things up for now! I'll provide sourcecode and detailed descriptions of the compression method etc. later.
The positions, orientations, and motion data were all generated offline and stored in the executable with a delta-encoding scheme. The placements of the blocks you see in the photos at the back (the built 'tower') is procedural, but the deltas for the foreground positioning and motion are stored as data.
I in fact ran a full rigid body simulation of the blocks being hit by a sphere. To do this I used the opensource ODE library so I can do some hacks and easily access the simulation state directly with C++ code. Yes, this required the same procedural tower-building code to exist in both C++ and GLSL.
The photos are not rendered separately: They act as 'portals' so that any rays hitting them are teleported back to a camera position and some global variables are tweaked so that the lighting setup is different and the tower of blocks is at a different stage.
There is only one rendering pass, although it is split into tiles to avoid driver timeouts. In any case each pixel is calculated only once, and by one pixelshader.
I hope that clears a few things up for now! I'll provide sourcecode and detailed descriptions of the compression method etc. later.
Much effort for a picture. But that paid off !
motion !!!
Treffer.
Rulez. Especially given the work for the back photos and such.
Awesome!
Works on many levels but I really love the technical details explained by fizzer above. Polaroid portals + a custom compression scheme for scene data = awesome!
great!
Conceptually the strongest entry in the compo by far. The photos in particular are a stroke of genius; they're subtle, but at the same time breathe so much meaning into the picture at a relatively small cost! Always fascinating to see such incredible asset reusal.
cool idea
This could be the cover of an OpenGL RedBook or Renderman cover. Very nicely done!
awesome sense of motion here, really stood out in the compo!
also cheers for the small writeup, much appreciated! I expected the "portal rendering" but the physics stuff was unexpected, very clever!
Nice tricks!
Nice tricks!!
Awesome idea with the photographs.,
Sorry to whoever built that tower
good one
Best concept. This scene seems alive.
????????? the little details on the toys, the progress photos, and physics ???????????? how??????
Absolutely love this!
nice!
Didn't feel this one, the colors / tone of the image is just too dull.
Nice one.
Just when you tell them to not play inside...
But nice result!
But nice result!
cool stuff
<3
something about the colors seems... washed out for lack of a better word? even though there's lots of stuff going on with what looks like global illumination. the sense of motion somehow doesn't work for me and I'm also not sure why, it seems like technically everything is there. still, lots of stuff going on and nice detail everywhere
submit changes
if this prod is a fake, some info is false or the download link is broken,
do not post about it in the comments, it will get lost.
instead, click here !