Problem summary
Importing an MNG made of paint nodes and/or bake points takes longer than importing an MNG made without any paint/bake nodes. In certain circumstances this performance hit can be severe (up to an hour, reported by the customer).
This appears to be affected by
a) the number of UDIMs the project has and
b) the resolution and bit depth of the paint node (ie. higher resolution = bigger performance hit).
Customer reported version
Mari 7.1v2
Customer reported platform
n/a
Steps to reproduce
1) Create a number of paint nodes
2) Export these nodes as an MNG
3) Import this MNG into a project with many UDIMs
4) Time the import time
5) Repeat the process but with an MNG made from non-image based nodes (eg. an HSV node)
Expected behaviour
Importing the MNGs should be very fast
Actual behaviour
The MNG which includes paint/bake points takes a lot longer to import than the second MNG.
Workaround
Creating the desired nodes directly in the project does not suffer from the same performance hit.
Reproduced by support
This bug has been reproduced in:
Mari 7.1v2 - Windows 11
Mari 6.0v1 (note: this is significantly slower than Mari 7/7.1) - Windows 11
Mari 4.2v1 - Windows 11
Earliest version tested
Mari 4.2v1 - This issue appears to be in all tested versions of the product