Author Topic: importing 3rd party DAE object  (Read 1012 times)

Zdenek Fajfrlik

    Reputation: 23
importing 3rd party DAE object
« on: December 26, 2012, 02:35:09 pm »
December 26, 2012, 02:35:09 pm
hi,
can anything happen to my 2.5 installation, when i put a folder with 3rd party dae-objects (here from m. bettke) into the library folder?
anything to be paied attention to?

i just ask, because i read somewhere in the forum, this was very easy and even subfolders could be created,
but on the other hand in the folder LIBRARY i can see files *.lib.inn,

so i am not really sure and must not damage anything because of my deadlines...

thanx for any advice...

stan

Re: importing 3rd party DAE object
« Reply #1 on: December 26, 2012, 11:31:13 pm »
December 26, 2012, 11:31:13 pm
Not going to cause any issues.

They are just files, and Lumion only reads the file types it needs to know about for the library.  Presume you are referring to the Imported Library which is my documents\Lumion 2\Library.

As the files you have are Collada .dae files you won't risk overwriting any other files (you would get a windows message anyway) as the Library files are as you indicate, a set of 4 files generated each time Lumion imports a mesh and creates the Lumion Imported Library objects *.lib, *.lib.inn, *.lib.txx, *.mtt

Lumion reads and searches for .lib files (the mesh object) and its associated resources files to build the thumbnail Library you see from the Imported Objects display.

Generally though, I would keep source resource models and exported meshes in their own project folder so that you can always track back to that project, and it keeps the Library and Scene folders clean with Lumion files only.


--------------------------------------------------------------
Facebook: LumionNZ
Web: Lumion NZ

Zdenek Fajfrlik

    Reputation: 23
Re: importing 3rd party DAE object
« Reply #2 on: December 27, 2012, 01:45:27 am »
December 27, 2012, 01:45:27 am
hi peterm, thanx,
so now the question is, if i can put 10 dae-files directly somehow to a new folder within the library, or do i have to import them one after each other from lumion menue?



regards stan

Re: importing 3rd party DAE object
« Reply #3 on: December 27, 2012, 08:03:12 am »
December 27, 2012, 08:03:12 am
Interesting idea.

It's not possible for Lumion to batch read, convert and create Lumion Library (Import Library)files from any source file type.

If you put the dae files in a new folder within the Lumion\Library folder structure you will still need to go through the process as with any new object to be Imported using Lumion to read and create the Lumion Library object files, that is, one by one.  Lumion only scans automatically through the Library folder structure to find *.lib associated files, so each must be made first via the Import process.

Maybe its something for the wish list, but in most cases I would guess the developers would see users importing and then placing and processing that object one at a time to the scene with only minor irregular need for some form of batch create.  But you never know, there would be times when it would be a time saver.


--------------------------------------------------------------
Facebook: LumionNZ
Web: Lumion NZ

Zdenek Fajfrlik

    Reputation: 23
Re: importing 3rd party DAE object
« Reply #4 on: December 31, 2012, 12:02:19 am »
December 31, 2012, 12:02:19 am
ok,
so i did some experiments to understand the library system of lumion:

results so far:

1. when i import a dae in lumion, the libfiles are placed in the main folder 'library'

2. folders under 'library' are shown as subfolders in the import-object menue

3. i created a new subfolder and moved 3 lib files   (  lib, lib.inn and lib.txx. ) of one object into this subfolder

but lumion doesnot show the object there, even after restarting

how can i sort imported files in the library then?

4. interesting behaviour in 'reload object'

when you replace an object  you can alt+reload, and it changes the object in the library, means, the old object is overwrittenp

so , if files in the library folder can be organized in subfolders, is reloading after moving them still possible ?

for me now this is the most important questions is:

how can organize my library in subfolders???

any tips?

thank you
stan





« Last Edit: December 31, 2012, 12:15:38 am by Zdenek Fajfrlik »

Re: importing 3rd party DAE object
« Reply #5 on: December 31, 2012, 05:40:45 am »
December 31, 2012, 05:40:45 am
1. when i import a dae in lumion, the libfiles are placed in the main folder 'library'

True, this happens when Lumion first imports a new mesh from a source file such as dae.  It has a default folder location where everything is placed - the root folder being \Library

3. i created a new subfolder and moved 3 lib files   (  lib, lib.inn and lib.txx. ) of one object into this subfolder

but lumion doesnot show the object there, even after restarting

Strange.  It should have worked OK, even if oyu had Lumion open and you did the moving in Explorer, once oyu shutdown and re-run Lumion and go to the Library menu it re-reads the files and builds the thumbnail list so you should have seen it in the correct place.

However, there are two cases where it won't:
1. if the files are copied rather than moved, creating a duplicate set of files, and they retain the same file name, then its the first instance of the objects file that Lumion reads will be shown in the Library (and the second is ignored).
2. if the 'subfolder' is only a subfolder of an existing subfolder eg \Library\folderA new \Library\folderA\folderAsub1 instead of \Library\folder then it appears within the base subfolder Tab group.

