Jump to content

Search the Community

Showing results for tags 'override'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Announcements
    • Announcements
    • News You Need
    • Job Board
  • Feedback
    • Roadmap
    • Wishlist - Feature and Content Requests
    • Known Issues
    • Wishes Granted / Issues Resolved
    • Forum Feedback
  • General
    • Troubleshooting
    • General Discussion
    • Architecture
    • Site Design
    • Entertainment
    • Vision and Previsualization
    • Braceworks
    • ConnectCAD
    • Energos
    • Rendering
    • Workflows
    • Buying and Selling Vectorworks Licenses
    • Hardware
  • Customization
    • AI Visualizer
    • Marionette
    • Vectorscript
    • Python Scripting
    • SDK
    • 3rd Party Services, Products and Events
    • Data Tags
  • Solids Modeling and 3D Printing
    • Subdivision
    • Solids Modeling
    • 3D Printing
  • Vectorworks in Action
  • Archive
    • Resource Sharing
    • Machine Design

Calendars

  • In-Person Training - US
  • In-Person Training - UK
  • Coffee Breaks
  • Essentials Seminars
  • Webinars
  • Community Groups

Categories

  • Knowledgebase
    • Tech Bulletins
    • Troubleshooting
    • Workflows
    • How To
    • FAQs

Categories

  • Marionette - Objects
  • Marionette - Networks
  • Marionette - Nodes
  • Marionette - Menu Commands

Product Groups

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Occupation


Homepage


Hobbies


Location


Skype

Found 7 results

  1. Hi, Having spent an hour or so on the phone with one of your very helpful support team I thought it prudent to add this feature request to save time and effort for others in the future. I have imported several DWGs into separate reference files and used reference viewports to view/snap to them in my main working file. However I want to grey out these backgrounds in the sheet layers so that my content (not the architect's) is clearly visible against their background. By using viewport class overrides this should be possible (setting the line and fill colours to grey). I was advised today that this only works if ALL the reference file objects have their attributes set by class. The DWG import doesn't have an option to do this. Setting all objects to by class manually after the import doesn't always work well since the AutoCAD layer definitions (which are converted directly to classes - which is the right thing to do) may not have been used by every object in the drawing (colour by layer/fill by layer etc) but instead set manually. Is there any clever way around this problem (perhaps creating more classes where manual overrides have been used). Creating and using classes based on an objects current line type/colour/fill type/colour etc to create a class automatically and apply the same class to objects with identical attributes and then setting all attributes by class? (I envisage hundreds of 'sub-classes' being created) The other problem arises when dealing with hatches. AutoCAD, unless I am mistaken, allows you to use hatches where the hatch line colour is determined by the layer, VW has individual hatches one per colour if needed .... adding to my problems. I went through and changed all the pen colours and set them to grey (but I don't think that a good idea). Love to hear your thoughts. R
  2. Hi, Override is a crucial part of our workflow in our office and we cannot make it work with curtain walls. See attached photo. With only one class in the model (Black pen white fill) it shows correctly in the Design layer on the right but when we override it to render it with orange pen it only works with standard walls and polygons, but not with curtainwalls.
  3. This one's be doing my head in for years and I haven't got round to troubleshooting it or submitting a bug because it's usually a last minute thing and historically I've just ended up just not presenting drawings how I want to present them. What I find is that the attributes of wrapped wall components ("External Wall Detail" and "Internal Wall Detail" in the door and window tools) cannot be controlled by Class overrides. Worse still you can't get around this by just changing the attributes of the original wall. This is because wrapped components take on the attributes of the wall *at the time* of being inserted into the wall and that's that. It's remains like that no matter what you change the wall attributes to. To change the attributes of the wrapped components you need to update the attributes of the wall and then remove and reinsert the windows/doors to take on the new attributes. Test file attached. If you've found any other way around this I would love to know it. Even if it's some way to reset all the windows at once without having to remove and reinsert them. test-file.vwx
  4. Hello, Could someone direct me in which file I can rename default naming for stories/levels structure? Will new names work with symbols/walls/slabs/roof that are bound to stories? That is crucial part. Thanks.
  5. I cannot do a viewport override on landscape areas, to have them show up with color in one viewport and grayscale in all others?
  6. I just ran into a situation where after some updating I wanted to publish just one sheet out of a set of sheets for review purposes instead of publishing the whole set. It would be nice if there would be an option to publish one (or more) selected sheet(s) from within the navigation palette through right-click on selected sheet(s) and select publish. This could then bring up the same publish dialog as usual but then only as a temporary "override" without having to mess with the existing set of sheets by removing not-to-be-published sheets and having to add them again later (yes saving the publish set could be an option if it were not for the constant renaming of sheets that I often face, which renders the feature less useful for me)
  7. Apologies in advance as this is quite long winded.. I've noticed some weird behaviour when trying to alter the way classes appear in certain viewports, through the viewport class properties panel. Essentially my understanding is that if I have class 'test 1' set to display by class (all aspects, i.e. fill and lines), then I can override the appearance of geometry on this class from say 'green with red outline' to 'yellow with blue outline'. I could also choose to display these items with a hatch instead of a solid fill, etc. However, if the class is NOT set to display by class, then its appearance cannot be overridden in a viewport. It would be good if this could be changed, so that ANY geometry could accept an override via the viewports own properties. This isn't my main query though. Now bare with me.. If I take some geometry on class 'test 1' and give it a solid colour (not fill by class), THEN set it to hatch by class, I should be able to override the fill in the viewport properties panel. This does work - partially - but the item retains the solid colour it was given before it was changed to a hatch. Essentially this means the item has hidden information contained within it, namely a fill colour, which effects how it behaves even if it is set to display a fill of say, hatch by class. I guess my query is, is this a bug or is this working as intended? It can be quite irritating, as in order to tell if each item has a fill colour attached (i.e. not fill colour by class), you have to look through each item individually (from hatch, tile, etc.). As a followup an add to wishlist, although perhaps someone can suggest me a more concise way of saying this for the wishlist item.. Thanks!
×
×
  • Create New...