Ok thanks we will talk to tech support!
It‘s Christmas soon, time to write your wish list
Hi Sassi, you‘re a legend, thanks for the detailed reply! Of course I don’t expect this to play smoothly. It’s just when I am, for example, looking at frame 40 and then click on frame 80, the scene takes 10 seconds to update. This just seems very, very long doesn’t it?
We have this rather huge VDB sequence that we load into cinema using the Redshift Volume Loader. One VDB frame has up to 2.5GB. The sequence is stored on a PCIe 4.0 Nvme which ( we checked) is able to deliver 7GB/Sec.
When moving around in the timeline it takes around ten seconds for the viewer to update. We set the preview to dots, switching to box doesn’t help either. Cinema takes very long to load these files. Is that expected behavior? What could we do to speed up things?
We have a midrez VDB as a stand in, but it’s not much faster and not if help when actually trying to shade the VDB to our liking.
i thought watch folders in the asset browser could display hdri images, it sure can in the databases, but not in a watch folder? Pleases se the attached screenshot, no thumbnail.... do i have to generate the thumbs first?
Thanks for any ideas!
Since the new 2024 version shador effectors with noise seem to be broken. I used to be able to add a shador effector, set it to noise and the animate it. The clones used to wiggle around. This is no longer the case... can you confirm? Attaching a test scene her:
Hi! I've noticed that my RTX 2070 is running at double the speed and FPS as the headless RTX3080ti i have in my system. So my displays are plugged in the 2070
and the 3080 is soleley there for computing.
When i select the 2070 and run a generic cube with a generic pyro tag i get around 8FPS in the viewport, whereas when i selct the 3080 i get only around 4 fps. I find that somewhat unexpected?
Any ideas why that would be?