Jump to content

Matt Overton

Member
  • Posts

    980
  • Joined

  • Last visited

Reputation

617 Spectacular

Personal Information

  • Occupation
    Architect (Reg NSW-AU 9462)
  • Location
    Australia

Recent Profile Visitors

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

  1. It really is a bad release. I wonder how it got out of the virtual door?
  2. You can hack this with various degree of success by using layer override colours. set the black line and fill squares to grey and most objects will respond. Not always all doesn’t change image based resources.
  3. I've seen slabs so polluted by trimming modifiers the only choice was to throw them out and start again. Does seem like the system should be rethought you can never really modify the modifiers as most edit operations make them unknown tot he slab, just delete them and reapply them.
  4. Tttleblock allow you to record both Revisions and issues. I've seen offices use One for client facing and have that list on the printed page and then use the other one showing up outside of the printed page for Internal tracking.
  5. Yes, Universal Vectorworks files would be great and it was put forward several times over the years as the reason for .vwx file change. Still as a show of progress and to improve the usability of the Libraries, it would be a good test bed. At a per-type level how many of the types have changed dramatically over the years? Lots of objects have got a revamp but at the same time, they moved from Red Symbols being stored in the library to Object Styles Types. The code to do the conversation if they are needed would exist, Sure doing the conversion each year isn't much work but it seems it is enough to mean people just don't use the system.
  6. To avoid redundancy and other management problems, Library files should not be in a specific version of the file format. They should be able to deliver the resource to the version of the app that being used regardless of what version of app saved the resource saved it. Given that most resources are fairly small objects anyway, any background data conversion that happens to get it to work would be quick. Benefits- - One True single library (per user or company-wide) - Smaller Install, smaller footprint - less management - Set and forget each version wouldn't need new locations to be set so could just read the settings from prior install.
  7. Yes surely the talent they might throw at AI could probably be more impactful targeting low hanging fruit of production killing issues.
  8. In theory, the AI could already author a vectorscript description of the Wall type you'd like to replace the wall type you had if there was enough of the function exposed in the VS documentation.
  9. My first lecture in my first year of architecture started with that very line. 30 years later it is only marginally more true today than then and fails to understand how much further it has to. So sure maybe in my lifetime I might read about it happening while in the nursing home.
  10. Or the Program ship from your local distributor with most of the common ones in your market. Then you'd only need to make a small handful of uncommon ones each year.
  11. Add the potential VisionPro is showing and you have the specs sheet for the last CAD program I'll invest in, in my life time.
  12. That shouldn't need AI just features like Materials to do the job they are said to do. 😉 Save the AI for Fun things.
  13. Storey Styles, LOL I sort of Kid, but it does seem like the way they do things like this these days. Still, a Storey Style might not be a bad single place to update in the project. We could have multiple in the same file, and we could transfer them from project to project or have a library of common project/construction types. That said, I will always upvote better Storey/Layers/Levels to better represent common building practice.
  14. With an option for stacking them all on top of each other but creating a layer for each
×
×
  • Create New...