Search Issue Tracker
Fixed in Unity 2017.1
Votes
12
Found in
5.6.0f3
Issue ID
899324
Regression
No
Texture Arrays work incorrect (only one Texture is displayed) in Standalone builds
Reproduction Steps:
1. Open User's project
2. Open "Example" scene
3. Notice how texture looks
4. Build to standalone and run
5. Notice that texture is incorrect
Expected behaviour: Same behaviour in standalone as in editor.
Actual result: Texture array looks incorrect (only one texture) in standalone.
Reproduced on versions: Unity 5.6.0a6, 5.6.0f3, 2017.1.0b1
Could not make it work correctly on 5.5
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
- Unity crash in SerializedFile::ReadMetadata<false> when AssetBundle. LoadFromMemory() is called
- ProceduralMaterial.ClearCache() on "Do Nothing" Substance triggers RebuildTextures
- Setting "Default Behavior Mode" to "2D" breaks HDR rendering
- Crash in GdipCreateBitmapFromStream when calling System.Drawing.Bitmap constructor
- DLL files are not excluded during building for standalone platform, even though they are selected to be excluded
Dwight_Everhart
May 16, 2017 18:37
This bug completely breaks MegaSplat. Please fix it in Unity 5.6 as soon as possible. Thank you.
WildStyle69
May 12, 2017 18:40
Please fix, people waiting on this issue!
dyox
Apr 19, 2017 16:47
Unity 5.6.0p1 : Texture Array working correctly on Vulkan.
DX9-11-GL not working.
dyox
Apr 19, 2017 16:43
Unity 5.6.0p1 : (Still not working)
Standalone : Only one texture used from TextureArray