- User Since
- Jul 30 2013, 12:03 PM (225 w, 3 d)
Thu, Nov 23
Tue, Nov 21
Please note that this isn't a bug in Blender. Animation Nodes have been redesigned recently to use a specific version of Cython. The reason was the massive speedups you were able to get with this. But as a result, AN is now dependent on a specific Python version (which is why you get that error). At the same time, the current development version of Blender has been upgraded to use Python 3.6, while the stable 2.79 still uses 3.5. Recompiling AN yourself using Python 3.6 *should* fix the issue for you, alternatively I believe that Blender can also be forced to use good old Python 3.5. Both is IMHO out of scope of the Blender bug tracker.
Thu, Nov 2
@Sergey Sharybin (sergey) Ups, thanks for clarification. Guess this can be closed then as invalid.
Sep 21 2017
I've tested this with a Blender version from the 18th of September, unfortunately didn't work for me. Same as Jan stated, if I copy my template the the AppData/Roaming location it works, but from my custom locations, neither user nor system template folders work. We're using the portable versions of Blender, and redirect unified settings to a server location so everyone shares the same install.
May 22 2017
May 16 2017
@Brendon Murphy (meta-androcto) Indeed this has been silently fixed somewhen, that's good news! Not sure when it has been adressed, but no crashes any longer
Feb 3 2017
@Thomas Beck (plasmasolutions) I Just checked out the master Branch and patched it with the current version of this patch here (and a few others in addition, like the SurfaceFollow Modifier one). But I haven't changed any ifndef defines due to the total lack of C++ experience. I was only dealing with Python and C# so far.
Jan 26 2017
FYI: Currently the patch fails to apply in three modules (tried applying in blender-v2.78b-release branch on commit c727bc7):
Jan 9 2017
I meant this guide: http://www.gizmoplex.com/wordpress/compile-blender-as-python-module/
Just verified the suggestions. Using the raw Pyhton console made no difference, import errors would remain the same. But following the guide here **http://www.gizmoplex.com/wordpress/compile-blender-as-python-module/** (especially the part of copying the needed libs over to the Python35 directory) made it work. Can now successfully use the bpy build!
Jan 6 2017
Thanks for your feedback,I will try your suggestions next Monday when I am back in the office.
Jan 2 2017
Dec 2 2016
@Bastien Montagne (mont29) HEAD BUMP You can close the report I guess. For one, the crash doesn't appear in newer Python versions, but further more my date format was nonsense. The formatter should have been:
@Vuk Gardašević (lijenstina) I've tested a version which I compiled on the 23rd of November (reports as 2.78.4), it crashes, but with some more latency. Testing VS2015 build, downloaded right now: WORKS! no crashes there!
Wasn't able to reply before as client projects kept me busy, sorry for the inconvenience.
Nov 15 2016
would propose the following fixes:
Nov 14 2016
Oct 24 2016
Oct 17 2016
Maybe even skip the "named", as afaik unnamed objects don't exist in Blender. Otherwise people might ask how to name them...
Sep 29 2016
@Julian Eisel (Severin) I tried to apply this as a patch today, but it failed for me (didn't find the lines to change). To I need to target a specific commit to make it work?
Sep 27 2016
Sep 5 2016
applying the patch currently fails, the kernel_types.h.rej file says:
Sep 2 2016
accidentally created ot twice, please delete this one
Sep 1 2016
Aug 31 2016
Jun 13 2016
Jun 11 2016
Jun 10 2016
found this dirty hacky workaround here:
I'm working on a script that will add some additional input sockets to a node group based on output socket names from another node (input image) in the Compositor. This is the script so far:
Jan 12 2016
Nov 19 2015
Oct 27 2015
Oct 18 2015
strage quirks... man I sometimes hate my keyboard...
Oct 7 2015
forgot to mention I am using the x64 Builds on two different machines, same behavior
Jul 24 2015
I am having the same issue too. We made a lot of use in a recent project of the file output node and rendered the passes to OpenEXR MultiLayer. Not every output file crashed however, it was very hard to reproduce the error. However we were still able to do the compositing without problems by using Blender version 2.72 for Comp. That one never crashed.
Jun 5 2015
same thing here, just one more thing: after confirming the "App has crashed" Windows Dialog, another line is added in the CMD Output:
Feb 26 2014
The weird thing is that this only seems to affect the 64bit versions of Blender. I tested with 32bit Builds on the very same machine under the very same environment and it didn't crash. So even the nvidia driver is identical.
Feb 12 2014