@okh
Which is why it can be a good idea to start out by using very simple models, and only put in the advanced ones (trees especially) at the very end. And/or keep the big models in a separate file and just paste them in for rendering.
I agree.
Another way do it is to place heavy objects on separate levels,
so we can make the most CPU-intensive objects disappear by making
their levels un-viewable whilst working on the basic construction,
and, as you say; just bring them in for rendering.
Especially trees... and yes, I have been constructing some trees
and plants from time to time, and the biggest ones can easily become
around 50 - 60Mb, including textures.
The textures of course have to be.png -files to support transparency, which adds even more weight.
A medium sized texture (good enough, unless you want real close-ups),
can easily be around 6Mb.
(Orig size)
But heck, it is a hobby, isn't it?
Exactly, and that's why we take it so seriously.
Cec
