Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
Issue ID
756429
Regression
No
Frame & Auto-fit
1) Frame ("f" hotkey) presently has two issues...
1a) Framing with multiple GOs selected, presently only frames the first selected GO. This should frame all selected GOs.
1b) Framing with nothing selected, presently does not do anything. This should frame everything in the scene view.
This behaviour is presently inconsistent with the Animation Window (ex: Dopesheet). The behaviours should be exactly the same (for less muscle memory) in the scene view and Animation Window (selecting GOs vs. Keys).
2) Auto-fit ("a" hotkey) feature request:
We should also be able to frame everything (exactly like "f" with no selection), but without having to un-select everything.
This should be possible using "a" hotkey, which ignores the current selection and frames everything.
This is extremely useful when you want to quickly back out from a selection, without loosing this selection in order to use "f" to re-focus on the currently selected GO(s).
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
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment