Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

14 Good



  • Rank

Personal Information

  • Location

Recent Profile Visitors

648 profile views
  1. @Peter Neufeld, thank you so much for your time. I will do some more research and probably report this.
  2. @Peter Neufeld, I have checked this one and still it is not the answer. No matter how you manage visibility settings, objects that should be partially covered by a solid are visible like they would be on top of solid, not inside it. See the picture in the attachment.
  3. So I am using clip cube to create some kind of horizontal section (like a plane, but by using clip cube). The thing is that if I use clip cube to create plan (horizontal section) there is a bug. But if I use the same clip cube to create classic section (lets say vertical) it works perfectly. Clip cube bug.vwx
  4. @Peter Neufeld, thank you for your time anyway 🙂 I really hope I will find where the problem is.
  5. It is not a solution. By changing cut plane to infinite you just show the top view. If I add "slab" to my solid (add an extrusion on top to mimic slab top view) chair is still not visible. More accurate model in attachment. Clip cube bug.vwx
  6. @Peter Neufeld, thanks for answer. But it is not the 3D view or OpenGL problem. My case is visible on the sheet layers (I have prepared one with explanations). You can see that there are differences between section viewports that go through solid with a hole and solid without a hole. I cannot see the chair in the section viewport on the sheet layer. Changing view from standard to orthogonal does not work. If I change rendering style to "Dashed Hidden Line" it works (chair is in place), but using option "Hidden lines" chair is gone some how but it should be visible.
  7. I think the same. This really looks like a bug or some kind of "work in progress" thing that was not finished. I will report it and maybe it will be changed in the next patch. It is a quite important node so it should be fixed as soon as possible. @AlHanson, @the frog - thank you so much for your time 🙂
  8. Hello, I have a problem with Clip Cube tool. While using clip cube to create sections it creates some kind of white mask (white filling) when cutting through solids. Objects does not appear if they are below cutting line and at the same time cutting line does not go through a hole in the solid. Everything works fine if cutting line goes through any kind of hole in the solid. Hope someone can help mi with that or at least explains why it works like this. Example file in attachments. Clip cube bug.vwx
  9. Hello, I tried to recreate my old script from 2019 and I have encountered strange thing. Group node in v2020 is different than Group node from v2019. In my example new node (v2020) does not work (gives 0 values), while v2019 node works fine. Does anyone has an idea why this node needed to be changed any why it does not work now? Both nodes in example file. Group test.vwx
  10. Thanks, I need to check this, but anyway can't wait for VW2021 then 🙂
  11. @Pat Stanford Values in OIP does show unit marks. Values without OIP does not.
  12. @Pat Stanford, I used your script and got results (attached file). 'CWDObj'.'OpeningWidth' and 'CWDObj'.'OpeningHeight' are "REAL", so they should be numbers, but they do not change according to current document units. 'CWDObj'.'OIPOpeningWidth' and 'CWDObj'.'OIPOpeningHeight' are "Real - Coordinate Displacement". I have no idea what this kind of data type is, but it is working. Information is correct in terms of document units. Do you know the difference between these two data types? I can not use math operations on both results, so it looks like they are not numbers.
  13. @Pat Stanford, thanks for a hint. Yes, there is a second formula #CWDObj#.#OIPOpeningWidth# that is working fine, but math operations still do not work. My formula looks like this: #CWDObj#.#OIPOpeningWidth# - 10 Maybe I am missing something like: #CWDObj#.#OIPOpeningWidth# - #10# ?
  14. Hi all, I have a problem with Data Tags. My custom data tag should return window's width. But despite the document units, data tag always shows number in millimetres. Option "document units" is unavailable in edit data tag mode. In my file there is a second tag that works correctly. Second question is, if it is possible to do simple math operations inside data tag definition. E.g. I want to show in my tag "windows width" - 10. I tried to use following formula "#CWDObj#.#OpeningWidth# - 10" but it is recognised as text and displays as 1000 - 10 on my tag. Any hints? DataTags.vwx
  15. Hi all, Is there any way to read a NURBS curve direction in Marionette, like we can using PIO? I would like to get direction vectors on certain points of any NURBS curve, but I can't find any node or vs.function that I can use. Any hints?


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.

  • Create New...