Search Issue Tracker
Won't Fix
Votes
0
Found in
Issue ID
923934
Regression
No
Reflection Probe's Box Offset is inverted after manually moving probe's origin and undoing
Steps to repro:
1. Download attached project: https://drive.google.com/open?id=1JfrNt_hJ3M8FqsfJUkuurdSOB0XWaw0X ;
2. Open 't1' scene;
3. In the Hierarchy select 'Reflection Probe' gameobject;
4. In the Inspector under the Reflection Probe component text click on a crossy icon to open Probe Origin reflection Probe editing mode;
5. With Editor gizmoz grab in the Scene view grab the reflection probe origin and drag it to the edge of the reflection probe box by Z axis;
6. Notice that reflection probe's box offset position is (0;0;-5)
7. Undo by either pressing Ctrl/cmd+Z or by selecting Edit>Undo Modified Reflection Probe Origin.
Expected result:
Box Offset position is restored to the default value (0;0;0),
Actual result:
Box Offset's position on modified on Z-axis got inverted after undoing the modified probe origin position (0;0:5). See attached video.
Notes:
- Reproducible in 2018.3.0b1, 2018.2.7f1, 2019.1.9f2, 2017.4.11f1;
- Reproducible on Windows 10 and OSX 10.13.6;
- Reproducible only when manually dragging the probe origin; not reproducible while changing box offset position by inputting value in the Box Offset field.
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
- Crash on when D3D12RenderPass::SetupDeviceResources when opening FBX animation preview
- Serialization errors are thrown when "com.unity.render-pipelines.core" is added as a custom package and Graphics window is opened
- Character Joints unexpectedly rotate when a ragdoll is created using the Ragdoll Wizard
- Crash on GfxDeviceD3D11Base::DrawBuffersBatchMode when rendering the Scene view
- The shared EditorBuildSettings.asset file of symlinked projects is not updated when changing the order of the Scenes in Build Settings in one of the projects
Resolution Note:
The reflection probe workflow is being moved to C#. Going forward the focus will be on that workflow.