Jump to content

B Cox

  • Content Count

  • Joined

  • Last visited

Community Reputation

27 Great

About B Cox

  • Rank

Personal Information

  • Location
    United States

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. sounds like the ODA library just cant handle common characters in file paths... I always use underscores in my file names and normally dont have problems exporting DWG..but exporting to a NAS device seems to have pushed it over the edge, probably because of the \\ in the file paths
  2. I am also having issues with this error. I tried purging what I could (I am not going to purge coincident objects etc.) but it didn't solve anything. Edit: I did solve this. The issue is it fails when writing to a network attached storage drive. it works when saving to the local drive. I have a Synology based drive.
  3. I mean, recursive references would be cool but honestly I'd settle for the ability to manually input the sheet number.
  4. Right, but you are doing this inside your design layer. Its grayed out if you do it within an annotation workspace.
  5. Hi I am working with a design group that has a specific approach to how drawing labels must be formatted. Instead of the drawing label referencing the current sheet (which always seemed like a useless function to me), they want the drawing label to reference the sheet where it is first buttoned. IE, if the plan is on sheet 1, my elevation is on sheet 2. Sheet 2's drawing labels are Detail 1/Sheet 1. You can set VW drawing label to show sheet numbers, but there is no apparently functionality to do custom sheet numbers. Does anyone have a in object work around? The only thing I've seen a few other people do is to paste the drawing label outside of the drawing viewport annotation onto the sheetlayer and explode the object, but its gonna get messy fast.
  6. @shorter The problem with your perspective is that it is as a salesperson not a normal professional user. If you cant contribute anything constructive to this discussion encouraging Nemetschek to improving subscriber experience, then stop replying. Maybe it's because you have a profit motive in selling licenses, that you feel that VW is unassailable? This is a continuously toxic problem with this forum's userbase.
  7. @shorter If you're only interested in gaslighting its better not to reply. You can read above this post of people who are having compatibility problems. And it sounds like you are describing exactly that software can only work on each annual release of OSX as described. Hence, works for one year.
  8. @Nicolas Goutte Gosh I cant think of a reason why... Maybe because there are 100 million OSX users? Are you trolling?
  9. @Jeremy Best OK BUT.... The new thing about VW in the past few years regarding compatibility is that typically VW launches its new annual version every september. Apple launches their new OS every october. The new software is NEVER compatible with the new OSX on launch. It's become the common wisdom NOT to upgrade to VW new versions until at least SP2 every year because they are not compatible with the new apple OS. This creates a situation where most users on OSX are a half year behind upgrade cycles. Because VWX file types are linked to the software version, this means offices have to migrate simultaneously. This means that Nemetschek, by not making sure VW is ready to go on day 1 of new OS releases, is creating a situation where most users are getting about half of their upgrade value by being always a half year behind the upgrade / compatibility cycle. This isn't the way a contract software should work. Adobe, hate em/love em, have this well under control. It would be nice if Nemetschek staggered their release cycles so they could work out all the kinks. It would be a major upgrade to user experience.
  10. Is it really so much to ask that Nemetschek works to make sure that this very expensive piece of software functions for more than a year? planned obsolescence much?
  11. Exactly this--everyone in my office knows not to upgrade until 6 months in. VW's timing of their releases so close to annual OSX refreshes in a guarantee that we'll likely have compatibility problems. Unfortunately these forums are only used by a handful of people so the depth of the problem is probably not well represented (like I know i'm the only person in my organization that bothers to read posts on here.) Every refresh cycle I look at the list of unrepaired bugs that i've reported in every release since 2016 and the relative cost of a Rhino license. All that 2019 introduced for us was it broke all of our organization wide title blocks. I'm not looking forward to exploring the issues of 2020.
  12. Where we are going we won't need revisions anymore. Thanks Nikolay
  13. Am I stupid? I'm also missing the Center Line Marker tool.
  14. This is a dumb question but what happened to the revision marking tool? it disappeared from my toolsets.


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