<?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 Elevators and Stories: a divorce waiting to happen. in Libraries &amp; objects</title>
    <link>https://community.graphisoft.com/t5/Libraries-objects/Elevators-and-Stories-a-divorce-waiting-to-happen/m-p/294420#M4058</link>
    <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;Elevator objects in the main libraries are great, we usually use them, until we reach a project where we have to use different Z heights for their doors for a multitude of reasons. For instance, if we have different buildings with different heights on them.&lt;BR /&gt;
&lt;BR /&gt;
And as much as we tried, we couldn't figure out how to divorce the height placement of these doors to the stories that are defined in the project. Using hotlinked MODs don't even work (!!!). This is crazy, because it feels it should be incredibly easy to add this option for every door in an elevator object, and what we do now is utterly stupid. Basically, we have to explode it into a morph and then move the vertices around.&lt;BR /&gt;
&lt;BR /&gt;
So, my question is, how long do we have to wait until we get this incredibly small update to the elevator?&lt;/T&gt;&lt;/DIV&gt;</description>
    <pubDate>Wed, 24 May 2023 08:44:11 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2023-05-24T08:44:11Z</dc:date>
    <item>
      <title>Elevators and Stories: a divorce waiting to happen.</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Elevators-and-Stories-a-divorce-waiting-to-happen/m-p/294420#M4058</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;Elevator objects in the main libraries are great, we usually use them, until we reach a project where we have to use different Z heights for their doors for a multitude of reasons. For instance, if we have different buildings with different heights on them.&lt;BR /&gt;
&lt;BR /&gt;
And as much as we tried, we couldn't figure out how to divorce the height placement of these doors to the stories that are defined in the project. Using hotlinked MODs don't even work (!!!). This is crazy, because it feels it should be incredibly easy to add this option for every door in an elevator object, and what we do now is utterly stupid. Basically, we have to explode it into a morph and then move the vertices around.&lt;BR /&gt;
&lt;BR /&gt;
So, my question is, how long do we have to wait until we get this incredibly small update to the elevator?&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 24 May 2023 08:44:11 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Elevators-and-Stories-a-divorce-waiting-to-happen/m-p/294420#M4058</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2023-05-24T08:44:11Z</dc:date>
    </item>
    <item>
      <title>Re: Elevators and Stories: a divorce waiting to happen.</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Elevators-and-Stories-a-divorce-waiting-to-happen/m-p/294421#M4059</link>
      <description>Hi.&lt;BR /&gt;
I signed the divorce papers a long time ago  &lt;IMG src="https://community.graphisoft.com/legacyfs/online/emojis/icon_lol.gif" style="display : inline;" /&gt; &lt;BR /&gt;
&lt;BR /&gt;
The elevator objects, as clever and complex as they are, work well with simple projects. I scripted an elevator object that models the shaft (with pit and overhead) and then used with SEO to cut slabs. It is just placed where the elevator starts and set in which story it should end. &lt;BR /&gt;
&lt;BR /&gt;
Elevator walls and doors are then modeled in each level as regular walls and sliding doors. This allows for control in details and surface per door per level basis, and can be scheduled.&lt;BR /&gt;
&lt;BR /&gt;
The downside with a scripted object that references story heights is that it breaks when used in hotlinks, as it will use the heights of the host file, but walls and door placement will be ok if the correct settings for hotlinks are used.&lt;BR /&gt;
&lt;BR /&gt;
The array that keeps story level information shouldn't merge with the one in a host file. They should be independent arrays. Changing this could allow, for example, for a second array that has sublevel reference planes information for each file.&lt;BR /&gt;
&lt;BR /&gt;
Hope that helps you a bit.&lt;BR /&gt;
Best regards.</description>
      <pubDate>Fri, 15 Jun 2018 13:46:27 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Elevators-and-Stories-a-divorce-waiting-to-happen/m-p/294421#M4059</guid>
      <dc:creator>sinceV6</dc:creator>
      <dc:date>2018-06-15T13:46:27Z</dc:date>
    </item>
    <item>
      <title>Re: Elevators and Stories: a divorce waiting to happen.</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Elevators-and-Stories-a-divorce-waiting-to-happen/m-p/294422#M4060</link>
      <description>I could never get these things to work to satisfaction. I just model the shaft + doors too. The cage I either model with a few walls or just leave as 2d polyline.&lt;BR /&gt;
&lt;BR /&gt;
Maybe the way forward is to have the cage as an object with proper story sensitivity.</description>
      <pubDate>Fri, 15 Jun 2018 14:37:20 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Elevators-and-Stories-a-divorce-waiting-to-happen/m-p/294422#M4060</guid>
      <dc:creator>Erwin Edel</dc:creator>
      <dc:date>2018-06-15T14:37:20Z</dc:date>
    </item>
  </channel>
</rss>

