Search Issue Tracker
Fixed in 2017.3.0f3
Fixed in 2017.1.X, 2017.2.X
Votes
3
Found in
2017.1.0f3
Issue ID
933023
Regression
No
Incorrect color calculation in linear color space using sprites packed with Sprite Atlas
How to reproduce:
1. Open user-supplied project
2. Load scene "scene"
3. Hit play and observe the Game View
Expected result: Both Images are the same color.
Actual result: Image on the right is brighter than the image on the left.
Reproducible with: 2017.2.0b3, 2017.1.0f3, 2017.1.0a5
Not reproducible with all versions prior to 2017.1.0a5 due to Sprite Atlas not being implemented yet.
Fixed in: 2017.1.1p1, 2017.2.0b9, 2017.3.0a5
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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Sluggy
Oct 12, 2017 05:42
Had this problem myself and was about to make a report when I saw this thread. it provides a simple, yet, unnecessary workaround. Basically, you can fix it if you view the Atlas with the inspector set to Debug mode.
https://forum.unity.com/threads/sprite-packer-does-not-work-correctly-with-linear-color-space.498439/
BlandonDu
Jul 31, 2017 16:53
Same here, this actually makes the sprite atlas nearly useless since no way to access correct the color space even via the UI-default.shader replacement.