OTOY Forums

At the moment, whenever an heavy asset (.vdb, 4k or 8k image texture) has to be loaded from a network drive (or storage server) a lock up will happen in Cinema 4D.
Network perfs are great with other applications, can reach up to 2.5Gbps if the files size allows it but in Cinema and Octane it will never exceed 50Mbps.

This is causing serious issue in my studio where we have to rely on a network storage to collaborate and use our render farm. When a scene is using around 1gig of data (either vdb or textures), well some actions like opening the scene, opening the material panel/editor will trigger a reading of the file thus resulting in a lockup for a few minutes. Using the octane texture manager is also very very taxing on Cinema and can trigger a lockup if the file are on the network.

I've managed to partially mitigate the issue via python script and the use of multithreading to do all the file transfer to a local drive when the artist feels like the scene is too slugish but it's only a bandaid as it seems that other parts of Cinema don't suffer from this speed limitation.

(I've already mentionned the vdb/asset browser issue in a thread a few months ago, any news on that subject?)

Which version of c4d? the c4d file handling network code was overhauled a couple of versions back and should be significantly faster.

We are using 2023.1.3 at the moment. Cinema 4D network handling is working as expected and is speedy enough when it's possible, but it seems like Octane is not using these improvements with Image Texture/Image Tile nodes and VDB files.

No answers about this? Do i need to do open a support ticket?

ShivaMist wrote:No answers about this? Do i need to do open a support ticket?

Yes please contact support so we can investigate further. I don't have a good answer what is going on and we would need to try to reproduce the issue first and for that we would need to know more about your setup.

One thing you can also test is, if it makes a difference if the image file is loaded into a C4D image texture or an Octane image texture node.

abstrax wrote: Yes please contact support so we can investigate further. I don't have a good answer what is going on and we would need to try to reproduce the issue first and for that we would need to know more about your setup.

One thing you can also test is, if it makes a difference if the image file is loaded into a C4D image texture or an Octane image texture node.

Thanks for you answer, i will create a ticket as soon as possible with all the information and data i can gather. I tested both nodes (C4D/Octane image texture) and the speeds are the same unfortunately.