version check ?

[Alessandro Padovani]

Unfortunately it happens that users make confusion and don’t update all the parts of the plugin. I mean daz exporter + blender importer + mhx runtime. So it may help if the blender importer could check the dbz and mhx runtime for the same version. It may also check for the blender version if it is required.

If an old dbz is found to be not compatible a warning could be shown on import. We may also use the same version number for exporter importer and mhx to make things easier.

[Alessandro Padovani]

Please Thomas let me know if you’re not interested or if this is too difficult to implement, so I’ll close this one.

[Thomas Larsson]

There might be cases where a version check could detect inconsistencies, but to do so one must maintain some kind of changelog, which would add extra work. And knowing myself I suspect that it would eventually not be updated properly. Which would be worse than not keeping track of the versions at all.

The Blender version is checked in a lot of places, and the code should work with all versions back to 2.83. I occasionally go back and test.

The dbz format hasn’t changed significantly for several years, apart for the addition of hair guides. But older dbz files work fine unless you specifically need the hairs, so it doesn’t make sense to discard them.

[Alessandro Padovani]

Thank you for the explanation.