Cage opened this issue on Dec 20, 2006 · 1232 posts
Spanki posted Wed, 05 March 2008 at 10:05 PM
Hey JP,
I'm happy to hear someone getting some use from the script - it was fun to work on. Unfortunately, I don't really have the time anymore to be 'back at work' on it though :).
Cage,
Keep in mind that when I last messed with this script, I was under the impression that it was working fairly well (relative to 'hits', etc). So without knowing the specific details (or having the time to investigate them), I'm reluctant to draw any conclusions.
But to respond to your suggestions and comments in general...
Yes, scaling the mesh up (internally) would likely help. But I wouldn't stop at 10x, I'd scale everything up by 1000x (which is how I typically work with Poser meshes in my 3D app).
If my suggestions about the rounding-error-values above are not working for you (? which would be a bit surprising, so I'm guessing you didn't try yet), then if you have other point-in-tri code that works better for you, I'd say use that :). I'm not married to that bit of code, I just tried to make it work in this implementation (and it does seem to be working well for me).
...I'm not sure I'd bother making the error variables a user-supplied value, you just need to find the ones that generally give the right answer. Or, as mentioned, if you think the other code you have works better, use that instead - I won't be offended or anything :).
Cinema4D Plugins (Home of Riptide, Riptide Pro, Undertow, Morph Mill, KyamaSlide and I/Ogre plugins) Poser products Freelance Modelling, Poser Rigging, UV-mapping work for hire.