Hi @ECHekman unfortunately without code I can't see what's wrong so if you can share it it will be appreciated.

However, keep in mind that only the generator is the owner of its cache meaning this generator can decide whenever it wants to rebuild it (even within a thread).

I'm not sure of your final goal, but for render engine, for example, their approach is to have their own scene representation of the current scene and they are doing like:

1. listen to EVMSG_CHANGE to know when something changed.
2. traverse the scene, and track new/deleted obj or see if something changed with obj dirty bit.
   See Why are GUIDs not Globally unique for keeping track of objects, and Dirty States for dirty bits.
3. If something changed, retrieve the cache and translate it into their Polygonal Representation
4. Store this custom copy into their Custom scene Representation.

Finally please for your next topic, use the Cinema 4D category if they are related directly to Cinema 4D development.
Hope this message helps you,
Cheers,
Maxime.

Hi As the documentation state since S22, DrawTexture doesn't copy in every situation the BaseBitmap (which is way more efficient). However, that implies either you ensure the basebitmap is allocated and alive as long as it is displayed or you pass the flag DRAW_TEXTUREFLAGS::TEMPORARY so a copy is done internally and you are safe :)

Hope this help.
Cheers,
Maxime.

Thanks a lot for your additional testing, I will for sure attach it to the bug report :)

Hi @jochemdk, thanks a lot looks like you found a bug. I opened a bug report to our development team :)

Another workaround is to use the effector not to define the visibility of an object but to define its scale to absolute 0.
This is more efficient since you don't have to re-enable the effector (which can be an issue and cause other dirty issues) since the effector needs to change the data generated by the cloner.

Cheers,
Maxime.

Hi @mastergog unfortunately, this is something not possible.

@rsodre this was moved into overall Preference (Ctrl+E) in Viewport Display category.

Cheers,
Maxime.

Hi @fwilleke80, plugins compiled with R23.008 are compatible with R23.110.
But the other way is not working (as it was always been the case with SP release).

Cheers,
Maxime.

Hi @mastergog please for your next topic, try to use the Q&A functionality.

Regarding your issue, you should first register your object plugin with the flag OBJECT_USECACHECOLOR.
Then if you are returning multiple objects a good practice is also to define an UniqueIP for each of them, for more information please read BaseObject - Generating

Cheers,
Maxime.

Hi @jcooper I'm afraid this is unfortunately not possible.

Cheers,
Maxime.

Hi thanks a lot for the hint, I restored them back, they will be there on the next documentation update.

Cheers,
Maxime.

Hi first of all thanks for reaching us, unfortunately, it's unclear to us if your question is directly related to scripting or if you use the regular Save project for Cineware with the Cinema 4D UI.

This folder is used for generated (baked) texture only, since, on the implementation itself, Cineware is able to provide the link of the original texture path.

So what you can do is before doing a Save for Melange, do a "Save project with asset" so this will relocate all texture to the tex folder.

Finally, if you think this is really a missing feature I invite you to our user support to do a proper feature request.
You could also ask the Element developer to support it since Cineware SDK properly expose to 3rd party developers the property of BitmapShader so they can Read and Write Bitmap Path.

Hope it helps you,
Cheers,
Maxime.