Jump to content

Katarina Ollikainen

Vectorworks, Inc Employee
  • Posts

    317
  • Joined

  • Last visited

Posts posted by Katarina Ollikainen

  1. Hi, my brain must have been on holiday already when responding to this post - the solution is so obvious.

    As long as the 'Add to Record' is checked, the data will go into the record attached to the tree object.

    You don't have to do anything fancy; it just works.

    The only thing is that it's not visible in the Shape pane in the Object Info Palette but in the Data pane.

    • Like 1
  2.  As a contour has only one single z value: if there are a lot of vertices, go to top plan view, and convert the contour to a polygon (make a note of the correct elevation first). Then convert it back to a 3D poly and give it the correct elevation.

    Modify > Convert > Convert to Polygons and then Modify > Convert > Convert to 3D Polys

    • Like 1
  3. @jeff prince - The crux (as I see it) is that you must have the fields inside the tool for the data to land on when performing the Existing tree import, instead of adding the info manually - there's no geometry to attach the record to as the trees are created at the import. It's the chicken and egg scenario 😁.

     

    Otherwise, the attached record is perfect.

    • Like 1
  4. All the Landscape areas in the Vectorworks libraries are set to only show fill colour as default instead of each individual plant (in 2D). However, the 3D geometry is turned on as default - you just have to be in a 3D view to see it.

    If you're looking for the individual plants to be visible in 2D, then you can go into the style and turn it on (see screenshot). 

    Screenshot 2023-07-11 at 11.34.45.png

    Screenshot 2023-07-11 at 11.30.53.png

    Screenshot 2023-07-11 at 11.35.35.png

    • Like 1
  5. Hi, this might be the wrong direction, but have you checked your origins? Often when you have strange geometry or things show up weirdly, it is because something in the file is too far away from the internal origin (the internal origin, not the 0,0 for x/y). This could be the issue if the texture is working correctly in another file.

    • Like 1
  6. @Tom W. Yes, the Hedgerow object is rounding numbers, as you can only place 'full' plants (the same behaviour as the Landscape area has).

    Also note that the calculation works 'as a Landscape area' if you're using 'Area' and as a Hedgerow if you're specifying per 'linear unit' (which is the standard way to specify hedgerow).

    Today there is no setting for staggered vs double rows - however, it's on the horizon and will be part of a future update of the Hedgerow tool. The same with the ability to edit the perimeter of the hedgerow without changing the quantities (if you're using plants pe linear unit).

     

  7. Sorry, I have never come by that setup.

    Perhaps it's better if you use a field in the plant style, for example Price SKU (one that you can have access to in the OIP, but that you don't use right now), set it 'per instance' and use this for grouping info. Then you sort your workshet by sum items on that - this will give you all single plants in one row and all grouped in one (or two or three, depending on how many grouping names you use). There wouldn't be anymore work than having to chose the correct data tag for the tagging - this way you can just go through the planting plan, find all groups and change the 'SKU' value for all of them at the same time. It seems a bit backwards to count plants via the data tag, but perhaps I'm missing something?

     

    Screenshot 2023-06-21 at 20.02.37.png

  8.  

    13 hours ago, DDD said:

    Is there anyway to report the actual plant quantity instead of plant object quantity? My file is attached and thank you for the help.

     

    Hi, if you report on plants (Plant Record) instead of the count of data tags, you'll get the correct quantity. I've added a very simple database report to your file, but you can use one of the preformatted ones - they're setup the same way.

     

    planting count v2022.vwx

  9. Yes, I've worked with it quite a lot and I haven't had any issues with it.  It's good for situations between other modifiers where you want to be able to fine-tune contours. Below is a simple example where I have adjusted the contours between the two pads - instead of having them perpendicular to the pad edges, I've added a slight bow to get a more rounded, softer form.

    Of course, there are many other ways to achieve this, but this is a good way for those awkward areas around other modifiers.

    If you have a file crashing, can you either post it here or send it to me directly so we can see what's happening. It should definitely not do that.

    Screenshot 2023-05-26 at 15.45.49.png

    • Like 2
  10. @jeff prince, you're right - the main issue was that the original site model data was rotated in plan view. I copied the data and recreated the site model in the same file, and then it worked fine. I did the same thing with the array to test 😁

    The landscape area was a case of just telling the site model to listen to the layer where the Landscape areas were and then connecting the Landscape area object to the site model layer.

    • Like 1
  11. @BCALJames, thank you for your input - we are working on the curb/border/edge and hope to come up with a solution that covers all kinds of edges, including 3D profiles. However, we're not looking at a solution only for the hardscape but a more overarching approach. I can't promise when this will be introduced, but it's a high priority.

    We do appreciate everyone taking the time to share ideas and requirements - this is how we can make our tools even better.

    • Like 1
  12. Hi, @bob cleaver. Plants and landscape areas shouldn't be sent to the surface - they automatically adjust to the site model surface.

    Plants don't have to be on a layer 'talking to' the site model - landscape areas do.

     

    Are you saying the plants don't automatically adjust to the site model? If so, try to nudge them slightly while the site model is visible. If that doesn't work, please post a sample file, and I'll look at it. 

    I haven't seen a bug in SP5 that would have stopped this from working - I just tested it in a file, and it seems ok, but I might be missing something.

     

    Screenshot 2023-05-22 at 11.25.46.png

    • Like 1
  13. The existing and proposed site model is actually the same (from a user standpoint). You create the site model once, with existing site model data. You can then specify in the Object Info Palette if you want to look at the existing or the proposed site model. Make sure the proposed is selected, and then add a grade limit to the site and add the proposed elevations. Update the site model and you'll see the changes to the site. 

    You can always change back to the existing view if you need it, or you can create a snapshot of it for reference.

    (you can also change the view in the Site model settings, but the OIP is quicker)

    Screenshot 2023-05-18 at 13.25.50.png

×
×
  • Create New...