Build 4013 under Monterey

[Dave Jochum]

I couldn't delay a computer upgrade any longer, so I have a new M1 Max Mac with Monterey. I knew, of course, I'd have issues, but I've had none of the problems documented. Here are what I've found with my first hour of work.

Select a newly created slab in plan view results in a crash. Every time.

Select a pre-saved 3D view, change various settings, right click and select "Redefine with Current Settings", and it reverts to former settings. Every time.

Model Views only partially work. I cannot get doors and windows to display properly.

Attempting to move a Trace Reference results in a crash.

I pray build 5000 is near release and it's stable.

[Barry Kelly]

---

@Dave Jochum wrote:

I pray build 5000 is near release and it's stable.

---

There is a preview available.

https://community.graphisoft.com/t5/What-s-new/Archicad-25-Update-5000-Preview-Released/td-p/328899

Have a read through the list of improvements.

There seems to be a lot of crash fixes.

If you are finding it not possible to work with 4013, there is probably no reason not to try this preview.

Barry.

[Dave Jochum]

Yes, I’ve read them too. Unfortunately not one of my problems listed above are discussed. But I’m thinking right along with you—how much worse can 5000 be than 4013?

Not being a code warrior, I don’t know what it takes to get a program as complicated as AC upgraded to not only a new OS, but new hardware/silicone and multiple platforms. I’m sure GS is hard at work, but the time lag seems excessive and it costs us significant $$.

Anyway, I’ll try out 5K Thu. and report back.

[Minh Nguyen]

Hello Dave,

Thank you for sharing the report and I am very sorry for about the experience!

At the moment, we are not aware of any specific crashes directly related to M1 chips. Perhaps the ones that you described here could have been reproduced on other systems as well.

As a start. I'm wondering if you could share with me some bugID numbers and the exact steps to reproduce the crashes?

Looking forward to hearing from you!

Best regards,

Minh

[Dave Jochum]

Hi Minh,

I'm glad to hear there are no known issues specifically with the M1. I imagine mine are all related to Monterey, as I ran big Sur until migrating to the new computer.

Is there a way to pull up bugIDs? I don't save them when they occur.

I am not able to reposition a Trace Reference without crashing every time. Workaround is to switch to the Trace in the foreground, reposition it with the working drawing view in the background, then switch back to the original.

Also, attempting to reposition a drawing within a frame will result in a crash. Workaround is to Fit Frame to Drawing, then resize and reposition the frame.

Others have been sporadic and I can't remember specifically what I was doing. I'll keep better notes.

[Eduardo Rolon]

FWIW running 24 and 25 preview versions without any issues doing the same commands that are crashing yours.

[Minh Nguyen]

Hi Dave,

If you send the detailed bug report and a bugID is generated in the end, it will be logged in a text file called SubmissionLog.txt. This file is located at:

• Macintosh HD/Users/<username>/Library/Logs (please note that the User's Library is a hidden folder)

Could you please send me this file for checking the crash reports sent to our system?

Thank you very much!

Best regards,

Minh

[Dave Jochum]

Minh,

This is odd, but the road map to Logs is <HD>/Library/Logs however there is no text file by that name anywhere on my computer. There is a second Library at <HD>/Users/Shared/Library/Application Support but no Logs folder or anything generated by AC. Other ideas?

[Minh Nguyen]

Hi Dave,

The correct directory is:

Macintosh HD/Users/<username>/Library/Logs

As I mentioned, the Library inside Userhome folder is a hidden one. Here are some methods to access this folder.

Could you please have a look again?

Best regards,

Minh

[Dave Jochum]

Ahh...Yes, Minh. I didn't realize it was a hidden folder. I emailed you the .txt file, though it seems to only contain reports prior to AC25. Let me know what I should do to get you better info. , if necessary.