Animation Nodes with python3.10 Mac giving me the following error when installing in Blender 3.3

[Apzzpa]

[Apzzpa]

I have no idea about Python or coding, or how to compile an addon myself so I thought I would raise it here. If anyone can help me I would really appreciate it. Thanks

[OmarEmaraDev]

Could this be the same as #1886?

[Apzzpa]

Hi yes, it is. Thank you

…

On Sat, Oct 29, 2022 at 10:21 PM Omar Emara ***@***.***> wrote: Could this be the same as #1886 <#1886>? — Reply to this email directly, view it on GitHub <#1887 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A34O4265QSYSB5D6C65ZSSLWFWIMDANCNFSM6AAAAAARR5ZGIQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[pkej]

animation_nodes_v2_3_macOS_py310.zip

Just compiled it. Works in Blender 3.3 M1 Mac, macOS 13.0 Ventura, Python 3.10.8. #1886

Info from another thread, since you won't be able to verify the developer you'll be asked to do manual verification for every library. Very tedious. Another user shared this:

xattr -d -r com.apple.quarantine ~/Documents/Blender/addons/animation_nodes

Would work. You might have to find out which directory your addon lives at. On my machine it is in:

xattr -d -r com.apple.quarantine ~/Library/Application Support/Blender/3.3/addons/animation_nodes

The zip might probably work on Blender 3.2/3.1, but I haven't verified myself.

[pkej]

I've installed it on 3.2, 3.3 and 3.4. I recommend running it on 3.2. In a test with 2500 instances of a bevelled box on a isosphere and an effector, there was a sudden drop when adding "mix vectors"-node.

The same file was unwieldy when reloading in 3.3 and 3.4, but it worked better in 3.2.

[Apzzpa]

Hey Paul, thanks so much for your help and advice. Really appreciate it

…

On Mon, Oct 31, 2022 at 9:27 PM Paul Kenneth Egell-Johnsen < ***@***.***> wrote: I've installed it on 3.2, 3.3 and 3.4. I recommend running it on 3.2. In a test with 2500 instances of a bevelled box on a isosphere and an effector, there was a sudden drop when adding "mix vectors"-node. The same file was unwieldy when reloading in 3.3 and 3.4, but it worked better in 3.2. — Reply to this email directly, view it on GitHub <#1887 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A34O423LPN3MBO3YSFJE5J3WGA2UJANCNFSM6AAAAAARR5ZGIQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Aliprandini]

Couldn't install with all that advice on Mac Intel. Blender 3.3, ventura 13. The same error is appear.

[pkej]

Get version info from the packages:

python --version
/Applications/Blender.app/Contents/MacOS/Blender --version

Then start Blender from command line like this:

/Applications/Blender.app/Contents/MacOS/Blender 

Look for:

Registered Animation Nodes

In the output. If not. Remove Animation Nodes. Restart Blender. Double check that you have installed the right version of animation nodes. Compare to the python version string. Install animation_nodes and wait for a while, before clicking the checkbox for activating. After activating wait even longer to make sure it registeres everything. Restart blender once more, and check the output one more time.

The important stuff is that python is at 3.10.x (mine is 3.10.8).

[Aliprandini]

As Blender 3.4 has new benefits I try it with AN2.3 compiled above with the same result:

[pkej]

I've built it on Apple Silicone, I guess that might be the problem? I have the same error in 3.5 alpha, so I have to rumble through my head and build it one more time, I can't remember how I did it the last time. I'll get back to you.

[pkej]

This is the latest build for 3.5-alpha (hash: 485c5abedc3a), built on Apple Silicon, macOS 13.0, Python3.10.8.

I tested with this file: https://bradley-animations.gumroad.com/l/sAsRo?layout=profile

• 3.5 alpha
• 3.4.0
• 3.4-alpha
• 3.3.1
• 3.2.2
• 3.1.2

When enabling Animation Nodes it starts instantly on 3.1.2, 3.2.2, 3.3.1 and 3.4.0, on 3.5-alpha it takes "forever" to load, as did on 3.4-alpha.

animation_nodes_v2_3_macOS_py310.zip

[pkej]

Couldn't install with all that advice on Mac Intel. Blender 3.3, ventura 13. The same error is appear.

I guess cython being C-bindings I need to compile on an Intel Mac. I can't promise when, I'm off to a party, so I might forget this... Try to @pkej in a comment on this issue to remind me :)

[pkej]

You could build Animation Nodes yourself. I don't know if my older Intel Mac can run the latest versions of macOS and Apple tend to change some of their bindings now and again.

This video shows you how to install cython and build AN. Just use python3.10 and pip3.10 where the video says Python, pip, python3.7 or pip3.7.

https://youtu.be/pNDArhsuRfo

[pkej]

TEST: Could you download the attached file and check if it works? It doesn't work on my Apple Silicon. It is built using github actions.

I just tried to install the command line tools for Xcode on the Intel Mac, and it stopped downloading after about 15%, and nothing for an hour. Therefore I can't compile for Intel Macs. I'm sorry.

EDIT: Updating the OS so I will test again when it is ready.
animation_nodes_v2_3_macOS_py310-intel.zip

[pkej]

Tested it on the Intel Mac (where I'm not able to install Python 3.10.8 in the OS for some reason) and the blend file linked above works. Test it on your mac on blender 3.4 and let us know if it works and can be distributed, @Aliprandini, @Apzzpa

[pkej]

@OmarEmaraDev I forked this repo and added "architecture x64" or similar to the yaml for build. However, I haven't been able to setup a matrix, so I can't get it to build both versions in one buld script. I think you could create a separate file just for macos_latest and architecture x64 and it will build the artifact separately.

[OmarEmaraDev]

The daily build available in https://animation-nodes.com/#download is for Intel x86 MacOS. So you don't need to comple one yourself. A daily build for ARM MacOS doesn't exist however, so you will need to compile it yourself.

@pkej Can you elaborate on that? What is the difference between x64 and x86-64 in this case?

[pkej]

I don't honestly know, I tried x86_64 and it failed, so I googled around and found that x64 should work. And my preliminary test shows it works.

Anyway, as long as I don't know how to a) add a matrix for architecture, b) just add it to macOS, and c) have it execute the matrix, I can't automate it properly to produce the ARM64 version.

OK, got you, about the download page, then I hope the guys in this thread who tried the ARM64 on intel reads your comment and downloads from the download page.

I will try to have autobuild of ARM64 so I can just rebase from you to trigger new builds. I learned some GitHub actions from all of this, and I will get to the bottom of how to compile for different architectures.

[OmarEmaraDev]

@pkej The reason why we don't have auto builds for ARM64 is that Github doesn't provide ARM64 runners in their free tier. So we are just waiting for them to add those machines to the free Github hosted runners.

[pkej]

aha! understand. Just ping me when you need me to build a new version until that happens.

[OmarEmaraDev]

@pkej Alright. Thank you!

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.