• EditorBugs
  • 在不知做了什么下,时间轴上的关键帧无法被移动

在一个3.8.99的项目中,当我正常得操作了一段时间后,在某一时刻我不知道做了什么,导致时间轴中的关键帧无法被移动,更加准确得来说,我无法选中并移动它。但在重启后,它又恢复正常,直到下一次不知道做什么后导致的无法移动。

它没有出现任何弹窗或者报错,一切都是悄无声息发生了。于是我尝试对spine进行重装,但那没有用。接着我打算在开着键鼠输入显示的情况下录制我的工作流程,以此来找到是什么导致这个问题。果不其然,这个问题再次出现了。录像总长约半小时,前面一切正常,最后问题突然就出现了,在反复观看下我并没有找到什么奇怪的地方导致这个问题,唯一可疑的是这个问题出现前半分钟我ctrl+s保存了两次,但这也太奇怪了吧?

我希望能找到方法来解决这个问题,这对我的工作带来了很大的影响

以下是我出现问题时的片段,无论是单击拖动,还是框选后再拖动,时间轴上的关键帧都无法被移动:
https://drive.google.com/drive/folders/17cCK7AgOKk3Y0Hziu-E400XW-diBlLue?usp=drive_link

    Related Discussions
    ...

    krammor I am sorry to hear that you are having problems. I tried to watch your video, but it says I don't have permission to access it and I couldn't check it out. Could you please check your permission settings?

    Since I have not seen the video yet, I do not know what the cause is, but please understand that even if it is a bug in the editor, we cannot fix it because 3.8 is already a version that has not been updated.

      Misaki 哦,抱歉,我忘记设置权限了,现在它应该可以正常被访问了:
      https://drive.google.com/drive/folders/17cCK7AgOKk3Y0Hziu-E400XW-diBlLue?usp=drive_link

      我观看了机器人的自动回复,但我没有开启比如筛选或者锁定等功能,只是正常的K帧,而且在我对软件的理解中,应该没有什么设置会导致这种奇怪的现象发生

        krammor Thank you for correcting the access rights! I was able to watch the video. The cause is still unclear from the video, but I would like to confirm one thing: Did you change the dopesheet row height in the Dopesheet - Dopesheet item height in the Spine settings? The default value is 23.

        If I remember correctly, the newer editor versions have already fixed this, but I believe there used to be a problem with key selection when a floating decimal was specified for the row height on the dopesheet. Could you please check what value is specified for this setting?

          Misaki 我没有调整这个参数的数值,它依然是23:

          如果设置有可能导致这个问题的话,以下是我根据个人习惯更改的设置:

            krammor Thank you for confirming the Spine settings! Nothing in the settings you have shown us appears to be the cause of this problem, so unfortunately we cannot answer further on this issue unless we know how to reproduce it. If updating the editor version resolves the issue, please consider updating your project version.