Skip to main content
Participant
July 10, 2026

Painter 11.1.3 | Output color spaces Not Compatible after reopen

  • July 10, 2026
  • 3 replies
  • 32 views

Windows 11 | Painter 11.1.3 | Nvidia GeForce RTX 3080Ti | 128 GB RAM | ADM Ryzen 9 5900X 12 Core

 

When I create a new File I set a OCIO (Custom, ACES 1.2 or ACES 2.0 doesn’t matter). Then I load in external texture files and set their Output color space. It doesn’t matter if I set this manually or automatic via OCIO rules All good and works like that:

After saving and reopen the file I lose all the “Output color space” OCIO rules/settings. It displays not compatible and only the defaults are available. 

When I check the Project Configuration it is still using the correct OCIO file and there is also no Error/Warning in the LOG: 

Does anyone else has this issue? It is a critical Bug in our case because textures load wrong and are not correctly exportet. Also it is very confusing. Sadly we can’t go to Painter Version 12 yet because of the python version switch.

 

Best regards,

Timo

    3 replies

    timo_lavaAuthor
    Participant
    July 20, 2026

    I checked this today in the Substance 3D Painter, version 12.1.1
    Build 5594 - 01d9317df5da2ac42d688b9acdd2ac1e537a5047
    also without any extra pipeline and the issue is still existing….

    Cyril Dellenbach
    Community Manager
    Community Manager
    July 21, 2026

    Sorry, I forgot to keep you posted, but we’ve in fact investigated after reading your post and we confirm this is an issue with current versions. We’ve put the problem in high priority, so except if there is a huge blocker to solve the problem, the fix should see the light in the coming minor bugfix.

    Cyril Dellenbach (Micro) | Product Manager | Substance Painter
    timo_lavaAuthor
    Participant
    July 21, 2026

    Thanks for your support! Would be great to have it in the next minor bugfix release.