Each subfolder (1 level down only) of \Library get their own Tab (limited to (was 9)).
All files belonging to the subfolder and any subfolders at lower levels are read and populate the thumbnail Library display of 28 objects and further for additional slots (and the number of slots is limited as well 19 I think but don't quote me).

So all these files are in no specific order, the only order is the top level folders.

how can i sort imported files in the library then?

how can organize my library in subfolders???

Sort of answered in above, only to the level of first subfolder, ( 'sort' meaning organised in a grouping).

I use subfolders for each project, then once its completed, archive it or move it out of the \Library root to make way for new projects, plus keep a set of folders&subs for generic objects.  Each time a new imported model is done I then maintain my Windows folders and files by moving things into their respective project folders (aftehr the end of a Lumion session).  Not needed but that's how I like to organise things.


4. interesting behaviour in 'reload object'

when you replace an object  you can alt+reload, and it changes the object in the library, means, the old object is overwrittenp

so , if files in the library folder can be organized in subfolders, is reloading after moving them still possible ?

Yes it is.  Think in terms of master (one only) objects.  Lumion reads all files to build its list of master objects, it knows where in the folder structure it is (in basic terms) and any updates to materials you make or reloads or new reloads(Alt+) update this unique/master and thus the files.

Essentially:
1. organise your files as needed, Lumion Import Library was designed to take a slightly different and project/object based focus rather than what most are used to of a resource-file and folder based organisation.
2. if you are doing maintenance of files to keep things organised as you like them/the way you are used to doing in so many other things, only do that once you have closed Lumion down.

Zdenek Fajfrlik

    Reputation: 23
Re: importing 3rd party DAE object
« Reply #6 on: December 31, 2012, 09:59:15 am »
December 31, 2012, 09:59:15 am
True, this happens when Lumion first imports a new mesh from a source file such as dae.  It has a default folder location where everything is placed - the root folder being \Library

Strange.  It should have worked OK, even if oyu had Lumion open and you did the moving in Explorer, once oyu shutdown and re-run Lumion and go to the Library menu it re-reads the files and builds the thumbnail list so you should have seen it in the correct place.

However, there are two cases where it won't:
1. if the files are copied rather than moved, creating a duplicate set of files, and they retain the same file name, then its the first instance of the objects file that Lumion reads will be shown in the Library (and the second is ignored).
2. if the 'subfolder' is only a subfolder of an existing subfolder eg \Library\folderA new \Library\folderA\folderAsub1 instead of \Library\folder then it appears within the base subfolder Tab group.

Each subfolder (1 level down only) of \Library get their own Tab (limited to (was 9)).
All files belonging to the subfolder and any subfolders at lower levels are read and populate the thumbnail Library display of 28 objects and further for additional slots (and the number of slots is limited as well 19 I think but don't quote me).

So all these files are in no specific order, the only order is the top level folders.

Sort of answered in above, only to the level of first subfolder, ( 'sort' meaning organised in a grouping).

I use subfolders for each project, then once its completed, archive it or move it out of the \Library root to make way for new projects, plus keep a set of folders&subs for generic objects.  Each time a new imported model is done I then maintain my Windows folders and files by moving things into their respective project folders (aftehr the end of a Lumion session).  Not needed but that's how I like to organise things.


Yes it is.  Think in terms of master (one only) objects.  Lumion reads all files to build its list of master objects, it knows where in the folder structure it is (in basic terms) and any updates to materials you make or reloads or new reloads(Alt+) update this unique/master and thus the files.

Essentially:
1. organise your files as needed, Lumion Import Library was designed to take a slightly different and project/object based focus rather than what most are used to of a resource-file and folder based organisation.
2. if you are doing maintenance of files to keep things organised as you like them/the way you are used to doing in so many other things, only do that once you have closed Lumion down.

hi peterm,
yes, great, i like to have organized things in similar way. it is no problem removing library folders, after finishing a project, when good organized.
i wil ltry, how the library system reacts to links, maybe the whole library could be held intact somewhere and only linking could be change (experiment).likefor the ipad : ON-folder + OFF-folder

i do the same with my scene files , btw, like lots of us ,i think.

when we first exactly know this system, we can take advantages of it.

the importing issue:

there are two different situations

1.
3rd party lumion-ready-lib-files can be placed in the subfolder directly (thanx for the info about COPIED  that could have been an issue in my tests in deed) and apear there after restarting

2.

importing dae yet always placed the files in the main folder . in my case, moving the lib files to a subfolder really did not work, the subfolder appeared empty
but i found out a way to get these lib-files directly to a sub-folder , while importing (subfolder-name as prefix followed by ' \ ' in the object name in the save-dialogue >>>> another topic)

then, after restarting, everything works

for organizing blocks i would like to work with groups of 16 (sort of pages)
filling smaller groups with dummies

but i still couldnot find out, how lumion sorts thefiles (not a-z,as far asi can see)

so the question is, how to get them sorted A 1 - 9 + dummie A10-16 / B 1-13 + dummie B 14-16 / C......

and so on...

any idea?

thanx so much for your infos and ideas, wich bring me further to a nice working ergonomic system (especially the reload-problem solved is great)

regards and with best wishes for 2013

stan