Jump to content


  • Posts

  • Joined

  • Last visited


9 Neutral

Personal Information

  • Occupation
    Landscape Architect
  • Location

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi Pat, Nope, Viewport Class are normal as per default. Just changing the Pen style & Color to 'By Class' is actually changing the Fill in the section Viewport which doesn't make sense... See example in the file attached Landscape area Test.vwx
  2. I've experienced issues with the Section Viewport and Landscape Area : Case scenario Vectoworks 2021 OZ SP1 Win 10 Landscape area applied to a site model (3D poly or Texture bed) and section Viewport is created. Issue Landscape Area Components (Fill/Texture/Hatches or Material) are not showing as they should in Section Viewport. Fix Select Landscape Area and Disable 'By Class' in the Attributes Info Palette as it is overwriting other set up options.
  3. @Dylan No worries 😉 Yes, Everything that needs to be scheduled. Note that you can also attach a record format to a group. And you can copy/past record format with Eyedropper. So if you've got a nice class structure you can easily select apply/modify an entire bunch of object. (e.g. bring a symbol with the vapour barrier record format attached and copy/past the record format to the group of line). Plus you can also select from your worksheet (e.g. every element having ID number 1.1) and modify the record format of those elements from your worksheet. So it's a pretty flexible solution. Takes a bit of time to implement at the beginning but you get your money back with the annotations and schedule process.
  4. @Dylan Hi Dylan, I'm implementing that workflow on a project for the moment. I've done it like this : Create a record format with all kind of information you would need in your future report ( I have : ID number, Description, Sheet detail, related Sheet details, Specifications, Manufacturer, Product Name, Size, Thickness, Color, Finish, etc) Attach the record to every object that you will need to be scheduled Create your worksheet and link all the data from your record format. Create different report depending on what you want to show. E.g. I have a report showing just : ID number, Sheet detail, Related sheet detail. ( this is on my general material plan) Another one for the size, color, finish, manufacturer, specifications etc. ( this is for my material schedule) Create a custom data Tag to show your ID number. I have for example : 1. Masonry (category) 1.1 Retaining wall (Element) 1.1.1 Blockwork (Parts) 1.1.2 Render( Parts) etc. Note : You can create a report with just 2 column to create your legend. The good thing with that workflow is that you can modify you ID number directly from your worksheet and all the same number at once. Here is a chart of my workflow
  5. @Elin Did you put your data tag on the viewport ? I Could not find a data tag just for elevation so I quickly made one. Have a look at the file attached. Is that what you want to achieve ? On your design layer : Set your 3D stakes on the site model Create a section Set your section viewport on a new sheet layer On the sheet layer : Enter annotation mode in your viewport Use the data tag on your stakes. (As mentionned, I made a custom one. It takes 2 min and you can save it in your library. See picture below) Elevation data tag.vwx
  6. @Elin Maybe try using 3D Stakes and Data Tag to get the elevation in your viewport
  7. What I meant is when you have a perspective viewport and you open the edit panel, there is that option 'Camera' that you can use to modify your point of view (even when you didn't set up a camera.. I know it's a bit confusing). But as for your case it does look really painful ! Are you working in Open GL to move around ? Textures are the next suspect to check. I tend to move around in Wireframe if I ever use a camera. Very rare thing.. I usually don't even touch the camera or use the rendering tool of VW. The gap with Lumion or Twinmotion is just too big. VW is great for lots of things but rendering...Haha. I think they already gave up actually. No one can be good at everything I guess !
  8. Well I've got the same results as you. The operation takes ~50s to perform. Looks like it's handled by only one CPU so hopefully this kind of operation will be improve in 2021 with performance enhancement on multi tread. Also you can reduce your waiting time by getting the right setting on a smaller sample of your curtain wall (or just one side). That's a lot less geometry to process -> much faster to perform. That's my best advice 😕
  9. Can you share your file ? or just what we can see on that layer if there's some sensitive info.
  10. Why editing your viewport point of view using crop and not camera ? My model does also lag if I edit the point of view with Edit/Crop but not at all when using Edit/Camera
  11. The viewport from the referenced file looks like a Wireframe Top view were the first one looks like a Top Plan View. Is your referenced viewport on a Design layer or Sheet Layer ? They're behaving differently accordingly. Are you trying to reference that viewport on a design Layer so you can make another viewport of that viewport to mix Top View(3D) and Plan View (2D)? (A viewport Inception 😛)
  12. @jeff prince I've finally been able to fix the issue ! Problem was coming from the source data... Even-though I thought I did a good job at having clean data input. Previous workflow Contour imported from surveyor Polyline simplified (50mm deviation) and converted to 3D poly Run 'Validate 3D data' to spot and fix eventual overlap Create site model from source Data Site model looks good and was fast to generate (good sign). Everything looks fine until issues with contour labels... BUT after careful analysis of source data it appeared that some 3D poly vertex were not on the same elevation (100mm difference, very hard to see, specially with hundreds of contour lines). Thus imported surveyor 3D data were the problem. Fix Convert 3D poly to contour lines (select all 3D poly/Landmark/Create object from shape/Site modifier/Contour). Leave elevation to 0. The faulty 3D poly will now appear as a contour (or pad) with a slope. select them all (Select similar Tool) and set slope to none. Convert the contour lines back to 3D poly. Now you have nice 3D poly with all vertex on same levels. This will be my typical workflow for now on as 'The Validate 3D Data' only is not enough. EDIT Problems are back. Playing with site modifiers and grading limit back and forth are causing contour labels to go crazy. And once it's started nothing can fix it (to my knowledge). Workaround Keep a copy of your site model (e.g. another layer, turned off). Save you Site Model settings. Once you are done with your Site Modifiers (and your contours labels are all messed up), use the 'original' copy to replace the messed up Site Model. Apply your saved setting and it should be fine now. (The problems start to appear when you play with modifiers back and forth. Not when initially applied)
  13. Same, Bring it forward (Ctrl+F) is my fix.
  14. Same problem as Jeff for the contour Labels stacking up. My Source Data are nice and clean 3D poly (Low vertex count and 3D Data Validated) Recreate from source data doesn't change anything D
  • Create New...