ok, in need of some help here...
when i move my camera at frame 3, it creates a key at frame 4 (!)
anyone knows why?
i thought it would be fractional frames, but that's turned off,... so...![]()
ok, in need of some help here...
when i move my camera at frame 3, it creates a key at frame 4 (!)
anyone knows why?
i thought it would be fractional frames, but that's turned off,... so...![]()
nope, no answer in the above video...
the issue >
![]()
Yep. That's definitely weird. I've never had that happen before.
Did this just start happening? Which version of LW are you using?
Seems to be an "Auto Key" issue. If you turn "Auto Key" off, and move to a frame and "Create Motion Key" at a particular frame, does that work?
Kevin Fanning
IMDB http://www.imdb.com/name/nm1891389/?ref_=fn_al_nm_1
YouTube: https://www.youtube.com/channel/UC2e...RzSQP2GCHGJ2RQ
Website: https://kevinfanning.myportfolio.com
no, no workie'If you turn "Auto Key" off
![]()
running LW11.6
Solved!
turning off Motion Blur solved it. (a bit' strange... never the less...)
edit; seems to be related to Shutter Open setting above 0%
Last edited by erikals; 11-29-2020 at 02:02 PM.
So creating a keyframe the manual way still adds it one frame ahead of where you are?
Does it show up in the Graph Editor the same way? Trying to figure out if it is just the timeline keyframes that are off. I'm running 2019 (and also have 2020, but it's too buggy).
- - - Updated - - -
Okay, that is weird...
Kevin Fanning
IMDB http://www.imdb.com/name/nm1891389/?ref_=fn_al_nm_1
YouTube: https://www.youtube.com/channel/UC2e...RzSQP2GCHGJ2RQ
Website: https://kevinfanning.myportfolio.com
yes.
a new note; seems to be related to Shutter Open setting above 0%
turn it to 0% and all is good.
![]()
Sounds like a bug, might as well report it.
There's no good reason why motion blur settings should impact keyframe generation at all.
I can kind of picture how the defect happened ("Shutter Open" is affecting global "current time/frame" in contract-breaking manner), but it's likely also a solid demonstration why affecting/manipulating global state directly became a coding "anti-pattern"/"bad practice".
Last edited by jwiede; 11-29-2020 at 03:00 PM.
John W.
LW2015.3UB/2019.1.5 on MacPro(12C/24T/10.13.6),64GB RAM, NV 980ti
Kevin Fanning
IMDB http://www.imdb.com/name/nm1891389/?ref_=fn_al_nm_1
YouTube: https://www.youtube.com/channel/UC2e...RzSQP2GCHGJ2RQ
Website: https://kevinfanning.myportfolio.com
running 11.6 so probably fixed in 2020.
even if it wasn't, all LW engineers are gone, so not any point really to report a bug to a ghost-mail.
Bookmarks