Hi,
Were running into another situation here with the vrscene exports, when using volumes (VDBs) the exports are taking quite a bit of time (some scenes taking hours).
The "file" nodes used are set to load as "Packed Disk Primitives" and display as "Bounding Box", and the VDB caches are big in some scenes, and other scenes have several caches loaded. The resulting vrscenes are small, just megabytes as expected since everything is set to Packed Primitives, but they are taking like 20-30 seconds per frame, and over 200-300 frames that leads to 1-2 hours.
I prepared a small test scene that is not as problematic but shows the issue a bit. Just 2 simple vdbs loaded and 20 frames take 1 minute to export and the resulting vrscene is 108kb. Why is it taking so long since it's not writting any data?
Another phenomenon is the increase of RAM when generating the vrscenes, the more caches and the bigger the caches the higher the ram goes. In this example Houdini goes from 400Mb of ram to 4Gb just exporting the vrcene.
Before vrscene start:
After/during vrscene creation:
In theory this should just be vray writting a vdb path to the vrscene, what's happening that causes the ram to go up and to take so long per frame? And is there anything that can be done to improve this?
Best,
David.
Were running into another situation here with the vrscene exports, when using volumes (VDBs) the exports are taking quite a bit of time (some scenes taking hours).
The "file" nodes used are set to load as "Packed Disk Primitives" and display as "Bounding Box", and the VDB caches are big in some scenes, and other scenes have several caches loaded. The resulting vrscenes are small, just megabytes as expected since everything is set to Packed Primitives, but they are taking like 20-30 seconds per frame, and over 200-300 frames that leads to 1-2 hours.
I prepared a small test scene that is not as problematic but shows the issue a bit. Just 2 simple vdbs loaded and 20 frames take 1 minute to export and the resulting vrscene is 108kb. Why is it taking so long since it's not writting any data?
Another phenomenon is the increase of RAM when generating the vrscenes, the more caches and the bigger the caches the higher the ram goes. In this example Houdini goes from 400Mb of ram to 4Gb just exporting the vrcene.
Before vrscene start:
After/during vrscene creation:
In theory this should just be vray writting a vdb path to the vrscene, what's happening that causes the ram to go up and to take so long per frame? And is there anything that can be done to improve this?
Best,
David.
Comment