Jump to content

Alex Sagatov

Vectorworks, Inc Employee
  • Content Count

  • Joined

  • Last visited

Community Reputation

89 Excellent


About Alex Sagatov

  • Rank

Personal Information

  • Occupation
    Senior Onboarding Specialist
  • Hobbies
    3D Modeling, Rendering, Videogames, and Level Design
  • Location
    United States

Recent Profile Visitors

1,831 profile views
  1. @Zach Miles As long as the license you are using matches on the website and the Vectorworks launch window, you will be good to go. Vectorworks should stop showing that message the next time it successfully activates. If not before, it will have to do an activation on April 6.
  2. @Zach Miles - The educational licenses do require an extension each year. I saw a pending extension request on your account and went ahead and approved it. You should be good to continue of the next year ūüôā
  3. You are correct. Connect/Combine Tool would be another way of getting them to join properly.
  4. @Giulio Can you just confirm for me what exactly looks worse on your end? When I am comparing these PDFs, they have some differences in geometry and some line weights, but the overall quality seems to be identical?
  5. So I ran a few tests here, and it doesn't appear that I can use compose to combine a mix of lines and NURBS. I can combine any mix of 2D lines/polylines/arcs/etc and any mix of NURBS Curves. In your case, if I concert the line object to a NURBS (Modify > Convert > Convert to NURBS), compose will also work. Based on other 3D Modeling I have done in Vectorworks, I am thinking the plane is causing the issue here. Technically, the NURBS curves are not restricted to a plane while the line in 3D is set on a "3D" plane. If objects are on different planes, this can cause them to not play nice together. --- I think the issue here is that the compose command isn't providing an error in the bottom right about differing planes, but I am not 100% sure. I will submit it to Engineering for confirmation. UPDATE: Submitted bug reference number --- VB-175514
  6. @DMcD We have seen this caused in the past by specific workflows/commands that cause a break in the undo. At this time, all known causes of this have been addressed. Based on what I have seen in the past, we will need to track down exactly what you are doing when it breaks. This can be complicated. When you do the undo command and it goes back multiple steps, we need to figure out what step you did at the point it goes back to. As an example: Step 1: Draw a circle Step 2: Draw a line Step 3: Draw a rectangle Step 4: Draw a hexagon Step 5: Draw a Wall UNDO --- Takes you back to just your circle on screen. In this basic example, this means drawing the line somehow caused the issue to occur. You can probably see why tracking this down is going to be a little complicated... If you are running into this on a very regular basis (multiple times a day), the easiest thing to do would be record your screen while you are working. At that point, whenever the undo issue occurs, we can review the video and figure out what step in your process it takes you back to and see if we can replicate it. If that isn't an option, it will be a little bit more hit or miss. If you can lay out the kinds of tools/commands you are working with, I can give those kinds of tools a run on my end and see if I can replicate anything.
  7. @Petaro1 Considering this issue is only occurring on this new machine, the issue here is likely tied to the operating system. Vectorworks 2018 is not supported on MacOS Catalina: If you can direct message me a copy of the file and the PDF result you are getting, I can confirm if the file exports properly on VW2019 and Catalina.
  8. @BGD @scottmoore - Sorry, I missed this notification yesterday! This was all done directly inside of Vectorworks. If I am understanding your question properly, I did this by stacking two viewports on top of each other. I had one viewport that was only displaying the plants and one that was displaying all other geometry. I'll upload a quick video before lunch.
  9. I can still select multiple classes by using Shift+Click or Command+Click. I just checked in 2020, and it seemed to function the same way.
  10. Just to rule out anything related to it being file specific, can you try just creating two new documents... In file one, make the classes A, B, and C. In file two, make the classes 1, 2, and 3. Save Both. Try the importing of the classes again with these? On my end, I get a list of classes when doing this, and any classes I have highlighted import properly in my testing so far.
  11. @SKSThis seems to be working for me. Can you please confirm what Operating System you are on? It sounds like this isn't what you are running into, but if the files already contain the same classes, the list will be blank.
  12. From the screenshots, I notice you are on 2019. Please make sure you are on the latest service pack for 2019. There was a bug I submitted about Offset Tool causing crashes when it would remove vertex points back in 2019 SP0 that was addressed in SP1. If the issue still persists, can you provide a file with just that shape in it for testing on my end?
  13. @wrios - This issue seems to be linked to your default attributes. If you click in a blank area so that nothing is selected (Object Info Palette says "No Selection"), and then look at your attributes palette, the default opacity is set to 50%. This appears to be causing the gray out effect we are seeing initially. If you click on this opacity drop down, you can set it to be by class like the other attributes you appear to be working with (if that is what you want). Nudging the object is causing it to redraw with 100%, because the class the lighting devices are in are set to have 100% as opposed to 50%. Doing a Spotlight Menu > Refresh Instruments will cause all of the lights to appear at 100% again. To be honest, looking at this, I am confusing myself a little bit in terms of if this is working properly or not...
  14. @BGD- If someone else has a better way of handling this, I am all ears, but I would normally approach this in the following way: First, a quick explanation: The "Plant" object you currently have in there are not showing up based on how they are built. Our default plant resources use Image Props in 3D which makes them significantly faster than using direct 3D geometry. In turn, they do not work well for render modes like this. The image prop is simply an image/texture on a plane, propped up in 3D... so a render mode like this doesn't really know how to display that. --- A fully modeled 3D plant (Such as VBVisual) also likely wouldn't work too well with a render mode like this as they will likely provide solid 3D planes where the different leaf/branch textures are located. Example: Based on what you want, I feel like we would need to go at this with stacking viewports. For this workflow to work, your plants would likely need to be on their own design layer(s). Here is a quick example from a file I just threw together: First, I started with a viewport that had all of the geometry besides the plants visible and used an artistic render mode. It came out looking like this: I then duplicated that viewport, swapped the layer visibilities to just show my plant layer(s) and I used an OpenGL Render mode: With the top, OpenGL viewport that includes the plants only... I then messed with image effects to get a grayed, no colors, slightly blurred look to try to match my other sketch as closely as I could (in ~3 minutes of testing): If you want to send me over a copy of the file (direct message), I can mess with it a bit in your file specifically.


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...