![]() ![]() I purchased an eGPU and added an AMD Radeon Pro WX 7100. Istat Menus is the tool I use to check on my GPU. Import it into a blank file and see if that helps.Īlso, all the mobile GPUs can have problems when they get short on memory, for any reason. I have not seen the problem in years, but perhaps your file has a problem. In VW2008(?)) it happened so often we published methods to recover your file to stop the crashing. there must be a way to check how it's working, I can do it on PC.Ī corrupt file can cause this problem too. I'm not very optimistic, I suspect the fix will have to come from Apple and VWx. I'll also try to replace imported symbols, move the origin (I'll make a new drawing and just keep a loci on the current origin, to return to it before exporting - not sure how this will work). ![]() ![]() It was closer to 50% while I worked on this file. That's a thought! I'll go tweaking! I'll increase the limit on virtual memory, but I wonder how it could run out of memory, while I have 32Gb, optimize it regularly and never use more than 75% of it. Independently, I seem to have some snapping problems (they were there since MC times, but seemed to have been largely addressed before), but I assume it must be the issue of re-setting the key preferences again. We also run an i9 PC with Nvidia 2080, I haven't tried the file on it yet, should I? Any help would be precious as I'm fighting against a deadline. The file has been made (and remade a few times through both: layer import reference and/or copy and paste) entirely in 2020 version. I clean all caches, do a safe boot and then reboot again after every crash or two, this seems to make no difference, neither does purging, compressing images, etc. But even saving and reverting to saved doesn't seem to help for long. My file is typically under 250Mb, which shouldn't be a problem for the RAM and VRAM to handle, I'd think. scaled symbols (coming from other consultants) data far from absolute 0,0 (I'm working on a large urban design project with many collaborators) I have crashes every hour or so, my autobackup is set for 7min so I don't lose too much work.įrom the list above, I observe crashes with: Which version was the file originally created in and has it been converted to 2020? Check by opening a copy of the file using TextEdit.ĭMcD describes exactly the same problems I'm having with VWx 2020 on loaded i9 MacBook 16" and i9 iMac, both w/32GB Ram and upgraded cards running two monitors. How large is the file or does it not matter? Probably only 15 minutes lost reconstructing files from backups.ĭoes this happen from the outset ie when creating a brand new file and copying a group?ĭoes the file contain legacy DWG import data eg line styles, hatches, symbols? Only two crashes yesterday and one was VW leaving the room while it was in the background.Sure there were feature limitations which largely still exist in 2020 but it did run reliably. The alternative is to call a live human at Apple (who I have not paid) for a chat about the problems with a third party app?Ģ018 was pretty solid. Any yet I have to search VW Help for advice which is normally 'nobody else is experiencing this, or 'your computer config is unusual' or 'wait for the next bug fix release.' While I know that Apple is to blame for a lot of the problems, I'm not paying them for system upgrades, but I am paying VW for service select. This is on several computers with everything from old messy drives to brand new top of the line clean computer installs… and the behaviour of VW is the same. I pay for VW service select every year and dutifully install increasingly buggy upgrades and lose time and work from continual bombs. Honestly, I think this is a huge cop-out and an abdication of responsibility to the customer. In which case I'd call Apple for support. If … your operating system upgrade went awry. …… Search the Vectorworks Help for more info on each of the concepts mentioned here. If Vectorworks behaves poorly after upgrading your operating system …… then reinstall Vectorworks. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |