Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
5.6.3f1
Issue ID
947845
Regression
No
Graphics.CopyTexture can not copy texture in Built project if "Read/Write" is not enabled
To reproduce:
1. Download project "NewWorld3.rar" that user sent and open in Unity
2. Open "Scene1" scene
3. Enter Play mode
Note: Observe that all objects in Game window have textures on them
4. Exit Play mode and Build project
5. Run the Build
Expected Result: Like in Editor all objects will have textures on them
Actual Result: Not like in Editor, all object will be white
Note:
- This issue appears only on Built project
- "Graphics.CopyTexture" is in "TextureAtlas.cs"
- Workaround of this issue: If you check "Read/Write" on textures, then everything will work on both Editor and Build
Reproduced on Unity 5.5.4p4, 5.6.3p3, 2017.1.1p1, 2017.2.0b11 and 2017.3.0a7
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash with multiple stack traces when playing video on a render texture with low-end graphics devices
- Circle handle of the Game view scale slider bar disappears when the scale is set to 1x
- Asset Bundles non-deterministic behavior with CRCs and hash when a video has Transcoding enabled and Sprite Atlas has an override option enabled
- [Quality Hackweek] Errors "InvalidOperationException: EnsureRunningOnMainThread can only be called from the main thread" and "NullReferenceException" shown when switching build platforms with Muse Texture package installed
- "Importer(DefaultImporter) generated inconsistent result for asset" warnings are thrown when reimporting the "URP" texture
Add comment