HayleyM

I have had SO MANY issues with Chief X15 Crashes on my 2020 M1 13" MBP and I almost never had monitors attached. When I reached out to tech support they basically just said "don't work in 3D" which is the entire point of Chief Architect for me as I am an interior designer... And I never use PBR anymore because even the simplest plans are painfully slow, I am always in Standard view (with lines but I've been turning those off to help). I was running Ventura until today when I updated to Sonoma, and now it's even worse. Now I can't even work in Cross Sections without crashing. It's become extremely frustrating.

@Ridge_Runner Yikes! Good call. I was half asleep when I posted that. Thank you!

Hey folks! Great news! I was working away on my 13" MBP M1 and wasn't even thinking about it and changed my camera view to Physically Based and... IT WORKED! Apple must have tweaked something in one of the Big Sur updates and now it works!!!! Very exciting news, for me at least! Also, in case anyone missed it, apparently X13 is supposed to run on M1 now...? I have yet to try it but I plan to install it soon to test.

No problem @benriver! I almost exclusively present Physically Based views to my clients since that became an option. Don't know what I'd do without it! Really hoping that Chief can port everything to an ARM chip model soon so that I can use my new baby to its fullest capacity!

@SNestor It is my understanding that the Physically Based camera view is different than the Real Time Ray Trace (which is the new, Windows 10 only feature). They are both camera views but one is actually a ray trace. I'm not enough of a computer person to understand the back end differences but I think the overall issue is that Chief Architect developers don't yet have enough information about the M1 GPU and its drivers. I believe this is why neither the PBR camera view or the RTRT works. But again, don't quote me!

Hi All. Benriver notified me that he posted on this forum about M1. I have had mine for about a week now, 16GB memory and 1TB SSD. Chief is running very well and I have Premier X12. It actually seems to be faster than my iMac at the office. My only issue so far is that the Physically Based camera does not work. @benriver I am able to get 3D renderings work just fine. I can see all my work in 3D using the "Standard" camera view. I believe Home Designer does not have the "Physically Based" camera view that @Chrisb222 asked about above. This is what does not work for me. It would be awesome to know if someone else is having this issue that has a Pro and runs Premier X12. I also exported my extensive User Catalog library from my iMac and loaded it and opened on the MacBook with no problems. Had no problems importing and using Bonus or Manufacturer catalogs either. I will post some screenshots below that might provide some context. 1. System Overview 2. Graphics processing report 3. What Chief Architect has to say about GPU 4. A kitchen plan, here you can also see how large my user library that imported perfectly from my iMac. Each folder has at least 10 items. 5. 3D view of the kitchen in the "Standard" camera view (shown selected up at top right). 6. 3D view of the kitchen in the "Physically Based" camera view (show selected in top right). Overall, I'm very happy with it. If I need a Physically Based camera view, I'll just wait and create it on the iMac at the office. Happy to try anything that anyone wants to test as well.

I just got a brand new M1 MacBook Pro 13" to work at home when necessary. I have a 2017 27" iMac at the office as my main computer. I would have waited for Apple to upgrade the MacBook Pro 16", or even the iMac, but my workload is such that I needed a home machine immediately rather than waiting until late summer/fall. I digress. Chief is working well. Everything is speedy on Rosetta 2. The only issue I'm discovering is that Physically Based camera views do not work. Screenshots below of a Physically Based camera view of a kitchen and the actual view taken from my iMac. I understand that Chief Architect is not currently supporting M1, but can anyone confirm if this is because of the GPU? Anyone having this issue with an M1 mini?