Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2020.3.X, 2021.1.X
All the textures are cleared when creating Texture array
How to reproduce:
1. Open the project the "1323870_Repro" project (the project is in google drive, the link is in the edit)
2. Open the "Terrain" Scene found in the Assets/MicroSplat/Core/Examples/Scene folder
3. In the Scene/Game view inspect the "Terrain" GameObject
4. In the Project window select the "MicroSplatConfig" GameObject found in the Assets/MicroSplat/Core/Examples/Scene/MicroSplatData folder
5. In the Inspector at the bottom press the "Update" button
6. In the Scene/Game view inspect the "Terrain" GameObject
Expected results: The "Terrain" GameObject renders correctly just like at the 3rd step
Actual results: The "Terrain" GameObject renders black (as if there were no textures)
Reproducible with: 2020.2.0b9, 2020.3.2f1, 2021.1.1f1, 2021.2.0a10
Not reproducible with: 2018.4.33f1, 2019.4.23f1, 2020.2.0b8
- Entering the Play Mode fixes the rendering
- Reproducible in Built-in, Universal, and High Definition Render Pipelines
Apr 23, 2021 14:21
This is a major deal breaker for our company right now since no procedural textures can be applied (since that requires an AssetDatabase refresh, which in turn triggers the textures to go black).
Please fix this any time soon!
Apr 23, 2021 08:32
Same issue also happen in 2020.3.0f1. Please fix this soon...
Apr 23, 2021 04:25
High priority for us
Apr 20, 2021 15:25
Same issue, I can't work at all with this bug.
Apr 20, 2021 14:47
We've reproduced this on Unity 2020.3.2 with HDRP 10.x. This is a rather glaring bug for an LTS release, and I'm surprised to see that the release notes for 2020.3.4 still show this as a known issue. It's impacting our project work, and although not a showstopper, it's a major annoyance and a drag on productivity for environment editing.
The bug seems to manifest in visually different ways for different scenes and team members. Entering Play mode fairly reliably restores the textures for me, and saving the scene fairly reliably reproduces the bug. I have seen occasions in which saving the scene again after the bug would restore the textures, but that's infrequent and may actually be a coincidence with some other, less obvious, factor.
Apr 19, 2021 12:04
Same here. I'm using the 2020.3.4 LTS. Is annoying.
Apr 16, 2021 19:55
+1, high priority problem for us, stopping our landscape team from working properly.
Apr 16, 2021 01:22
Reproduced this in Unity 2020.3.2 LTS, HDRP 10.4.0.
Apr 09, 2021 19:43
So when I make that change in 2018.4LTS, then references to the texture arrays are broken. So this isn't a workaround I can ship.
Apr 09, 2021 17:22
I have rounded down this issue to using CopySerialized in this function. If I comment that out and force it to recreate the array from scratch every time, the scene does not go black. But that means that something in CopySerialized has changed and is triggering this side effect.
static void CreateArrayAsset(Texture2DArray array, string path)
array.Apply (false, true);
// in 2020.3LTS, on windows, this causes terrain to go black..
// I am worried that this will break something else though.. ugh..
var existing = AssetDatabase.LoadAssetAtPath<Texture2DArray> (path);
if (existing != null)
array.name = existing.name;
EditorUtility.CopySerialized (array, existing);
AssetDatabase.CreateAsset (array, path);
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
- [URP] Exceeding the platform's supported light limit gives shadow distortion when using Deferred Rendering Path
- URP Sample Buffer Image Tile is moved when the Offset Value is changed
- Static constructor in a struct returns false when running tests with IL2CPP
- Console throws warnings and a MissingReferenceException error for XR packages when doing a clean project import
- [Linux][IL2CPP] Dedicated server crashes when calling Socket.Send
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0a17
Resolution Note (fix version 2021.1):
Fixed in 2021.1.8f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.10f1