Jump to content

Ross Harris

Member
  • Posts

    262
  • Joined

  • Last visited

Posts posted by Ross Harris

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

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

  3. 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
  4. 14 hours ago, Todd McCurdy said:

    Empathy, Dude. It's still a thing. An email warning should have been the minimum. Not everyone hangs out here.

    You don’t have to hang out here... it was posted on the support channel of the website months ago. I also got an email saying not to upgrade to Mojave the other week.

     

    It sucks for those who did upgrade - but lets employ some logic here. What was the current OS 2019 was developed on? 10.13. What was the current OS when 2019 was released? 10.13. So it stands to reason that there may be issues in a new OS released post VW 2019 development and release. Apple have never given a rats arse about their user base - they will always do what they think is best and develop the OS and the product as they see fit. I’m sure if they did, they wouldn’t have dropped the openGL bombshell from a stage. Did Vectorworks get an email from Apple about dropping open GL? Probabaly not....

     

    Here’s an example.. when Apple brought Emagic for Logic Audio, they promptly did a version update from 5.5 to 6 - to basically kill the windows version - their arrogant response? Buy a Mac. Then they decided they wouldn’t support the then current cross platform plugin format VST and created Audio Units - meaning every single plug in developer now had to port their software to be AU compatible to work in Logic - and that took some time beyond the version released with AU; and just for good measure - they canned support for the then current cross platform audio computer to hardware interface streaming format ASIO and developed their own one - Core Audio. So now all the hardware vendors had to make new drivers; the fallout from this making a lot of hardware redundant with no drivers as the development costs weren’t worth it and they focused on newer or upcoming products. This made a lot of people, developers and companies incredibly angry and like everything, this furore is now lost in the mists of time; but I’ve never trusted Apple since and boy, it was a top learning experience. Compare that to making a poor judgment call to upgrade to a not supported OS is a drop in the ocean, so to say this doesn’t or shouldn’t happen is very naive.

     

    Anyhoo, by the time the first developer beta was released 2019 was likely feature locked and development was focused on bug fixing (yeah....) for the final build for release, so it stands to reason when Apple announce a new OS with OpenGL deprecation it was going to be a kick in the balls for VW. Graphisoft were most probably in a better position to deal with the issue having been at the end of development and had released Archicad 22 before Mojave was announced, so could tackle it quicker. 

    I also bet there is a tonne of disclaimers in the small print of Apples’ developer agreement to access the developer betas, covering things like OS features announced, yanked or not included because of xyz reason and not being a done deal until the golden master is announced, so they don’t get sued. So VW rightly so don’t blow their engineering resource on something that could very well change at Apples whim and of course they don’t need to tell anyone.

    • Like 3
    • Dislike 3
  5. Lol fanboy... seriously, what is so amazing in Mojave that you just have to have it? I love new bells and whistles, but if it affects my income I’m not going there. If you browse my recent posts you’ll see I’m far from a fanboy. 

    A few years back I upgraded my recording hardware with a new product from a long-standing audio manufacturer and a new OS rolled around - after six months of promises and no drivers it was getting annoying, but after 12 months it was frustrating considering the DAW software was moving on (these companies are VERY small) the hardware line was promptly discontinued with no driver support - so I know how this goes. At least in this game I don’t have worry about outboard hardware obsolescence... and in the grand scheme of things wating a few months for VW to work is nothing by comparison..

    Like I said, all software works and is coded differently and I can only assume archicad is considerably different than vectorworks, so you are comparing apples with oranges, let alone the completely different development cycles of both.

    Jim has said its being worked on - so I’m not sure what more you want. I’m more concerned about the number of serious bugs highlighted after a week of 2019’s release than Mojave or Windows 10 1809 compatibility. 

    • Like 2
  6. On 9/19/2018 at 8:01 PM, Nicolas Goutte said:

    I would recommend that you would take the time to re-create the template from scratch

     

    Totally agree with this. I worked at an archicad practice before going out on my own - they had massive problems with speed and crashing and calling/emailing cadimage for help. When I was deciding which platform to invest in I sat down with cadimage during the course of the discussion, and they rolled their eyes and pointed to the ancient template they used that had been upgraded through many versions and had told them many times to redo it because archicads database had gone through so many changes.... they also had a bizarre policy of skipping a version - so as well as subjecting the template to a bigger translation to a new format, their trading slipped and they were so backward in how they used it.

    Even though that story isn’t VW, the advise i think is fairly universal - keep the template lean and do a new one every few versions, keeping symbols in dedicated library files.

  7. Can the break line tool be enhanced with an adjustable solid fill behind like the attached? The fill should have adjustable handles that can be used to make it cover extraneous line work without needing to fiddle in a dialog box.. like the detail callout tool.

    Can the line break also have a definable lineweight in its options so it can be set? I usually give a thicker weight to stand out and having to change it everytime or copy is just another step.

     

    This would be a small functional enhancement, yet big detailing time saver!

     

     

    Break line.png

    • Like 2
  8. In my version the beam is rotated 90 degrees in top plan view. For example, a 200mm x 50mm beam it is 200mm wide in top plan view and in any 3D view it’s 50mm wide - the correct orientation. Rotate the profile and it’s right in top plan but not in 3D.... was a promising feature...gave up on it very early on.

  9. That would be a better look - anyone reading this and a couple of other 2019 threads after looking at the glossy publicity would be sensing some red flags...

    Here's a good example of open community testing for a DAW (Digital Audio Workstation) ... don't let the price fool you - the platform is incredibly powerful and has many long time protools users (the defacto standard in the industry) migrating to it due to bugs and Avid's arrogance toward its user base... 

  10. With the amount of quite serious bugs that have come to light in less than a week and confirmation of longstanding broken features not fixed, is it time for a renewed call for open beta testing or an insider preview setup like MS have been doing for Windows 10? 

    • Like 3
  11. Because if you buy a new mac soon it will have Mojave preloaded... and you'll have to muck around back-dating it. But if refreshed macs come out soon as well, that might not be possible. A total pain for those hanging out from more powerful macs.

    • Like 1
  12. That's looking very cool!

    Andrea's tools are excellent - I happily pay for them and the contribution for me anyway, is hugely appreciated and can't be overstated; but why should someone have to come up with a solution for a standard feature on buildings? I'm not fussed if its not an all encompassing tool but does most of what I'd like to achieve; anything that helps is better than the status quo!

    @BillV - certainly not small, hence the quotes. It seems that these things fall into the bracket of 'there's a way to do it so its OK'. Just looking at the comments related to 2019, people (especially longtime users) are getting considerably more vocal about some of the official buzzwords for this release in terms of the tools and delivering on customer feedback... I'd prefer this gutter and downpipe tool in a roof tool that could deal with roof overhangs properly over fluff like the new image features i'll probably hardly use...

    • Like 3
×
×
  • Create New...