Jump to content

DMcD

Member
  • Content Count

    15
  • Joined

  • Last visited

Community Reputation

0 Neutral

About DMcD

  • Rank
    Greenhorn

Personal Information

  • Location
    Afghanistan

Recent Profile Visitors

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

  1. DMcD

    macOS Catalina (10.15) Compatibility

    Hello Shorter. All the other software works fine so why spring clean? No bombs. No lost work. No requirement to change the computer or video card. VW 2019 works fine now. VW 2020 bombs. So I have to completely clean out and reinstall my software just for VW 2020? I can almost guarantee that in 6 months, if I do nothing. VW 2020 will work ok. Maybe but then again, that's their job isn't it. I know it is not mine! But what are the mainstream Mac setups? In fact, what are the recommended setups? Is the Mac Pro on the list? I would expect it is. Is the MBP? I doubt it since most people who spend the day with CAD software need a larger monitor. Fortunately 2019 works well and 2020 doesn't appear to have enough new features that make it worthwhile changing. I just wish I didn't have to pay for being a beta tester. D
  2. DMcD

    macOS Catalina (10.15) Compatibility

    HA, First up, the 2020 install I did was a full install on a high spec 2018 MBP running the latest Mojave. I had three or four crashes a day. That's enough for me. In comparison on the same computer, 2019 is very stable and hardly ever bombs (now). 2020 did not have much in the way of speed improvement over 2019 when rotating complex 3D shapes although the compressed save files are nice. The Mac Pro is still a current computer. Yes is old but was high end and at the time of writing, the replacement is not on sale. Comparing the performance of iMacs and the MBP, I'm happy that the Mac Pro outperforms them, especially with 2 x 30" monitors running VW 2019. It's VW2020 which plays up on the same Mac Pro. We develop software and there's no doubt that Mojave was a nightmare for developers and we have been very cross with Apple over this year. However, our software runs on Catalina without any changes. That being said, have no intention of upgrading to Catalina for anything other than testing our software for end users who update by mistake. It's fine to say reformat but… if VW was the only software I used, then this would be easy. But it's not the only software on the computer and re-downloading a host of Adobe stuff, X-Code, FCP, and all the rest would take close to a week at our internet speeds. Doing a migration of an old OS back to a new install seems to be the worst solution. BR D
  3. DMcD

    macOS Catalina (10.15) Compatibility

    I'm not sure if this should be a Catalina post or a Mojave post… It's both really. I spend the weekend with the new VW 2020 working in Mojave on a 12 month old touchbar 15" MacBook Pro. The tiny screen isn't ideal so I changed to a Mac Pro with two 30" Apple monitors also running 2020 and set the MBP to upgrade to Catalina (on an external SSD.) What I found was the normal hatful of rain. VW2020 crashes more than VW2019 on Mojave on either computer. Too much to be acceptable and I'm too busy to bother to bug search for another company who ought to do their own bug fixes before release with a 12 month old OS. VW2020 doesn't work at all well with the Mac Pro and 30" monitors. The screen graphics are woeful but more importantly, there are huge problems with screen refreshes. For example, you can double click on an object to edit it… for example to edit an extrude… and the screen shows the original image with stray handles all over the place so you can't tell if you are in edit mode or not. Heaps of problems along these lines forcing a Z key refresh every time you do a command to make sure you're seeing the right things. Objects appear to hyperspace, disappearing off-screen and requiring recentring all the time and groups won't ungroup etc. On the same computer, VW 2019 works fine or probably will until I get to work to be told I have used up my registrations and have to send a stamped addressed postcard to VW to de-register an installation. Catalina took all night to install… about 24 hours between connecting an external USB 3 SSD, cloning the original HDD and then updating. The installer sat for hours on 11 minutes remaining. Once that had finished, I found that a handful of key apps… including Aperture (not news there) and all the CS6 Adobe programs wouldn't run, so I disconnected the drive and went back to Mojave and VW2019. I honestly don't understand why VW releases happen like this. Why not release as a beta version for the first 9 months? I think it was May to June before 2019 was stable enough to really use. And for me, not being an architect, there's little reason to use the update anyway and the 3D history 'feature' doesn't appear anywhere, in spite of reading some very vague documentation in the help pages. Not entirely happy! I wonder if my 'service select' (no idea what that actually means in English) program can be delayed by 12 months? D
  4. DMcD

    macOS Mojave (10.14) Compatibility

    A huge amount of problems were caused by Mojave with many apps. A lot of this was due to changes in the graphics APIs, many due to OpenGL support or lack of it. Many of us involved in app development had similar problems to VW. I don't think that excuses VW entirely though. If I was VW I would not time my annual release to be exactly when the Mac OS was released. They could have seen from the Mojave betas that there were going to be problems and alerted users. These days, there's a lot of nonsense talked about 'Pro' users… I mean, who apart from a politician would be a 'Pro' phone users. Nevertheless, many of us depend on software like VW for our income and it shows a lack of understand and respect for their user base to dump known buggy software onto the market. It reminds me of……… MS Word 3.01. On the other hand, we've tested our apps with Catalina and there appear to be far less problems… well none so far as we can see. That being said, I'm not going to rush to upgrade because I am sure there are lots of 32 bit things I use on a regular basis. D
  5. DMcD

    Uninstall to Deactivate

    I can't believe I have been caught with this one again. At home for the weekend with some pressing work to do and decide to use my desktop with a bigger screen and… nothing… can't reactivate my own software. Many software companies live in an isolated world with high speed internet connections while some of the rest of us have either thirds world internet speeds, or are out of contact with internet or even mains electricity for periods of time each year… in my case often 3-4 weeks… and when I start up my computer and find VW needs reactivation and it can't get it. For example, crossing the Atlantic on a sailing boat a year or so ago. Nearly a month without the ability to use an essential work took which I paid for. Yes, people may break the rules but why are they prioritised over legitimate paid up users? I wonder what the breakdown is between VW programmers spending time perfecting annoying and damaging copy protection compared with fixing long standing bugs, erroneous behaviour and adding features loyal customers have been asking for for many many releases? A very annoyed VW customer. D
  6. DMcD

    macOS Mojave (10.14) Compatibility

    HA >>our office is planning to change to one of the big and really reliable cad software houses If it were only as easy as that. I tried switching and spent months with Solidworks and some days with Rhino and found that especially SW was more buggy and unreliable than VW with all sorts of limitations and tools that did not work. I agree that VW could do a lot better and offer more in the annual upgrades… I can't remember when there was a "must have" tool or release, but regrettably, I have not found something better. D
  7. DMcD

    macOS Mojave (10.14) Compatibility

    I wonder if this has something to do with your computer. We have Mojave on two Touch Bar type MacBook Pros with SP1 and Mojave. It totally fails. I also tried a downgrade to High Sierra which also fails as many have pointed out on Mac OS sites. If you actually work in VW for a living, I'd really suggest waiting to upgrade to Mojave. On the other hand, VW 2019 appears to work OK on a Mac Pro (2013). I say OK… I have had only one crash in 3 weeks but have all sorts of graphics problems which mean restarts and closing and reopening files. JC
  8. DMcD

    macOS Mojave (10.14) Compatibility

    I have been using 2019 on High Sierra OK but not on Mojave. I could not see if you stated your OS. That being said, there are some problems which were visible with 2018 which are still there but worse with 2019. The worst of these by far is the way that objects can disappear when you're trying to edit them. By this I mean that you can enter a group or symbol to edit it and either the object's control handles are not aligned with the entities in the object or the handles are visible or there's nothing visible at all and even doing a select all, shows nothing in the info pallet… yet when you exit the symbol or group, everything is back to normal. There are occasional work arounds… quitting and restarting, closing the drawing and reopening, selecting Unified View and deselecting, changing the view etc, but these work only occasionally. This is a huge time waster and the behaviour is worse with 2019 than 2018. I don't think this is a bug with the graphics card since it happens on laptops as well as desktops. So while I would not say that it's not worth upgrading to 2019 yet, I would avoid Mojave and 2019 like the plague for some time. Part of the reason for these problems is that Apple have deprecated OpenGL and it appears that VW relies fairly heavily on OpenGl and maybe have not done all the work necessary to make it fully compatible with the new OS. Yes, Apple have caused a lot of problems but not the problem of disappearing objects. D
  9. DMcD

    macOS Mojave (10.14) Compatibility

    Agreed. After dragging two laptops on an overseas trip, one with Mojave running emails and the other with High Sierra running VW 2019, I should remind myself to wait 6 months before installing any update for VW. The alternative is that VW gives Service Select members a 6 months free period and updates VW six months after each Apple upgrade. As software developers who use both VW and Mac OS, having one incompatible with the other is a nightmare. I updated a Mac running Mojave with the SP1 version of 2019 very unsuccessfully. The app loads but bombs instantly when opening anything, including creating a new empty drawing from VW's one template. The SP2 update better work OK! D
  10. DMcD

    Vectorworks 2011 = SLOOOW!!

    Hello Ref There was a problem with some Macs from three-four years ago where some video cards would give a massive speed hit. Frankly, I did not believe NNA's claims that the video card was a problem but after swapping video cards, the speedup was instantaneous and crashes stopped as well. The problem for me was that either I could not find an OK video card for one mac I had which resulted in a new computer. D
  11. DMcD

    Enhanced Push-Pull capability

    >But hey, don't get me wrong, vw2011 has improved. Maybe but the progress seems glacially slow. I can work in 2011 and apart from the new bugs, it's just like 2010. I can't find the killer features in 3D and still have to pay outside contractors to use Siemens stuff to do what I would like to be able to do myself. I'm also bewildered at how many bugs are not fixed? such as filleting and Compose. Compose ought to be great, but without a "fuzzy" input to join things which are not quite touching, it's almost useless. Chainmaker showed the way, but is broken in 2011. NNA are not alone. Most software these days seems to advance in terms of icons and packaging but not program content and functionality. Just as long as we keep upgrading. D
  12. DMcD

    VW Machine ?

    I've been doing machine design in VW for 16 years or more. Since MiniCAD 4 or thereabouts. I've flirted with other options such as ACAD, Rhino etc, but always returned to VW. The main reasons are: Speed. The VW environment is a lot faster to work in that others. I've found that you can design nice shapes in Rhino but it's really hard to redesign or reshape them compared with VW. Output. What's the end purpose of your drawings? Mine is normally to output parts for CNC machines. These are either 5 axis turning or milling centres. In most cases we're not really working in 3D or machining 5 axes continuously. For that reason, having full 3D facilities in VW isn't a drawback. Being able to simulate mechanisms isn't too much of a drama for us either, especially after watching an ACAD inventor simulation of an aircraft undercarriage at a trade show where the mechanism penetrated the fuselage side! Great video, useless as a working tool. Yes, it is worrying that NNA steams off into the sunset without a map that we can read, but this is no worse than most other software developers. We're as flies to gods. D
  13. DMcD

    2009 speed and RAM requirements

    >As you said, it runs fine on your laptop, so there is something >going on with your MacPro. >Have you called Technical Support to >try and work through the problem? >Have you run Software Update to make sure >you really have the most current versions of all the drivers? The problem is a bit bigger than this. I neglected to say that I have two Mac Pros, one at work, the other at home. Similar specs except that one has a 8800GT video card and the other has something like a 7600. Both similar large screens. Initially, when the problems first occurred, I did all the normal things like starting in safe mode, rebooting as another (new) user with extensions off etc. However, the only thing which got the performance up to speed was using only the smaller monitor. So the problem is probably not the CPU. Add to that the fact that all other programs and VW13 run fine, and the finger is firmly pointed at VW14. I have the latest OS and updates on all computers. I have talked via email with some people at NNA and run some tests for them doing screen timings. I think there is an admission that there is a problem, but it appears to be a low priority. For me... if I get something intensive to work on, it is better to downgrade. DMcD
  14. DMcD

    2009 speed and RAM requirements

    >I'm also experiencing significant slowness in 2009, seems to take forever to edit >groups, symbols, redraw the screen when zooming, panning, nudging... I updated >my graphics driver, no improvement there. I have no issues when opening the same >drawings in VW12. Ditto. Running VW 14 (2009) on a Mac Pro 2 x 2.8, OS 10.5.6, 4 GB RAM etc. and a 30" and 24" monitor. Runs like glue. As quoted above, nudging takes incredibly long. So long that the selection handles move seconds before the object redraws. As noted in some posts above, VW 13 runs fine and full speed on the same system. And when used on a laptop the performance is remarkably good. As noted in some quotes, I have turned off all the ant chappies on screen, so no "interactive" elements are used. Release 3 upgrade installed etc. etc. Still runs like glue. There are no drivers available for the graphics card since they are included with the OS. I can find no reference to any other slow downs to software other than VW. And this behaviour was noticed immediately after installing VW14. Is anyone else still getting this behaviour after installing the latest upgrade? Or is it just a few elitist folk with too many big screens? DMcD
  15. DMcD

    VW 2009 Slow

    VW 14 with the current (first or second upgrade) is slow for me too. Sloooow. Very very slow. In fact so slow that most of my drawing, especially dimensioning does not work at all. I made a funny video where I rapidly draw 6 rects. In 2008 the rects are drawn right off the mouse moves. In 2009, the rects take another 6 seconds to completely draw after the mouse has stopped moving. I have a Mac Pro Dual Core Xeon with 5 gigs of RAM and an NVIDIA GeForce 7300 GT card at work. I have a similar but newer and higher spec version of the same thing at home, with a higher spec video card. Something GT, but probably desmo as well. I also run VW 2009 on an Intel Macbook Pro. The two Mac Pros are running two screens, one 30" and the other 23". It appears to be the screen size that causes the problems. VW 14 runs fine on the lapdog, and fine on the Mac Pro when only the 23" screen is attached. Change to the 30" screen and things go slow as glue again. Start without extensions etc in safe mode and things are even slower... so never mind about that. The point is, VW 13 (AKA 2008) is perfectly fast. It is only VW 14 which is unuseably slow. And I mean seriously unuseably slow. There's another post somewhere about speed where Sean F claims users enjoy a certain lag. For me, it is just like using a phone with a delay. The feedback circuits go wrong, and you can't talk. Hanging up is the only option. Which is what I am thinking of doing with 2009. Is this delay or slow speed a problem for others still, or is it something unusual about my configuration? DMcD Mac Pro 2.66 Xeon stuff NVIDIA GeForce 7300 GT Desmo 30" and 23" Cinema displays. Mouse and keyboard.

 

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.

×