Is it possible to disable all the unused materials while working in the live viewer window? Couldn't find such option in settings. This would sped up workflow drastically.
Moderator: aoktar
[ Play Quicktime file ] Cinema_4D_W3gavaHi7j.mp4 [ 2.49 MiB | Viewed 805 times ]
Aleksei wrote:That's right, and that's why it would be good to a have a checkbox to switch between different scenarios: loading or not loading the unused materials. And if user does someting wrong, (like trying to apply a non-loaded into VRAM material) gently inform him about the situation without crashing the entire Cinema 4D. That could be a better UX for us.
Caching is effective when you send the scene again. As said "ignore unused materials" is not safe for Live Viewer. It will cause a lot of problems, I know because I've tried to implement it and switched back after many issues.
Aleksei wrote:That's right, and that's why it would be good to a have a checkbox to switch between different scenarios: loading or not loading the unused materials. And if user does someting wrong, (like trying to apply a non-loaded into VRAM material) gently inform him about the situation without crashing the entire Cinema 4D. That could be a better UX for us.
frankmci wrote:Aleksei wrote:That's right, and that's why it would be good to a have a checkbox to switch between different scenarios: loading or not loading the unused materials. And if user does someting wrong, (like trying to apply a non-loaded into VRAM material) gently inform him about the situation without crashing the entire Cinema 4D. That could be a better UX for us.
It's easy for users to say, "Just ad a checkbox to enable function X." It's not unusual for a function to require major changes to the underlying code, especially when that function was specifically discounted while designing the core architecture. I'm not just talking Octane, but any complex tool.
I've heard our own developers complain about it on several occasions over the years. "Yes, we can do that, but since the original design specs were for something else all together, and the whole logic is built on different assumptions, it will take an estimated additional XXX manhours to implement, test, and deploy, along with the associated cost (which is way more than the client is willing wait or to pay).
Users browsing this forum: No registered users and 20 guests