Graph Editor’s Cursor: X values do not affect the position of the cursor #54569

Closed
opened 2018-04-11 17:58:52 +02:00 by Hoang Duy Tran · 4 comments
Member

Tested on 2.79b (Date:2018-03-22 14:10, Hash: f4dc9f9d68), Linux

Reproduce procedure:
1. Open Blender and leave the cube as is
2. In the Timeline window, click the RED button to turn on Automatic Keyframe Insertion.
3. Make sure the time line cursor is at keyframe 1 position.
4. Hold down Ctrl and make a gesture as if you are dragging an axis arrow, but not actually moving anything, then release the mouse. This should trigger the keyframe 1 recorded.
5. Move time line cursor to frame 40 or something, use transform to perform some changes on the cube.
6. Switch to Video Editing screen layout (use the button next to Help menu on top).
7. Change the black screen on right to Outliner, and select to view ‘Data-Blocks’ instead of ‘All Scenes’.
8. On the Outliner data-block tree, select ‘Screens→Video Editing→Areas’, select the 4th area from the top, the ‘Graph Editor’.
9. Click on ‘Spaces→Space Graph Editor’ and scroll down to see the two boxes for:

     
       - Cursor X-Value 
       - Cursor Y-Value
         
10. Use the left mouse button to drag and change values in those boxes and you should find only values in the ‘Cursor Y-Value’ reflects on the green cursor line on the Graph Editor window on the left. Changes on the ‘Cursor X-Value’ doesn’t do anything at all.
11. Now use the mouse pointer to drag the graph cursor on Graph Editor and you should see that only value in the ‘Cursor Y-Value’ changes with the movement. The value in ‘Cursor X-Value’ remains static.

See the demo in the screen-capture clip below:

20180411_graph_editor_cursor_x_value_doesnt_work_0001.mp4

Tested on 2.79b (Date:2018-03-22 14:10, Hash: f4dc9f9d68b), Linux Reproduce procedure: 1. Open Blender and leave the cube as is 2. In the Timeline window, click the RED button to turn on Automatic Keyframe Insertion. 3. Make sure the time line cursor is at keyframe 1 position. 4. Hold down Ctrl and make a gesture as if you are dragging an axis arrow, but not actually moving anything, then release the mouse. This should trigger the keyframe 1 recorded. 5. Move time line cursor to frame 40 or something, use transform to perform some changes on the cube. 6. Switch to Video Editing screen layout (use the button next to Help menu on top). 7. Change the black screen on right to Outliner, and select to view ‘Data-Blocks’ instead of ‘All Scenes’. 8. On the Outliner data-block tree, select ‘Screens→Video Editing→Areas’, select the 4th area from the top, the ‘Graph Editor’. 9. Click on ‘Spaces→Space Graph Editor’ and scroll down to see the two boxes for: ``` ``` - Cursor X-Value - Cursor Y-Value ``` ``` 10. Use the left mouse button to drag and change values in those boxes and you should find only values in the ‘Cursor Y-Value’ reflects on the green cursor line on the Graph Editor window on the left. Changes on the ‘Cursor X-Value’ doesn’t do anything at all. 11. Now use the mouse pointer to drag the graph cursor on Graph Editor and you should see that only value in the ‘Cursor Y-Value’ changes with the movement. The value in ‘Cursor X-Value’ remains static. See the demo in the screen-capture clip below: [20180411_graph_editor_cursor_x_value_doesnt_work_0001.mp4](https://archive.blender.org/developer/F2661684/20180411_graph_editor_cursor_x_value_doesnt_work_0001.mp4)
Author
Member

Added subscriber: @hoanguk

Added subscriber: @hoanguk
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Philipp Oeser self-assigned this 2018-04-12 09:23:17 +02:00
Member

Cursor X-Value can only be seen (is reflected in the green line) when the Graph Editor editor is in Drivers mode, otherwise (F-Curve mode) the green line is hocked up to frame_current.

See 65072499c6 and #46004 for reasoning / details.

Closing as this is somewhat hidden, but not a bug...

`Cursor X-Value` can only be seen (is reflected in the green line) when the Graph Editor editor is in `Drivers` mode, otherwise (`F-Curve` mode) the green line is hocked up to frame_current. See 65072499c6 and #46004 for reasoning / details. Closing as this is somewhat hidden, but not a bug...
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
2 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#54569
No description provided.