Ok, I got it partially working with a Linepick replacement. It seems the rounding errors are occuring here too :(
Additionally it ssem I got troubles with the backface culling flag of the rit function (ray intersect triangle).
This version is faster than the Linepick version, even with this whole brute force triangle intersection scanning:
with Linepick it took 235 millisecs, with "rit" only 131ms.
Nevertheless, one thing is clear: the entire linepick (and rit) philosophy is way to slow for practical use. Using this for a scene of several thousand tris may take several seconds to complete.
So I'd suggest we stop this and try to do it the correct, official way, checking the neightbors normals etc. as described in some of the pages I linked to.
Additionally it ssem I got troubles with the backface culling flag of the rit function (ray intersect triangle).
This version is faster than the Linepick version, even with this whole brute force triangle intersection scanning:
with Linepick it took 235 millisecs, with "rit" only 131ms.
Nevertheless, one thing is clear: the entire linepick (and rit) philosophy is way to slow for practical use. Using this for a scene of several thousand tris may take several seconds to complete.
So I'd suggest we stop this and try to do it the correct, official way, checking the neightbors normals etc. as described in some of the pages I linked to.