Jump to content

Michal Zarzecki

  • Posts

  • Joined

  • Last visited

Everything posted by Michal Zarzecki

  1. Hi J. I seem to have a similar issue. We have had VW for a short while now, but we are using it to create a site model based on our previously designed levels. Also to see if they work with the water flow. It appears that stakes produce localised depressions and peaks, rather than having a wider effect on the site model. In your case, if you are creating a pond, then a series of contours or pads - one per each depth, e.g. every 250 mm. They should modify the site model to faithfully shape the bowl of your pond. I think you should also have a Grade Limit object of the shape of your pond to containg the modifications within it. I am writing that from top of my head, but when having some time I will see if I didn't miss any step. I hope this helps.
  2. @Tony Kostreski Thanks for replying to this one. I have tried various properties of Hardscape objects, including slabs (Datum top and bottom), pad modifiers etc. It seems that something is not working properly. I made a simple trial. I created a simple flat Site Model and created a few Hardscape objects with elevation set to be slightly higher than the model itself. Then I tried different combinations of Slab settings. When Slab Datum was set to bottom (Slab thickness remained positive) nothing changed, i.e. the elevation in properties indicated to be at bottom of slab. Nothing seemed to change when I set Datum to top. OK, the thickness of slab changed automatically to negative value. I considered that bizarre. But, when I changed slab thickness manually to negative value - Eureka! The Hardscape object dropped - the elevation became the top of slab. I just can't understand why it didn't react this way when I set the Datum to top in the first attempt. It must be a bug. Perhaps someone else can review that behaviour?
  3. 1. Hardscape Object 'Levels' I am not sure how about others, but I feel very confused about elevation property of hard landscape elements (Hardscape objects, Steps etc.) in VW Landmark. I mean, I think I understand the concept - it is a vertical value over the Design Layer. However, the interpretation is very confusing and counterproductive. An example: If I have a Hardscape object set to be 3D slab in my site design with an elevation of say 10,000, it means that the bottom of the slab is at this elevation. Technically, everything is logical and terminology consistent. Now when I assign a slope to my Hardscape, I will get properties to show what is the elevation at the start and at the end of the slab. But how does this information help me understand and design the levels, since I am not interested what the bottom of hard landscape surface is - I am interested in the top surface! If I understand the tool right, I always need to take into account the slab thickness when thinking about the level on top of the Hardscape object's surface. This is an extra maths I need to do which is hardly helping me in my work - it's actually to the contrary. I may have a wrong understanding, but I always thought that computers and software should help us with productivity. So, when working with a digital tool with powerful site modelling features, I would really appreciate it being helpful. I appreciate all the work which has been done to the Hardscape tool, but could at least the Finished Surface Level (or something along these lines) be added to the properties tab? This really needs to be a term used in the industry, not some developer's lingo developed for the sake of the software. 2. Stairs 'Levels' Stairs is yet another helpful tool in creating parametric objects. Again, rather than performing maths here with setting up height, can Finished Surface Levels be added here? When setting up the Stairs, under General Tab, the general geometry parameters include Height, which can be set up by value or layer elevation. Why not by top and bottom lovels? For example: I have to design steps to the existing building, where new doors have been made. I have an FFL given as well as surface level of paving around the building. It would be very helpful if I could start creating stairs in VW by typing in these values. The rest should be calculated by the software itself. Also, an optional tag with Top of Steps and Bottom of Steps would be much appreciated. As in the first part of the question, VW adds to the confusion around spot levels here. Rather than Elevation property, we only have a Z Value, which practically seems to be elevation. What would be more practical for landscape professionals, is the bottom of steps level property, which should tie the stairs with the finished surface level of Hardscape objects. I hope the above description of my issues makes sense. I am really curious if this is only my impression or other users also have hard time with getting these right. Regards, G
  4. I have just used the tool for the first time and feel really disappointed - again 😥. I can't understand that there had to be maths behind rotating them posts, but apparently they [VW] can't update the tool to give the user the flexibility and choice. Similarly, I found the post positioning tool extremely unintuitive. Seems that I will have to model that from scratch. I second that. Tried to create a bin store with metal frame inside the enclosure. I couldn't find a way to offset the timber slats from the frame. Now I can understand why - there is no such option. It seems that there should be separate tabs for panelling and frame. Then once could specify the number etc. of horizontal or otherwise frame bars and separately what is attached to them. I haven't even got there yet, but I wonder what I will come across when trying to specify the gates 😱
  5. I second the wish. It was quite surprising to me that there is not proper hedge tool in VW Landmark. I would envisage such tool to create a hedgerow with number of rows set by the user. One should be able to specify planting in staggered arrangement as well, as this is the typical planting method. Ideally one could specify the profile of a hedge for better representation of the design intent, such as tapering or box shape. I wonder if such hedge could also work similarly to the Wall tool, i.e. where hight could be modified along the hedge. Native, mixed species hedgerows are very often specified in the countryside, so this should be an obvious option for such Hedge Tool. Sometimes, this is actually explicitly conditioned by local authorities. There should be no need for a workaround to achieve such a basic task undertaken by landscape professionals. I hope that will be picked up by the developers.
  6. @bgoff , that sounds promising. I need to try out how that works.
  7. Hi All. Interesting ideas and solution above. Will definitely need to try these out. When using the Hardscape tool for the first time I felt that the tool needs a bit of love. I think that it's not only about the visual aspect, but also the specification. I was quite surprised that the information in the tag was so limited. It would be amazing, if one could not only define the visual side of things but also the technical one. Imagine there are fields where you detail the proposed manufacturer, jont width, perhaps mortar etc and this is then automatically included in the tag. The latter could be styled, i.e. one could choose what item of the spec to include. Another thing is the edging discussed in this thread. Perhaps one could define the profile of edging, similarly to the possibilities offered by the Railing tool. So, imagine you have a default choice of BS kerbs, block eding, setts and you can add your own. And the concrete bedding and haunching as well 🤩 . What do you think about it?
  8. In the practice I work in we have only recently started using VW Landmark as the first step towards BIM. Having trialled a number of landscape packages I must admit I am quite disappointed about the translation of the physical process of thinking of and designing site levels and drainage into the digital processes within software packages. The way we usually do it is by working out the spot levels and falls, based on the existing levels, FFL, drainage strategy. Basically, we calculate everything and try to make sure it's compliant and would drain efficiently. I was hoping that software would do part of it for me and I could annotate the resulting levels on a plan. In the process, I was shocked to learn that stakes do not read elevation from hardscape objects/ surfaces, walls etc. These are basics! I was modelling external steps recently and had a really hard time understanding what level the landings were at etc. I then tried to find a tool to actually allow me to read the spot levels from the resulting design. Another struggle. I needed to read the elevations from the end of slopes to hardscape slabs, figure out what levels that actually was and use a stake as a marker. Perhaps someone here can advise on the better way? I really wish that the developers take these requests seriously into consideration, since at the moment we need to do workarounds rather than being supported by the software.
  • Create New...