Jump to content

str

Member
  • Content Count

    29
  • Joined

  • Last visited

Community Reputation

12 Good

3 Followers

About str

  • Rank
    Greenhorn

Personal Information

  • Homepage
    www.b22.it
  • Location
    Italy

Recent Profile Visitors

576 profile views
  1. @Elite Exhibits not sure this is the answer you’re looking for, but this might help: panorama images are exported with a 45 angle counterclockwise (10.30 hrs). Therefore if you want a panorama facing your target, rotate the view 45 clockwise. Nevertheless this is not so relevant when you combine panoramas together in a tour via VW Cloud: there you can pick your target/orientation within the image very easily. This video might also help:
  2. @Luis M Ruiz I am not sure whether this post (or Troubleshooting & bug submission) is the right place to share it. I find Panorama & Cloud presentations a wonderful, reliable and intuitive tool, both on the designer and on the client side. While testing a couple of tours with some of our clients, we bumped into this issue: any suggestion? Are we doing something wrong? Thanks in advance.
  3. I bought mine in January, used it heavily with very detailed building models in VW Architect, everything works smoothly although often with fans on for cooling. Specs: Intel Corei7 6-core 2,6 GHz, 16GB RAM, AMD Radeon Pro 5500M 8GB, SSD
  4. Hi, When accessing a panorama tour via Vectorworks Cloud Services on a browser, switching to the cardboard view (via the cardboard icon on the lower part of the screen) gives a 90° counterclockwise frozen rotated image. I tried both in Safari e Google Chrome and on different devices with no success. Via Nomad app direct opening a panorama file works smoothly as expected. Should I submit this as a bug? Thanks.
  5. I follow this topic with great interest. A while ago I bumped into this by @Hippocode but it looks like is meant for mep design rather than architectural design.
  6. @Nikolay Zhelyazkov thanks for your reply. Project/Data fields are visibile in the Setting/Manager (i am aware of field visibility) dialog but not in the “splitted” Title Block graphics: we had the exact situation of @rexwexford. It also happened to us with a customized title block, re-inserting title blocks (and their style), after erasing and purging solved the issue for us. I had the feeling it could be related to file/style conversion between different VW versions, but I can’t confirm. I’ll send it to you if it happens to us again. Btw I find Title block a powerful and well design tool, very useful for controlling project info.
  7. We occasionally run into the same issue (splitting and losing information). If I remember correctly title blocks data become invisible while still accessible in the database (editing title block). Trying to fix it editing title block layout was no success. Ended up erasing all title blocks in the file, purging the file and inserting title blocks again (with some frustration).
  8. @Jeremy Best we spent some time at the office testing with the following result. I have the feeling it might be related to the macOS version (= progess bar not showing on versions later than macOS 13), but I would love to know if this only occurs to us. Otherwise it might be related either to our localised version (I just shared this with our distributor as well) or to some other condition I am not aware of. MacBook Pro Mid-2010 - macOS 10.13 - VW2019 & VW2020 > PROGRESS BAR SHOWING iMac Late 2012 - macOS 10.14 & macOS 10.15 > VW2019 & VW2020 > NOT SHOWING macMini Late 2012 - macOS 10.15 >>VW2019 & VW2020 > NOT SHOWING MacBook Pro 16’’ 2019 - macOS 10.14 VW2019 & VW2020 > NOT SHOWING Edit: our distributor just replied (@Pier Luigi thanks for it), they are aware of this issue
  9. All machines running VW2020 Architect (localized Italian) till SP1 (Service select subscribers)... till we discontinued our MacBookPro Late 2010 (replaced by the new one a month ago) and therefore we are unable to reproduce it now. For a month I’ve been working/testing on both laptop, before finally switching, and than is when I realized something strange was going on everywhere but on the oldest and weakest one: on the new MacBookPro I had the feeling VW was going worse than before, often freezing with certain operations, while it was simply not showing the progress bar. So I tested at the office on our 2 iMac (Late 2012) and there also progress bar was missing. There is still one more configuration I’ve not tested yet (MacMini Late 2012 running VW2020 US international) Progress bar is not showing, for example, with walls (e.g updating wall styles, “fitting walls to objects”, creating recesses) and space planning (again updating styles)... both heavy operations on complex projects. Not sure with PIO and if progress bar is supposed to appear when updating doors/windows styles (VW US window/door... which we prefer to use even in our localized version instead of the Computerworks/German “Fenster”). I would say, but I might be wrong: most of operations with lot of CPU load (up to 10-20 seconds and more...).
  10. Hello everyone, Any idea/suggestion on how (if) we could turn on the green progress bar for commands and operations (lower right corner)? We're experiencing inconsistent behaviour (VW2020 Architect latest version, localised and international): progress bar is always showing for backup autosave, but not for other complex operations (updating walls, spaces etc.). It seems to us this behaviour could be hardware or install related: progress bar is showing in a VW Mac Book Pro (Late 2010, vram lower than recommended specs) but neither on iMac (Late 2012, vram lower than recommended specs) nor on MacBookPro (2019, vram higher than recommended specs). Not sure if there is any setting/preference we could change. Since at the office we do work with detailed and sometimes complex files not having a progress bar is very frustrating: most of the times we're struggling understanding if VW is freezing or not, with no way to understand if a "force quit" (rather than waiting for an unpredictable time) is the right thing to do. Any suggestion is more than welcome.
  11. str

    Lift

    Hi Angelica, all you can do with the lift/elevator tool is to 1) place and set your elevator on one floor (inserting it into a wall) 2) create an elevator style, if needed (VW2020 only) 3) copy-paste it on each floor. Besides creating an opening when inserted in a wall, there is no other smart behavior (e.g. slab modifiers, top and bottom, etc) using the the elevator tool, which is basically a 2d/3d parametric symbol.
  12. hi @Amorphous - Julian, Here to share our office experience with Project Sharing. What we’ve learned is that a lot, much more than we could believe, depends on server and network configuration and even more when it comes to save&commit which is a key operation. We have been operating for a long time in a Mac OS Server environment, since it was still a Os and not a cheap and fragile app, as it is now. In several years - especially at the beginning - we’ve pushed it as much as we could, with advanced configurations (e.g. network home folders) and professions advice on set up and management. 12 months ago, planning server hardware replacement, we decided to “downgrade” from a server configuration to a nas configurations, given that we were mostly using our server for file sharing only, having slowly moved any other “service” (mail, calendar etc) to cloud services. After quite a long research (we also came from a long frustrating time with project and file sharing issues on Mac OS server, which got worse after the new Apple file system was introduced on some clients and smb also pushed on the Apple side also), we moved to a mid-high range Synology NAS, following also testing and suggestions by VideoCom, our localized VW distributor. High range Synology NAS apparently have a better afp/smb file management. Most of our issues, which were similar to yours, have since than disappeared: no more file permission issues, no more save and commit issues, much higher stability. We still find Project Sharing not intuitive in some parts (e.g. when prompting confirmation about updating wall styles to unaware users) but working on detailed drawings in a similar configuration (small firm, max 3 people one file) is much better now. I must admit we still have the “fear” that sharing may not reliable especially under deadlines (due to some unexpected behaviors we experienced in the past, which drove us to crisis situations) but in the last 12 months, after the move, no big issue was raised working with Project Sharing. Not sure this could help you, but on our side it has been quite a positive surprise, and a big step toward an efficient management of time spent on design rather than on IT technicalities.
  13. Hello everyone, we had a similar - but less detailed - discussion/request here a few months ago. Thumbs up!
  14. Toolset images are stored in the workspace (.vww) file as ASCII: the easiest way to copy them from an old/different workspace is to copy/paste lines of text from file to file, opening the .vww file with a text editor. Backup your .vww files before editing them: it works on VW2019 and migrating icons from VW2019 to VW2020 but having a backup of the .vww files is safer. More info, and some helpful tips by @Robert Anderson here:

 

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.

×
×
  • Create New...