Search Issue Tracker


Fixed in 2021.3.29f1, 2022.3.5f1, 2023.1.0f1, 2023.2.0a15

Won't Fix in 2020.3.X



Found in







Issue ID




“UnityException: Could not find the requested Platform Texture Settings” is thrown when multi-selecting textures



Steps to reproduce:
1. Open the user’s project
2. Navigate to AllIn1VfxToolkit → Demo & Assets → Textures → Trails
3. Select any texture(s) of the first three (Digital Trail) and any other(s)
4. Observe the Console

Expected result: No errors
Actual result: Error “UnityException: Could not find the requested Platform Texture Settings” is thrown

Reproducible with: 2020.3.40f1, 2021.3.11f1, 2022.1.18f1, 2022.2.0b8, 2023.1.0a10

Reproduced on: macOS Monterey 12.5.1 (Intel)

Note: Error “TextureImporterInspector.OnInspectorGUI must call ApplyRevertGUI to avoid unexpected behaviour” is thrown when after the steps one click in the Hierarchy

  1. Resolution Note (fix version 2023.2.0a15):

    Fixed in: 2023.2.0a15

  2. Resolution Note (fix version 2023.1.0f1):

    Fixed in 2023.1.0f1

  3. Resolution Note (2020.3.X):

    2020.3 has reached end-of-life.

Comments (5)

  1. ParhamXTT

    Aug 18, 2023 22:29

    It is not fixed

  2. N1warhead

    Aug 02, 2023 12:45

    Every single 2023 version has this issue, including the newest 2023 beta (2023.2.0b2).
    doesn't even have to be multi texture stuff, even single texture selection has this same exact issue, they all give this annoying AF error, so I literally cannot use 2023 AT ALL. Yes there's supposedly this whole edit the metadata file, yeah no, i'm not doing that BS. This is totally 1000% ridiculus and to think once it is finally fixed, we'll have to wait like 9 months to get a non beta version of it released.

  3. OlofAviron

    Jul 04, 2023 11:10


    If you are still noticing the "Could not find the requested Platform Texture Settings" error appearing in versions that should have been fixed, I would highly recommend reporting a bug (make sure to include a minimal project with repro steps!) as we definitely want this to be fully fixed.

  4. RyanGarber

    Jul 01, 2023 21:10

    @admin_8C - it says that it was fixed in 2023.2. You say you are using 2022.2, which is a year older.

    That said, I have tried the correct version (2023.2.0a20) and can confirm it is NOT fixed.

  5. admin_8C

    May 14, 2023 11:49

    Nope, it is not fixed !

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.