Itoo Software Forum

Author Topic: manual install questions  (Read 126 times)

RF1950

  • Newbie
  • *
  • Posts: 4
manual install questions
« on: February 08, 2019, 07:20:03 PM »
Hi i'm doing a manual install of 6.1.5
I skipped the 6.1.2m but noticed some changes in it in the way folders are placed and named.

For many years we've operated with the folder called "matlib" is it now officially changed to "matlibs"?
And also, when i'm unpacking starter library and any of the newer 3d libraries the have folders called "objects" and "thumbnails", nothing in my regs points to them. What do i need to add to the regs for them to be found, or where do i need to place them so they are found recursively? The closest thing i see is "lib" folder, but it's a mess to sort through that one for every archive that i unpack.

thank you!
tony

RF1950

  • Newbie
  • *
  • Posts: 4
Re: manual install questions
« Reply #1 on: February 08, 2019, 08:54:47 PM »
i think i got it ... the objects folder contents being placed in the root of a category is what threw me off
it looks like a bunch of new assets look for the objects folder, while some of the older ones don't

RF1950

  • Newbie
  • *
  • Posts: 4
Re: manual install questions
« Reply #2 on: February 08, 2019, 10:03:29 PM »
alright it's mess!
apart from the objects being all over the place the matlibs are also stores differently
some need to be in the root\matlib , others in the respective categories under matlibs
it's driving me nuts trying to sort through this stuff!
i'm sure the guys who are packaging this stuff for new releases feel the same

can you please create some sort of central config app or script that allows to re-path things in a more coherent way?

thanks!

iToo

  • Administrator
  • Hero Member
  • *****
  • Posts: 3411
    • iToo Software
Re: manual install questions
« Reply #3 on: February 09, 2019, 09:05:46 AM »
Hi, before FP6 there was an unique folder with all material libs ("matlib" in the root path), and other for the maps ("maps").
We keep the same structure for these libraries, to avoid incompatibilities with existing scenes.

But for the new libraries, each one have its own local folder for materials and libraries ("matlibs" and "maps", within the folder of the library).
This structure is more convenient because all dependent files are stored together. Also it was necessary for Update Manager, to unpack all files of a same library in an unique location.

This change should not affect in any way to the materials ("matlibs"), because each libray has a custom script to load the their materials from the right location.
This is done when a item is imported in the Library Browser.

Regarding the maps, Forest already includes an process to collect recursively all "maps" folders.
These folders are added to Customize->User Paths->External files. In this way, Max can locate and load the textures automatically, and the "relink" process should not be necessary.

The collecting maps process is launched once by Max session, the first time a Forest object is used. It works both in workstations and render nodes.

Carlos Quintero
iToo Software