I’m working on a product visualization. For some reason I get very messy rendering results. V-Ray clipper isn’t working either. I believe the tiny scale of my scene is causing the problems. This somewhat complex product is less than one millimeter in size. Obvious thing to try would be scaling the scene up. Does V-Ray have any parameters, that would help without scaling?
Hmm…I just tried this with a tiny teapot of 0.005mm radius. I haven’t worked out how to get it to display in the viewport at that scale using a camera or in persective mode (with mm set in both settings) but
as far far as rendering goes there is no problem, apart from adaptive dome giving obvious block artifacts.
With a 1mm cube there are no issues here at all, so you should be ok with the correct scene settings.
EDIT: Clipper also works ok here with those settings.
EDIT: Silly me…of course you need to adjust viewport clipping at that scale also.
Not sure what I’m looking at tbh…can you share a stripped scene with just a part maybe, with your lights?
To be honest I can’t really be sure what the object is and so what might cause it. It looks like a bevel on a cylinder, so it could be the geometry is not right somehow. Or something else entirely…
Without more info you probably need to send it to support, to cover NDA issues here 
That doesn’t unfortunately identify any bad geometry, as other renderers will render bad stuff quite happily, whilst Vray will not. As in this post a while back https://forums.chaosgroup.com/forum/…em-please-help
Your object could have a simlar thing going on - easily fixed with the same technique. I hope that helps
This is what I would do. I think it would make your life a lot easier.
On a few projects in the past, I’ve had to work with scenes that were extremely large and very very far away from the world origin. So large that even in the viewport and in animations (this was Maya, but probably applies to other software too), when objects or cameras got way way far away from the origin things would start to jitter around due to precision error of the enormous size of the numbers. Even if the camera and the object you were viewing were next to each other, just being that far away from zero caused problems. Plus, working with those giant numbers was difficult, having to stretch your interface out just to see how many zeros or commas were in the numbers. 
Our solution wasn’t to scale the scene down, but to shift everything so that the camera and objects were closer to world zero. That fixed the problems. Scaling would have worked too, but we opted to move instead of scale.
If your scene is that small, I would scale up by a factor of 10, or even 100 or 1000, and move on.
It’ll need to be exported with higher tessellation is all - sounds like they gave you a viewport resolution version rather than the hi-res one.
And whoever is exporting it needs to make sure that they join all the surfaces etc., to prevent these errors
and make it generally nicer to work with, i.e. less for you to potentially fix
I didn’t even know Polytrans was still in existence…not used it for years so can’t help with that - but you shouldn’t need it, as Max can import step files.
If you get stuck then I can most likely sort it out but that of course means sharing the model - totally secure this end but I understand any reluctance
Thanks again,
I use Polytrans almost daily, have been using since mid 90’s. Sometimes I even Fix my corrupted Max meshes there. I also use the PT polygon reduction tools of it a lot. In this case I used most dense settings for meshing, but still got too few polygons.
I have not yet tested Polytrans mesh healing tools for built in Max imported geometry.
You could check out this https://www.npowersoftware.com/NewPo…oOverview.html as an alternative, which will allow you to have basically the same level of control in the model as in the original software but within Max.
A little follow up. I managed to do better tessellation by using Polytrans import. Rendering the same model, I didn’t get the artefacts. So it seems Max built in importer was the source for the rendering problems.
That’s a good result then, I’m glad.
I remembered that Max’s import module for these wasn’t good - haven’t tried in a while.
Anyway, problem solved
Actually the ATF importer works really really well on Step/Iges and Catia files. Doing it all the time, never got a serious issue.
Maybe they improved it since I last tried.
I miss Deep Exploration which seemed to magically be able to open any file format that was ever invented. A life saver at times when nothing else seemed to work properly or quickly or whatever was the issue.
Hi again,
I have similar problem with very large scene. I have this 100 km long renderable line in my large landscape model. I’m looking a way to point out distant objects in a landscape. I changed it to mesh, but it didn’t change anything. Should I maybe try chamfering edges?
By the way, I was surprised to see how quickly the scene rendered with all the 2 million trees consisting 1,5 million polygons each, not to mention grass on the ground.
Not sure what you mean exactly. To test, I just made a line that was 100km long with an arbitrary thickness…made it pointy like yours and it all renders fine.
All I changed was the scene/system scale.
I tested shortening the line to 5 km lines put one after another and the ghosting was gone.
Still, odd that it works here - but glad you found a solution