Thanks, that was really helpfull. But what exactly you mean by ” read the documentation to understand how meshes work and how to work with them”?

I really wouldn´t call it lottery because if lottery would worck this way, I´ll be very rich. It´s not a random precision problem, in my case, I have …

Yes I am, but why it´s only Z-axis having problems with precision?

I know, but at least $.max returns not 100% corect value, example real max is (1, 1, 1) but $.max returns something like this: (1.0, 1.0, 1.000001).

Thanks a lot. Wondering why the maxscript documentation never mentions that .mesh property. Is the order of .mesh.vertices always the same? I mean .me…

Thanks, that looks very interesting, let see what I can do with it using my very limited maxscript knowledge, but sincerely grateful. Just 1 question…

Like I said, really apologize for the misunderstanding. I know it´s hard to believe, but english is really a much biger problem for me than math. I am…

Man, really not understanding why you always geting it wrong? I ageed with you, just wanted to know if there is posibly a way to improove my solution….

OK, thanks for the example. However the reason the bounding sphere in your example is not optimized, seems to be because the center of bounding box an…

So I am going to try something like this fn getBoundinRadius center spheres =( rMax=0 for s in spheres do ( r=length(s.position-center)+s.radius if r…

Thanks, have already seen that CGAL APi, but have not found the sorces and even if I do porting that C/C++ code to maxscript will defently go over my …

But I would like to have an optimized bounding sphere and for spheres this algorithm retuns a bad aproximation. For meshes and boxes it worcks fine.