<?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 BIM server 18 slow send/recieve in Teamwork &amp; BIMcloud</title>
    <link>https://community.graphisoft.com/t5/Teamwork-BIMcloud/BIM-server-18-slow-send-recieve/m-p/231315#M1926</link>
    <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;We are using mac, all work stations meet the spec requirements for AC18.&lt;BR /&gt;
When new views are created in either the view map or project map other work stations (than the one the view was created from) struggle to receive the changes in a s/r operation.&lt;BR /&gt;
I have read a couple articles with recommendations on speeding up s/r, none of the solutions I have found work. This seems to be linked in some way to the view map.&lt;BR /&gt;
Any thoughts about what could make s/r more efficient? right now a send and receive with a single new view added to the view map can take up to 10 minutes  on a small project.&lt;BR /&gt;
thanks,&lt;BR /&gt;
Patrick&lt;/T&gt;&lt;/DIV&gt;</description>
    <pubDate>Fri, 12 Dec 2014 21:55:37 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2014-12-12T21:55:37Z</dc:date>
    <item>
      <title>BIM server 18 slow send/recieve</title>
      <link>https://community.graphisoft.com/t5/Teamwork-BIMcloud/BIM-server-18-slow-send-recieve/m-p/231315#M1926</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;We are using mac, all work stations meet the spec requirements for AC18.&lt;BR /&gt;
When new views are created in either the view map or project map other work stations (than the one the view was created from) struggle to receive the changes in a s/r operation.&lt;BR /&gt;
I have read a couple articles with recommendations on speeding up s/r, none of the solutions I have found work. This seems to be linked in some way to the view map.&lt;BR /&gt;
Any thoughts about what could make s/r more efficient? right now a send and receive with a single new view added to the view map can take up to 10 minutes  on a small project.&lt;BR /&gt;
thanks,&lt;BR /&gt;
Patrick&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Fri, 12 Dec 2014 21:55:37 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Teamwork-BIMcloud/BIM-server-18-slow-send-recieve/m-p/231315#M1926</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2014-12-12T21:55:37Z</dc:date>
    </item>
    <item>
      <title>Re: BIM server 18 slow send/recieve</title>
      <link>https://community.graphisoft.com/t5/Teamwork-BIMcloud/BIM-server-18-slow-send-recieve/m-p/231316#M1927</link>
      <description>Just commenting for two reasons. First, we found today that sending changes, regardless of what is changed is fairly quick. Receiving changes however takes a minimum of 5 minutes, up to 30 minutes for major changes.&lt;BR /&gt;
This is fairly consistent for all AC18 projects. All 17 projects function in teamwork as they should. We are at the point now where we are looking at saving back to AC17 for all teamwork projects.&lt;BR /&gt;
I'm still hoping to get some kind of solution...</description>
      <pubDate>Fri, 19 Dec 2014 21:37:55 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Teamwork-BIMcloud/BIM-server-18-slow-send-recieve/m-p/231316#M1927</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2014-12-19T21:37:55Z</dc:date>
    </item>
  </channel>
</rss>

