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
- [macOS] Rendering Debugger Volume's "Component" dropdown is opened with a big offset when "Component" field is set to any "Sample Scene"
- [iOS] Metal API validation error thrown when MSAAx2 and Depth&Color Texture are enabled
- Pressing “Open” button in Inspector > “High Quality Lines” Override throws “Item m_RenderPipelineSettings.supportHighQualityLineRendering not found” warning
- Overlays are immediately undocked when the Overlay is docked to the right side of Scene View and the Overlay's Handle is clicked
- Crash in PhysicsManager::IgnoreCollision when a GameObject with “Is Trigger” enabled enters a collision in a specific project
Add comment