Alert icon
We're changing our privacy policy. This stuff matters.  Learn more  Dismiss

Animated Sparse Voxel Octrees: In-depth pt 2/3

Loading...

Sign in or sign up now!
Alert icon
Upgrade to the latest Flash Player for improved playback performance. Upgrade now or more info.
9,190
Loading...
Alert icon
Sign in or sign up now!
Alert icon

Uploaded by on May 26, 2011

pt 2/3 of the in-depth video series on animated sparse voxel octrees.
Contents:
- Why is voxel animation considered not feasible?
- How does my animation technique work?

Car model by Onno van Braam:
- onnovanbraam.com
- youtube.com/user/onnovanbraam

more info at: http://bautembach.de/wordpress/?page_id=7

Category:

Science & Technology

Tags:

License:

Standard YouTube License

  • likes, 2 dislikes

Link to this comment:

Share to:

Uploader Comments (radulphi)

  • This is good work... you have essentially a point-based renderer using octree as bounding volume hierarchy. A sphere tree might have been used instead to circumvent the rotation problem (not to take anything away from your solution, which is very nice).

    See also "ManyLoDs: Parallel Many-View Level-of-Detail Selection for Real-Time Global Illumination" which discusses a sphere-tree-based point renderer.

  • @theb1rd Thank you for your input, your observations are right. I'll check out the paper you mentioned.

  • Where can I read your thesis? Can't find it.

  • @Rubuler there's a link to my homepage in the video description -> Animated SVOs -> asvo.pdf

Top Comments

  • There are some really cool ideas here.

    Once you get all three parts up, I'll be sure to start sharing this with people.

see all

All Comments (18)

Sign In or Sign Up now to post a comment!
  • @Rubuler it's in the vid info above the link is to a page which links to a pdf.

  • it is that bwm that I want get !

  • @buzinaocara In theory it would. But I restore the octree property (all child nodes lie completely inside their parent node) by stretching the voxels/enlarging their bounding boxes. Though this doesn't break the algorithms you mentioned, it makes them more costly (for example a bigger BB means more ray hits => less optimization potential). This issue is also covered in part 3/3.

  • 1) Voxels are not memory efficiant. When you say something stupid like 1 bit per voxel, that does not contain color, or normal, or texture information. Once you add that, BAM your out of memory.

    2) i dont know about that

    3) LOD such as octree can be applied to triangles, so this is not a advantage of voxels

    4) streaming has nothing to do with voxels vs triangles, so this is not a advantage of voxels

    5) voxels only have color, no texture, so texturing is a disadvantage of voxels.

  • This is so stupid. Scaling the voxels to fill the gaps is a horrible soloution. This will break rendering optomizations that expect voxels to have a constant size, and orientation. You re-invented the wheel, and now its jagged, and blocky. Your wasting your life playing with cubes, when the rest of the world is rendering triangles at rates you will never, ever achieve with voxels.

  • This is awesome. Thank you so much for explaining how sparse voxel octrees work in and understandable way. I couldn't find anything helpful on Google. So this was great, not to mention incredible!

Loading...

Alert icon
0 / 00Unsaved Playlist Return to active list
    1. Your queue is empty. Add videos to your queue using this button:
      or sign in to load a different list.
    Loading...Loading...Saving...
    • Clear all videos from this list
    • Learn more