<?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: BIMCollab changes FoV and cut surfaces - why!? in Collaboration with other software</title>
    <link>https://community.graphisoft.com/t5/Collaboration-with-other/BIMCollab-changes-FoV-and-cut-surfaces-why/m-p/253875#M33119</link>
    <description>(I've moved this to the "Other Products" forum, since BIMCollab is not a GRAPHISOFT product.)</description>
    <pubDate>Mon, 22 Mar 2021 18:06:17 GMT</pubDate>
    <dc:creator>Karl Ottenstein</dc:creator>
    <dc:date>2021-03-22T18:06:17Z</dc:date>
    <item>
      <title>BIMCollab changes FoV and cut surfaces - why!?</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/BIMCollab-changes-FoV-and-cut-surfaces-why/m-p/253874#M33118</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;R&gt;I have two issues in AC24 with BIMCollab 5.3 (BC)&lt;BR /&gt;
&lt;BR /&gt;
1.&lt;BR /&gt;
Why does BC changes my view cone (FOV, field of view) when I change camera position using BC issue double click:&lt;BR /&gt;
Origina FOV 90:&lt;BR /&gt;



&lt;BR /&gt;
After using BC, FoV 119?:&lt;BR /&gt;



&lt;BR /&gt;
I always have to manually set back FOV to 90.&lt;BR /&gt;
How can I avoid that?&lt;BR /&gt;
&lt;BR /&gt;
&lt;BR /&gt;
2.&lt;BR /&gt;
Cut elements get dark grey after using the zoom-to function from an issue.&lt;BR /&gt;
Original view&lt;BR /&gt;



&lt;BR /&gt;
After double clicking / zoom-to from issue manager issue in AC24:&lt;BR /&gt;



&lt;BR /&gt;
How can I avoid that?&lt;BR /&gt;
&lt;BR /&gt;
Another thing is that changing camera position is much too slow.&lt;BR /&gt;
Any other tip to speed that up? (We use selected only for view creation, max 20 elements, limit active layers to the max.)&lt;BR /&gt;
&lt;BR /&gt;
Thanks for any hint/ tip!&lt;BR /&gt;
&lt;BR /&gt;
BR, Florian&lt;/R&gt;&lt;/DIV&gt;</description>
      <pubDate>Mon, 22 Mar 2021 16:09:55 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/BIMCollab-changes-FoV-and-cut-surfaces-why/m-p/253874#M33118</guid>
      <dc:creator>Florian Lohberger</dc:creator>
      <dc:date>2021-03-22T16:09:55Z</dc:date>
    </item>
    <item>
      <title>Re: BIMCollab changes FoV and cut surfaces - why!?</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/BIMCollab-changes-FoV-and-cut-surfaces-why/m-p/253875#M33119</link>
      <description>(I've moved this to the "Other Products" forum, since BIMCollab is not a GRAPHISOFT product.)</description>
      <pubDate>Mon, 22 Mar 2021 18:06:17 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/BIMCollab-changes-FoV-and-cut-surfaces-why/m-p/253875#M33119</guid>
      <dc:creator>Karl Ottenstein</dc:creator>
      <dc:date>2021-03-22T18:06:17Z</dc:date>
    </item>
  </channel>
</rss>

