long time calculating lightcache

[DaForce]

ok 16m33s slightly quicker, but i would put that down to the change in teh co-eff.

So either way.. its about 50% slower

[jacksc02]

cool, wait for 64bit max/vray and static is all you need

[CT]

Thanks for the info Vlado, kpavlov and DaForce. I haven't had time to test my scene again as I have had another job to complete.

chris.

[dgsantana]

Hi all, just a note, we can set the memeory value to a high value and maintain the geometry at static and it will speedup the scene (that contains proxies/fur/displace). Since the limit is for dynamic geometry like proxies/fur/displace. Only when setting the geometry also to dynamic will it slowdown since everthing is "converted" to dynamic geometry and it will do lots of loading/unloading of all the scene geometry.

Best regards,
Daniel

[kpavlov]

I didnt changed static to dinamic, I used static memory but I changet 400 mb as default to 800 mb in slot for dynamic memory limit and it solved the problem. Dont ask me why, it works.

[jujubee]

So basically 'Dynamic memory limit' values work regardless of 'Default geometry' set to 'Static' or 'Dynamic'? And this would be faster in some situations?

If it's true in almost all cases, perhaps I'd recommend an increase in this value as default in future releases.

[dgsantana]

Yup, it works. The memory limit is for dynamic geometry regardess of the setting in the geometry type, and since since vrayproxies, vraydisplacement and vrayfur are always dynamic geometry, so yes putting a high value will in most case speedup, but can also cause the memory to overflow in some situations (resolved setting geometry to dynamic or render to a vrimg file). I usually set to 1200-1400, as long it doesn't reach 2.4 Gb in taskmanager and we have the /3GB setting it will speedup things.

Specs Office: Dual Xeon 3.2, 3 Gb RAM, /3GB
Specs Home: Core 2 Duo 2.4, 2 Gb RAM, /3GB


Best regards,
Daniel