Apple Silicon
Comments
-
Well, in the past V20 did not work on Big Sur beta.
First V21B did.
But with following releases that always switched between
both versions, which runs and which not.Currently on Intel Mac Big Sur, both V20/V21 are running.
0 -
For me I can't print in V21 on Intel. I get crazy lines all over the place and it crashes opening some drawings. I sent in a bug report to them so I will will just pay for Autocad until V21.2 or 3 or 4 or V22. I was hoping to save some money but man I didn't realize how much I missed editing dynamic blocks. Autocad works perfect on M1 as a side note...
0 -
V21 does definitely not work at all for me on Apple Silicon.
But V20 doesn't really work either.
In 40% of cases V20 offers the same bahavior like V21 and crashes
already when trying to open existing files, while a second try may
be successful. (ok that is something Mac users are used to anyway)
But today V20 will crash with any attempt to open anything.0 -
Hmmh,
all my Apps are running fine.
3D Apps like Modo, from the beginning, with current Betas even better.
Cinema4D in my R21 version, 2 years behind, flawlessly,
Vectorworks 2021 like a charm, Blender and Twinmotion, also via Rosetta,
and everything peripheral Apps, except 32 bit Apps, without any issues
on M1 Mini.Just Bricscad V20 does not really, V21 not at all.
I really start missing Direct Modeling and Bricscads AI.0 -
No V20 doesn't work for me either.
(11.3 latest Public Beta)It crashes more often that it opens a file.
0 -
Michael & betazero, I see the latest beta version BricsCAD-V21.2.01-1-en_US that came out yesterday addresses the 22 Service Requests for "M1 Rosetta" so hopefully V21.2.01 will now work on your M1's.
Really keen to see if that is the case. You would need to register as a Beta user to be notified of it I think.
V21.2.01 does seem smoother than V21.1.06 on my Intel MBP but I have not done much on it yet. Communicator is also still working correctly.0 -
As it is likely a Beta so I would not talk about it in public.
But I agree with your experiences ....
0 -
I realized there is now also an official V21.1.09 for every OS.
Did any one check if it will also run on M1 Macs ?0 -
V21.1.09 is running very nice on my 2018 i3 Mini, not really interested in even loading it on my M1 as I'm sure it won't be a great experience.
0 -
Hmmh,
Went from the Beta we aren't allowed to talk about to official V21.2.02
and hmmm it is still crashing a lot on my M1 Mini.
Have to test a bit more though ...But Now my V20 crashes all the time when I want to open ANY file.
I had the latest Big Sur 11.3 Public Beta yesterday (Beta5 ?)
I had the new 3DConnexion Beta driver yesterday.(3D Connection is mentioned on Top of Tasks, but Bricscad is mentioned as crashing task though)
((At least not RedSDK as always))So I am not sure if that is the V20 weakness crashing after V21 being installed,
(mentioned by "forgot the user name) or just a new thing.
Does V20/V21 work for you with latest official Big Sur 11.2.x ?0 -
(mentioned by "forgot the user name)
It was @betazero of course ....
0 -
Who little old me? Yea V21 and V20 do not play nice on Mac at least.0 -
official V21.2.02
and hmmm it is still crashing a lot on my M1 Mini.Filed some Service Requests.
The good news :
The developers are aware of those issues and are working on fixing them,
so that (later ?) V21.2 will be able to work on M1 Macs via Rosetta.0 -
-
I have 11.3 since public Beta.
It still did not fix the BiG Sur problems
(after wake up : external disk not thrown out properly, monitor awakes at wrong resolution, ....)I see V20 crashing when I try to open an existing file from Start Screen.
V21 works so that I can examine my files.
But there still are lots of M1 issues.
Opening Command Line can freeze Bricscad, File Tabs gone, GUI/Palette issues, OpenGL issues, ...
which are being in repair. But I would wait for the next release with fixes, before using Bricscad
seriously on M1.0 -
Thanks @Michael Meyer.
I noted you had the 11.3 Beta running but was wondering if the final Gold Master was an improvement. Really waiting to see the M1 running BricsCAD properly and hopefully natively (not on Rosetta) before getting an M1 (M2?). Hopefully the 14 and 16" MBP will also be released by then.I should add I am still on Catalina (10.15.7) and V20 & V21 are OK on this 2018 Intel MBP. Reluctant to upgrade to Big Sur until I feel confident it will not break my system. Spare 2015 MBP is still on 10.14.6 as it runs some 32 bit programs. Might update that to Big Sur first.
0 -
I use Big Sur only since first public beta and there were issues.
I think the most Big Sur issues are already fixed.
(beside the long lasting things that might even happen in Mojave)
So I would not mind going Big Sur on Intel Macs.It is more about these extra issues when running Bricscad on M1
under Rosetta. These were said to be fixed.
Yesterday I noticed a new V21.2.03, but no M1 related changes.
So it might need a few more .0x releases.
But I am confident that will happen before Apple releasing the first
Pro MacBooks in 2nd half of 2021.If Bricscad finally will run ok on Apple Silicon without issues,
I am fine for now. Speed and capability is pretty ok on my M1 Mini,
even with Rosetta penalty. So I could at least work with Bricscad.There were hints on the forum that running behind fixing OpenGL
issues may not be very productive and that Apple Silicon might need
a bit more love and some deeper changes.
But I don't expect such a Apple Silicon optimized Bricscad before V22.
(Which may still happen before the large and more powerful iMacs
may be available)0 -
Running V21.2.04 on my M1 and am extremely pleased with the performance. The program loads unbelievably fast and is loading large drawings up in less time than my i5 Win 10 machine, no crashes or any glitches that I can tell. Super happy!! Thanks Bricsys team!
0 -
Is 21.2.04 for Mac out now - great !
(I searched every day for it ...)I think there are still a few bug fixes on their way.
But I can also state, even in the current M1 support level, Rosetta and such,
for me it also works with very huge files more fluent than on my PC
(Ryzen3950X 16 core, AMD RX 6800 16 GB VRAM, 64 GB RAM)
Of course with 10 GB or more Swap File.Just that I can't open 3-5 of these files or more CAD/3D Apps at the same time
0 -
Is there still an issue with the cursor vanishing and being jittery? I am going to have to try it for sure.
0 -
Hmmh, I still have issues.
Strange artifacts for selection marquee in 2DWireframe.
Slow in BIM View Style and again freezing.
(Just a 53 MB only Revit imported file)I don't think V21.2.04 did anything in favor of M1 for now.
I think it was just a hot fix for a general, non M1 related, issue.0 -
I’m just using the lite version as I only do 2d layouts. Nothing that requires really anything. Possibly the more intensive drawings, etc are more taxing on the system.0
-
Yes, strange demanding files here.
0 -
Dear Michael,
Just that I can't open 3-5 of these files or more CAD/3D Apps at the same time
likely caused by the limited amount of RAM (16 GB) that M1 can access/use ? The rumours tell that M1X will allow more memory ...
many greetings !0 -
Yes, Macbook Pros in summer may be amazing and another step forward.
But it looks like a really powerful 27" iMac replacement may need
10 month or so in the worst case.0 -
@Michael Mayer said:
Hmmh, I still have issues.Strange artifacts for selection marquee in 2DWireframe.
Slow in BIM View Style and again freezing.
(Just a 53 MB only Revit imported file)I don't think V21.2.04 did anything in favor of M1 for now.
I think it was just a hot fix for a general, non M1 related, issue.Bricscad V21.2.05 is now available.
Realese Notes for Mac mentione a fix for the OpenGL problems under
Rosetta 2.
I am excited !0 -
@Michael Mayer Now that MacOS 11.4 is out and Bricscad V21.2.05 is available how is the combination running on your M1 ?
With the WWDC about to happen in less than a day, where the new MBP 14 & MBP 16" with M1x or M2 silicon is rumoured to be announced and my 2018 MBP showing keyboard issues I am exceedingly interested in your experience with that configuration.
0 -
I had more overall issues in general with 11.4.
I'm on Beta 11.5 now which looks like before again.
But for me basically everything still like 11.0 Public Beta from last August.
I don't see much progress in 11.x since then.I think V21.2.05 is definitely better on M1 and less crashing.
But I am still more annoyed by general Bricscad on Mac issues like
UI customization and GUI problems.
I don't think these problems are related to M1 in special.0 -
@Michael Mayer - Interesting.
I am running Catalina (on an Intel i9) and have also been having problems with the UI customisation on V21, particularly in the default.cui file going back to the original as installed settings after a crash. It also often changes the template to a default one and goes to imperial (instead of metric) for a new drawing.Easy to change and I have copies of a good file in the Library/Applications Support/Bricsys/BricsCAD/V21x64/en_US/Support/default.cui but it does seem to be worse in V21.
Disappointed that there was no mention of the new MBP 14" and 16" or M1x or M2 silicon at the WWDC today.
0 -
Yes, GUI problems on Mac has always been that way.
Recently I tried to save as a new Workspace, which made my Structure/Project
Panel have double entries. A bit later the whole Panel has gone.
When you right click on an Icon to add or remove Panels, these gone Panels look
still activated in the list and trying to switch visibility does no more work.Will have to try a Partial CUI again.
And maybe it is a good idea to add a few extra Profiles in User Profile Manager
to switch between corrupt and default settings and have a few spare Profile
Backups.Yes, that was a cool PR stunt from Apple.
No word about Apple Silicon and its Transition, nor Hardware at all.
Not even any word about what great success M1 was.
I enjoyed the keynote nevertheless and am looking forward to some of the
developer videos.They can prepare, organize and produce any Events freely offline.
They can publish such Events whenever it fits Apple best.
So I hope it won't take that long until they present the next generation.0
