Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

2 Neutral

About RonMan

  • Rank

Personal Information

  • Occupation
  • Location
  1. I have been consistently using VW2020 Designer on Catalina for weeks. I have found no major problems. I am adding a eGPU and an AMD Radeon Pro WX 7100 to improve performance. My system: Model Name: MacBook Pro Model Identifier: MacBookPro15,1 Processor Name: 6-Core Intel Core i9 Processor Speed: 2.9 GHz is bogging down with this graphics configuration: Radeon Pro 560X: Thunderbolt Display: Display Type: LCD Resolution: 2560 x 1440 (QHD/WQHD - Wide Quad High Definition) UI Looks like: 2560 x 1440 Framebuffer Depth: 30-Bit Color (ARGB2101010) Thunderbolt Display: Display Type: LCD Resolution: 2560 x 1440 (QHD/WQHD - Wide Quad High Definition) UI Looks like: 2560 x 1440 Framebuffer Depth: 30-Bit Color (ARGB2101010) The screens will not refresh under load. I have to either force an update by moving the view slightly (I bump the scroll wheel forth and back), or quit VW and wait until GPU memory has been cleaned. That can take 15-20 minutes. I am specific about my configuration because others have had no issues or some minor ones. I believe VW2020 is ready for prime time now. Don't forget to do your updates.
  2. I agree that VW should wait 3-6 months after the release of a new macOS, but I can think of a reason they won't; taxes. Releasing the latest version before the end of the year gives them tax breaks the can take advantage of immediately. After Jan 1, those breaks don't happen until the end of the year. Yes, that stinks, but they are in the business of making money, as we all are. I don't have a fix for this, I just understand this portion. The user community will be 3–6 months behind at all times. Sometimes we don't have the time for the testing, and we get two versions behind and scream at support because we can't get any work done. I was never happy about the yearly subscription model, but these are the times we live in. It makes more money for VW and causes us headaches. We either go along or quit using the product. There is nothing else worth a sh*t for macOS. We have to live with the problems. What we don't have to do is be quiet about them. Keep those cards and letters coming. Maybe VW will invest in better testing and QC, and maybe my next job won't have unreasonable requests to do impossible things without a change order or additional costs. I can only hope.
  3. I can respond to your first paragraph; Vectorworks has created PDF files with these kinds of problems for years. Adobe's Reader program renders them correctly but Apple's Preview does not. I have spent time changing fonts, simplifying hatches, and more. I have never found a consistent reason for the problem. You can print to Preview, and get a correct PDF, but the extra steps are not worth the effort for a large project. I have never had a problem with Reader gagging on something after Preview opened it. That is a new problem. VW may have some blame here, if their PDF generator does not stick with the standard exactly. Preview is very strict, while Reader is extremely forgiving. If your workflow can accommodate it, use the PDF generator in macOS rather than the one in VW. You will then get consistent results.
  4. Thank you for the update. We will be doing some final testing later this week. I will update here if we have problems.
  5. Will any of these work for you? http://sketchup.google.com/3dwarehouse/search?q=dog&btnG=Search&styp=m
  6. I found that HDR Mill, http://www.hdrmill.com/Skies_Uncategorized01.htm produces some very realistic skies that don't cost a lot. Check them out. I tried some of these: http://www.accustudio.com/index.php?option=com_remository&func=select&id=19&Itemid=54 but I was not happy with the results, but they are free. RonMan
  7. Hmm? I have only had to do this once and it worked out OK. Your milage was different. VW handles True Type fonts well, others it ignores. If you really need to use Helvetica Nue, then you will need to convert it to True Type. TransType handles this well. We have some 300 MB files that perform just fine on my system. My partner's G5 has some issues with the size so we do all the renderings on my system. He handles the annotations. Other than the methods suggested, I really know of know other way to accomplish what you want. Good luck RonMan
  8. This is not trivial, but one way of doing it is to create the annotations you want, convert everything to a group edit the group, convert the text to polylines and then extrude everything to 0.01. I would do this on another layer. If you do it on different layers at different heights you can do multiple floors in the same viewport and it will all look pretty.
  9. 51 MB is a bit too big to upload. When you say that it won't render, are you getting any error messages? Check the console (in the Utilities folder) and see if you are getting anything there. Also, are you trying to render after you have been using the app a while or just after restart? There are memory leaks that can cause problems with rendering in VW2008. Starting fresh allows me to do renderings that I cannot do if I have been using VW for a few hours. Other than these things, I don't really know enough. If you contact me off line, I can give you a place to upload the file so I can look at it. RonMan
  10. Not really enough information, but if you attach the file I will look at it as my setup is similar to yours. RonMan
  11. Here is one from Sketchup 3D warehouse. http://sketchup.google.com/3dwarehouse/details?mid=e20bd667b4b8320e9566662a26e53fef&prevstart=0
  12. RonMan

    Notes Sheets

    Try here: http://vectordepot.com/market/ Items VM001- VM004
  13. The memory leak is very real on the Mac side. I am unaware of the details on the Windows side of the world. VW will not correctly release memory when it finishes a rendering. When it gets to about 1.5 GB to 2.0 Gb (it varies a lot) VW will either warn you that you are out of memory, mess up your rendering, leading you to save and restart, or just crash or hang. RonMan
  14. There is no way to edit or allocate more virtual memory. This is a Vectorworks problem that "will be fixed in a future release". Memory management in VW stinks and an would love to see it improve. We wait and see. RonMan


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