<?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 Re: Publishing In Teamwork with separate model and layout fi in Teamwork &amp; BIMcloud</title>
    <link>https://community.graphisoft.com/t5/Teamwork-BIMcloud/Publishing-In-Teamwork-with-separate-model-and-layout-files/m-p/216305#M3254</link>
    <description>Hello,&lt;BR /&gt;
&lt;BR /&gt;
Do you have everything in one file? Having 'typical' separated from &lt;BR /&gt;
the 'changing' information is a good start to have smaller file sizes.&lt;BR /&gt;

&lt;BLOCKQUOTE&gt;When starting the Construction Document stage of a project we typically separate the model file from the layout file because of the large project size. Both files reside on the BIM server - AC15 &lt;/BLOCKQUOTE&gt;</description>
    <pubDate>Thu, 20 Dec 2012 17:49:46 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2012-12-20T17:49:46Z</dc:date>
    <item>
      <title>Publishing In Teamwork with separate model and layout files</title>
      <link>https://community.graphisoft.com/t5/Teamwork-BIMcloud/Publishing-In-Teamwork-with-separate-model-and-layout-files/m-p/216304#M3253</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;Hi everyone&lt;BR /&gt;
&lt;BR /&gt;
When starting the Construction Document stage of a project we typically separate the model file from the layout file because of the large project size. Both files reside on the BIM server - AC15&lt;BR /&gt;
&lt;BR /&gt;
When we try to publish sets of drawings to DWG, the layout file always tries to check for updated model file information and gets caught in some crazy routine and won't stop until it is manually cancelled. As a result nothing gets published. &lt;BR /&gt;
&lt;BR /&gt;
- All drawings placed onto layouts are manual updates,&lt;BR /&gt;
- The last thing done before publishing is sending/ receiving in both the model and layout files,&lt;BR /&gt;
- Restarting both AC sessions sometimes resolves the problem temporarily,&lt;BR /&gt;
- Publisher does not have this problem with PDFs (unknown how well other formats work),&lt;BR /&gt;
&lt;BR /&gt;
We would like to publish layout files with cropped drawings contents ideally. We have tried all kinds of variations in the DWG translator but this has not changed anything.&lt;BR /&gt;
&lt;BR /&gt;
Anyone who has found the cause or has a workaround for this prblem. I'd really appreciated hearing your thoughts.&lt;BR /&gt;
&lt;BR /&gt;
Thanks&lt;BR /&gt;
e&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Tue, 18 Dec 2012 21:29:54 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Teamwork-BIMcloud/Publishing-In-Teamwork-with-separate-model-and-layout-files/m-p/216304#M3253</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2012-12-18T21:29:54Z</dc:date>
    </item>
    <item>
      <title>Re: Publishing In Teamwork with separate model and layout fi</title>
      <link>https://community.graphisoft.com/t5/Teamwork-BIMcloud/Publishing-In-Teamwork-with-separate-model-and-layout-files/m-p/216305#M3254</link>
      <description>Hello,&lt;BR /&gt;
&lt;BR /&gt;
Do you have everything in one file? Having 'typical' separated from &lt;BR /&gt;
the 'changing' information is a good start to have smaller file sizes.&lt;BR /&gt;

&lt;BLOCKQUOTE&gt;When starting the Construction Document stage of a project we typically separate the model file from the layout file because of the large project size. Both files reside on the BIM server - AC15 &lt;/BLOCKQUOTE&gt;</description>
      <pubDate>Thu, 20 Dec 2012 17:49:46 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Teamwork-BIMcloud/Publishing-In-Teamwork-with-separate-model-and-layout-files/m-p/216305#M3254</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2012-12-20T17:49:46Z</dc:date>
    </item>
  </channel>
</rss>

