Hi all
I’m new to Blender (coming from Modo) and I’m animating a character via the Rigify Add on.
I’m exporting the animation from Blender via Alembic to render in Modo.
The workflow has been working really well but for some reason I’ve started to get export fails on several Blender scenes that used to work just fine.
As soon as I hit ‘export’, Blender just quits.
I know its a a needle in a haystack but does anyone have any ideas why certain scenes are crashing Blender on Alembic export and why they have just started to fail?
Does Blender generate a crash log anywhere that might point to a more specific issue?
The only thing that I can think that might have changed is that I added the Blender GIS landscape generator addon. I have since disabled it again but the issue persists.
Some of the scenes that involve the same rig export just fine. There is nothing else in any of these scenes as I only need the character animation,
I’ve found the crash file but to be honest I have no idea what I’m looking for here.
The last few lines are:
I meant more changes on the scene but you are right to check the addons too
The log should tell something about the location if the crash; maybe even segfault in or something… so if the rest looks similar this is in fact not very usefull. You might try some more informative debug levels because this tells almost nothing ( The Python backtrace is actually empty… ).
The only real change to the scenes is the inclusion of animation. Ironically the scene that fails most easily is the default scene that has the rig in it. I took all the other scenes from that and made versions on a per shot basis to animate with. Most of the animated scenes are okay and export fine. I havent added any extra geometry because I only need the animation so I think I can rule that out.
I’ve done a search on the crash file to look for segfault but there is nothing there. Debugging is a bit beyond me unfortunately. How might I go about this?
I should say that this is all in Blender 4.1. In case its relevant.
Set the logging verbosity level (higher for more details) defaults to 1, use -1 to log all levels.
and writing into a file; linux directly writing stdout and stderr to differrent files
blender --log-level -1 > mylog.txt 2> myerr.txt
if i remember correctly this should also work on windows but i’m not absolutely sure about that.
So those may have some more info and may worth uploading if no other user have some “problem experience” with alembic ???
