Vray proxy export issue
-
Is anyone else having issues creating higher poly proxies? I'm trying to create a proxy of a 22k face tree from 3d warehouse and every time i try to export the proxy, sketchup freezes up and my processor gets stuck at 13%. I realize that sketchup is not able to utilize multi threaded processors, but it defeats the purpose of proxies if it can't handle hi poly more gracefully than this. Just curious if anyone else is having this issue.
windows 7 pro
I7 Processor
8 Gig memory
Dell Keyboard -
How long has it been frozen for? I know that I've made proxies of Xfrog trees that were larger than 22k and it did freeze for a bit but always came back.
-
It could very well be a lack of patience issue. I haven't let it run for longer than 10 min. It's just frustrating having close to 90% of my processor sitting idle while I wait for an hour to make one proxy. After making a few proxies I would have already reached the point of diminishing returns on my time.
I don't have 2.0 loaded now. I had installed the demo to play around with the new bells and whistles, but i had to go back to 1.4 to finish up some client projects. 2.0 dongle is on its way though.
-
we had a faster export method previously, but we had an issue when someone would try to export a model that had been mirrored. The normals would be inverted, and we were unable to easily remedy this without changing how we exported to utilize SketchUp's explode command... which as we have been told, and you can see... is slow. We will continue to try to optimize this process, but for this release, we opted for correct but slow, over fast and incorrect.
-
Good to know. I haven't made it as far as importing previously created proxies. Should I expect similar times bringing them in or is this a more streamlined operation?
-
when you import a vrmesh, it should be faster than going through the whole export/import process, however the vrmesh does not contain detailed material information. When you import a vrmesh, it will be assigned default materials in place of whatever materials were previously applied to the object prior to exporting the vrmesh. The recommended workflow at this point, is to create the proxy in-place, in order to preserve material information, and then export the component to a separate .skp file. All of the preview geometry and material info should be preserved in the skp, so when you import that file as a component, you won't have to wait for us to read the vrmesh file, create the preview geometry, and create or hook up materials.
-
I also have the same problem when exporting components to proxys. It doesn't freeze, it just takes a very long time. I had a tree from 3d Warehouse(file = 7 mb, cleaned out) and it took 45 minutes. The process only used 8% of my processor capacity. It's indeed a little frustrating to work with, especally when you want to create a whole garden
-
only a small portion of your processor is being utilized, due to the single threaded nature of Ruby. We have identified the cause for the slow export process, and it is fixed in a nightly build. If anyone is interested in testing a nightly build to see if it works better for them, please contact me.
-
I have been testing this nightly and I can safely say that the mesh export issue is resolved. Thanks Devin!
-
@valerostudio said:
I have been testing this nightly and I can safely say that the mesh export issue is resolved. Thanks Devin!
and thank you for testing!
-
@dkendig said:
only a small portion of your processor is being utilized, due to the single threaded nature of Ruby. We have identified the cause for the slow export process, and it is fixed in a nightly build. If anyone is interested in testing a nightly build to see if it works better for them, please contact me.
Devin, I'd like to be a tester. I need to convert the Willow Tree High Poly model from 3d Warehouse into proxy and my computer freezes every time i try... (i7, win 7 pro) I tried exploding this component to simple polygons, but then it grows from 1.7 mb to over 70 mb when exploded. Simple export to proxy fails. Thank you!
-
It really isn't a great tree, to be honest. You would be much better off using my Onyx workflow that's on the Chaos website.
-
@dkendig said:
only a small portion of your processor is being utilized, due to the single threaded nature of Ruby. We have identified the cause for the slow export process, and it is fixed in a nightly build. If anyone is interested in testing a nightly build to see if it works better for them, please contact me.
Hi, how can I contact You ? Cause i have the same issue - sketchup freezes and nothing happens. Small object are ok, and I can export them to proxy without any problems, but objects with larger geometry always cause problems. I just can't export them.
Has anyone else solved the issue ? -
We have finished developing the service release that addresses this issue, you should expect to see it available for download on our website in the next couple of days.
-
@dkendig said:
We have finished developing the service release that addresses this issue, you should expect to see it available for download on our website in the next couple of days.
What do you mean "available for download"? We must to reinstall the v-ray for that or…???
-
yes, it's a service release. It will be version 2.00.24261 I believe. We are experiencing some technical difficulties at the moment, but it should be posted on the site soon.
-
@unknownuser said:
@dkendig said:
We have finished developing the service release that addresses this issue, you should expect to see it available for download on our website in the next couple of days.
What do you mean "available for download"? We must to reinstall the v-ray for that or…???
Yes, the updated version will require uninstalling the older version and then installing the new version.
-
And it's totally worth it. This service release fixes many little annoying bugs and adds some awesome features. Batch Render and Auto Material ID are my new best friends! Hooray to Devin and the Chaos crew!
-
Cool update, fixed the export proxy issue but sometimes RT render crashes while in high resolutions.
-
check your memory usage. SketchUp is a 32bit process, so if you get close to 4gb of ram being used, you're going to get a crash. One day SketchUp will join the 64bit world, and this won't be a problem. Until then, try to keep RT renders in lower resolutions if you can.
Advertisement