- User Since
- Sep 12 2004, 3:45 PM (705 w, 4 d)
@Atomic (atomic) please attach example files to the task description, so that people interested in solving this don't have to read through each individual comment to see which file(s) they should be using.
Also see e12c31100. Guessing for default values is a tricky thing, especially since Alembic doesn't seem to have a standardised property for the curve resolution (I'm gladly proven wrong on this one). Having resolu=12 is fine for a simple case like T53839, but brings down Blender to a crawl when importing animated hair from another package.
Wed, Mar 21
This is fixed in 09c88fed1f58df642c7a13fc5a32057b7160f85c
Tue, Mar 20
Mon, Mar 19
@Johannes Dietmar Breuer (JD) where did you get the files for 2.79b? If you're basing this on the daily builds, then you're not looking at what will become 2.79b. The daily builds are based on the master branch, which indeed has moved to Python 3.6. However, 2.79b will be a different build, and include the changes listed in T54255.
Sun, Mar 18
Fri, Mar 16
Thu, Mar 15
Wed, Mar 14
Oops, thanks for correcting that!
Tue, Mar 13
Resolved in rB50dde3d01ac5
Sat, Mar 10
Fri, Mar 9
Thu, Mar 8
LGTM. Just found one thing that could be improved, but use your own judgement in that.
Wed, Mar 7
Tue, Mar 6
Looks good, just a few style issues to nag about.
Fri, Mar 2
Thu, Mar 1
Wed, Feb 28
I'm making sure this is handled in BAT🦇; see commit 8ae400acbeb.
The webserver isn't the only thing that I'll address. The current code of BAM is quite a mess, and it's very hard to figure out what's going on. I'm talking about conditionally defined inner functions with duplicate names, which are undocumented. There is a tuple indexed lookup depending on the endianness for every read on a blend file, even though the endianness of that file will not change. It's also the inconsistent ways in which reporting is done throughout the project (logging module, print statements, reporting callback functions, conditionally-defined functions, yielding strings). Cyclomatic complexity of the BAM code is also very high, whereas there is no way to easily measure unit test code coverage due to the non-standard way of doing unit testing.
Tue, Feb 27
Looks good to me :)
Mon, Feb 26
The blendfile parsing, and writing string properties, is all ported from BAM as of commit 127f357e49acc4c144d9c49c10f875ac91fc942e.
Sat, Feb 24
Fri, Feb 23
@joel heethaar (joel_nl) I've added Brecht's script to Flamenco Worker, to the T53099-gpu-rendering branch, but I haven't created anything around that yet. Can you test that the script works by adding --enable-autoexec --python "/path/to/flamenco-worker/flamenco_worker/enable_all_gpus.py" to the blender variable in your flamenco-manager.yaml?