Jump to content

Hello Community!



  • Content Count

  • Joined

  • Last visited

Everything posted by STERNontwerp

  1. @DomC: I have changed the network, so that the last +1 vertex = vertex 0. As it is, the inner corners come in pairs. With a non-orthogonal shape they don't, so this network only works fully in a orthogonal shape. (But even when not working fully, it eliminates some of the vertices in non-ortho shapes, see below.) smallest distance beta 0.8.0 _EV2.vwx
  2. This might help, although it has not been done with the original poly. It gives the inner corners, the only corners that need to be checked. (If a node would exist that enabled a change of the start vertex of a poly, marionette-live would be a lot easier.) Ernst van der Vecht smallest distance beta 0.8.0 _EV.vwx
  3. Great, thanks, (I could send these things directly to you, but I suppose it is usefull if others can see what is happening) Ernst van der Vecht
  4. According to the description of the SetLineAttribute node I can set a dashed linestyle with f.i. a -1 input. But I don't think it works. SetLineAtt_iLinestyleQuestion.vwx
  5. STERNontwerp

    Vortex box

    It works with 3D objects, but I don't think it works with groups. You could use [Ungroup] & [Solid Boolean] (Objects/Solid) To make 1 object from the path-extruded squares. (But actually you don't have to mirror, move and rotate should be enough)
  6. STERNontwerp

    Vortex box

    When you input something else then 9 into 'Number of Boxes', then it goes wrong. The squares are out of line and there are still 9. There are 9 outputs of the ordered list when you input 3 into Number of Boxes. Maybe there is a solution without the ordered list with the [mul list] node (basic math), [Repeat], and [Sequence]?
  7. STERNontwerp

    Vortex box

    There's a Mirror node in 'Operations'
  8. STERNontwerp

    Vortex box

    Since it is symmetrical you could start with just a path-extrude of a square and mirror/rotate that six times.
  9. I changed it, using eyes instead of windows to show the viewpoints. Easier to show what is happening, easier to make, and probably easier to use to give feedback. Also attached records to all the eyes for further use. It is possible to: change the eye height of the ground floor separate from the other floors. choose to look out perpendicular, or to have diagonal windows when near a corner (as shown here) change the distance between eyes No views can be seen from the eyes yet. No analysis or the views can be made (that is my next step, I'll start at heving a look at ImgProcessing) No feedback can be give with f.i. red eyes . ParaViewAna030.zip
  10. Something else: It is a pity that the input 0 into the contour node gives a error message, while the output is ok: a single contour-line. There is a workaround: make more contours and just use one.
  11. When I changed the line into a window it also went away
  12. Yes, this happens. Don't expect too much from old networks and nodes.
  13. In the meantime I attached records and names to the windows. Something goes wrong when attaching the names: two windows go missing. Bug or my fault? ParaViewAna018zonderWS.zip
  14. I have a reason to start at the building looking at the church/trees/whatever: I don't know what a client wishes to query. It might be a church, it might be 'a beautiful view' f.i. defined as a park, water, trees, monuments etc. In my idea I can give all these thing a color and make the rest of the model white and find out if (and maybe how much) it can be seen from the window. Another idea is to save the view and use the appropriate view in a sales brochure. And another idea is to attach the point of view to a 3D-person which can be placed freely in the model. So it seems I should start at the point of view. However, it seems like you have an idea about how to 'project' the church to the building and that might overrule my arguments. If so, please let me know. Thanks Sarah and Marissa for thinking with me.
  15. I have started with the first step. But first some explanation on my choises/hopes Make picture: I really don't know how to do that and can't use Python/Vectorscript myself. I hope something with the vs.VSave command can be used. Center, church, BIM etc: This is meant to be used by architects an urban designers to decide the mass and placement of the buildings and/or to check the view/placement of the windows. Probably no BIM-model is used in this phase of the project, so it will have to work with volumes without an allocation of rooms or windows. I assume floor heights are known or can be guessed for now. Working with a view-direction will limit the possibilities. I'd rather just look at a wide angle out of the window and query that image. This will allow the query for multiple objects, such as trees in a later stage. Setting this up in separate modules will allow further adaptions. For instance: 1: viewpoint from mass or BIM or... 2: setting up records or worksheets for every window (my next step, will have to learn to work with records/spreadsheets for that) 2: saving and querying image 3: reporting / feedback in model Querying the Image: I hope I can adapt your/Alan Woodwell's ImgProcessing network (with Pillow). I am an architect working with marionette, not a software engineer. No cross-platform writing possible when I have to write it, but how to install of Pillow can be found on this forum. The first step is to cut the volumes into layers and assign windows to ALL the facade (done with boxes for 1 floor). Next step is to calculate a point and direction for the cameras/viewpoints (done with 3D lines on 1 floor). A recurring quention when working with Marionette: 1: I rather not work with List Explode. I'd rather use Get Item, but can't get that to work. The number of floors will be limited when using List Explode. (I have used a vwx-model of Mart-Jan Oosterveld, www.moost.nl to experiment on) ParaViewAna012.zip
  16. Hi DomC, I just thought it would be handy, but if there are problems with it, I won't use it. I suppose this means that using the 'set name' and 'name' nodes in the same network can go wrong in other uses too. Another case of the secret lives of nodes.. I wish there was a wiki where we could find these tips (or f.i. that 'move' doesn't work with groups, the use of 'get XYZ' with lists, ...). Maybe I'll start a topic to see if a wiki can be made. Thanks for the comment, Ernst van der Vecht.
  17. Version 1.0.0


    Nodes that make it possible to transfer data without wires (For instance if you want to use the info that was used 100 nodes back and your wires get too long)
  18. Before starting this new project I would like your opinion and tips. The idea is: make a network that analyses the view from a lot of apartments. For instance: Check which of the 444 apartments can view the church. Is there a solution for the points that I deem impossible? Steps: 1 identify the 444 apartments in the model 2 identify the facade of the apartments (for now the whole facade of the appartments can be glass) plan a: 4a1 place a camera behind the facade 4a2 make a jpg from all 444 camera's [impossible ???] Is it possible to make a jpg (or PDF) in marionette using the camera? 4a3 identify if there is a red color on the jpg 4a4 give feedback in the model (f.i. make all appartment that can view the church red) plan b: same as plan a, but with a 3D-view instead of a camera [impossible ???] Is it possible to make a jpg (or PDF) in marionette using the camera? plan 😄 4c1 place a light behind the facades 4c2 turn on the lights one by one 4c3 identify which lights shine on the church [impossible ???] Is there a way to identify if an object receives light? ❕ 4c4 give feedback in the model ❕: that would be really cool and make a lot of other things possible
  19. I've made a new tesselated morphy with puzzle-peaces and cleaned up the network a bit so that I can upload it here. Save first. Ernst van der Vecht Morphy050-Tessel_VWforum.zip
  20. Since I don't know how to use Python, I've used a Group node followed bij another Group node to put one series of objects on top of another.
  21. That is great, the whole network, but also the new nodes! I don't understand all of it yet, but here are some possible improvements: If the width of the 2D BBox > 400: the scale of the viewport could be 1:50 instead of 1:20, or have a varying scale depending on the width. There is an error in the description of the VP Layer Visibility node: sLinvis is described as grey instead of invisible (and I think it would be easier on the eye if the standplaenung-layer was grey in the overview viewport)
  22. Thanks for your explanation. I tried searching for iPrefiD on Vectorworks help, Google and this forum with no usefull results at all! How did you know to put -1 into iPrefiD? Is there an explanation of nodes I don't know about?
  23. After making the pawn-queen morphy, I continued working on the node and made a tessellation of the morph. See explanation below
  24. The picture looks similar to a file I once downloaded: ObjectInfoByLayerExample.vwx . I think it was made by DomC, but I can't find it on the forum anymore. I have attached it, hope DomC won't mind. I haven't worked with it, so no garantees. Ernst van der Vecht ObjectInputByLayerExample.vwx





  • Create New...