ryan constantine wrote:
> 
> i've run a few tests with simple objects and everything works fine.
> then i try to scan the complex object i was talking about in my previous
> post and megapov closes on me with no explaination!  i barely starts to
> parse, and then blamo!  it blows up!  how do i fix this?

What precisely are you trying to scan? Is it, or does it contain
a triangle mesh, perchance? I did run into a problem while developing
triscan that MegaPOV 0.4 went boom when the trace() function was used 
against a mesh{...} object. Same deal with mesh2{...} The only way
around it was to change mesh{...} to union{...} (which you can
still see in the routines which export the culling.tmp file)
It's not an ideal solution, since the mesh primitive has memory
advantages, but for the nonce, it's a workaround.

I reported the problem, but, as I recall, I was too late, and
there was an acknowledgement that someone else already reported
that, and that it is supposed to be fixed in the next release 
of MegaPOV.

The only other thing that ever crashed MegaPOV entirely without
error message was running a scene with no objects in it, but I
added the generic Triscan_Setup() submacro to cure that by adding
a simple camera and text object, so that shouldn't be it anymore. 
Let me know if any of this helps. If not, can you make the 
troublesome target object available, and we'll see if I can 
confirm it so I can make a deeper inquiry into it.

Charles

Post a reply to this message