Search Issue Tracker
Won't Fix
Votes
5
Found in
2017.4.0f1
2018.4.0f1
2019.2.0a1
2019.2.9f1
2019.3.0a1
2020.1.0a11
Issue ID
1191876
Regression
No
Non-RGB images are shown as red question marks when loading them using UnityWebRequestTexture.GetTexture()
How to reproduce:
1. Open the "SampleScene" in the unity-image-201929 project using the EnvIronman VM
2. Enter play mode
3. Press 'B'
Expected results: An image is loaded successfully
Actual results: Red question mark is shown instead of the image
Reproducible with: 2017.4.34f1, 2018.4.12f1, 2019.2.11f1, 2019.3.0b9, 2020.1.0a11
Additional notes:
1. The images that is failing to load are using embedded color profile - Coated FOGRA39 (ISO 12647-2:2004)
2. Pressing 'W' during play mode loads a RGB/A or CMYK/A images successfully
3. Importing the "broken" images via drag & drop into the Editor works without any issues
Comments (2)
-
St-Aaron
Feb 18, 2021 07:28
Issue still present in 2020.1.16f1.
-
Suryakant
Apr 30, 2020 14:25
It is still present in 2019.3.2f1. Any ETA to fix this? or any temp fix?
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- DownloadHandlerScript.CompleteContent is called twice when building for WebGL
- Scene view has Y coordinates of the Screen Position node flipped when some of the URP features are disabled
- Volumetric fog shader variants are missing from build when "Strict Shader Variant Matching" is disabled
- Unnecessary modifications clutter the Scene when using a RectTransform driven by a LayoutGroup in a Prefab
- Files in the target folder are deleted without a proper warning when building an iOS project
Resolution Note:
Every few months we look at bugs which we have not had the opportunity to fix yet. We try to be as diligent as we can and want to prioritize bugs that are causing issues with shipping and frequent pain points in day to day works. To ensure we are targeting the most important bugs we regularly close out older bugs that have not reached this threshold over the past months. The bug you have currently raised has not met this threshold for fixing over the last few months. If you feel this bug has been closed by mistake then please reopen the case.