![[ChimeraX Issue Tracking System]](/trac/ChimeraX/chrome/site/ChimeraX-icon.svg){kind=icon}
Opened 9 hours ago
Last modified 9 hours ago
#20800 assigned defect
'rock' frame rate
| Reported by: | Owned by: | Tom Goddard | |
|---|---|---|---|
| Priority: | moderate | Milestone: | |
| Component: | Core | Version: | |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Notify when closed: | Platform: | all | |
| Project: | ChimeraX |
Description
From #20432: the framerate of ‘rock’ command isn’t stable, and changes sometimes on window focus change, or seems to be creeping a bit over time, so sometimes rocking seems faster or slower at the same ‘cycle N’
Note:
See TracTickets
for help on using tickets.
The rock command renders a specific number of frames each cycle of going back and forth. It does not attempt to make the perceived speed the same. If your graphics rendering slows down then it will appear to rock slower. Also it remembers the center and axis of rotation, so as you move the model (change focus) it may appear to rotate about a different direction (not fixed to the vertical screen axis) and the center of rotation stays fixed with the atomic structure which may be off the screen (ie it does not stay in the center of the screen) if you zoom in on a different part of the structure.
Is what you are observing consistent of this explanation of how rock is supposed to behave?