Problem summary
Channel Transfer triggers various unexpected behaviours with specific Project, depending on the setup used. The DIFF Channel used in testing is 16k 32-bit. The Channel also has a MipMap corruption at the back of the head, as per the gif attached. The original Object has 1 UDIM, while the new Object used in the Channel Transfer has 13 UDIMs.
Customer reported version
Mari 6.0v2
Customer reported platform
Windows 10
Steps to reproduce
Please note that certain adjustments need to be done based on the descriptions under
Actual Behaviour. The following steps are the steps that are common to all behaviours:
- Launch Mari.
- Open the attached Archive.
- Select Channel > Channel Transfer.
- Set up a transfer of the DIFF Channel into the new Object.
- Select Ok to initiate the Channel Transfer.
- Wait for the Channel Transfer to complete in order to experience the chosen behaviour.
Expected behaviour
Channel Transfer should complete without issues.
Actual behaviour
Depending on the setup used, the following behaviours have been experienced:
Linux - RTX A4000 16 GB
- Using the Channel Transfer's default settings results in a popup message that only says "Internal Error". Once the message is closed, Mari crashes.
- Changing Object Has Moved to Yes and Bleed Edges to No causes only certain parts of the DIFF channel to be transferred, while the rest is transparent, as per images attached.
- If the MipMap corruption in the DIFF Channel was removed before Channel Transferring, such as by using Bake to Paint Node on the affected Paint Node, then Channel Transfer is successful, regardless of the settings used.
Windows - Quadro M6000 24GG
- All Channel Transfer settings tested resulted in a popup message that only says "Internal Error". The Node Graph of the Object meant to receive the Diff Channel didn't receive anything. On Windows, removing the MipMap corruption does not prevent the error.
Workaround
Unknown.
Reproduced by support
This bug has been reproduced in:
Mari 6.0v2 - Windows 10 - CentOS 7
Mari 4.2v1 - Windows 10 - CentOS 7
Earliest version tested
Mari 4.2v1 - This issue appears to be in all tested versions of the product