Welcome to mirror list, hosted at ThFree Co, Russian Federation.

git.blender.org/blender.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2019-11-29Alembic: fixed unit test for exporter API changeSybren A. Stüvel
2018-11-26Cleanup: unused vars, importsCampbell Barton
2018-07-03Cleanup: pep8Campbell Barton
2018-03-01Python tests: Split re-usable test related functionality to a moduleSergey Sharybin
The idea is to avoid re-implementing this for an upcoming FFmpeg tests.
2017-06-19Alembic tests: make failures a bit easier to diagnose.Sybren A. Stüvel
2017-04-28Fix T51331: fixes for Alembic unit tests on WindowsSybren A. Stüvel
2017-04-25Fix T51262: Blender CRASH with alembic fileSybren A. Stüvel
Also added a unit test for exporting & importing very long names.
2017-04-19Alembic import/export: added as_background_job optionSybren A. Stüvel
The ABC_export and ABC_import functions both take a as_background_job parameter, and return a boolean. When as_background_job=true, returns false immediately after scheduling a background job. This was the old behaviour of this function, which makes it very hard for scripts to do something with the data after the import or export completes. When as_background_job=false, performs the export synchronously, and returns true when the export was ok, and false if there were any errors. This allows further processing. The Scene.alembic_export() function is deprecated, and will be removed from Blender 2.8 in favour of calling the bpy.ops.wm.alembic_export() operator. As such, it has been hard-coded to the old background job behaviour.
2017-04-19Alembic export: made hair/particle export optional.Sybren A. Stüvel
The export is still slower than needed, as the particle systems themselves aren't disabled during the export. It's only the writing to the Alembic file that's skipped.
2017-04-18Alembic import/export: write curve resolution to user propertySybren A. Stüvel
Curve resolution isn't natively supported by Alembic, hence it is stored in a user property "blender:resolution". I've looked at a Maya curves example file, but that also didn't contain any information about curve resolution. Differential Revision: https://developer.blender.org/D2634 Reviewers: kevindietrich
2017-04-18Alembic unittest: pass unknown CLI arguments to unittest.main()Sybren A. Stüvel
This allows specifying test names on the CLI, in order to run only one of the tests.
2017-04-18Alembic export: fixed curve type and order.Sybren A. Stüvel
The order number written to Alembic is the same as we use in memory, so the +1 wasn't needed, at least according to the reference Maya exporter maya/AbcExport/MayaNurbsCurveWriter.cpp, function MayaNurbsCurveWriter::write(), in the Alembic source code. Furthermore, when writing an array of nurb orders, the curve type should be set to kVariableOrder, otherwise the importer will ignore it.
2017-04-14Alembic import: fixed dupligroup export when the dupli-empty has a parentSybren A. Stüvel
2017-04-14Added simple unittests for Alembic exporterSybren A. Stüvel
This test checks that a set of cubes are exported with the correct transform, both with flatten=True and flatten=False. This commit also adds an easy to use superclass for upcoming Alembic unit tests.