Search Issue Tracker

Fixed in Unity 2017.2.0f3

Votes

23

Found in

Issue ID

956693

Regression

Yes

[XR] "Unsupported texture format ..." error is displayed in the Editor

VR

-

-

Priority: 3Not yet prioritized for a release

-

Severity: 4Minor or cosmetic issue

This issue has no description.

Comments (20)

  1. 7f22b06f8f561669a99a1c5bb9d3e1ed?d=mm

    jeromeWork

    Mar 20, 2018 00:23

    Fixed? I'm still having this issue in 2017.2.0f3 with Oculus Rift

  2. Af32e20edaf1fe90d3386724854e8c75?d=mm

    JJones57

    Dec 18, 2017 04:49

    I am still running into this error when using the headset.

    Although running the game on the Mixed Reality Portal simulator works.

    THIS IS NOT FIXED

  3. E510be50dc2dcf910e6a84269e5b9b81?d=mm

    Makaell

    Dec 12, 2017 11:42

    Also having issues in 2017.2.0f3 with Oculus Rift

  4. 05fcbaf150c24d813219fc67bdab81fb?d=mm

    pwnd

    Dec 08, 2017 11:44

    Can confirm. Still present in 2017.2.0f3 with Oculus Rift

  5. 3e2ae4101faf1b19afa71b4540d5dac6?d=mm

    MrDude

    Nov 28, 2017 00:14

    I just filed a bug report using this thread's subject and asked them to change the status from "Resolved" and to then resolve it for real...

    Let's hope they listen. Touch wood

  6. B940618813c66043a1888dbb94e133de?d=mm

    MikePeters

    Nov 17, 2017 19:57

    Does this have to be resubmitted seeing as it is listed as fixed, even though, as a few have said, it isn't yet? Of which I can confirm as I'm receiving this error in a VR project.

  7. 14b4b1a75a5f1cac048fd3082ed9ea62?d=mm

    jasonrwalters

    Nov 17, 2017 17:52

    "Unsupported texture format 0x1B" in Unity 2017.2.0p2.

  8. 958e29074afa0b460e68375225595780?d=mm

    batpox

    Nov 17, 2017 17:50

    This is one of those very discouraging errors that really halts production. Please fix this.

  9. De2c4d1ae55f19d60bbbe896dd5b9c4f?d=mm

    adhocdown

    Nov 13, 2017 15:32

    Issue prevails in Unity 2017.2.03f

  10. 6d858a8443ed0e63be764709af5a2435?d=mm

    roger64093

    Nov 05, 2017 21:37

    Only workaround I found was to downgrade from 2017.2 to 5.6.4

All about bugs

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