!! THE FORUM IS UNDERCONSTRUCTION CURRENTLY !! WE NEED TO REPAIR THE PLUGINS DATABASE. 8(
Until we fix this issue, you can ask questions via our social media accounts below.
For Bug Report use the Support Ticket System. 😉
Just a note on macOS and M1 compatibility.
As is always the case, Apple don't always make everything easy for developers and while BaseHead is moving towards M1 compatibility, there are still some kinks to be straightened out.
If you are a user of the Cloud Pack Manager (CPM) store you may have to launch BaseHead in Rosetta compatibility mode or you will see a "Degrader Error" due to a plugin used by CPM which is not yet M1 compatible. Running in Rosetta mode should resolve this and we are looking into possible fixes for this.
This same problem also affects the use of things like the M/S function in BaseHead and the use of plugins in the process panel. Lots of moving parts to make compatible for M1 processors and will be ongoing work so please get into the Betas when they release to let us know of any problems.
Additionally, because of the differences between an M1 and Intel processor you may also find when running in M1 native mode that your license file is not being recognized when using a system bound license. A quick solution to this is to switch your license to "Floating Cloud" license on your BaseHead account which you can find out how to do here:
https://baseheadinc.com/index.php/knowledge-base/convert-license-to-cloud-key/
When do you estimate that your app will be 100% compliant with M2 processors?
Ron. I could be wrong but there is no difference between M1 and M2 regarding code.
Apple Silicon should be Apple Silicon. Post a link if you find some info on the web of other programs not working on M2 that were with M1
thx!
Also this is an old pinned post that I just unpinned.
BH is 100% Apple Silicon compliant for months and months now. 😉
