Jump to content

brandon.stewart

Member
  • Posts

    6
  • Joined

  • Last visited

Everything posted by brandon.stewart

  1. Hi Andy, My condolences! I have good news and bad news. Luckily the problem no longer afflicts me. But the bad news is I don't know what stopped it! I had done everything I could think of to stop the problem (including updating Mojave and VWX all the way, and also installing and re-installing VWX TWICE, the second time telling it NOT to migrate my user data) and STILL had issues for about two days. I got really good at always creating an object alongside a wall that I wanted to select (like a line or another wall) and then selecting BOTH of them. As long as I never had a single wall selected by itself. Super annoying. Then without warning the problem stopped. I do have one other theory though... I take some of my work files home to work on at night, and my laptop is a PC (as opposed to my Mac at work). Also, my PC is currently running 2018 (just haven't gotten around to upgrading). So maybe somewhere along the line the switching between a PC and a Mac corrupted my file? Or switching between 2018 and 2019 corrupted it? Weird though because I could easily open the same files on my colleagues' slightly older machines (I have the newest iMac in my office) and couldn't get the problem to replicate. And either way, even if that WAS the issue, I have no explanation as to why it suddenly stopped being a problem. Good luck. I'll be watching this thread to see if you figure anything out. God speed. Brandon
  2. Hi Jim. An update: I've seen a hint of things getting better, but they're also getting weirder 😕 I just uninstalled and re-installed. This time I did NOT migrate my old user data / workspace. And the problem persisted, even in a clean, brand new file. But THEN, if I go up and change the workspace from "Architect" to "Architect-BIM", then I'm able to select single walls without any problem. As soon as I switch back to the "Architect" workspace, the problem comes back and it crashes when selecting single walls. Any idea why this might be? -B p.s. I thought it might have to do with my non-Apple bluetooth keyboard having different shortcuts set up for different keys that clashed with the default keyboard shortcuts in the "Architect" workspace. I thought that maybe, even though I'm not doing any keystrokes to trigger the problem, maybe there's some crossing-of-wires. But then under my Apple keyboard system settings, I tried setting ALL keyboard shortcuts back to their defaults, and then using a DIFFERENT hardwired keyboard (this time Apple) and the problem is still exactly the same.
  3. Thanks for the quick reply, Jim. I did NOT already speak with support, should I have? You mean calling the Service Select number and speaking to someone on the phone? No we have not done that. To answer your question, when I re-installed vwx2019, I DID restore my workspace. Do you think that might be the problem? If you think calling support would be effective, please let me know and I will try speaking with them. Thanks, B
  4. Hello All, Every time I select a single wall object, I get eternal rainbow wheel / application not responding and I have to force quit. If I marquee-select two or more walls, it's fine. Or if I marquee-select one wall and any other object, it's fine. But click-selecting one individual wall crashes me every time, no matter the file (even the extremely simple file uploaded below). -Yesterday I un-installed and re-installed VWX 2019 (so Vectorworks is up to date, with all service packs installed) -Mojave is up to date (osx 10.14.2, see attached system info) I understand that most of the bugs are Apple bugs and not VWX bugs. But even after this upgrade yesterday, I'm still having the same problem. And I'm not seeing any threads on here discussing it. Any ideas? Thanks, Brandon VWX test file.vwx iMac - B. Stewart - 12.14.18.spx
  5. Hello Jim, I've had a similar problem, but with VWX 2019. (I'm kicking myself for installing it BEFORE reading on these forums about the Mojave issues!). Every time I select a single wall object, I get eternal rainbow wheel / application not responding and I have to force quit. If I marquee-select two or more walls, it's fine. Or if I marquee-select one wall and any other object, it's fine. But click-selecting one individual wall crashes me every time, no matter the file (even the extremely simple file uploaded below). -Yesterday I un-installed and re-installed VWX 2019 (so Vectorworks is up to date, with all service packs installed) -Mojave is up to date (osx 10.14.2, see attached system info) I understand that most of the bugs are Apple bug and not VWX bugs. But even after this upgrade yesterday, I'm still having the same problem. And I'm not seeing any threads on here discussing a problem with selecting single walls. Any ideas? Thanks in advance, Brandon VWX test file.vwx iMac - B. Stewart - 12.14.18.spx
  6. I have stumbled upon a major issue with one of the new 2018 features. I was just playing around with the Andersen window catalog, and very easily made some troubling discoveries. First of all, when looking at Picture Windows in the Andersen 400 Series, only 14 units show up. The Andersen 400 Catalog, both on their website and in the up-to-date hard copy we have here in the office from 2015-2016, contains 52 Picture-type units. Furthermore, of the 14 listed Picture-type units listed in the VWX catalog, only half of them are listed correctly; "P35" thru "P60" don't even exist, they are mislabelled and should read "P3535" thru "P3560". Perhaps the most troubling discovery of all is what happened when I tried my very first window placement in a vwx document from this catalog. After placing an Andersen 400 Awning window (AW41), I went to the auto-created window schedule in my document AND I went to the window settings to see if the unit was listed correctly and, while the unit width was listed correctly as 4'-0", the rough opening width is erroneously listed as 4'-1", instead of 4'-0 1/2". Again, 4'-0 1/2" is the rough opening width listed for this unit BOTH in the online catalog AND in the hard copy catalog. I was really looking forward to being able to pull windows directly from these built-in vwx catalogs, but now after finding these grave errors so easily, it doesn't inspire much confidence in being able to trust the rest of the catalogs either! During several of the Vectorworks Design Summit workshops I just attended in Baltimore, many other attendees were also excited about this new functionality (at one point there was even open applause when the feature was explained!) Please let us know when this issue will be resolved and when we can trust the catalogs you have built-in. Thanks, Brandon
×
×
  • Create New...