On Jul 31, 2013, at 03:56 PM, Harmanpreet Singh <[email protected]> wrote:

I already encountered this problem. Are there any test cases available
for g-obj's unexpected behavior or I have to have checks of my own on
it?

Quick answer is that you have to do your own checks, and should be doing them anyways as Rai mentioned for all operations.

This gets back at my earlier comment.  Converting geometry from our mathematical representation (implicit format) to facetized polygonal geometry (like OBJ) is not robust.  In fact, the method employed is non-deterministic, very sensitive to tolerances, and (probably) np-complete.

Currently, the process is:
implicit+CSG to [tessellate] to mesh+CSG to [CSG Eval] to mesh

The new process will be:
implicit+CSG to NURBS+CSG to [CSG Eval] to NURBS to [tessellate] to mesh

Cheers!
Sean

p.s. Don't forget to submit your student evaluation.  You have less than a day remaining.

------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent 
caught up. So what steps can you take to put your SQL databases under 
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
BRL-CAD Developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/brlcad-devel

Reply via email to