CINEVERSITY

Hi jesfrigon,

Since I have no idea about your setup, the question's answer could be very long and just guesses. This is not what I do here. I do not answer from memory when I have a file, nor without testing if that works with the current version. Your 16GB excludes this sadly.

To get to 16GB seems odd, but again, perhaps that is what you need if your setup is not possible in another way.

This leads me to problem-solving strategies, which are the skills that 3D artists need to have.
Here are a few: (Surely not complete.)

• Reverse Engineer: Deconstructing the Problem.
• Algorithmic Approach: Step-by-Step Solutions.
• Pattern Recognition: Finding the Underlying Structure.
• Hypothesis Test: Proving or Disproving Assumptions.
• Constraint Analysis: Working Within Limits.
• Root Cause Analysis: Digging to the Core.
• Scenario Planning: Preparing for All Outcomes.
• Prioritization Protocol: Focusing on What Matters.
• Simplification Strategy: Reducing Complexity.
• Visualization Technique: Seeing the Solution.

What happens if… is one core question here.

One method is checking the backup sequence you typically get while setting up a large project.
When the size jumped is an indicator.

Another method is to create a copy and delete all parts that you suspect are driving the size up, saving it into a new file, and checking the size.

Could a different method of creating the scene (RS Proxy, XRef) have been used as a problem-solving question?
Perhaps we should avoid using Vertext maps and use image-based maps.

Are all the details needed, e.g., the Foreground, Middle Ground, background evaluation, and Level of Detail, or even 3D with image replacement?

Typically, I ask for a file, but I will not download anything larger than a few hundred MB, which is surely not a 16GB file. Just to avoid work on your side.

Create a new scene, save incrementally while building up a mini version of the scene, and, as mentioned above, check when the size jumps. With that jump, typically, one of the reasons is clear.
Please search for an alternative, (Sprites/Cards, Digital Matte painting for Background. etc. Since I don't know where you created 16GB of Data, which might unfold even more when opened, you need to explore that)
Perhaps switching off all Generators and keeping the Time slider at zero while clearing Chaches will also help. (Yes, that is the guessing part, and I stop here.

If that has found a solution, move on and see if the steps towards completing your mini setup create similar jumps in size. Repeat.

All the best

Hi MaverickMongoose,

Thank you very much.

I tried to reproduce this, but I can't. I tried copying and pasting them one after the other into a new file, but I couldn't.
I also placed everything in a new Simulation Scene. No change.

I hope you get your project successfully done without further hick-ups.

My best wishes

Thank you very much for the kind feedback, Adam; I love to do that.

If there is anything else, I'm happy to look in the morning into it. (midnight here)

My best wishes for your project.

Yes, Dutchbird.

Since processing time becomes faster, I can see that as an advantage. But also, drives have gotten to $20 per TB, and even running the standard Project file/BU/BU (three places in distance to each other) is not a problem anymore, money-wise; keeping the drives alive, as they are degrading over time is. Another point would be whether future app versions can read the cache files anyway? I keep my old laptops here to have things available, like some old Quicktime codecs (e.g., Sorenson movies would be lost otherwise, as I noticed a while ago).

All the best

Thanks a lot, Mike.

Let's hope that the Prefs will not go back at any time to the state that caused the problem.

My best wishes

Hi background-permit,

So far, I know that would be possible with the Point Cache; after the Point Cache has stored the data, the Cloth can be switched off.

https://help.maxon.net/c4d/2023/en-us/Default.htm#html/TCAGEOMCACHE-ID_TAGPROPERTIES.html#ID_CA_GEOMCACHE_TAG_CACHE_LIMIT

All the best

Hi max1e,

Thanks for the question. The situation has not changed, as before, and with the version released on Wednesday this week.

The only way to cache is with all frames before they need to be calculated; the RS Volume allows them to reload and offset the range if needed.

Please open a "ticket" with the "Share your Idea" here:
https://www.maxon.net/en/support-center

I indeed will support anything in this direction.

Cheers

Thank you very much, leather-recipe,

Yes, there are post-production ways. Thanks for pointing this out.

As a side note: Back when Twixter (RevisionFX) was The way to go, the suggested use was that already slowed-down footage from the camera resulted in even better quality when "time-stretched" in post. Combining these two might be something to keep in mind.

Thanks again!

My best wishes

You're very welcome, Alex.

The idea was to provide these dynamic or progressive Voxels to limit the memory needed. The more classic approach is to define a single space that requires a lot of memory from the start.
But, yes, when you go tiny, as mentioned, you quickly have a thousand times more of these cubes, which goes tough on the memory then.

In the old Pyro (two decades ago), there was a 2D version for a more distant objects, I wish we had that also here, even just to comp on the 3D view 🙂

All the best