Problem summary
Converting projects can cause baked Bake Points to go out-of-date
This issue only seem occurs when the Project Conversion dialog appears during project load.
E.g. When projects are converted from Mari 4.7v7 > 4.8v4, but not Mari 4.7v6 > 4.7v7.
Customer reported version
Mari 4.8v4
Customer reported platform
Multiple
Steps to reproduce
1) Open any project in Mari 4.7 or earlier
2) Create a Cloud node
3) Connect it to a Bake Point node and bake it
4) Save the project and exit Mari
5) Load the same project in Mari 4.8/5.0
6) In the Loading Project dialog, click Yes to convert
Expected behaviour
The Bake Point should stay up-to-date and green as nothing upstream has changed.
Actual behaviour
After the Shader finishes compiling, the Bake Point turns red/out-of-date.
Workaround
Unknown.
Reproduced by support
This bug has been reproduced in:
Mari 5.0v4 - Windows 10 - Only reproducible on CentOS 7.9 with projects from Mari 4.6
Mari 5.0v1 - Windows 10 - Only reproducible on CentOS 7.9 with projects from Mari 4.6
Mari 4.8v1 - Windows 10 - Only reproducible on CentOS 7.9 with projects from Mari 4.6
Mari 4.7v1 - Windows 10 - CentOS 7.9
Mari 4.6v1 - Windows 10 - CentOS 7.9 - regression Note: Bake Points in projects converted from Mari 4.5 > 4.6 go white, as if they are not baked, rather than red/out-of-date. The bake is still stored in the Bake Point.
Unable to reproduce bug in:
Mari 4.5v2 - Windows 10 - CentOS 7.9
Earliest version tested
Mari 4.5v2 - This issue doesn't appear in this version and has regressed