Spline dynamics & live viewer

[Yambo]

I aware that dynamics require caching. If they not cached there are some live viewer updates issues (for example changing post processing parameters causing live viewer updates every parameter change) So every time i'm doing dynamics simulations i'm caching everything and things seems to work properly.

I got a spline dynamic simulation (very simple one actually) , I've cached it and still there is live viewer update issues - The live viewer updates too frequently (Same post processing issue i've mentioned above)

Ahmet do you aware of it? The plugin suppose to address spline dynamics same is rigid bodies for example?

Thanks.

[aoktar]

Propably i'm aware of. Anyway can you post a scene to check?

[Yambo]

Sure, Simple scene attached.

[aoktar]

Yes. That's the most horrible side of C4D. Some effectors or this kind of effects are generating some messages and refreshes the cache of generated objects. Even with a little click or mouse movements. Here dynamic effect creates a new cache on every change on scene. This is very similar to using a shader effector on cloner. It does similar feedback on every click. Also there is a bunch of effector or objects, they work like this. Thought that I have spent weeks/months to avoid this behaviours without any success.

Maxon don't never thought the plugins which is like ours. Their concentration is on renderers which works as "start and wait".

[Yambo]

Interesting.

Just a point of UX view - If users will got even some kind of octane cache tag in future version it could be very useful. A tag dedicated to all those effects that creates new cache on every scene change and cache the simulation in a way the plugin can work with. It's not optimal solution but i thing it's better then nothing.

But sure i'm talking without understanding the technical side - Just a point of view.

[aoktar]

I don't mean dynamic cache. Generator objects like cube,sphere, cloners, helix, etc.. produce some virtual objects. They have a internal point caches and invisible. I mean this. And they recreate this cache objects and generates update messages. It's not a problem while working on a scene or viewport. Because it can refresh very quickly. User is not aware of these operations. But Octane's mesh feeding is much slower than these. So this causes some lag due this resending of geometry. This is one of my biggiest challanges to provide a fluent user experience and correct output in LV.

[Yambo]

got you