Jump to content

rDesign

Member
  • Posts

    2,710
  • Joined

  • Last visited

Everything posted by rDesign

  1. @DomC - thanks for uploading the new version. Out of curiosity, I tried changing the control geometry to a NURBS surface to see if it would work on a 3d surface, but it didn't seem to like it. Do you know if this Marionette object could be made to work on a non-flat or sloping 3d surface? Thanks.
  2. Since installing Vw2016, the Mac OS X Finder Icon now shows all Vectorworks files as Vw2016 version with the 'red icon' - regardless of what version they were saved in. The Finder 'Get Info' on a Vw2015 file does not tell me that it is a Vw2015 file but only says 'Open with Vectorworks 2016 (default)'. There is no way to know that it is in fact a Vw2015 file. I don't know whether it's an Apple or Vectorworks issue, but it makes it a not-much-fun guessing game about which Vw version a file was created in.
  3. Click the Preferences button for the Eyedropper tool, there is a checkbox for 'Pickup Sets Default'. Checking this box changes the default Attributes palette settings to match those of the source object; objects created from then on use the attributes of the source object.
  4. Take a look at this thread: Invisible Attributes & Snapping Palettes HTH.
  5. @barkest: Thank you so much for making & sharing that subdiv tutorial! It was very informative. Staring at a blank screen while contemplating using these new Vw2016 tools can be somewhat intimidating. Now at least we know how to start. Thanks again. P.S. You don't happen to have any tutorials on getting started in Marionette, would you?
  6. You could either put it on its own class as a Clerestory window so you could turn off that class, or you could put some dashed lines in the 2d part of the window symbol to indicate the window above on the floor plans.
  7. It's probably just that the geometry in your symbol is not in the correct orientation. Go into the Symbol and rotate both the 2D and 3D by 90 degrees around the Origin (clockwise from what I can guess by your image).
  8. Are you trying to use 'Top' view or 'Top / Plan' view? Because they are not the same: 'Top' view is a 3D view, while 'Top / Plan' is a 2D view. Plant symbols are 2D / 3D Hybrid symbols where the 3D image props part of the symbol is visible in 'Top' while the 2D symbol graphics part is visible in 'Top / Plan'. Assuming you're using either Landmark or Architect, you can project 2d plant shadows in a Top / Plan view with File > Document Settings > Document Preferences (quote from the Vw2016 help file): (Since we don't know which version & package of Vectorworks you're using, it will make troubleshooting easier if you update your signature with info similar to my signature).
  9. I completely agree with Art V on the question of subscription model licenses. Adobe suckered me as well with the tease of buying CS6 now so you can get CS7 later. I'll keep using CS6 until hardware or software prevents it from working. Then I'll be looking for alternative software to replace the Creative Suite, as I am not going back to Adobe. Autodesk is following Adobe's lead by also dropping perpetual licenses and going subscription-only, and I can tell you none of the Autodesk users that I know are happy about it. If Vectorworks ever follows this path I will be faced with a very difficult decision.
  10. Benson is exactly right: this is how the new palette docking feature works on Mac OS X. Vw2016 Help :: Docking Palettes
  11. It seems like it could work just the same way as current site modifier error notifications, where you get the 'caution' icons upon updating the site model.
  12. Yeah - I agree with JimW that having the site boundary automatically generated would not be a good thing. You'd probably end up with a potato- or 19-pointed star-shaped polygon. What about tagging site modifiers that lie outside the boundary with the yellow 'caution' symbol that we currently get with other site modifier errors?
  13. +1 In Rhino it's called the 'Gumball' widget. If something similar were to be implemented in Vw, which I think would be great, there should be a button to turn it On or Off. As it is, I'm already always struggling with Automatic Working Plane mode not being very 'automatic'.
  14. @FunkyBass - thanks for the instructions, I'll give it a shot. So can I assume that if there are any other Python packages that we want to install and use in Marionette, one would follow similar steps by manually copying them into the Vectorworks.app package? Thanks again for your help!
  15. Here's a step-by-step from Jonathan Pickup's always-helpful blog Archoncad: Archoncad :: How Can I Build a Window in Vectorworks With A Sloping Bottom?
  16. I don't have an answer to your script question, but I have also noticed in both Vw2015 & 2016 that the screen does not always refresh after changing something; It's like the change I made wasn't big enough to trigger a refresh. There's a chance your script might be working correctly and Vectorworks is just not redrawing as it should.
  17. Great - thanks for the clarification Mark. It was installing pip3.3 where I ran into difficulty with the VW package-installed Python version. Does the Python version have to be 3.3.2 for Vectorworks? I noticed on the Python 3.3.2 release page that a newer security-fix release 3.3.6 is available. (They recommended using 3.3.6).
  18. Mark - thanks for the reply. That would be great - I was just attempting to follow the steps in the .txt file you posted regarding installing Scipy and Numpy on Mac OS X. Perhaps I misread your post and thought you would need to install these two Python modules if you wanted to work with the Voronoi Marionette example. It may have been unnecessary research, but I found what seems to be a good resource on initial setup for Python on Mac OS X: Hackercodex.com :: Configuring Mac OS X on Yosemite & Mavericks
  19. Gotcha, sounds good. Thanks JimW for the reply.
  20. @MBrown: Any progress on this? Is there anybody at Vectorworks, Inc. with an iOS 9 device having trouble viewing the Vw2016 online help file in Safari landscape mode? Maybe it's just me and my two iOS 9 devices. I submitted a bug report for this issue on my VSS account almost a week ago and haven't received any response. Thanks in advance.
  21. +1 Additionally, I have often found with the Offset distance text box (on the tool bar) will cut off the dimension. This was also the case in Vw2015. If you input an offset distance of say, 155'-10 1/2", the Offset distance text box will only show 10 1/2". If you click in the box you can scroll or cursor up to see the 155', but you can't see it all in one line. This for me is a big pain: Make the the text boxes large enough to see the number.
  22. @simbob: I do your last thought and set up Sheet Layers with rendered viewports as I find it works pretty quickly and consistently. When I present design options, I create several 8.5"x11" or 11"x17" sheet layers and put a rendered SLVP of the RW camera view on each sheet, one to a page. Then I can add title block, date, title, etc. SK101 - Option A - View 1 SK102 - Option A - View 2 SK103 - Option A - View 3 ... You can then either export all of those SL one at a time as individual PDFs or batch them with the Publish command. If PDFs are in color and I don't want to show colors yet, I have an Automator script (on Mac OSX) that converts them to greyscale via drag-and-drop. When I need to present design option B, C, D & E it is just as easy as duplicating all of those SL, renaming & renumbering them, and changing the class and layer visibility for the various options. Since duplicating the SL also duplicates the SLVP, I know that the different options will have the same exact camera view. I find it is a pretty quick and easy workflow. When it comes time to make Constructiion Documents, I can copy or move those SLVP to a sheet in the drawing set. I don't export images from a Design Layer because, as I understand it, it is rendering at full-resolution and will take much longer to render than if you had set up a SLVP where you can control the size and dpi of the rendering.
  23. 1) Did the Site Model have the red-and-white striped border indicating that it needed updating? Unless you were doing something incorrectly, I thought that using any site modifier object (like the stake object) will require updating the site model. 2) Stake Object: which mode was selected when you inserted the new stake object? Include as site model data Set elev to site model Use as 2D graphic only Site modifier object And if you were using the stake object as a site modifier, did you specify whether it affects the existing or proposed site model?
  24. +++++1 to all of those. Submitting on the VSS bug submission section is the worst, as you don't get any recognition of what you submitted until Tech Support replies to your request. All you get is a bug tracking number, which I guess you are expected to write down. It would also be helpful if the VSS bug section listed in tabular form all of the bugs that you have personally submitted over the years, and what is their status.
×
×
  • Create New...