- User Since
- Nov 23 2021, 11:54 PM (52 w, 6 d)
Sep 25 2022
I think this is a very strange conclusion, @Germano Cavalcante (mano-wii) that you made. Original poster clearly stated that the problem is that only Face Corner attributes gets exported (in my case not even that), and you confirmed that it is the expected behavior. But that means that Alembic Export itself is an incomplete feature in Blender, and should be clearly marked as such in UI. Somewhere in the Alembic export panel, it should be stated that the exporter is limited to a certain number of features (such as face corner data only). If there are not limitations listed, then users will rightfully think that the feature is broken. We can spend hours or days trying to troubleshoot something that wasn't even supposed to work, so putting a line in an exporter saying "Alembic Import/Export is very limited, Click Here for details" would be the least that can be done.
EDIT: Or at least, the limitations of Blender's Alembic Importer and Exporter should be clearly stated and highlighted in the Documentation. Currently reading the Documentation for Blender's Alembic, we are led to believe the importer and exporter behave as expected, when in fact I'd say about a half of alembic functionality is covered.
Sep 20 2022
I too noticed memory leaks, I'm only rendering on Metal (not the CPU), it's Blender 3.2.0 on MacBook Pro 16 with AMD 5500M, 32Gb RAM. I don't use Persistent Data, and yet the memory is not freed so -depending on the scene complexity- the memory will often max out when rendering an animation. I did not try to render the same files as image sequences, just seen that note - that may help fix the issue for now.
Jun 1 2022
I tried to get a crash report to provide you with the stacktrace, but unfortunately as this bug freezes the entire MacOS the crash report is not saved at all. If you have any suggestions how I could provide you with more detailed/useful information, please let me know.
Apr 25 2022
Looks like it works correctly on M1 devices, but not on Intel/AMD combo. I tried it on my older MacBook Pro, which has Radeon 560x card, and it did not crash but I could not even get particles to show in the viewport (in none of the shading modes).
Apr 23 2022
Thanks for checking this. Please note that the error does not appear with low hair count, more less below 10 000. Also I have an AMD card, not M1, and it all worked fine before 3.1 - if all this info can help troubleshoot
Apr 22 2022
Yes it still happens, and let me give you more details.
Sometimes, Blender will crash without freezing MacOS.
It seems to be the problem with the GPU, because often the crash
will start by GPU glitching (screen artifacts), and then either
the system will frieze or Blender will show up normally again
for a moment and then crash.
Notice that when using Cycles rendering in viewport, it does not crash.
It only crashes when using Shaded or Wireframe views.
Hope this helps, let me know if you need any more information.
Jan 6 2022
Thanks @Andreu Pellisa (andre1) this is good to know (although in my case I'm exporting from Houdini so this is not an option).
Nov 23 2021
@nizar amous (zinar) thanks for the solution, however, as of version 3.0.0 2021-11-08 this workaround is no longer working. are there any other possible workarounds anyone is aware of? thanks!