Jump to content

Tamsin Slatter

Vectorworks, Inc Employee
  • Content Count

    1,714
  • Joined

  • Last visited

Everything posted by Tamsin Slatter

  1. VB-175107 VB-175105 (Note that these are internal links and serve only as a reminder to Vectorworks staff that the bug has been reported.)
  2. Thanks for sharing your file. I hadn't spotted that. I am sorry to say that the Image scaling issue is still there in 2021, but I will file a bug for this straight away, using your excellent example file. Also, the issue with the None class is the same. I will file that in a separate bug report. Regarding referencing resources, here is the article you need from Vectorworks Help >>
  3. Hi @Tbai Thanks for posting this and for attending this morning's LI session. Data Visualization in 2021 DOES include the ability to override the opacity on fills. It also offers the chance to create a blend of colours between two selected colours, and to export these as a named colour palette. If the fill is something that requires a named resource (such as a hatch or image), then the resource would need to be the same across a file set. Another option would be to have a resource file, that is used to reference resources into a number of files across the project. But this comes with a health warning. Referencing resources in this way can be disastrous unless everyone is well aware that editing a resource will cause it to update across the entire project!
  4. @jpccrodrigues All I can say is hold that thought...
  5. I have downloaded the file and made two changes: I reshaped the long hardscape that was closest to the kerb (curb). It had an extra vertex, which was shooting to 0. I removed it and brought the kerb in line with the curved hardscape. I also changed the elevation on the curved hardscape to 0 - it picks up its elevation from being aligned to the roadway. No crashes for me... Hope this helps. HARDSCAPE TEST.vwx
  6. I've had a look at the Roadway, and notice that it is created as a Roadway (Custom Curb). I am not sure that this is supported with the aligned slab - but I will check. Meanwhile, I replaced your roadway with a Roadway (Poly), and now the hardscape aligns. I also edited the components, and set the alignment to be the top of the component, so that the top of the hardscape grades to the top of the curb (kerb). Hope that helps. road-hardscape test.vwx
  7. Thanks for sharing this feedback. Have you tried using the Grade tool? It won't solve all your desires, but a network of grades can have each connection point set to a specific elevation or you can set a specific grade to calculate the elevation at the connection points. To view the elevation of the site at a specific point, the Stake tool will report the surface of the existing or proposed site. It doesn't show the direction of fall, but it does provide the elevation. You can move it across the surface and it will update.
  8. Thanks for sending the file through... I am looking at it!
  9. Hi Could we have a look at the file please? Preferably the 2020 elements and the 2021 version, then we can try to work out what's going wrong.
  10. The symbol you are editing may be made of multiple symbols, so it could be that you are just editing a different element within the symbol. Have another go, making sure the cursor is positioned exactly over the element you want. The library symbols are not locked, so you will be able to get to the geometry. To completely "explode" the symbol, so it is no longer a symbol, in a 3D view, choose Modify > Convert > Convert to Group. Then Ungroup to get to all the elements. Note however, that with a hybrid symbol, this will discard the 2D element. Similarly, if you were to run Convert to Group on a symbol in Top/Plan view, you would lose the 3D elements. I hope that helps.
  11. To which video are you referring? The Landscape Area tool has had some significant changes in Vectorworks 2021.
  12. The Wall tool (and other architectural tools) are not included in Vectorworks Fundamentals. You can find a complete list of what is included in each edition of Vectorworks, here: https://app-help.vectorworks.net/2021/eng/Commands_Tools2021.pdf
  13. Thanks for sending it in. I had a quick look - please could you also send the referenced DWG files and the original file before updated to 2021, so I can confirm how the coordinates should work? Thanks
  14. Can I suggest you send it in to tech support please? They will have a look at it in the morning and call on my help if they need it.
  15. Hi Michal This is to do with the GIS setting in the file. To resolve it, choose File > Document Settings > Georeferencing. Uncheck the first box, and your stakes will display plain old CAD coordinates, instead of the ones that match the GIS coordinate system. If you want to find out more about how GIS works in Vectorworks files, Katarina and I presented this webinar a few weeks ago: https://university.vectorworks.net/mod/scorm/player.php?a=448&currentorg=articulate_rise&scoid=896
  16. The trick with imports is to first click the Existing Tree tool Preferences dialogue and then make active all the fields that you are going to need. For example, if you want to import radius values from tree centre to N, E, S and W, click Irregular Canopy Size and then click OK. Then place one tree on the drawing area. This creates the necessary fields to receive the data. You can delete the tree after this, and go ahead with this import. To make changes to the appearance, select an Existing Tree and click the 2D Properties. Choose the new display properties, and then on the left of the dialogue, choose Apply Properties to All objects on all layers. Check Also apply as the document defaults, so that any new trees will also adopt the properties.
  17. Hi @Michal Zarzecki I have had a good look at the file. It's a mystery. In your file, I can see the problem. If I add a standard plant from the Vectorworks library into your file, it exhibits the same problem. If I copy that standard plant into a blank file, it takes the problem with it. HOWEVER, if I create a blank file, and then start with a fresh copy of the same standard plant from the library, it works as it should. So... I have not solved the problem, but I am on my way to narrowing it down. I will keep looking at it in between other meetings. But in the meantime, I just wanted to give you an update so that you know you are not forgotten!
  18. You are correct in your assumption. We think it should work from the layer plane elevation too. The bug is filed and we'll get it resolved as soon as we can. Meanwhile, the creation of a site model, even if it's completely flat will provide a workaround to the issue. You can find our events here: https://www.vectorworks.net/events Agreed, Hardscape fill rotation is different to how fills are managed for other objects, and it's something we have raised as a potential change for the future. We'll update the report on the style name issue and make sure they have all the information.
  19. The component issue is reported. If there is a site model present, the components work as expected and align themselves to the surface of the site model, using the datum preferences you express on the Components dialogue. I looked into the Eyedropper issue. It seems that because the Landscape Area is now a true Object Style, this is no longer the best method of transferring the information from other objects. I will be running a webinar on this topic next Friday and we'll be taking a close look at the tool there. I do hope you can join us.
  20. Hi Michal We are so glad you like the Landscape Area. I will try to answer your questions: 1. The Eyedropper. You need to choose Plugin Parameters to be able to take the settings from one plugin object to another. 2. Hardscape mapping. You don't use the Attribute Mapping tool for this. Just use the Selection tool and then use the blue handle to select and move the origin of the pattern. You can change the angle using the Joint Pattern Angle field on the Object Info palette to rotate the pattern. 3. The Datum issue. I am testing this in a blank file and have been able to recreate this. I will report. It was definitely working during testing earlier in the summer, so it looks like something might be broken, but I will check with my colleagues in the engineering team. 4. The Plant tool. There have been no changes to functionality of the Plant tool in this release, so I suspect the problem with the polyline is local to the file, but we'd love to take a look, if you wouldn't mind posting the file. 5. The plant naming... we do know about this and it is reported. But it will only duplicate if the Latin Name was already in that central field. If you leave the middle field blank, and just choose Latin Name as the prefix, it will use whatever is in the Latin Name field as the Style name. Hope that helps.
  21. And Plants-Component-Canopy if you are using tree symbols. 🙂
  22. I can't download your file Daisy - it requires permission. Could you add it as an attachment to this post? I would like to see the source data in DWG format - not just your Vectorworks file. Thanks.
  23. A Stake will only report elevations of the Site Model in Top/Plan view. If you don't have a site model, you can still use the Stake. Just go to a 3D view and click on the corner of the hardscape that interests you, then return to TOp/Plan. The stake will show the elevation.
  24. It may be a problem with the user folder. I will ask the UK tech support team to email over instructions on how to reset it.
  25. Have you tried restarting Vectorworks?

 

7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114

 

© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

×
×
  • Create New...