Itoo Software Forum
RailClone => RailClone Pro (*) => Topic started by: lukasso on March 25, 2022, 09:55:48 AM
-
Hello,
I am working on some scene, I have not yet added many bricks but I'm starting to getting error at render. I know it's probably more to v-ray related thing but can someone please help me understand how railclone is managing memory? for me stats of railclone object looks fine and nothing should cause problems to render. There is 3 more objects like this, ok brick itself it's quite dense I can optimize it, but still I'm not understanding how this is possible. Maps for this have displacement off but error is even occurring when trying to render everything without maps. I have 64gb of ram but when trying to render it doesn't even go above 12 and error "Building Embree Voxel Tree failed" is there.
Can someone please help me understand what's going on ?
-
HI,
It would appear from your stats that none of the bricks are being instanced, which seems strange. If possible, disable slice and bend for the bricks and make sure you haven't added a modifier to the RC object. If that's not the issue, could you upload just the bricks so that we can better diagnose the issue?
Thanks,
Paul
-
Well, when turned slice and bend off there were a holes to pattern that I'm cutting my bricks so didn't try tu run render. RC objects have no modifiers.
I have uploaded scene with one spline with bricks. Maybe it's my method that is causing some problems.
please take a look :)
-
Thanks for the file. Unfortunately I can't reproduce it. Also instancing is fine at render time, my fault for not spotting that mode was set to Viewport. Does that file give you the error?
(https://i.imgur.com/M2nbw8g.png)
Are you using the most recent version of RailClone? It could be there is some compatibility issue between the version of RC and the version of V-Ray you are using.
Thanks,
Paul
-
Yes RC is most recent version.
when I copy 8 times this brick wall it reproduces error for me in this file.
edit : updated vray to newest version and now it's stuck at building light cache infinitely for 8 walls.
-
OK, I could certainly slow it down a lot by cloning it 8 times, although eventually it recovered. It would appear to be linked to the Capping, probably it is causing some problematic geometry. Disabling capping made a big difference to the light cache speed. Unfortunately, we have very little control over that capping feature because it uses a 3ds Max function for booleans.
Paul.
-
hmmm for me it was not recovering....maybe You checked on better machine and my old I7 8700k is not able to handle it anymore...I think that all settings for memory usage I have set properly. But still it's weird that crash occurred before using up all available ram memory.
-
Converting it to native instances using RailClone tools results in a near-instant light cache build. Something seems amiss here. I'll need to talk to the development team and see if we can isolate the issue.
Best,
Paul
-
Converting it to native instances using RailClone tools results in a near-instant light cache build. Something seems amiss here. I'll need to talk to the development team and see if we can isolate the issue.
Best,
Paul
thank You :)
-
Hi,
A workaround for the moment it to enable the proxy cache from the Display rollout. Alternatively, you can disable Dynamic Geometry from the registry
(https://i.imgur.com/AGZLQ32.png)
Many thanks,
Paul