Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.2.0f2
Issue ID
1061769
Regression
No
[LightProbes] Probes could not be duplicated when 2 Inspectors are added to the Editor's layout
Steps to repro:
1. Open the attached project and 'LightProbeGroupBug' scene;
2. In the Hierarchy click Create>Light>Light Probe Group to add Light Probe Group gameobject;
3. Select Directional Light gameobject in the Hierarchy;
4. Select light probe group gameobject by clicking its gizmo in the Scene view;
5. Select one of the light probes in the Scene view by left-clicking on them;
6. In the Inspector click 'Duplicate Selected' button;
7. Using Editor's transform gizmos move selected probe around the scene view.
Expected result:
The new probe should be added to the scene view and should change its transform position, while the initially selected one should preserve the same position.
Actual result:
The initially selected probe changes its transform position; the duplicated light probe is not created. See attached video.
Notes:
- Reproducible in 2018.3.0a5, 2018.2.0f2, 2018.1.0f1;
- Reproducible on Windows 10;
- Duplicating with Ctrl+D shortcut works as expected;
- The issue reproduces only when there are 2 Inspectors added to the Scene.
Consider checking out https://fogbugz.unity3d.com/f/cases/1061785/ as well.
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
- 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
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.