Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
Issue ID
751175
Regression
No
ReflectionProbe Previews Do Not Scale With Scene 'Gizmo Size'
Info
====
Version 5.3.0f3 (fdc0acad47d2)
Tue, 01 Dec 2015 19:16:49 GMT
Branch: 5.3/release
Decription
==========
The large mirrored spheres that appear in the scene view to preview the probe output do not scale when the 'gizmo size' is altered. This means that objects <1m which are using that probe, and are at the same location (which is frequent) are completely obscured when changing parameters on the probe. This makes the process of checking the appearance of the probe impossible without repeatedly selecting and deselecting the probe, which is clunky as hell.
Repro
=====
Create a sphere with a scale of 0.8,0.8,0.8 at the origin. Create a reflection probe at the origin with default parameters. Select probe.
Note
====
The mirrorball probe obscures the object when selected. This might seem trivial, but represents a real PITA for artists placing probes, especially in complex scenes.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment