Handles API render in a wrong location when using a subwindow with PreviewRenderUtility

6.7.X

As Designed

Thank you for reporting a bug to Unity. After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We will close this case as 'As Designed.' The issue is how Handles API were used with the PreviewRenderUtility. Since the preview already sets up a camera pixel rect and has a render target texture configured. Attempting to then setup and draw handles outside of the Begin/EndPreview scope is very brittle. The issue is essentially a mismatch between different render targets and coordinate spaces. Recommendation for the user is to draw Handles within the preview's Begin/End scope. In ScenarioEditorWindow.OnPreviewGUI, just before `var result = _previewUtility.EndPreview();` do the Handles render pass: var previousActive = RenderTexture.active; RenderTexture.active = _previewUtility.camera.targetTexture; using (new Handles.DrawingScope(Matrix4x4.identity)) { Handles.SetCamera(_previewUtility.camera); DrawGizmos(); } RenderTexture.active = previousActive; Then replace the // 2. Draw Handles Overlay (On all layout and input events) step with: if (evt.type != EventType.Repaint && _previewUtility != null && _previewUtility.camera != null) { Handles.SetCamera(_previewUtility.camera); DrawGizmos(); } This configuration fixes the issue on our end and matches the handle rendering with the preview's content.