Just opening the windows-small.shapr by itself takes just a few seconds.
Also, I can now import windows-small.shapr back into mac-large.shapr without it causing performance issues, however, the import takes about 7 minutes on a windows-small.shapr file size of 5mb. It used to take less than a minute to open it. The only problem now is that it takes 17 minutes to open/import mac-large.shapr when I want to edit it. Now I am able to successfully use both mac-large.shapr and windows-small.shapr on the macOS with pretty much normal performance. I opened windows-small.shapr by itself on the macOS and exported it back to the macOS file system. This was successful and it became responsive again. I deleted the newly imported bodies from mac-large.shapr. To make mac-large.shapr responsive again. That’s when the response in mac-large.shapr became unusually slow. I created a newer small design on the windows version called windows-small.shapr and imported it into the mac-large.shapr design on the macOS. My large design, call it mac-large.shapr is being edited on the macOS because the windows version of shapr3d is too slow and can’t export the design back to the file system. The following is the story of how everything happened and how I got around it: I was able to get around the worst part of the problem where my large design was reacting too slow to work with. The reason I uninstalled it is that it seems like it is at least partly responsible for the problems I am having. I can’t tell you what the Windows 10 version of Shapr3d is because I just uninstalled it before reading this post. I am using macOS Big Sur Version 11.6 on a Mac mini (M1, 2020) - 8 GB memory
0 kommentar(er)
