Skip to content
Compare
Choose a tag to compare

just a recompilation of the script against python 3.10 via github actions.

In order for a manual recompilation just run
python make_release.py on your desired platform, with python 3.10 being installed (and cython, too. with pip)
Or alternatively, run
python setup.py build_ext --inplace from the "sources" folder.

This is a recompilation of the mac OS version in order to get a "fat" binary or universal binary for both intel and M1 / arm macs.
See the setup.py for more details.

Edit: updated the mac zip for arm64e instead of arm64

2f932a0
Compare
Choose a tag to compare

just a recompilation of the script against python 3.10 via github actions.

In order for a manual recompilation just run
python make_release.py on your desired platform, with python 3.10 being installed (and cython, too. with pip)
Or alternatively, run
python setup.py build_ext --inplace from the "sources" folder.

Since I do not own a mac with M1 chip, i am still investigating on how to cross compile from an intel mac for M1.
Probably this is done by adding '-aarch64' or '-aarm64' or some flag like that to the compiler.

Github has also no M1 / mac os ARM hosted runners yet.
So I need to find out how to cross compile this from my local machine or an intel mac runner.

fe11cab
Compare
Choose a tag to compare

just a recompilation of the script against python 3.9 via github actions.
Linux version may require a python .so lib....
TODO need to find out how to install libpython.a on the github runner and link statically against it.
Edit: seems this is not necessary with python 3.9 any more

Compare
Choose a tag to compare

includes the fix #4 by @William-Edward
The linux build has been built locally against the bundled python version of blender, still 3.7.x.
It may happen that linux distro builds use different python versions (for example 3.9) , then this version wont work.

The last release build was taken from Github actions, but it seems the Python setup there bases on a shared library
libpython3.7m.so.1.0 instead of the libpython3.7m.a static build.
Not sure how to set this up in github actions...

For now, i will build the linux builds locally on my machine, which uses blender's static python setup.

60385f5
Compare
Choose a tag to compare

Built against Python 3.7 ! (instead of Python 3.8, blender 2.90 still seems to use Python 3.7)
includes the fix #3 by @MarBasso.
Additionally a setup for github actions (to build binaries automatically when a commit happens) was made.

d4cd1bd
Compare
Choose a tag to compare

Built against Python 3.8 !
includes the fix #3 by @MarBasso.
Additionally a setup for github actions (to build binaries automatically when a commit happens) was made.

Compare
Choose a tag to compare

fixed baked UV rendering

just tricked blenders pointcache to accept angular velocity data, by enabling rotation and angular velocity mode "RANDOM". Then overwrote simulated data (not relevant in molecular) with the UV data, which then is stored in the pointcache each frame. When baked, it will be available in rendering and after loading the blend file, too.

151fdcd
Compare
Choose a tag to compare

fixes for missing context.scene.update() function and "Set Active UV" operator as well as for "Bake UV after ending"

Compare
Choose a tag to compare

fix for correctly resetting the cache prior to re-simulate, else parameter changes are not taken into account
because the cache is just played back again.