Search Issue Tracker
By Design
Votes
0
Found in
2017.3.0a1
Issue ID
933525
Regression
No
Need to save the scene to save changed colors if the color change was done inside an asset
Reproduction steps:
1. Open "MinimalReproProject"
2. Open the "Main" Scene
3. Navigate through the Project window to "Resources" -> "Color Schemes" -> "0.Color Scheme"
4. Change the "Red" to anything else
5. Reload the Scene
6. Notice that the color changed back to Red
7. Click on the "0.Color Scheme"
Expected Result: As the color of the Grid Objects is set in the "0.Color Scheme", the colors should change without having to save the scene
Actual Result: You have to save the scene to save the newly set color, even though it stays the same in the "0.Color Scheme"
Reproduced with: 2017.3.0a1, 2017.2.0b4
Did not reproduce on: 2017.1.0p1 (TileMap was not yet implemented)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Add comment