wtf? Vrscene size is exploding

[fixeighted]

So if I understand what you're saying, even if the car in the scene was static and there was no animation, if I exported any arbitrary frame range then the file size would be same mesh of the car (and any other geometry) at each frame?

[^Lele^]

If it was perceived as a deforming mesh, yes, surely so.
If it is a clean (albeit parented or controller-driven) animation, then no, only transforms per each node are dumped.

[fixeighted]

Ok, so if that's all precisely what should happen then the fact that I only have the rig shouldn't make this happen and in theory it should be that one space warp that is doing it. We'll see in about another hour.
Thanks for the explainations

[^Lele^]

You're very welcome!
EDIT: little addition to the mesh dumping is that it won't even just dump it by the frame, but by the moblur interval.
So imagine if you had *many* geometric subdivs for your deforming, rotating tyres, like 64, then you'd be dumping 128 versions of that mesh per frame (with the default moblur duration of 0.5).
Ouchie. ^^
Remember we'll be eagerly waiting for your scene should you find it's a possible bug!

[fixeighted]

Well that's that solved
Forest was the culprit - deleted them and it saved at a smaller size in seconds.
Would it be Forest that is bugged or the export in that case?

EDIT: and then a instant search yielded this https://forum.itoosoft.com/forest-li...lone-any-tips/

So now we know

[^Lele^]

So now we know

Lol yeah, that'd send me loopy each time! XD
Very glad it's sorted!

[fixeighted]

There is the option to instantiate all the forest stuff, so that's something.
Anyway I'll rebuild the scene so the cloud can take it and see what I get for my money
It's all alearning experience and at least there was a simple solution.
Thanks for your help. I can now go back and see what difference having deforming tyres makes.