Jump to content

RonMan

Member
  • Content Count

    96
  • Joined

  • Last visited

Community Reputation

9 Neutral

About RonMan

  • Rank
    Apprentice

Personal Information

  • Occupation
    COO/CIO
  • Location
    Texas

Recent Profile Visitors

381 profile views
  1. No problems on my end. I have been using them together for many months now.
  2. A corrupt file can cause this problem too. In VW2008(?)) it happened so often we published methods to recover your file to stop the crashing. I have not seen the problem in years, but perhaps your file has a problem. Import it into a blank file and see if that helps. Also, all the mobile GPUs can have problems when they get short on memory, for any reason. Istat Menus is the tool I use to check on my GPU. I purchased an eGPU and added an AMD Radeon Pro WX 7100. It is FAST, and has made my system much more stable for both VW and other graphic stuff I do. (I am also a photographer)
  3. It looks like you ran out of virtual memory. I didn't spend much time on the crash dump, but memory is the problem. I could be physical or virtual, but the exception happened when trying to expand virtual memory beyond the allocated memory. How much memory do you have on your system and in your GPU?
  4. The monitors do not have speakers or cameras. I got better monitors at a lower price because of it. I use an external speaker at my desk and the camera on my laptop when I need to do Zoom or Skype. I have a OWC Thunderbolt 3 doc that I use for just a couple of things. I only use it for GB Ethernet and my SpyderX. There are 4 extra USB ports if I need them. I could put a camera on it. Everything else goes to the eGPU, Razor Core X Chroma; two mice and my 3Dconnexion Space Mouse. I have a Logitech G700s for normal use, and a Razor Naga Trinity for VW. I program the mice with the SteerMouse preference panel. I did not choose the BlackMagic eGPU based on cost and comments from others. The Core X Chroma is great, but the GB Ethernet port does not work well on Windows, and not at all on a Mac. I decided to keep it after getting everything set up. I already had GB Ethernet from the OWC dock. The AMD Radeon Pro WX 7100 came up because it was supported and AMD recommended it for VW (on Windows, but who cares about Windows). I would have had to spend another $300-500 to get a better card from AMD. You saw the performance in my previous post. I'm doing OK. One thing I did learn, you can get battery swelling if you use your system with a dock most of the time. I got the battery replaced (three days without a computer–it was hell). Now I have it on a laptop stand that has a USB fan underneath. I found it at Fry's or Staples years ago. This is a great use for something that to gather dust previously. The temperature of my MacPro is down 5-10 degrees. The battery should not swell again. There is a 34 TB NAS in the cabinet along with a UPS for it. My wife might disagree, but this is a simple layout. The monitor you might consider is the Dell UltraSharp 27 4K Monitor: U2718Q. It comes in a 30 inch version as well. A webcam is $50, and you likely have speakers laying around somewhere. I recommend you try Geekbench to see what kind of performance you get in different setups.
  5. In daisy chain mode, as shown, the Mac GPU would be hard pressed to keep up. If the daisy chain has the eGPU before the MacBook, you would get all gate benefits of the eGPU. I think that is the ideal configuration. If you can't daily chain, there is a way to make the eGPU primary in System Preferences. Go to Displays/ Arrangement and make sure the menu bar is on the display from the eGPU. You won't need to change the setting in Get Info. When you use the system by itself, the internal GPU will take over, but whenever you use the eGPU, you will get the eGPU performance by default. The only time I use the internal GPU is when I am traveling. Otherwise, I drive everything from the Radeon Pro WX7100. Here are some test results Using GeekBench 5.01, OpenCL test 40,336 AMD Radeon Pro WX 7100 Compute Engine, eGPU 13141 AMD Radeon Pro 560X Compute Engine, internal Using GeekBench 5.01, Metal test 45,878 Radeon Pro WX 7100 Compute Engine, eGPU 14,031 AMD Radeon Pro 560X Compute Engine, internal The difference is easy to see when using VW. Both monitors are Dell UP2716D models. They have excellent color. The resolutions are 2560 x1440. There is an equivalent 4K model. Of course it costs more. I think that is all I have. Forgive and spelling for grammar errors. I slapped this together in just a few minutes. I did run the GeekBench tests again for this.
  6. It took me a moment to get your setup. One monitor is directly connected to your Mac while the other is on the eGPU. Yes, that will cause a problem depending on where you have the control bar in the Display/Arrangement setting in System Preferences. If at all possible put both monitors on the GPU and set the control bar on one of the eGPU monitors. You can determine what is running where by using System Activity and selecting the GPU tab. You can then see what is running where. I hope this helps.
  7. Ten minutes ago I had the first crash I have had in days. I use the Razor Chroma X eGPU and the Radeon WX7100. This is a very good combination, but make sure your monitors can handle display port. If they cannot consider a different card in the WX series. The less and greater models feature mini-display port. The faster one is not worth the money in my view, and the slower one does not have the power. Note the Radeon WX series are workstation cards, not gaming cards. I would NEVER use a gaming card for CAD work. The optimizations are totally different. The crash-dump is not as clear about the cause. There was a EXC_BAD_ACCESS (SIGEGV) fault. These are usually a code errors. It looks like VW tried to access something that was no longer there. I was designing a space craft (don't ask), changed views to move something, touched it, and boom! The object was real but VW lost track of it. I won't say I have never lost an object while programming, but I usually can find and fix it. The problem VW has is they have no idea which object I created, or where it was. Either the rendering engine or the user interface lost track of the object. After all that BS, I still believe the Razor and the Radeon WX7100 are a great combination. I did have to get rid of my Apple Thunderbolt displays (I loved them, but they are old and available in Dallas). I would like to hear from others on which eGPU and card they are using. I think the Mac Pro would kick ass, but I don't have the cash to buy a used Ferrari, let alone that rocket.
  8. Which graphics card are you using? I have the Radeon Pro WX-7100 and everything is fine. I would check your memory when using VW. Istats Menu lets you see what the GPU is doing. I also have an i9 in my MacBook Pro 15"
  9. I chose the Razor Chroma X. It has GB Ethernet and four USB ports . To get two FireWire ports I would have spent another $300. I didn’t see the value.
  10. I have added the eGPU since this update. What a huge difference. The card is an AMD Radeon Pro WX7100. Both the faster and slower cards in the series use mini-display port connectors. The immediate impact is all visualizations. I can crank OpenGL settings to the moon and still move smoothly. I changed the setting on my 3DConnexion mouse because the card is so much faster. I also crash less often. The built-in graphics card does not have enough memory to handle complex renderings. Once it is full you either quit Vectorworks for a while, or wait for VW to crash and quit VW for a while. memory does not clear quickly from the graphics card. Use istat Menus to see what your GPU is doing. I did change my monitors. I now use two DELL UP2716D monitors. My Thunderbolt displays are for sale in the Dallas area. Note: If I had chosen a different AMD card I could have kept the Thunderbolts monitors.They cannot be used with a full-size display port to mini-display port adaptor. The new monitors calibrate extremely well with my datacolor SpyderX. They do lack speakers–not an issue. I do not regret changing monitors. The color gamut is much better and they have excellent uniformity. (I do photo editing) Radeon Pro WX 7100: Chipset Model: Radeon Pro WX 7100 Type: External GPU PCIe Lane Width: x4 VRAM (Total): 8 GB Vendor: AMD (0x1002) Device ID: 0x67c4 Revision ID: 0x0000 Automatic Graphics Switching: Supported gMux Version: 5.0.0 Metal: Supported, feature set macOS GPUFamily2 v1 GPU is Removable: Yes Displays: DELL UP2716D: Resolution: 2560 x 1440 (QHD/WQHD - Wide Quad High Definition) UI Looks like: 2560 x 1440 @ 59 Hz Framebuffer Depth: 30-Bit Color (ARGB2101010) Display Serial Number: KV97096J195L Main Display: Yes Mirror: Off Online: Yes Rotation: Supported Automatically Adjust Brightness: No Connection Type: DisplayPort DELL UP2716D: Resolution: 2560 x 1440 (QHD/WQHD - Wide Quad High Definition) UI Looks like: 2560 x 1440 @ 59 Hz Framebuffer Depth: 30-Bit Color (ARGB2101010) Display Serial Number: KV97096J183L Mirror: Off Online: Yes Rotation: Supported Automatically Adjust Brightness: No Connection Type: DisplayPort
  11. My testing indicates the chart is accurate. I keep a virtual machine of macOS Sierra in case I need it.
  12. 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.
  13. 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.
  14. 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.
  15. Thank you for the update. We will be doing some final testing later this week. I will update here if we have problems.

 

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