<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Library Management in Libraries &amp; objects</title>
    <link>https://community.graphisoft.com/t5/Libraries-objects/Library-Management/m-p/43121#M34233</link>
    <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;Probably a basic question....but anyway.  I'm creating new materials in the Materials library within AC9.  There are made with texture maps that I have saved in the project specific library.    If I copy the .pln file and the project library to another machine, the new materials are not there even though the texture map is available in the project library.&lt;BR /&gt;
&lt;BR /&gt;
Is there some way to copy the materials library from machine to machine like the project library.&lt;BR /&gt;
&lt;BR /&gt;
  If not, I assume the new library will not overwrite the older version.   How do I keep those custom materials current on all machines.  I'd like to merge the old materials, and definitions of them, into the newer library.&lt;BR /&gt;
&lt;BR /&gt;
Otherwise, I'm constantly recreating materials. &lt;BR /&gt;
&lt;BR /&gt;
Thanks.&lt;/T&gt;&lt;/DIV&gt;</description>
    <pubDate>Thu, 16 Mar 2006 00:20:02 GMT</pubDate>
    <dc:creator>Tom Krowka</dc:creator>
    <dc:date>2006-03-16T00:20:02Z</dc:date>
    <item>
      <title>Library Management</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Library-Management/m-p/43121#M34233</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;Probably a basic question....but anyway.  I'm creating new materials in the Materials library within AC9.  There are made with texture maps that I have saved in the project specific library.    If I copy the .pln file and the project library to another machine, the new materials are not there even though the texture map is available in the project library.&lt;BR /&gt;
&lt;BR /&gt;
Is there some way to copy the materials library from machine to machine like the project library.&lt;BR /&gt;
&lt;BR /&gt;
  If not, I assume the new library will not overwrite the older version.   How do I keep those custom materials current on all machines.  I'd like to merge the old materials, and definitions of them, into the newer library.&lt;BR /&gt;
&lt;BR /&gt;
Otherwise, I'm constantly recreating materials. &lt;BR /&gt;
&lt;BR /&gt;
Thanks.&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Thu, 16 Mar 2006 00:20:02 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Library-Management/m-p/43121#M34233</guid>
      <dc:creator>Tom Krowka</dc:creator>
      <dc:date>2006-03-16T00:20:02Z</dc:date>
    </item>
    <item>
      <title>Re: Library Management</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Library-Management/m-p/43122#M34234</link>
      <description>would attribute manager and a saved .aat file do the trick?&lt;BR /&gt;
&lt;BR /&gt;
be careful with the index numbers. That may foul up the transfer - that is to say make sure the material index numbers are the same across your distribution.</description>
      <pubDate>Thu, 16 Mar 2006 01:00:32 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Library-Management/m-p/43122#M34234</guid>
      <dc:creator>Aaron Bourgoin</dc:creator>
      <dc:date>2006-03-16T01:00:32Z</dc:date>
    </item>
  </channel>
</rss>

