Graph editor: "Frame selected" zooms in so much that Y axis disappears #115678

Closed
opened 2023-12-01 18:02:12 +01:00 by Martí Gimeno · 3 comments

System Information
Operating system: Windows-10-10.0.22621-SP0 64 Bits
Graphics card: Quadro RTX 5000/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.67

Blender Version
Broken: version: 4.0.1, branch: blender-v4.0-release, commit date: 2023-11-16 16:40, hash: d0dd92834a08
Worked: 3.6.6 (in blender 3.6.6 the frame selected operator was working on keyframes with values -1.0 in normalized mode only with bezier interpolation)

Short description of error
Given the following conditions:

  • Graph Editor is set to Normalize mode.
  • Interpolation mode is not Bezier (linear, constant, etc...)
  • Selected frame has a Y value of exactly -1.0
    "Frame selected" command zooms in so much to the selected frame that the Y axis collapses and it can no longer zoom out.

Exact steps for others to reproduce the error
From the default startup

  1. Go to animation workspace tab
  2. Activate the Normalize mode in the Graph editor
  3. Insert two keyframes with different values to the default cube, for instance: (frame=0, location x=0) -> (frame=10, location x = 1).
  4. Set interpolation mode to any other than Bezier, for instance: linear.
  5. Select the lower keyframe (at Y=-1.0) in the Graph editor and execute the Frame Selected (Numpad .) operator
    After that the Y axis to disappear and the user is unable to move in the Y direction.
    This only happens with the lower keyframes at y = -1 and in certain interpolation modes.
    In blender 4.1 alpha version it happens in all interpolation modes. In blender 3.6.6 only happens in bezier mode.
**System Information** Operating system: Windows-10-10.0.22621-SP0 64 Bits Graphics card: Quadro RTX 5000/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.67 **Blender Version** Broken: version: 4.0.1, branch: blender-v4.0-release, commit date: 2023-11-16 16:40, hash: `d0dd92834a08` Worked: 3.6.6 (in blender 3.6.6 the frame selected operator was working on keyframes with values -1.0 in normalized mode only with bezier interpolation) **Short description of error** Given the following conditions: - Graph Editor is set to Normalize mode. - Interpolation mode is not Bezier (linear, constant, etc...) - Selected frame has a Y value of exactly -1.0 "Frame selected" command zooms in so much to the selected frame that the Y axis collapses and it can no longer zoom out. **Exact steps for others to reproduce the error** From the default startup 1. Go to animation workspace tab 2. Activate the Normalize mode in the Graph editor 3. Insert two keyframes with different values to the default cube, for instance: (frame=0, location x=0) -> (frame=10, location x = 1). 4. Set interpolation mode to any other than Bezier, for instance: linear. 5. Select the lower keyframe (at Y=-1.0) in the Graph editor and execute the Frame Selected (Numpad .) operator After that the Y axis to disappear and the user is unable to move in the Y direction. This only happens with the lower keyframes at y = -1 and in certain interpolation modes. In blender 4.1 alpha version it happens in all interpolation modes. In blender 3.6.6 only happens in bezier mode.
Martí Gimeno added the
Priority
Normal
Status
Needs Triage
Type
Report
labels 2023-12-01 18:02:13 +01:00
Member

Can confirm the issue

(for me, the behavior is the same in 3.6 LTS though...)

Note: as a workaround, you could still use the scrollbar widget here to bring it back (drag the upper dot upwards):

image

Can confirm the issue (for me, the behavior is the same in 3.6 LTS though...) Note: as a workaround, you could still use the scrollbar widget here to bring it back (drag the upper dot upwards): ![image](/attachments/4733df27-e81f-4a4a-9fcf-a2372fe8edc2)
Author

I've found a solution that I don't fully understand:

image

I've built the source code with that change and it seems to fix the issue.

@ChrisLend can you please provide some insights on that fix? Does it make any sense?
@lichtwerk do you know what is the general process that I should follow to contribute fixing a bug like this?

Thank you

I've found a solution that I don't fully understand: ![image](/attachments/7d36a308-630d-431b-b63c-a91b0bc5f467) I've built the source code with that change and it seems to fix the issue. @ChrisLend can you please provide some insights on that fix? Does it make any sense? @lichtwerk do you know what is the general process that I should follow to contribute fixing a bug like this? Thank you
330 KiB

since this only happens with normalization turned on I think the clamping needs to respect the normalization factor.
But I am not sure. Will check

since this only happens with normalization turned on I think the clamping needs to respect the normalization factor. But I am not sure. Will check
Blender Bot added
Status
Resolved
and removed
Status
Confirmed
labels 2023-12-05 12:03:16 +01:00
Brecht Van Lommel added
Type
Bug
and removed
Type
Report
labels 2023-12-11 16:06:29 +01:00
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#115678
No description provided.