Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

194 Spectacular

About DomC

  • Rank

Personal Information

  • Location

Recent Profile Visitors

3,255 profile views
  1. DomC

    Rectangle Packing

    @Gescher Hallo Ich kann mir das gerne anschauen. Es gibt zwei Tabellen-Inputs. Einerseits die Teileliste, andererseits eine Plattenliste um für verschiedene Materialien, verschiedene Plattengrössen zu definieren und um zu sehen, welche Platten bestellt werden müssen. Wobei man auch bei der Lager-Liste Stk 1 verwenden darf, wenn man das nicht braucht. Also Board-List ist der Platten-Lagerbestand und Stückliste-Küche ist die Stückliste. Es könnte dann Fehler geben, wenn die Spaltenreihenfolge nicht stimmt, die Zahlen mit Komma getrennt sind (7,1 statt 7.0). Poste doch mal Deine Beispieldatei und Beispieltabelle.
  2. DomC

    Reshape Node 2D

    Another example usecase of parametriced drawers.
  3. DomC

    Error loading Vision Library

    Post removed: (Wrong Thread, sorry)
  4. DomC

    Converting Strings to Numbers

    Hi Generally this are common issues: 1. If you have a String of 0.30000 and want to have have a string output from 0.30 you can youse x[:4]. The first 4 character of the string. If you have 100.45987 you will get 100. with this formula. If you use x[:-2] the last two characters are lost. To Prevent this, you could first split the string in number and digit and then operate with this. 2. Sometimes there are Units like m2 mm m qm etc. 3. Sometimes we want to have prefix like +. - and +- etc. 4. Sometimes there are , instead . of decimal seperators. The attached Nodes, addresses all of this common issues. Simple issues, but relatively complexe to solve. I attached some node to solve them. The error message you got is because to substract two items from a list (a string is like a list '0', '.', '0', '0' etc. or a list of numbers will be [0,5,3,4.5,]). So with a Number of 0.30000 it will not work, this is just one item. You could convert to string str(x)[:-2]. Then it would work. Do not know what mapping is doing. If it converts the string of 0.3 in a number it Maybe by standard makes again 0.300000 in the IFC Export. You see, not so trivial. I Recommend using the Attached Node Digits from string and try with this. Set Digits From String.vwx
  5. DomC

    Apartment Area

    Hi Pat Thanks for reaction. You are right and I already switched to 11_Area in the 2019 File.
  6. DomC

    Apartment Area

    @Luise It hard to intercept every bug in other components but I think this Update will fix it: 1. Uses 11_Area which seems to be m2 instead of cm2 2. separate numbers from unit and can handle , as dezimal delimiter. 3. Returns 0 for Bottom elevation if elevation is negative (can't fix this, maybe I could by getting the IFC elevation height, but I don't want to) You can try the attached Update File it will work without error Message Apartment Area v1.2.1 v2019.vwx
  7. DomC

    Apartment Area

    Are you testing in 2019? In 2019 space delivers cm2 for area and negative elevations will result in empty output. That will result in issues because the script is not made to deal with empty input. I will look what. Also the "Get Record Field" Node from 2018 will be broken in 2019.
  8. DomC

    Apartment Area

    Hi @Luise An Update is available. Now it eats comma separated numbers together with units.
  9. DomC

    TV All-in-One

    Good and purged script design with a user friendly info-palette. Thanks for sharing.
  10. DomC

    If in String - Result not as desired

    As Marissa mentioned 1. Replace code inside "Get Record Field", which is from 2016, use an outdated vs.GetType() command and is not update-ready. 2. I would solve the prefix with the if node: 3. I would try to keep the symbol record format workflow. Because it is so much easier to change the look of your stamp. 4. Uploaded an update of my example here:
  11. DomC

    Automated Layout

    Hi There is an update. The "VP Layer Visibility" has no bug. It just set the same visibility in all created vp. So not very usefull for creating more than one viewport with different visibilities. However I made this node new. It works now with different input sequences. So every created vp can have different visibilities.
  12. DomC

    Automated Layout

    Hi Matt Hm ... it's seems to be a bug in the "VP Layer Visibility". I will look into this to provide a fix.
  13. DomC

    Automated Layout

    the first two handles are different from the others. Follow the handles from right to left in the script. Then you will see, that they are strings before they got handles. They also will be the same string. That's how I search an error. Like the TV, if cable connection is broken. Follow the cable back and you will find the faulty connection. The name is built from the Room Number "11_Number". Which maybe is empty in your file and the Layer name of the space. If this is being the case all spaces from one layer will putted on the same layout on the same place. To fix that: 1. Take another (unique) data from the space. Or create room numbers 2. Feed the Sheet Layer name producer with a series of numbers. 3. Make the Position of the Viewports a Serie of coord Points and the will lay side by side.
  14. DomC

    Automated Layout

    Hi Use "Print Debug" to see, what's coming in the "Create Layer" Node. If you have always the same layer name (input) or the same layer handle (output), all your viewports will created on the same sheet layer.
  15. DomC


    Sure The Script needed a little Updates for 2019. Cause the Path Handling in 2019 is better than in 2017/2018 I had to delete some lines. Halftoning Farbige Punkte.vwx


7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114


© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.