Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.3.0a5
Issue ID
1061793
Regression
No
[LightProbes] Probes gizmo color is changed after adding another Inspector tab
Steps to repro:
1. Open attached project and 'LightProbeGroupBug' scene;
2. Select 'Light Probe Group' gameobject in the Hierarchy;
3. In the Scene view select one of the probes - observe that selected probe has blue color;
4. Right click on the Inspector tab, select Add Tab < Inspector to open another Inspector instance;
5. Observe the color of the selected probe.
Expected result:
Selected probe has blue color. See attached 'expected.png' screenshot.
Actual result:
Selected probe has incorrect yellow-green'ish tint. See attached 'actual.png' screenshot.
Notes:
- Reproducible in 2018.3.0a5, 2018.2.0f2, 2018.1.0f1;
- Reproducible on Windows 10 and OSX;
- Duplicating with Ctrl+D shortcut works as expected;
- The issue reproduces only when there are 2 Inspectors added to the Scene.
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
- 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
Resolution Note:
This issue has been identified as having low priority and has been closed without a fix. If the bug has no workaround and is blocking your production please feel free to reopen it with any additional information you might have. Sorry for the inconvenience this might cause.