Author Topic: Export full scene  (Read 6441 times)

sach

    Reputation: 17
Export full scene
« on: May 14, 2012, 08:59:58 pm »
May 14, 2012, 08:59:58 pm
I don't have the pro version but i have a question, can the "Export full scene" option save a file as a single file that won't effect the file previously saved...

Ex. if i save an original file as "A" reopen the file ans save it as "B" and make some changes to the "B" file and save it as "B".  will the "A" be unmodified so i could have differents materials applied to the 2 files.

With 2.2 Ultimate, how can i play with 2 files that has the same model without destroying the setup of the first one, and without having to start from scratch with a  "NEW" scene.

Re: Export full scene
« Reply #1 on: May 15, 2012, 02:13:44 am »
May 15, 2012, 02:13:44 am
With 2.2 Ultimate, how can i play with 2 files that has the same model without destroying the setup of the first one, and without having to start from scratch with a  "NEW" scene.

1. Close Lumion
2. In Windows Explorer, copy the 4 object files, .lib, .lib.inn, .lib.mtt, .lib.txx, rename (essential) as needed.
3. Open Lumion and your model just copied should now be listing in the Imported Objects Library. 
4. From here you can use it and change as its own source/master object and place it in any scene, for example saveAs a new scene name remove the old object and place the new one and make changes.

It's not quite copy/paste or duplicate but it only takes a minute to go through the steps.

Morten mentioned in a topic recently but can't find the thread easily.

Re: Export full scene
« Reply #2 on: May 15, 2012, 03:02:00 pm »
May 15, 2012, 03:02:00 pm
I don't have the pro version but i have a question, can the "Export full scene" option save a file as a single file that won't effect the file previously saved...

Ex. if i save an original file as "A" reopen the file ans save it as "B" and make some changes to the "B" file and save it as "B".  will the "A" be unmodified so i could have differents materials applied to the 2 files.

Regarding the "Export Full Scene" function in Pro, you can export and import socalled .ls2 files that include any user-imported models (from the Library folder) that you are using in your scene.

However, if you import an .ls2 scene (version B in your example) and this scene contains a user-imported model that already exists in the user-imported Library folder, Lumion will ask you if you want to overwrite the version in the Library folder.

You can only complete the import if you choose "yes" and there is no "rename" option.

However, since you have saved .ls2 files of version A and B of your scene (including the user-imported models), the different "states" of those models would still be 100% intact, regardless of whether you import & overwrite the models in the user-imported Library folder.

In other words, once you start to use Pro you will probably want to use .ls2 files most of the time, and it doesn't really matter which version of a user-imported model Lumion stores in the Library folder, since you always have the saved model "states" in each .ls2 file.

I hope this makes sense - but do let me know if it doesn't :)

SEVERINO

    Reputation: 25
Re: Export full scene
« Reply #3 on: May 15, 2012, 10:02:18 pm »
May 15, 2012, 10:02:18 pm
Hi Morten and the free version for viewing files ls2 ..... We know when we will be ready to download?.

Forgive my impatience, but my best customers are very interested in this product.

Thank you for your attention.
Yours,
Severino

Re: Export full scene
« Reply #4 on: May 15, 2012, 10:27:49 pm »
May 15, 2012, 10:27:49 pm
All I can say is that it will be possible to install Lumion and load Lumion .ls2 files without a license key in the not too distant future :)

Jacobs Architekten

    Reputation: 14
Re: Export full scene
« Reply #5 on: May 15, 2012, 10:56:14 pm »
May 15, 2012, 10:56:14 pm
All I can say is that it will be possible to install Lumion and load Lumion .ls2 files without a license key in the not too distant future :)

... this always sounds for me as it could take while... it's definitely not tomorrow!
J-P.