2021-07-01 07:05 PM
Solved! Go to Solution.
2021-07-02 12:16 AM
2021-07-02 07:29 AM
2021-07-02 10:52 AM
2021-07-06 04:29 AM
Podolsky wrote:Yeah.. no. I get that Macs are not always super stable, particularly when the new OS comes out. And I knew what I was getting into installing it in the first couple of months Big Sur's release, so all in all I'm not terribly surprised or disappointed.
So why I'm writing all that. Get Bootcamp (if your Mac is on Intel) install Windows 10 or 11 by insider program - and you can have your ArchiCAD there as additional option - until Graphisoft searching incompatibilities with new OS.
Maybe Apple will understand soon that they again started to do sucks - as it was before in history. But until that you can have backup as Windows on your machine.
2021-07-06 04:40 AM
mikas wrote:It's possible the eGPU is causing some issues, but as I mentioned, I can get the same crash to occur without it plugged in. Could be some drivers maybe, though those are going to be the ones that come with the OS for Mac. When the eGPU is plugged in, I have told the OS to force Archicad to use it over the built in AMD 5500. But obviously can't do that if it's not plugged in.
It could be a driver problem with AMD RDNA GPU. Maybe try disabling your dGPU (whatever you've got, 5300M, 5600M..) and try again to crash, to troubleshoot that one out. There has been some talk about not so complete drivers with RDNA architecture for intel Macs earlier. I do not own any of those so I haven't tried it myself.
I'm considering eGPU too right now to help me jump to Big Sur, but if it's not perfect, or if it's unreliable that much, I might have to reconsider and stay at Mojave for now.
OT3. First there was a Motorola to PPC transition and only after that to intel. Now we bet on Apple Silicon. I have survived all of them, let us see what happens with this latest one. Huh.
2021-07-06 08:36 PM
Chris wrote:I should update that to say if the FLOOR PLAN is active when you make changes to the surfaces dialog box, the program works fine without a crash. I was also able to get a repeatable crash in the Section Elevation window by opening the Surfaces Dialog box (while the SE window was active) and altering the vectorial hatching for one of the displayed surfaces. Crash occurred upon closing the Surfaces dialog box and returning to the SE window.
If the 3D window is active when a surface is being modified (typically an alternate texture map is being applied to the surface) the machine briefly hangs after closing the Surface dialog box and returning to the 3D window, then the beach ball, then a crash.
If the change to the surface is made while the 2D window is active, everything works as expected without crashing. So that is a sort of workaround (though not ideal obviously).
2021-07-08 01:18 AM
2021-07-08 01:36 AM