Hi(gh)!

Finally, I succeeded in compiling POV-Ray 3.7-stable... so now I can 
start to think in a more detailed way about my modification project.

I want to introduce a new mesh object, the geo_mesh, which is meant to 
be a mesh2 following the curvature of a spherical body, but without 
generating the ASCII code overhead like the current mesh2 object does.

Instead, the geo_mesh object should treat triangles internally like the 
height_field object does - using binary data rather than generating 
ASCII SDL text.

I'm an absolute newbie in POV-Ray code hacking, so I might spend a 
fairly long time in exploring the existing code, notably the parser, 
error handling and height_field definition files.

I already started to think about the syntax for the geo_mesh:

GEO_MESH:
geo_mesh
{
   [GEO_MESH_TYPE] "filename"
   [SW_CORNER] sw
   [NE_CORNER] ne
   [RADIUS] radius
   [LOWEST] lowest
   [HIGHEST] highest
   [VERTICAL_EXAGGERATION] exaggeration
   [GEO_MESH_MODIFIER]
}
GEO_MESH_TYPE:
   ascii | gif | jpeg | png | tga | tiff
SW_CORNER:
   [LATITUDE],[LONGITUDE]
NE_CORNER:
   [LATITUDE],[LONGITUDE]
LATITUDE:
   float value ranging from -90 to 90
LONGITUDE:
   float value ranging from -180 to 180
RADIUS:
   float vector, each value greater than 0; default is <1, 1, 1>
LOWEST:
   float value greater than 0, corresponding to radius; will NOT
   override given values if GEO_MESH_TYPE is "ascii"
HIGHEST:
   float value greater than 0, corresponding to radius; will NOT
   override given values if GEO_MESH_TYPE is "ascii"
VERTICAL_EXAGGERATION
   float value greater than 0, default is 1
GEO_MESH_MODIFIER:
   smooth_triangles

What do you think of the concept?

See you in Khyberspace!

Yadgar

Post a reply to this message