"Rarius" <rar### [at] rariuscouk> wrote:
> I did a similar image of Mars a year or so back, but rather than creat a
> mesh, I used the image to create a pigment function and from that an
> isosurface. Effectively I created a spherical heightfield. It renders quite
> fast and doesn't use that much memory. It also has the added benefit that I
> can exagerate the relief in code without rebuilding the mesh.
>
> Rarius
That's interesting. I did experiment a bit with heightfields, but couldn't
figure out how to wrap it onto a sphere. I'll have to read up about isosurfaces.
My original aim was to create a high resolution image and make an animation
of an orbit around the moon. But this needs too much memory, I reckon nearly
64Gb. Effectively I split the DEM data of the moon into about 14 strips North to
South, rendered each separately and combined the resulting images together. Each
strip used about 3.5Gb RAM, so I guess the whole moon would need 14 x 3.5 =
49Gb. If using an isosurface will let me get everything into my 4Gb I'd be
pleased.
Cheers,
Peter
>
> "geep999" <nomail@nomail> wrote in message
> news:web.4bd58963692fcaae380f8080@news.povray.org...
> > False colour image (lowest altitudes violet, rainbowing through red to
> > white
> > highest) of the back of the Moon created from data from the Japan
> > Aerospace
> > Exploration Agency Laser Altimeter on the KAGUYA (SELENE) Mission
> > http://www.selene.jaxa.jp/index_e.htm.
> >
> > There is a such a large amount of data that the image (a triangular mesh)
> > was
> > rendered as overlapping strips which were stitched together with
> > ImageMagick.
> >
> > The more familiar, but less colourful, front of the moon is here:
> > http://pgg999.co.uk/moon/
> >
> > Cheers,
> > Peter
> >

Post a reply to this message