Jump to content

Ross Harris

Member
  • Posts

    468
  • Joined

  • Last visited

Posts posted by Ross Harris

  1. @Nikolay Zhelyazkov - I'm not sure a vwx would be much help as most of how it would work would be behind the scenes.

    How I would envisage the system to work would need the title block manager to have a revision manager that works holistically with a revamped cloud tool, data tag, title block and sheet list as so:

    • Manager: You set the revision up first (lets call this Revision 'A') before you cloud the changes.
    • Manager: This would need the ability to 'close off' a revision so that the next revision becomes active i.e. rev 'B' and so on..
    • Cloud Tool: The cloud tool would need to capture the active revision for tagging purposes and placing the correct revision in the title block. When a revision is closed off (lets say 'A') new clouds would be created with revision 'B' data. Clouds would also need to update the title block if placed in the annotation/sheet layer.
    • Data Tag: Scrap the revision tag tool and incorporate this into the data tag - there is tonnes of potential for the new data tag to be a one stop shop for many duties - this would be perfect and reduce the number of tools. With the data tag pulling the revision numbers from the cloud in the design layer/annotation/sheet layer these should be able to be added when the cloud is drawn or added later (Cloud tool/OIP pref?) and should be fully drag able with a leader line attached to the cloud for optimum positioning.
    • Title Blocks: Title blocks reflect the current revision of the sheet pulled from the highest revision cloud present
    • Sheet list: Should include the sheet, title, current revision and date at a minimum, but should be able to list the past revisions that have occurred on each sheet and the corresponding dates. Other folks might have more in depth requirements here...

    Typical workflow:

    • Open title block manager, go to the revision tab create first revision (A)
    • Cloud changes - automatically adds tags, updates title blocks and sheet lists as you cloud.
    • Close revision of in manager, revision B loaded as active and ready for clouds...

    At present its:

    • Cloud changes
    • Tag each cloud with revision tag tool
    • Update title block manager for each sheet
    • Make sure the sheet list recalcs and shows the revision.
    • So much room for error and labour intensive...

     

    • Like 4
  2. On 5/10/2016 at 9:47 AM, Tom Klaber said:

    Rather it would be great if the wall components could have a frame settings that tell VW if that component should be framed - and what to frame it with (metal stud, wood stud, hat channel, or generic to match thickness of component

    On the back of the awesome Autoturn partnership - if interoperability with something like Framecad would if at all possible would be a way to not have to spend resource time on the inbuilt framer tool for light steel framing.

    • Like 1
  3. On 12/4/2018 at 4:04 AM, TDimov said:

     

    We don't have multiple leaders and don't tag multiple objects because their data can be different

    What if the additional leaders were ‘dumb’? If the designer knows the other objects they would like to be identified are the same as the primary object tagged then there should be no need for these additional leaders to pick up data... or be slightly smart and alert the user that the object the leader could snap to isn’t the same object a Athen primary object tagged.

    Would be a welcome functional addition.

    • Like 3
  4. Bricscad V19 looks pretty awesome... but they all do in promo vids! I've just spent an entire evening and day trying to get VW to render elevations.. and its not even a big project. The lost time with 2018 and now 19 on random things is frustrating. Now that v19 has site modelling, it might be work another look - I cerrtainly don't want to have to learn another package like I did moving from Revit to VW... the thought is depressing... but so are the tools that need way to many clicks to use and the hanging and bugs..

    I thought the conference keynote where they said the focus was on quality was a kick in the teeth with this release.. I'd just like the essential stuff to work but I get a image editor I'll never use.

  5. Yep, just about every day I think to myself how truly lucky we are to have software that does amazing things - no matter how big the small issues become. When you have clients start crying when they see visualizations of their dream project, its all worth it - thanks Vectorworks and thanks Jim - as the face of the company we see the most in these forums your effort is outstanding and makes it totally worth the price of entry no matter how much I get teased by my colleagues I must be the only person left in NZ that uses VW 🙂 

    • Like 2
  6. Whoa - back up the bus a minute! I'm not seeing any attacks on your practice or how you work. rgcn's post is a 'nothing ventured nothing gained' scenario - if you don't ask you'll never know - I think we all understand we can't email everybody, but sometimes a friendly email to a supplier you use the most might yield a positive response and go a small way to making life easier... if not then nothing changes.

    As a former revit user I can attest to manufacturers families being badly made and shonky - I've had to fix a number of them - and when I've emailed the company the fixed file, I heard  nothing but crickets - and the shonky file doesn't get updated. Not all things are created equal in any platform... I worked at a practice where the architect was using slabs to make garage doors....

    Unfortunately, Autodesk are only adding IFC compatibility because they have to ... they certainly don't look like they want to embrace it. 

    Here in NZ, there is virtually nothing for VW outside the included library... I have to make it all myself, so I totally get your frustration

    • Like 1
  7. I'm doing feasibility studies for a regular client and part of it includes doing a a glass box type height in relation to boundary planes. I show a few OpenGL perspective views on the plans to show the lack of of the extent of infringement, but with an image underneath the site model, the height planes disappear depending on where the view is set - without an image it works as expected.

    When I first started doing these it worked as expected, but possibly sing a 2018 service pack and in 2019 it does it all the time - regardless or ortho or perspective views. Restarts don't help.

    Is this s a bug or view setting possibly? The rear view shows how it should look and the front shot shows some of the planes missing.

     

     

    75 Riverpark option 2 perspective 1.png

    75 Riverpark option 2 perspective 4.png

  8. As attached - I've imported an image, resized it to fit my panel on the sheet layer, copy the panel rectangle, crop image and paste in the rectangle. When exiting crop image the handles are are away from the image -to get it to snap back together, you have to resize it with one of the phantom handles and then ctrl-z it to get it back to the size you wanted.

    More annoying than anything else... but 😣

    crop weirdness.png

  9. 5 hours ago, zoomer said:

    Looks like Mac Rumors readers aren't very enthusiastic about the Macbook Air

    and iPad prices either.

     

    Gouged is a term I’d use for NZ prices 😬... glad I was sitting down when I read them...

    The 12.9 iPad Pro is ridiculous now.

  10. 8 hours ago, Kevin Allen said:

    The Callout tool could use some love,

    Heck yes it could - formatting for one (bullet points pls!) and having to different callout tools - one for text entry and one for database text. Its a pain in the butt to go between the two functions at present.

    I'm assuming that if the database is a single file accessed by all the project files, opening an old project and needing to modify database callout notes could create some issues - I'm not wanting to test it so I copy the database from my library to the project folder just so any new tweaks are incorporated.

    I have a reasonably standard set of notes in the database - I found that I ended up with 20 different roof entries due to differing projects having variations on roof design.. so I culled the notes to a general wording to suit most stuff I do and then alter them to be job specific when I do the first section and elevations.

    Same with my standard note symbols - they have variations in them so I delete the paragraphs not applicable (how about a rich text toolbar in the text box when selected?).

    My usual work flow is to start on the first section  - I set up my database keynotes on that page (I hate having all these notes on a single page separate to the drawing) and I usually cover all the notes I need and the wording changes required. I then copy the callouts  and keynote to the next sheet, select all and assign the callouts to the keynote on that page and move the callouts to the right places and add new ones to the database for details not on the other section(s) - super easy, quick and looks organised. Then I keynote the elevations, etc from there.

    I do put my standard notes on the 2nd and 3rd pages because its more product specification and code compliance jargon/cited standards, etc. As an ex builder I found it frustrating to read a section then have to leaf back to another page to find out what the keynote abbreviation meant... some jobs though, its the only way, but works for the stuff I do.

     

    Hth 🙂 

  11. All my standard notes are page based symbols in my library file purely because there is no way to format text how I want it with indents,tab stops,etc or  let’s with legends. I only use the database for keynotes - although I found that quickly blew out and became unwieldy with to many variations, so I have a set of general things in it and copy the database to the project folder and tweak them to be job specific from there. I find you on;y need to alter them once as well as adding some new ones and doesn’t add that much extra time - certainly quicker then typing them all out from scratch and copy pasting to other sheets.

  12. A quick scan of the ol’ google and it would appear archicad 19 ain’t getting a patch either - the last one being June 20, 2017.

    You can’t expect a small company (compared to say, Autodesk) with in a small highly competitive industry to dedicate resources to old software while trying to keep on top of bugs and developing software to keep users happy and stay competitive - especially on macOS where Apple have been pretty cutthrought in drawing lines in the sand to keep old software by other vendors going. OS development is beyond everyone’s control and companies need to make hard decisions, otherwise they go bust and there won’t be any more software...

    • Like 1
    • Dislike 1
×
×
  • Create New...