File Savings are saving way too large.
![Cyberdene](https://secure.gravatar.com/avatar/71cf62181b5e288a140edf41ce61433a?&r=pg&s=100&d=https%3A%2F%2Fvanillicon.com%2F71cf62181b5e288a140edf41ce61433a_100.png)
I have some scenes saved, and the amount of memory of that file saved wil have like 14.MB or sometimes even 300mb but I have some with at least one figure and I'm seeing 4.44GB even when I remove certain things its still saving at these ridiculous large sizes. It never use to do this before, and it's doing it a lot now. I even have some figures saving at really low file sizes like 1MB. This has got to be an error in the program since a lot of the stuff that's hiking up in the GB range wasn't doing that originally. Now all of a sudden I cant even save one figure without it going over 2GB or something like this even if their naked, and I have some figures saved with three figures and it's not even in the GB range.
Comments
I've seen this before when using Fit control clothing enhancements. I had to delete the unused morphs to reduce the file size down.
Yeah I'm not using that morph, I tried to save the figures fully naked with no hair, and it still did it. I dont know what the cause of it is. I realize some scenes I save will save much much lower in file size even if I have a lot of figures in that scene, then I have some where I have one figure saved and its literately pushing 1GB or 4GB this cant be right..Now it takes forever for scenes to open and save because of it.
Check SubD settings on the characters. Also check for hidden morphs that shouldn't be included.
SubD isn't saved as mesh data - that's rather the point, it adds detail dynamically. Morphs would be stored as links and values unless they were freshly imported/spawned custom morphs. Weight maps (e.g. from dFormers) would also add data to the save.
IIRC didn't the Reality plugin cause a similar issue several years back, @ OP you aren't using any 3rd party plugins by any chance.
Im not using any third party plugins no. I only recently started to notice this issue, and no it is not the Sub division thing either because it did it even to a figure with it set to 0