Ruby S

Thanks for reporting @rDesign. We've had some on and off again issues with this. I will look into this and report back here.

Check out the card on the roadmap! https://www.vectorworks.net/en-US/public-roadmap?url=worksheet-slicing

Ah. Revizto has been requested a few times. I'm happy that you've asked them directly. We're hoping that the more they hear about Mac compatibility, it increasing the likelihood that they may consider adding it to their roadmap. Thank you Steven.

@shorter - many time these limitations are due to the compatibility of the partner product and not a decision from the Vectorworks team. If you have specific, Mac compatible plugins or integrations that you'd like to see, we'd love to hear from you. We're expanding our partner network on a regular basis and want to include those that will benefit our customers most. Thanks in advance.

In case you may have missed this post in the Announcements, we are looking for volunteers to help us test a new Door and Window Assemblies tool. You can see the original post here:

I'll ask the team to look into this as soon as possible. Thank you for bringing this to my attention!

Hi @zoomer - we do have a "stair re-engineering" card on the public roadmap as well. https://www.vectorworks.net/en-US/public-roadmap?url=redshift-rendering-mode?url=stair-reengineering-2025 This under the hood update is required for all the things we would like the stairs to do.

Yes, this change will be made, but likely will not get implemented until end of Q1 next year. If our timeline moves up, I'll be sure to let you know. In the mean time, please do, use the "nice to have" as the lowest vote to leave your comment.

Yes, we can absolutely make this change. We are looking to make some changes to this page in the near future and we can include this update. Can you give an example of when you wanted to make a comment, but didn't want to vote? I'm assuming you don't want to vote because the card is not a priority for you?

Hi @cberg Thanks for your post and your question regarding the public roadmap. First, I just wanted to point out that you can filter the roadmap cards by industry. Core technology covers areas of functionality that are not industry-specific, like user interface. Hopefully, this will help you navigate and view the information that you’re looking for or that you feel is relevant to you. Before I address the voting system question, I think a little background on the public roadmap will help. The public roadmap is a record of both our short-term and long-term roadmap (reflected by the status of the cards – “scheduled,” “in development,” etc.). The roadmap also reflects all of our industries and all of our markets. A card is added to the public roadmap only after it has been given due diligence and considered for things like usefulness, relevance, and long-term impact on our customers and the development goals of Vectorworks. We make these considerations and decisions based on customer input (through the form of wishes, feedback, etc. – not specifically the voting system), industry trends, and our own internal goals of technology modernization and continuous development. So, the roadmap is a place for you to see what we’re working on and what we hope to execute in the short and long term. Therefore, the feedback we seek helps us determine priority, not whether a specific feature or tool should be developed and ultimately implemented or not. Which leads me to the question about the voting system. Perhaps understanding how we use the voting system will give some insight into the language we have chosen for this. This can essentially be thought of as a priority system of 0-3, with 0 being the lowest priority and 3 being the highest. A zero is assigned when there is no vote. If we have a card on the public roadmap that has gotten 0 votes, then it’s automatically placed at the bottom of our priority list. (I can assure you right now, that there is no card on our roadmap that has not received a vote and/or comment). Lastly, we request names and emails, as our development team will often contact those who leave feedback, and we need learn more or get clarification on their feedback. Your feedback about more communication about what we are prioritizing is heard, and we will work with our teams here to make sure we are doing more to talk about this. Thanks. I hope this is helpful.

Hi Steve. Check out this card on the public roadmap. https://www.vectorworks.net/en-US/public-roadmap?url=object-visibility

Hello all. We have created a card on our Public Roadmap. We would love any additional input to help us with our research and to plan a useful Community Resource Share. Please submit any feedback via the Roadmap or by using the wishlist section of the forum. Thank you in advance for your input and wishes.

Hi @efa. You can vote "down" or "up" anything on our roadmap here: https://www.vectorworks.net/en-US/public-roadmap Simply click on the card and label it as "nice to have" which means a low priority. the "startup screen" which is labeled the "welcome screen" can be accessed at this card: https://www.vectorworks.net/en-US/public-roadmap?url=welcome-screen Thanks for your feedback!

Hi Christian! As Matt mentioned, the features that I highlighted are not necessarily implemented for 2021. This was to give everyone a better idea of some short term projects we'll be be undertaking for future releases. Thanks! Ruby

I think this is an OpenGL redraw issue. What works for me is selecting the object and then toggling any option in the render tab of the OIP. This forces that redraw. This seems to keep the visibility in the file. Even after I open and close the file or start a new session of Vectorworks.