Jump to content

KenAB94662

Member
  • Posts

    55
  • Joined

  • Last visited

Everything posted by KenAB94662

  1. Just revisiting this topic in case someone now has a nifty new solution. After turning on Log time in program (VW Prefs / Session), there's a data file (in Mac, it's in the hidden Library / Application Support / Vectorworks / 20xx / Vectorworks Log). However, it only shows the date, timestamp, and the name of file when opened and when closed. Is there a way to get more out of it such as when multiple drawings are opened, how much time is allocated to each drawing? Ideally, it would go further in tracking the time of application focus, such as when I click away to check email, the internal clock would automatically pause, then resume when I click to focus back in Vectorworks. I would hate to suggest more bloatware. If not possible, are there any third party apps that's more than a simple manual toggling on/off a stopwatch?
  2. From the other discussion about flickering, could this be related to compatibility of Vectorworks v2023 SP7 with macOS 14? I feel so unlucky. I stayed in v2020 due to incompatibility with macOS newer than 11 Big Sur — stayed until September 2023, suffered an older version of Xcode, FCP, etc. Then, after saving some money, I dived in with huge payments for Vectorworks v2024 along with new hardware and macOS 14. But it was only to find v2024 so raw and undeveloped that I had to install v2023 instead. Now, as seemingly mature as v2023 SP7 is, it's still problematic in macOS 14. I suppose this is the cost of the bleeding edge technology.
  3. Thanks but I don't have Photoshop. I also periodically restart anyway (for Google folder connection issues). And the problem in VW persists regardless. It's a good clue though. Perhaps it's caused by another similar app that uses interactive cursor? But how to tell? I often concurrently run Mail, Slack, Quicken, Calculator, Thinkorswim, Numbers, Google Chrome, and a surveillance cam app. I don't think any of them have interactive cursor.
  4. Sadly, I suffer the same problem in my current v2023 / macOS 14 / M2 Pro. Mine include flickering of the Vectorworks cursor. Previously did not have any such problems in v2020 / macOS 11.7 / M1 Mac mini. I wonder if it's related to macOS 14.
  5. The response lag is about half second. It's very consistent. When compared to my previous v2020 in macOS 11.7, I'm now doing things faster than the computer, which should not be the case. I work very quick with lots of keyboard shortcuts, but v2020 was a tool. Now I have to wait for processing to complete. It's been over a month after upgrading everything and three complete projects to get used to it. But I cannot get used to the lag. Outside of Vectorworks, everything is blazing quick and instantaneous as it should be. The M2 Pro is greased lighting — boots up in a split sec, loads apps faster than anything I've ever had. I'm also on fiber Internet at 370/370 Mbps and 4ms latency. File transfers online are sometimes quicker than my external SSD. So it's only a problem with Vectorworks, and apparently only with v2023. What adjustments am I missing?
  6. This flicker problem is in v2023 SP7 as mentioned. But would having v2024 installed yet not even running cause the problem?
  7. Sometimes the cursor does not show any tool at all. I upgraded from v2020/ macOS 11.7 Big Sur/ Mac M1 to v2023/ macOS 14 Sonoma/ Mac M2 Pro. Everything else in the M2 Pro is extremely quick/ fast/ responsive. Only problems are in Vectorworks. flicker.mov
  8. Thank you for the suggestion. I'm now trying it out. Now for the feature phased out, how do you quickly find the reference datum Z in a model? Here's what I see. In this project, there's a change in floor height — a step up where some door thresholds are higher than others. Previously, I snap to the 2D line extended far to one side.
  9. Sorry to be 3 years late, but I recently upgraded from v2020 to v2023. My setup used to be a "model" layer in unified view looking at all 3D layers. On this model layer, I would keep a horizontal line on "screen" plane (as opposed to "layer" plane). The purpose was to use the line as datum reference to finished floor on the main floor. It was visible in any orthogonal side view (side elevation views). This allowed me to offset-duplicate it for Z reference when modeling different elements. Now it's all gone. There's only "3D" plane if not "layer" plane, and the line in either 3D or "layer" is not useful. Any help?
  10. Welp. Vectorworks v2024 will have to be next year for me. I'm now in v2023 (upgraded from v2020). What a relief! It's again simple, sprite, responsive, useable.
  11. I'm thinking to delete v2024 and install v2023 instead. There's just too much visibility lag right now. Simple things like going up/down layers, in/out of groups, zoom in / zoom out, are just undeveloped. I've tried turning OFF Accelerate Graphics. Same thing.
  12. I've decided to give v2024 a fair chance. So this weekend, I embarked on creating my template from scratch in v2024 instead of importing old. This is v2024 SP1. Lo and behold, there's still a lag when activating my Saved Sheets. I was pulling my hair out recently from fighting through my older drawings opened in v2024. The lag is most noticeable upon first activation of a Saved Sheet, but repeating the activation of it goes quicker. I activate by double-clicking on the name of it in its palette kept open. It's like 200 to 800 milliseconds — not a full second lag, but stilll very noticeable. Also similar with Sheet Layers and the Visibility tool (V key). My layers are all same scale. Some have custom colors and different opacity settings. Some have my pre-assigned Z values as placeholder. I have not yet inserted any custom scripts. Is any of the above deprecated? What am I doing wrong? This is Mac Mini M2 Pro and macOS Sonoma — all the latest as of this writing. Everything else outside of Vectorworks is super quick and fast.
  13. Was it only in version 2024 that tool icons became dumbed down with muted colors and rather indistinguishable from each other? Version 2020 had it better, in my opinion. Tool icons were more distinct and intuitive so I didn't have to stare and study the toolsets. Yeah yeah I'll get used to it (v2024), but it's still very poor very weak graphic design.
  14. Need to hear actual users' experiences, not website advertising. I do not have time to beta test v2024. Already paid way too much for someone else's featuritus. All I need is steady, stable, quick, and bug-free. So tell me, fellow architects and Vectorworks professionals, what do you find most compelling in version 2024 compared to version 2023?
  15. Well, indeed something does happen, and it's slightly better — after disregarding the ominous warning beep, the multiple back-n-forth clicks did close the gap. But it still left a seam.
  16. OK. Thanks for the alert on SP1. I got suckered into the paying the promotion.
  17. The necessary gap was already a peculiar behavior in v2020 (and maybe earlier I forget). But now, it's not even allowing click on the pillar. No can do.
  18. Thanks again. Bookmarked. But really, I really really hate being beta tester. What a PITA filling out all that. They don't even have the current macOS Sonoma listed.
  19. Is the bug submit page also now different? Even submitting a simple bug is frustrating. I don't want to be a beta tester. https://www.vectorworks.net/en-US/support/bugsubmit HTTP Error 404
  20. In v2020, joining wall to pillar was easy. Now in v2024 it is not possible. Worst is just trying to find online help or documentation to learn about new features. Already tried Vectorworks Help, searching these forums, even general Google search. I've added Unified View toggle button in the View Bar. I realize there's something different where Unified View ON (or is it OFF? whatever is the blue indicator) shows the pillar object, whereas the other toggle makes it disappear. Neither allows join. Furthermore, just testing in a blank new untitled drawing is another pain the ass — even the Unified View toggle button is gone! This is frustrating.
  21. I found the answer on my own. Thank you.
  22. This weekend, I upgraded three things: 1. New MacMini — mild upgrade from M1 to M2 2. New macOS — relatively big jump from 11.7 Big Sur to 14 Sonoma 3. New Vectorworks — seemingly gargantuan leap from 2020 to 2024 Apple's Migration Assistant was great. It brought in everything nearly intact. I simply re-entered passwords here and there. All the deprecated apps are, of course, disabled. Some files, including the old Vectorworks 2020 folders in the hidden Library, still came in seemingly untouched. However, Migration Manager in VW 2024 is not recognizing anything to "select the location of the user data to be migrated..." Am I screwed? Must I create all my settings from scratch? I now have only one Sunday afternoon to ram my head against the brick wall. Advice?
  23. I'm long time user of v'20 now trialing/testing v'22. Noticed something entirely different has replaced Stack Layers aka Unified View. Don't know when the change occurred, whether v'21 or v'22 but don't care. Just searching for a quick guide or tutorial on how to deal with it and get back to work. Okay if somebody made demonstration video of the change if it was early in v'21 plus more changes if it's shown anywhere. But where? What explanation/ demonstration/ tutorial/ help reference is available just to get me adapted to v'22 on the lack of Stack Layers aka Unified Views? Seeking ideally a short video, but cannot find any. It's frustrating. I'm usually self-taught but this monster of v'22 has grown too big. Feels like bloatware. Help.
  24. First, yes my trial version of v'22 is latest service pack. Splash screen says SP5 (Build 664120) (64-Bit). Should I start a new discussion topic on only the lag I notice when merely opening a new blank document, drawing simple rectangle, then drag screen quickly left-right with Pan Tool? — as described above. And so, the lag is not just with imported PDF. It's just raw simple Vectorworks version 2022 launching by itself after restarting my Mac, and there's huge noticeable lag. For this reason alone, I'm thinking of not upgrading. What else am I missing?
×
×
  • Create New...