Seeing how Ogawa is superior in every way, and how little requests for HDF5 I’m aware of, I would say let’s remove it. IMO we should either properly support HDF5 or remove it altogether and clean up the code. Now that I’m working on improvements to the Alembic exporter, I’m once again seeing the #ifdef WITH_ALEMBIC_HDF5 conditionals in the source code, and I want to get rid of this. ![]() After I suggested to check whether that software had an update I never heard back, so I guess they also upgraded to Ogawa. As a matter of fact, I only remember getting such a request once, and that was to support very old software. It brings you advanced Maxwell Render technology in a simple, self-contained package. This product has been specifically designed for rendering in Maya with a simple yet comprehensive Maxwell toolbar. In the years that I have been maintainer of Blender’s Alembic code, I’ve seen very little requests to enable HDF5 support in an official release. Maxwell 5 Maya offers seamless integration, allowing you to work comfortably within the Maya interface. There is a build-time option WITH_ALEMBIC_HDF5 that can be used to enable HDF5 support in your own build, though. Ogawa replaced HDF5 and is smaller and much faster (4-25x) to read ( source).Īs long as Blender has had Alembic support, it has never supported the HDF5 format in any release. ![]() A bit of background for this topic: Alembic is not a single file format, it can be stored in two different ways: Ogawa and HDF5.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |