Search Issue Tracker
By Design
Votes
0
Found in
2018.3.0a3
Issue ID
1053100
Regression
No
[Improved Prefab] Override indicator won't show for "Trigger" and "Collision" Module visualize bounds property when its toggled
Override indicator (It's a blue line which comes next to the edited property and the property name being bold) won't show for the "Trigger" and "Collision" Module visualize bounds property when its enabled or disabled
Steps to Repor:
1. Open attached or create a new project
2. Hierarchy window > right click
3. Effects > particle system
4. Drag the particle in the project window to create its prefab
5. Enable "Trigger" module and click on it to expand
6. Enable "Collision" module and click on it to expand
7. Disable and enable visualize bounds property for both
Actual Result:
Override indicator won't show next to visualize bounds property
Expected Result:
Override indicator should come up next to it
Environment:
Windows & Mac
Occurring with:
Version 2018.3.0a4 (e10bd691e1ef)
Mon, 25 Jun 2018 15:31:25 GMT
Branch: prefabs/improved
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment