Jump to content
3DCoat Forums

Mac chat - any info about 3DCoats' performance on any new M1 machine ? - thx!


erb
 Share

Recommended Posts

  • Member

Hi everyone, this is mainly about #2 below.. but #1 is good for context.

1: I have planned to make a video of performance for 3DCoat on an i3 & i5 Mac with an iGPU.  I mentioned this earlier this year and have yet to do complete the video.  I'll get to it before too long!
**In case you're curious why; because 3DCoat performed well above expectations on my Mac Air from 2010  and I want to share any Mac-iGPU-performance info with people as there was almost-nothing to read about 3DCoat on Macs with iGPU.  #Knowledge Is good.
//The Mac Air from 2010 has an Nvidia GT320.  - I suppose that I expect similar performance from the 8th gen iGPU in the mac I'll be testing and we'll see..hopefully sometime this month!

2: Now that the M1 macs are released, I am curious about the performance of 3DCoat on any of the M1 machines.  I do not have an M1 to test.  So if someone has tested an M1, it would be nice to hear about your opinion of performance.

- Thx
Enjoy your week.

 

Edited by erb
correct error
Link to comment
Share on other sites

  • 1 month later...

1. Thanks for sharing. I had tested "3DCoat" on my old iMac (CPU i3 3.06 GHz, RAM 8 GB, GPU Radeon HD 4670, VRAM 256 MB) and "3DCoat" allows painting texture with resolution up to 2K and sculpting up to 2 million triangles with comfort performance (about and above 30 FPS).
2. We don't have a Mac with an M1 processor yet. But "3DCoat" uses proprietary Intel libraries for some functions (Sculpt > AUTOPO, Retopo > UV > Mark Seams > Selected > To ABF/GU/LSCM/Planar). Probably those functions will fail on M1.

Link to comment
Share on other sites

  • Member

Are you running the App directly or through Rosetta ?
I'd be curious how the mentioned intel based functions perform through Mac's Rosetta or if they just work.

I bought a new Mac this Summer.. it mostly sits gathering dust due to the underwhelming performance and heat it generates. I was thinking about selling it and buying an M1 Mac.. *shrug* IDK.

  • Like 1
Link to comment
Share on other sites

  • 1 year later...
  • Advanced Member
Posted (edited)

@SERGYI As this thread is more than a year old: how is 3DC 2022 performing on macOS? Does everything work?

And is there a chance Apple Silicon / M1 chips / Metal will be natively supported for more Mac power utilization?

Thanks.

Edited by Metin Seven
Link to comment
Share on other sites

  • Member
Posted (edited)

I have an M1 Mac Air, I can load Sergyi's linked build if anyone has any specific questions for me to test.

@Metin Seven

Q: "And is there a chance Apple Silicon / M1 chips / Metal will be natively supported for more Mac power utilization?"
A: While I can not provide an answer, I feel I should mention that the Dev Team is in Ukraine.  I think about them and Ukraine each day.

Edited by erb
condensed and clarified
  • Like 2
  • Thanks 1
Link to comment
Share on other sites

  • Advanced Member

@erb Any reports about 3DCoat's overall performance on an M1 would be much appreciated, particularly in the Sculpt Room, thanks.

And I also think about the 3DC developers a lot, and really hope and wish they will remain alright in these crazy times. War is madness.

  • Like 1
Link to comment
Share on other sites

  • 1 month later...
  • Member

I forgot to reply, my apologies to you.
Overall, it feels good. (using latest version on M1 Mac Air)
Without a specific context, I can only provide a general overview..

As long as you keep your detail work on the resolution levels that are generally expected ..  (AKA: don't try to sculpt a human from a 20million sphere).
• An object with:
<5 mil range = good
10 mil range = performance might hiccup on certain things like large radius brushes doing complex operations. Cuts can take a couple/few seconds.
15 mil range = a smaller radius brush feels good, a larger radius brush will hiccup. Cuts start to feel heavy.
20 mil+ range = stick to adding fine / small details. Resampling to 20mil range takes < 20 seconds avg. Cuts take  <20 seconds.

• Multiple objects of 3-5 million each seems fine. Hide whatever you're not working on.. etc.

..Please remember that this is extremely generalized.
IMO, the performance is good.
 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...