Hello, we’re on version 3.60.04 and experiencing very slow .vrmesh loading of heavy proxies, much slower than versions 3.50.xx
According to changelog, this was supposed to be fixed, but we’re still having slowdowns. Are we missing something?
Any help will be appreciated!
We did fix it, but it turned out the fix included in 3.60.04 was not enough, as it was still slower than 3.50, like you’ve noticed. Our developers are still working on it. Sorry for the inconvenience.
Thanks. I’ve been reading here posts from other people with similar problems with vray proxy linking/loading times, dating months back.
VRay proxy usage (lots of them!) is absolutely essential for our workflow, and I’d guess equally important for other professionals & studios.
We’d really appreciate a fix as this problem is seriously impairing productivity, affecting scene loading, test rendering & final rendering times
Same problem here, very slow loading a most of time i dont have time to wait for it.
How it looks ? Any progress here ? @yolov
This should be fixed in the stable builds for 3.6 - those will appear as 3.60.05 in the stable folder on the nightlies server. See if you have access to those.
Any build number higher than 28245 should have the fix.
Are you on another version of V-Ray?
Yes, i have access and i do some tests today with scene opening.
Maya 2017 - V-Ray 3.52.03 => File read in 2.9 seconds.
Maya 2018 - V-Ray 3.60.05 build (28392) => File read in 150.2 seconds.
Rasto
The issue we’ve been originally discussing was about loading the proxy files at render time.
You’re talking about the time it takes for Maya to read the scene file itself.
What you’re describing is not normal, though.
Could you send us the scene so we can run some tests here and see if there’s something wrong that we can fix?
It’s looks like same problem. We have files on network, because of renderfarm.
When you’re opening the scene - are the proxies on the same location for both maya/vray setups?
Can you get us the scene with the proxies to debug it?
The issue was not about scene opening, but linking the proxies at render time. Maybe there’s another problem.