Jump to content

Search the Community

Showing results for tags 'annotations'.

  • 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 10 results

  1. Hoping someone can help with this and we're not missing something obvious. When using coordinated section markers on a plan viewport (1:50) we also show these on the section sheet layer adjacent to the associated section viewport in a contextual plan viewport at a smaller scale (e.g. 1:200) - to allow those reading the drawing to easily identify where a section is taken if reading the section drawing in isolation. Our issue is that the scale of the section markers on the 1:200 scale context viewport appears to be a universal setting across all instances of the marker that are associated with that particular section viewport, meaning they show as either impractically large on the context plan (as shown below) or too small on the main plan if scaled to suit the context plan. Trying to scale markers/symbols etc. in the Advanced Properties for the viewport doesn't appear to affect them and if we change the scale factor for the marker in the annotation layer of one viewport it affects the markers in all other viewports. Is there a way to individually scale these markers for legibility? We are currently working off VW 2022 SP1.1 - While we are aware that SP2.1 is the latest version, there is a known issue with wall hole components of symbols attached to walls that is yet to be fixed.
  2. Hello, Am I missing something obvious... when trying to data tag objects (with record format attached) on annotation layer of viewport with 3D view I see highlighted eligible objects absolutely off rendered ones. You can see in background all three posts and other parts of structure scaled down and forming some kind of different view... My viewport use hidden line renderer and is up to date. Any clue?
  3. Hey all, I have Vectorworks 2020, when I export DWG & re-import I've noticed my dimensions & drawing number info are outside the viewport and are on the sheets, as groups. Is there a way to solve this issue? Thank you Olivia
  4. Is there a way to place different types of annotations on their own class/layer/visibility within the sheet viewport? ie. wall tags on a layer, window tags on a layer, door tags on a layer, dimensions on a layer, notes on a layer, room labels on a layer...etc I'm about to go back to annotating everything on the design layer within different classes in order to keep better track of each type. It just gets too crowded to catch mistakes/omissions/changes once you have a full set of working drawings going. I've got a client that keeps changing their mind and I know I must be missing some changes in the annotations. I can't believe I have to ask this. We were arguing about using the viewport annotations versus annotating right on the design layer when I worked in an office back in 2005! Please tell me I've just missed a setting! Thanks!
  5. Is it a known issue that hidden line sketch mode (I'm using Section viewports in this case), produces seriously unstable results? I've run into a few different ways it fails to draw the expected result: The most common issue is that it displays everything in the view, but sketch mode does not appear to be activated. In some cases, the line work initially displays in sketch mode, but then after drawing annotation in the viewport, sketch gets deactivated. To be clear, sketch is still checked off as the desired render option, but the viewport behaves as if it's been turned off. Other times, all of the lines "beyond cut plane" simply don't display at all. Silver lining here is that for whatever reason, this seems to reactivate sketch mode for the cut plane elements and the annotation. There's also cases where the model line work maintains sketch display, but the annotative layer displays without sketch. I've also gotten the reverse situation, where only the annotation was displaying in sketch! It's really all over the map. There does seem to be one way to control this situation (at least it's worked so far). I discovered that by setting the line style of objects beyond cut plane to "use original" in the advanced properties, I can stabilize the sketch render setting, and both model and annotation maintain the correct display. When this is overwritten with a single class, all bets are off. Unfortunately, using the original line style of each modeling object requires a lot more work than being able to quickly set all lines to the same weight. So this is an unfortunate work around to have to accept. Thanks, Matt
  6. After a recent career move, I am back at working on VW2015 (MAC) after being on VW2018 previously. I am experiencing what I can only describe as a serious bug in viewport annotations for the first time. Text, linework, dimensions… annotated jump and shift position within the viewport, it can happen as easy as returning to the file the next day or moving the viewports around. The shifting is not always at unison; elements can go ‘all over the place’. This has caused tremendous strain to my performance to the level of a project successful completion being compromised. I have a hunch it could be related to rotated ‘view plan’ in design layers as well as copied annotations from one viewport to another retaining some sort of fixated origin point. But there seems not to be a single cause of the problem. I contacted our local representative but basically was told “bad luck” for using such an “old version” of the software. I have expressed my desire to upgrade within the company but I am afraid they will wait for VW2020 to do so. Any help / advice in solving this issue will be appreciated…
  7. I may have heard from a little birdie that a broad overhaul of labeling capabilities/tools may be in the works in coming versions. As I have become recently aware, the solution may already be hidden in the irrigation tool suite and it might not need much tweaking to become the full scale labeling tool we need. The Tag/Label Tool within the irrigation tool suite not only has the ability to label irrigation objects with inherent data in a variety of customizable label styles; thanks to @Bryan G. I just learned that the tool can actually represent ANY data attached to objects in plug-in parameters or custom record fields. This is HUGE. In order for this tool to become the tool we need however, there are still a couple of tweaks that would inform an ideal workflow. The Tag/Label, when placed on an object, needs to lock relative to that object. This means that if the tagged object moves, the tag/label moves relative to it. Note that not all labels need to point directly to the object, but in the general direction and this functionality needs to still exist, but in this case, if the tagged object moves, so too should the tag/label move. Ability to save styles and remember most current - When tagging/labeling different objects the style or data labelled might change. There needs to be a way to store these different styles and the ability to choose from them, but also remember the last one used so that it doesn't revert to a default setting each time a label is placed. Act Like Keynotes Placed as Keynote Callouts - Auto-numbering and organization are the primary benefits of using keynote callouts currently and we use them almost excessively considering the difficulties with managing the callout database. This tool has the potential to offer the benefits of that tool without the fuss. If the tag/label chosen has the ability to be represented by a Keynote Callout that puts the label in a Keynote Legend and auto-numbers/letters similar to callouts currently, we could then build extensive keynote legends/worksheets based on objects' inherent data that auto-numbers. Place in Annotations - I imagine that this is perhaps the hardest ask, but it is potentially the most influential...we need the ability to somehow use these Tags/Labels in the Viewport Annotations space while still linking to the objects present in the design layer. It is far easier to organize labels for legibility when placed in the annotations and it removes design layer clutter. Additionally, when placing callouts in Viewport Annotations you can take advantage of the viewports margins and white space to aid in legibility and organization. This isn't something you can do when placing on design layers. Finally rotation...many viewports are rotated and in order to represent labels on these viewports when placing in design layers, you must rotate them to read horizontally...often in very extreme angles which just adds to the clutter, confusion, and chance for error. All in all, this tool is very close to what we need and I am excited to find ways of working it into our workflow. My hope is that VW takes this into consideration when working on any new Tag/Label tool.
  8. Is there a way to control the appearance of auto generated Annotations on a per file base in a centralized way, without the need to go into Annotation Layer for each Viewport ? For example the Viewport Titles appear in the bottom middle only. When I move them and change Crop Geometry they don't follow. Is there a way to define them globally with XY distances from a fixed origin like bottom left or bottom right ? Or a centralized file setting to define a global Font to a document ? I created Text Styles but every time when I create new Viewports, things start "undefined" and for later edits I can only change 1 Viewports Annotations at one time (?) Did I miss something or doing it wrong ? Are there already kind of "Section Line Styles" or global Headline, Sub Headline, Standard, ... Text setting like you would do for a HTML web page by CSS ?
  9. It would be nice to have some indication that there are objects in the annotations level of a viewport. Maybe this is shown as an icon that can be switched on an off directly on the viewport, or some notice in OIP. Or maybe a dialogue box that alerts you to the objects after you try to delete the viewport if you forget.
  10. Hi I have a structural model, and I've done section viewports in a plan view, to be rendered as hidden line. I have 3d conversion set to low for speed, and they have a depth set (not infinate) I render the section, and it looks lovely... when I go to annotate it, on entering the viewport it displays as hidden line, with tonnes of unnecesary extra lines making redraw very slow and difficult to annotate. When you exit, you need to update the viewprt and then it displays as expected. Previous versions of VW always allowed you to annotate the hidden line render, and not go to wireframe.... anyone else with this issue? PC, Win 8.1, Nvidia graphics Cheers
×
×
  • Create New...