Filter: Safe | Tue, Jul 14, 8:16 AM CDT

Renderosity Forums / Carrara



Welcome to the Carrara Forum

Forum Coordinators: Kalypso, Anim8dtoon

Carrara F.A.Q (Last Updated: 2026 Jul 11 2:50 am)

 

Visit the Carrara Gallery here.

Carrara Free Stuff here.

 
Visit the Renderosity MarketPlace - Your source for digital art content!
 

 



Subject: Volumetric clouds not showing in network render


tkane18 ( ) posted Mon, 30 January 2006 at 3:34 PM · edited Tue, 14 July 2026 at 4:21 AM

file_322547.jpg

I have a scene (as shown) which renders differently depending on whether I use network rendering or not. For some reason, the volumetric clouds will not render using network rendering. I have another file which renders the clouds either way.

Just wondering if anyone else came across this?

I am using 1 render node and everything is updated to 5.0.2.


bluetone ( ) posted Mon, 30 January 2006 at 4:52 PM

Is it Primivol, or the new Carrara5 native volumetric clouds? The reason I ask is if you used Primivol and didn't have a copy on the render node machine, it would fail. (But, then again, I thought it would fail the network portions or completly, not give you something with a piece missing... hmmmmm)


Kixum ( ) posted Mon, 30 January 2006 at 7:37 PM

bluetone had my idea. Since you can get it to work either way for a different file, I would rule it out. Send it to Eovia and see if they can hack on it. -Kix

-Kix


ren_mem ( ) posted Mon, 30 January 2006 at 10:54 PM

Unless as mentioned you are using native carrara volumetric on one and primivol on the other. Also you can try turning multi threading off to see if that makes a difference or change tile size.

No need to think outside the box....
    Just make it invisible.


tkane18 ( ) posted Tue, 31 January 2006 at 9:05 AM · edited Tue, 31 January 2006 at 9:06 AM

This file just uses the C5 volumetric clouds - in fact, I don't own any plugins...yet.

I tried ren mem's suggestions of turning multi threading off and changing the tile size but I still got the same results.

When I get a chance I will send it off to Eovia support.
It's not a critical file...just a test file.

Thanks for the responses.

Message edited on: 01/31/2006 09:06


LCBoliou ( ) posted Tue, 31 January 2006 at 10:42 AM

There is a problem with the new volumetric clouds -- depending on scene configuration. This was acknowledged by Eovia's folks after I sent them a scene with V-clouds that was having memory allocation errors. I also noticed that it seemed there was some sort of weird network render time-out(?) when rendering with high quality V-clouds -- took a very long time for the render to start, and when it did, I would be missing the V-clouds on one or more nodes.

Eovia's team seems pretty much on top of things, as they seem to frequent Eovia product forums to see what's going on, so they likely know about this problem? Still, I would definitely sent Eovia an email detailing the problem even if you don't send the file.


ren_mem ( ) posted Tue, 31 January 2006 at 9:07 PM

tkane18, Did you try it w/ the new patch, yet?

No need to think outside the box....
    Just make it invisible.


tkane18 ( ) posted Wed, 01 February 2006 at 8:44 AM

The same thing happens with the new patch. I sent the file to support and received this response: Hello, I have been able to reproduce the problem. Actually it is not the network rendering but simply when the file is rendered in the batch queue I have filed a bug for this and we should get it fixed soon. Thanks for taking the time to report this issue. Charles


ren_mem ( ) posted Wed, 01 February 2006 at 5:59 PM

Well at least it was quickly determined. :)

No need to think outside the box....
    Just make it invisible.


Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.