Topic: a question about lumion speed

[Zdenek Fajfrlik]

hi everybody,
since i work on a wide ranged project, which grows every day a bit, i have now about 18000 tree and plant object in it. together with all the architecture, light elements etc. lumion works in build mode still good, but not so quickly anymore (display showing 1 to 3 fps). no prob, i can still move around, it"s ok,

but: i thought, moving all trees to a separate layer and switching the layer off would fasten lumion in some way.

to my surprise, the speed with displayed trees or without ist the same. ok, i did not restarted the pc yet, so it could be a ram issue, but my question is:

should lumion become generally faster, when we separate the elements to layers and switch them invisible?

my pc is 6 / 12 / 3

thanx stan

[Biju Kumar]

It's better if you have a massing version of your buildings on a separate layer so you can switch -off your detailed buildings instead of the trees. The trees are already optimized for lumion. The detailed models are the ones making Lumion slow.

[Zdenek Fajfrlik]

It's better if you have a massing version of your buildings on a separate layer so you can switch -off your detailed buildings instead of the trees. The trees are already optimized for lumion. The detailed models are the ones making Lumion slow.

ok, than you , i already thout of keeping simple models for the "overall-work" and finaly replacing them by the detailed once. i will check this way of working.

the question is, if moving objects to "off"-layers also help to improve the speed of lumion, research goes on.....

now, one question is interesting:

if i define, let us say 100 colours for the detailed object, and then replace (reload) it by an simple object with 10 colours,

will the 90 other colours remain in the lumion-object-database until i replace the object again by the detailed one? i will explore this tonight....

again and thanx for helping

stan

[Gaieus]

Do not use the reload function for this. Simply make a "dummy" version of your model and add it to  Lumion. Then put it on one layer and put the real model on another layer. You can then toggle them and while working in build mode, you can keep the dummy version active and after setting all scenes, placing entourage and all, switch back to the real version and export your movie that way.

Are you working in SketchUp (if I remember correctly)?

[Biju Kumar]

Do not replace-reload with other model, you should have 2 models in different layers that you can turn-off/ON.

[Gaieus]

...are you working in SketchUp (if I remember correctly)?

Yes, I remembered well (just seen in another topic). Here is a good plugin to create "ghost components" (i.e. simplified versions) that you can export as a light weight "dummy" model:
http://forums.sketchucation.com/viewtopic.php?t=21469

This one simply makes bounding boxes which may serve just as well:
http://forums.sketchucation.com/viewtopic.php?p=179953#p179953

[Zdenek Fajfrlik]

hi gai & Wendell_Biju,
thanx very much.
the usage of 2 models on 2 layers is a much better way, of course.

it's funny, i use the technique of two version of models in skp since a longe time, i save a dummy of every model , work on it independently and keep a master file for the whole landscape. at the end i reload all components manually and have a finished master.

when this works automatically with the ruby , GREAT, and since i now switch to V8, it's agood time to implement this. thank you very much fir the tip.

regards stan.

and for my "TOTAL RECALL" wishlist topic it then would be important, that

the total recall view can switch all layer settings per view , BUT.  a special override function for the model layer must be implemented, to be able to switch the model-layer in all saved views at once( a sort of overall layer switch behind the recalled set of parameters). i use this technique too in my programms. together with the batch picture export.....a dream.

btw, gai, if you can speak to su developers:

i miss a shadow on/of override function , which would allow to switch shadows for the working session, independently of the shadow setting in each scene.
advantage: every scene can be saved with or without shadows, but for the workfllow shadows could be temporarily switched off

and : a function for shadows, where i can change shadow settings for ALL scenes, where the shadow is switched on ( so i could switch off the "shadows on floor parameter" for all scenes at once). i often have 200 scenes in a file, so both functions would really improve my workflow.

regards stan and thanx once again for the lumion tips.