Avisgrafik_Corona_tests(WIP)

[snakebox]

I have to ask, what settings are you using for large scale volumescatter setups?  are you using the global volume material in the render settings? or are you placing a box with scatter shader on?

I often find that my setup either turns solid black or I have to up the distance so much that it looks like the effect isn't there at all?  for how simple it really is, it amazes me how much I can make it NOT work. 

thanks

[tolgahan]

I have to ask, what settings are you using for large scale volumescatter setups?  are you using the global volume material in the render settings? or are you placing a box with scatter shader on?

I often find that my setup either turns solid black or I have to up the distance so much that it looks like the effect isn't there at all?  for how simple it really is, it amazes me how much I can make it NOT work. 

thanks

[tolgahan]

I don't understand what's going on ?

world record : )

Total elapsed  : 1 hour

passes total : 0

[zuliban]

im not sure if you have the same problem than me but maybe you are running out of ram and corona 1.4 have low thread priority enabled all the time.
it took me like 1 hour for parsing 10 min per pass in 1.4 for a close up and switched to 1.3 like 30 secs per pass  and 5 min parsing in the same scene.

[tolgahan]

im not sure if you have the same problem than me but maybe you are running out of ram and corona 1.4 have low thread priority enabled all the time.
it took me like 1 hour for parsing 10 min per pass in 1.4 for a close up and switched to 1.3 like 30 secs per pass  and 5 min parsing in the same scene.

Unfortunately same problem.How can I solve this problem.I  havent got a time to switch 1.3. bullshit :(

[cecofuli]

The RAM is finished, I'm sorry.
You can buy more RAM, or you can reduce the complexity of your scene.
You can use ProOptimizer modifier to reduce the poligon count o your trees.

Anyway, just for debugging, you can install v1.3 in 5 seconds with the official installer. I don't see the problem.

[tolgahan]

The RAM is finished, I'm sorry.
You can buy more RAM, or you can reduce the complexity of your scene.
You can use ProOptimizer modifier to reduce the poligon count o your trees.

Anyway, just for debugging, you can install v1.3 in 5 seconds with the official installer. I don't see the problem.

Thnks.

Most of the scene is proxy and scatter.
At the same time , similar of the same scene is rendering in vray
What is problem that you can solve in 1.3 but not in 1.4
I have 20 machine should I have install 1.3 to each one.There should be a more logical solution. :)

Same proxies same textures same polygons at the vray

[tolgahan]

How can I closed all the displacements at the same time close ?

[romullus]

Do you mean to tun off displacement? There's a global switcher in render setup>common tab.

[cecofuli]

Try to install in two or three machine and see what happens.
Anyway, Corona, in my tes,t eats 20-30% more RAM thatn VRay.
It depends of the scene.
Anyway, try to debug your scene:

(*) disable displacement
(*) disable heavy layers
(*) disable render pass
(*) reduce the resolution
(*) disable VFB
(*) override material and see if there are problem with textures

etc...

[tolgahan]

Try to install in two or three machine and see what happens.
Anyway, Corona, in my tes,t eats 20-30% more RAM thatn VRay.
It depends of the scene.
Anyway, try to debug your scene:

(*) disable displacement
(*) disable heavy layers
(*) disable render pass
(*) reduce the resolution
(*) disable VFB
(*) override material and see if there are problem with textures

etc...

Unfortunetely at the era of industry CORONA makes us live in renaissance period.I mean we shouldnt be having such problems.

I tried 7.5 k render when the render elements and displacement were off and it didnt cause any trouble.

[Frood]

Well that´s a strange statement... Your scene just needs more ram than you have, what´s the problem? When you render a heavy 20k pano with a lot of render passes and denoising activated (makes huge difference), you could easily fill the double of your ram.

Cecofuli just summed up for your very convenience what you could try to do. Maybe disabling denoising or removing half of the passes or adjusting displacement settings would already be enough. You just need to "touch" the RAM limit to have this effect, maybe it´s only about 2GB you have to find somewhere.   (Just discovered the Commit value)

Good Luck

BTW:
http://i15.photobucket.com/albums/a376/halberciro/CORONA%20RENDER/deneme48_corona2.jpg is very convincing, nice!

[Ondra]

also it is a strech, but the standalone eats about third to half of memory 3ds Max uses. You could in theory export and render in standalone - "only" problem is that DR is not supported by standalone yet

[Frood]

Err... yes maybe it would use as less memory but it´s in fact only theory. Still too many unsupported maps/features atm. for this kind of practical use, or a scene that was not explicitly built with standalone in mind - unfortunately.

Good Luck

[tolgahan]

also it is a strech, but the standalone eats about third to half of memory 3ds Max uses. You could in theory export and render in standalone - "only" problem is that DR is not supported by standalone yet

Cecofuli and Frood  Thnks for your helps..

Actually these are not big problems.There are things that can be sorted out with post.Since now 32 gb ram was enough
for more massive scenes.The main problem is when starting the job we make full hd tests.Everything seems ok ( scatter  , Fog , displacements , shaders etc. all are on.But when  we are about to the
NEXT STEEP ( Final step ) we face the problems ( memory - dr etc. ) At the end of the day we want to finalize it with taking 7.5K render and turning on the passes.
Well I will sort it out somehow.I will do as you say with displace and folige


Thank you all...

Lets continue blue part...