Jump to content

Mike Lamb

Vectorworks, Inc Employee
  • Posts

    74
  • Joined

  • Last visited

Everything posted by Mike Lamb

  1. Hi Abby, I think your trouble is coming from the hardscape in the existing class, that you put inside your massing model. I have highlighted it in the attached image. Not sure why you would do that, you can check the "draw floors" box in the OIP and simulate the slabs that way. You have that hardscape set to act as a modifier, so it is pulling up the edges of the site model to meet it. You'll need to set the site model interaction for that hardscape to "no site modifier". Then update the site model. I did see a second modifier in that same spot, you may need to remove that too. You will need to turn on the Site->DTM->Modifier class to see it.
  2. Hi Ned, thanks for reporting this. I see what you mean, the contour at 45' has not been created as shown in the source data. I'll write up a bug report for this.
  3. Thanks Michael for bringing this to our attention, it looks like it is a bug and I have reported it.
  4. I would say hardscape path on a site model, using transverse and longitudinal profiles to shape the hardscape path.
  5. Hi benaus, can you post your file here so I can take a look?
  6. Hi AnneSea, I downloaded your file and had the same issue. As a workaround, I discovered that if you select the 15 3D polygons and copy them over to a new blank file, the site model will generate successfully, at least it did for me. Let me know if this works for you. I'll report this issue to engineering. Thanks, Mike
  7. Hi soorya, can you post your file here? I'll take a look. What version of Vectorworks are you using?
  8. @alfresco - Looks to me like you need to set 3D display style to "proposed only" for the site model. Those modifiers on the hardscape only affect what is shown on the proposed model.
  9. @alfresco - Post your file, and I will give it a look.
  10. Hi Parveenkd, this is happening because you have two objects placed waaay far away from the origin in your drawing. To fix, go to the drawing window and use cntrl-A to select all, then fit to objects. You will see that it zooms way out. Now use fit to page area, draw a marque to un-select everything there in view, and you will have two objects left. Delete those, and the drawing will be back to normal. Let me know if this works. Mike
  11. Marshallae, I don't think there is a way to wrap a texture to the curve of radial pavers. You could also use a try a hatch or a pattern, something with uniformity, they will not follow the curve either, but they might give you the textured look you are looking for. Set the fill opacity lower, maybe like 30 to 50 percent.
  12. Hope this helps! You will probably want to set the control point of the radial pavers to the center of the pool in your drawing, that should make the pavers wrap around that curve nicely. hardscape radial pavers.mp4
  13. Have you tried the pavers-radial joint pattern option for hardscapes?
  14. @elch Just heard back from the development team, I'm pasting their response below. I'll also attach their files. Notice that: There is a set of adjacent Roadway (Straight) and Roadway (Curved) objects as an attempt to model a complex roadway consisting of straight and curved sections. Actually, the Roadway (Straight) and (Curved) objects are not suitable for modeling such complex poly roadways as it is hard to vertically align the separate objects/road segments (as every separate roadway object could be sloped differently). As a result, the site model recognizes modifiers conflicts exactly where the separate roadway objects align to each other. In such cases, it is preferable to use the Roadway (Poly) object which models continuous roadway along a polyline and overcomes the vertical alignment issues. The Site model collects modifiers from a custom set of layers (see "modifs_from_custom_set_of_layers.png”) which includes the "modifiers” design layer. This means that all modifiers from the "modifiers” layer will be recognized and collected by the site model no matter this layer is set invisible. Notice that there are modifiers from the "modifiers” layer which overlap some of the Roadway objects, i.e. they conflict with some of the modifiers that comes from the roadways. Please see the attached "Research_Conflicts_Reasons_1.png" which illustrates why the site model recognizes conflicts between the modifiers it collects. I have prepared a fixed version of the file (see the attached "p80III_modell_fixed_v2019.vwx") where: The set of Roadway (Straight) and (Curved) objects are replaced by two Roadway (Poly) objects (they follow the same path and model the same geometry). Some of the 3D modifier polygons in the "modifiers" layer are slightly reshaped (using the Reshape tool) so they don't overlap any of the roadways. p80III_modell_fixed_v2019.vwx
  15. @elch I think the site modifier of the roadway is causing this. I can go in and edit the contours, but they get overridden by the roadway modifiers after you exit the edit mode. I guess one workaround would be to uncheck the "use site modifiers" checkbox on the roadway, or have the site model ignore the elch-weg layer for site modifiers. I'll write up a bug for this.
  16. Hi elch, what version of Vectorworks are you using? Would you mind attaching your file here so I can take a look? Mike
  17. I exported it back to 2018 for you. Let me know if this works! EXE CR59 v2018.vwx
  18. @Phileas - I was able to reproduce this using 2018 on my Mac, but not in 2019. It's much easier to select the site modifiers in a 3D view now as well in 2019. Unfortunately we've stopped releasing service packs for 2018 at this point, so this will not be fixed in 2018. If you would like to try this in 2019, you can go here for a free evaluation copy: https://www.vectorworks.net/trial/
  19. @Phileas, what Mac OS are you currently on?
  20. Hi Phileas, any chance you could attach your file here, and post a short screen capture video of your workflow? You're on 2018, right?
  21. @Phileas - Glad you were able to work around it. I did file a bug report for it, but it probably won't be fixed until version 2020.
  22. Inserting the site model into a new file is going to cause this to happen again, because the site model effectively gets rebuilt as part of the process. Just make sure whatever design layer you place it into does not have a story assigned to it. After the site model has been inserted, then you can go back in and re-assign a story to the design layer. Hope this helps...
  23. Here you go. I also attached a video showing the steps. CRA_EXE_50 Site Model fixed.vwx site model fixed.mp4
×
×
  • Create New...