tpaviot/oce — pull request #196 by QbProg (2011-11-20 14:39:54+00:00)
Title: Disable BSpline Mesher Option

Hello,
in OCE-0.7.0 we disabled the BSpline mesher.
I did some tests at work using some real world models, and I ended up with disabling this change. Many NURBS models , with the same precision, look ugly. It seems that the
calculated normals are much worse. I can't post the originals here, but I'm finding a way to recreate similar cases that I'll add as tests.To solve the issues I found I had to increase the precision
which led to a global slowdown.
I don't want to discuss again the current mesher limitations, and please don't take this as rant, but just as a feedback.
To point for this is that IMHO we should be a bit more carefoul when doing these breaking changes, at least if we want a relatively stable OCE behavoir.
Of course the really cool thing about OCE is that one can revert the commits and have the desired behavoir :)
Personally I prefer overmeshed to undermeshed/ugly normal models, but this can change depending on the application field.

Anyway, we can use this pull request to discuss again:
- If we should have an option to disable the bspline mesher (until it gets better)
- The default for that option

To me, it is YES,OFF. The current code reflect this, but can be easily changed.
Let's try to have a more complete scenario (i.e overmeshed vs. undermeshed models), I will try to provide both and add them in this branch during the next week.