Eyecatcher im Echzeit 3D-Rendering

1,155 views

Published on

3D- Animationen können schon lange in Echtzeit gerendert werden. Was bisher aber oft nicht zusammenpasste sind realistische Bilder und Echtzeit Rendering.

Der Vortrag gibt Hinweise wie die Quadratur des Kreises gelingt und stellt Ergebnisse aus einem GPU versus CPU Wettrendern vor.

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,155
On SlideShare
0
From Embeds
0
Number of Embeds
74
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Eyecatcher im Echzeit 3D-Rendering

  1. 1. Eyecatcher in Real-Time 3D-Rendering At the example of reflection effects Tobias Günther, Videocamp Essen, 20.06.10
  2. 2. Reflection and Refraction E. Veach, L. Guibas, Metropolis Light Transport
  3. 3. Caustics Tuffenta, TU Münschen Jeremy Birn in Mental Ray, Image Copyright © 1999 by Jeremy Birn.
  4. 4. Realistic Lightning and shadows Interior 5 by bbb loaded from indigo.com
  5. 5. Hair rendering ● One of the most difficult procedures ● simulation of naturally looking hair and movements Hair rendering with D3D11 tessellation NVIDEA GeForce Demo
  6. 6. Render Quality – Reflection example 3D Real-Time with 3D non-Realt-Time without 3D non-Real-Time with Simulated Reflection Effects Reflection Effects Dynamic Reflections
  7. 7. Comparison Reflection rendering ● GPU Realtime Rendering simulated reflections ● JavaME+OpenGL (scanline rendering) ● CPU-Rendering without reflections CPU Rendering ● Blender (scanline rendering) Baked Textures 0.3 Frames/s Speed*: CPU=1/100 GPU ● CPU-Rendering with dynamic reflections GPU Rendering Baked Textures 30 Frames/s ● Blender (raytracing & scanline CPU Rendering rendering) Raytracing 0.15 Frames/s * Intel Core 2 Duo CPU 1 Ghz 512 MB RAM Mobile Intel 965 Graphics Chip 384 MB RAM, OpenGL 1.5
  8. 8. Render farms for Rendering ● Connects thousands of CPU or GPUs to one cluster ● Amazon 1 cent per hour per virtual CPU ● Oracle/Sun 1$ per hour per real GPU ● Costs CPU = 1/100 GPU
  9. 9. Over-engineered? ● Big-Buck-Bunny (2008) by Blender http://www.hpcwire.com/features/Rendering_in_the_Cloud_or_Not.html Institute ● Rendered with Sun-Cloud ● 50k computing hours (5.7 years of continuous rendering) – Sponsered by sun for PR-campaign ● 1-2 hours of rendering time for a single frame ● Total length of movie 11 min
  10. 10. Cloud rendering is a success story http://www.tomshardware.com/reviews/render-farm-node,2340.html ● 40 million hours for Monsters vs. Aliens ● 30 million hours for Madagascar Escape 2 Africa ● 6.6 million hours for Revenge of the Sith ● 72 hours per single frame for Transformers 2
  11. 11. Conclusion ● Simulating eyecandy effects in realtime rendering is kind of the art ● Disadvantage: no dynamic “corrections” after baking ● Law of speed and costs: CPU ≈ 1 ⋅GPU 100 ● Render farms “allow” for “battle of over-engineering”? Tobias Guenther Elaspix UG Twitter: @elaspix

×