ID 315917 - Shader Compiling failures may have caused mip-map corruptions in user archive

Problem summary
Shader Compiling failures (caused by skipping versions during the upgrade conversion process) may have caused mip-map corruptions in user archive; resulting in loss of textures and limited export capabilities.

Customer reported version
3.3v1
Customer reported platform
windows10

Steps to reproduce

1) Open the affected archive in 3.3v1 (commented)

2) Notice the geometry and textures cannot be viewed due to a Shader Compiling error, unless viewed in 'Current Paint Target'

3) Attempt to export the layer. In most cases it will fail, or show mip-mapping corrupt areas over the texture.

4) Open the archive in 2.6v5, save and rreopen in 3.3v1

5) There should be no Shader Compilation error in 3.3v1 but the mip-mapping issues will persist meaning that the textures will need to be recreated.

Workaround
Ensure that you always include a version of 2.6 in your upgrade process.
Textures that are affected by the corruptions will need to be recreated manually.

Reproduced by support
Compile errors will persist in all versions of Mari 3 until correctly upgraded but can be viewed in 2.6v5 regardless.

Earliest version tested
2.6v5

Expected behaviour
Mipmapping issues should not occur during Shader Compile failure. Compilation should not fail if users skip versions.

Actual behaviour
Shader compile fails if the user skips 2.6v5 in the upgrade process. Mipmapping issues persist.