Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2019.2.X
Votes
1
Found in
2018.3.0a4
2018.3.5f1
2019.1.0a1
2019.2.0a1
Issue ID
1126400
Regression
Yes
Terrain's Texture2D Texture appears white when copied using Instantiate Method via Script
How to reproduce:
1. Open the "SampleScene" in the attached "splattest.zip" project
2. Enter Play Mode
3. Observe the two terrains
Expected Behavior: Two Terrains are identical because they have the same properties
Actual Behavior: Terrain with copied Texture appears white instead of green
Reproducible with: 2018.3.0a4, 2018.3.5f1, 2019.1.0b3, 2019.2.0a5
Not reproducible with: 2017.4.20f1, 2018.3.0a3
Note: If you copy the Texture without using Instantiate(for ex.:terrainTexture1Copy = terrainTexture1 as Texture2D) - the issue does not reproduce. One(green) terrain has its Texture assigned to the public value via editor while the other one(white) copies that Texture using Instantiate.
-
Logopolis
Mar 19, 2019 19:13
I copy and modify textures before using them as terrain splat maps. This allows me to gradually vary the coloration of the landscape for different parts of the game world, without requiring a large number of different textures.
This bug makes it impossible to do this (because copied textures now appear white when used as splat maps). I therefore cannot update my game client until it is fixed.
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
- Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note (fix version 2019.1):
Fixed in 2019.3.0a3 backported to 2019.1.4f1, 2019.2.0b7