flipCode - Tech File - Conor Stokes [an error occurred while processing this directive]
Conor Stokes
(aka DirtyPunk)
Click the name for some bio info

E-Mail: cstokes@crytek.com
http://www.claustrophobe.8m.com



   05/04/1999, More on Volumetrics


Spherixals, or Spherical Volumetric rendering is actually rather a nutty idea of mine. If you read my previous post. It means that instead of having 4 sides to represent a voxel object, and mip maps of them and the multiple layers of maps, you only need the sphere map and sphere layers.

I think they have a lot going for them. They do need a hi res mesh is needed close up, but I think that the same can be said for voxels. Spherixals can be rendered using bilinear height filtering. They can have details applied. They can be procedurally generated. They can have multiple passes. They can have fogged rather easily (and rather quickly). They could be used as fog volumes too, with a little thought.

Volumetrics like the one above are rather interesting. They could create rather odd shapes, and such. One possible use I can think of is shadowed volumetric light. Think of a green glow. It is through a gas or something. There is a rather large grill obscuring portions of this. So as you walk past a normal occurance of this. You would get some rather odd effects. Volumetrics like spherixals on the other hand could render them fine.

One rather odd idea I did have though, was using spherixals to represent normal lights. This one is a little bit odd, because effectively it is using saved pregenerated rays.

One sphere map would be needed per point light. Then, at each point on the map, you shoot a ray in that direction of the normal of the sphere (your sphere is constant). You record the distance to the the polygon it struck. This can be precalculated. At that point, the opposite of the original normal from the sphere, is then the light vector in unit form.

Of course, this could be used to do shadows as well... But there is a flaw in that, if you do, you could end up with a shadow holes. So I recommend using a pregenerated set of only the lighted polygons.





  • 12/29/2000 - Techfile From Somewhere Different
  • 10/10/2000 - Some Fun, And A Cameo Appearance
  • 08/10/2000 - Déjà vu - And I've Done It Before
  • 07/08/2000 - Various Loose Ends To Hang
  • 05/15/2000 - The Way To Hit A Ball With A Bat. Or Not
  • 03/28/2000 - The Fine Art Of
  • 02/13/2000 - A Life Time of Learning, Teaching and Eating M&Ms
  • 12/09/1999 - Strangeness And Wondering If You Are Taking Innovation A Tad Too Far
  • 11/12/1999 - How to Break Exam Tension? Update Your Techfile
  • 09/14/1999 - Lots of Ramblings, personal things and comments on why SNFU
  • 08/23/1999 - Trials and Tribulations of Being Cerebrally Defunct
  • 07/29/1999 - Quick Update about Stuff and Things
  • 07/25/1999 - I'm Back Baby
  • 07/01/1999 - Is it so? Or am I just a Psycho Babbling Mental Hobo, who's Brain has No Home?
  • 06/25/1999 - Another Couple of Things
  • 06/17/1999 - I Am A Naughty Little Boy ;( But I Have A Way To Make Up
  • 06/16/1999 - What the hell? A new data structure for visibility? I don't know, I haven't heard of it.
  • 06/05/1999 - A Little Right Brained
  • 05/12/1999 - A Couple O Things
  • 05/08/1999 - Pre Computable Nice Visibility Sets
  • 05/04/1999 - More on Volumetrics
  • 04/30/1999 - Generic Update
  • 04/27/1999 - Spherical Volumetric Rendering (Mapping)
  • 04/25/1999 - Fractal Curves, Emulation Of Nature
  • 04/25/1999 - Claustrophobic Irony Level Loading and Manufacture
  • 04/24/1999 - Visibility Ramblings
  • 04/21/1999 - Why Software Rendering Is Not Dead
  • 04/17/1999 - Optimizing For Specific 3D Hardware

  • This document may not be reproduced in any way without explicit permission from the author and flipCode. All Rights Reserved. Best viewed at a high resolution. The views expressed in this document are the views of the author and NOT neccesarily of anyone else associated with flipCode.

    [an error occurred while processing this directive]