Hi,
Just noticed on recently setting up a trial of Max and V-Ray 3.3, that for a scene with two million polys there is a massive discrepancy in translation times
3DS Max = .8 seconds
Maya = 1 minute 13.3 seconds
Is this something that can be improved on or is it an unfortunate limitation with Maya?
as far as i know max does not have to translate the scene… vray will render the stuff native…
yes as above.. its probably related to the fact that vray is a native renderer in Max. (all?) other versions use a connection to vray-standalone, and require scene translation.
It’s very likely that it can be improved. If you can get us that specific scene for testing, it will be very helpful to figure out what can be done about it.
Best regards,
Vlado
What is preventing Vray from being a native renderer in Maya? Can it be a Maya native renderer one day?
No; Maya does not expose its scene geometry in the same way as 3ds Max does. With that said, there are probably things that can be done to optimize the process.
Best regards,
Vlado
Sad…but thanks Vlado.
Hi,
for me, the translationg times are sometimes much to high too, when I´m rendering with DR.
When DR is “Off”, the render starts very fast, is DR “On” it needs much more time for starting render process.
As example… while working on a vessel scene with different cameras (150mb scene size),
I decided, as usualy, to put 5 bigger regions into 5 groups, than I can switch their visibility on or off, if I need them or not.
The translation time becomes nearly 45s.
But when I switch the 5 groups off, the translation time is the same! Nearly 45s.
When I delete the 5 groups the translation time shrinks to nearly 10s!
I think, that vray translate in every situation the whole scene and not only the visible parts.
Is this possible? Don´t know how I can test that, but I´m realy shure.
To translate only the needet scene parts, could be a big timesaving step.
Maybe I didn´t found the correct switch for that turbo!?
Cheers Jörg
(Win7, Maya2015, Vray3.3002)
Edited!
Hi Vlado, sure thing.
This particular case, the model is a high polygon tree. It is a commercial model, so I can’t upload here. Did you want me to upload them to oneDrive and PM you the link?
Obviously I eventually turn these sorts of models into proxies but sometimes on other objects it’s not always a solution.
Yes, you can email me a onedrive link to vlado@chaosgroup.com - thanks!
Best regards,
Vlado
Vlado, will send some scenes, too. The Maya guys have the same problem all the time. In Max the render starts almost instantly, in Maya it takes much longer.
I always put objects/groups I don’t really need to see right now in the render on layers and switch their visability … that works fine for vray to translate the scene faster.
We made serious improvements to the translation time for polygonal objects in the 3.10, but I guess we can do even better. 
If you can share scenes, we will be happy to look at them and try to improve the performance.
In general scenes with <10m polygons should translate for 5-10-20 seconds maximum. If this is not the case then there is some problem.
@snivlem:
I’ve got your scene. On my machine i7 5820 on Linux it exports for 23 seconds.
I’ve profiled it and I think I know what to do to make the translator faster.
My prediction is that it is possible to lower the export time to 12-15 seconds for this scene.
Sounds good! Thanks for taking a look at this.
I have one model that I gave up on after 5 minutes of waiting for it to translate if you would like this as well. It was under 5M polygons. I think it might be the multiple shaders to one object
Yes, this is what Teodor found out as well.
Best regards,
Vlado
If you have the time to send this model, I’d like to check it, too.
It might turn out that this is caused by something else.
The more data we have the better we could optimize.
I’ve PMed you the link to the larger model.
I also noticed an interesting thing. I’m aware the devs seem to be actively working on VP2 display but I can across this interesting issue. This is rare, but I’ve seen this issue in the past on a few models too.
In 3.4 Stable build the textures appear perfectly.
But in 3.4 nightly build (the latest 30th of may update), it has reverted back to the regular issue of V-Ray displaying some textures incorrectly in VP2 and they are slightly lower res too;
Again, I know it’s still WIP and under nightly builds but I think I should mention it just in case
Snivlem thats the baked Viewport texture.
select the object open the uveditor and switch to the original texture…
UVTextureEditor --> Textures -->
or set the VP2 baking setting to a higher resolution…
While that is probably true, V-Ray mtl should perhaps be displaying textures the same as maya standard shaders (blinn, phong do) as the object only has one uv layout.
Try the 3.4 stable build if you want yourself, something was definitely changed there. All textures appear really nicely and there is no need for that extra step you mention - it just works. Anyway, i sent that scene in for the other matter so maybe one of the devs can clarify what’s happening with the display.
