• EditorBugs

  • 4.2 Export to binary IKConstraintTimeline bug

    anglais

Hello,

Upgrading to 4.2 from 4.1 and I am noticing an issue with the 'bendDirection' in IKConstraintTimelines not using the proper value when exporting to binary, exporting to JSON seems to work correctly.

For example when exporting to JSON I get these values:

      "IK_AnkleR": [
      {
        "softness": 5,
        "stretch": true,
        "curve": "stepped"
      },
      {
        "time": 0.0667,
        "softness": 5,
        "stretch": true,
        "curve": "stepped"
      },
      {
        "time": 0.9667,
        "softness": 5,
        "bendPositive": false,
        "stretch": true
      }
    ]

Notice that at "time": 0.9667 that "bendPositive" is false, but when I use the exported binary I am getting a value of '1' for the 'bendDirection'.

Related Discussions
...

  • Nate

  • Message #3
  • Modifié
  • Ce post est en anglais

What runtime are you using to read the binary data?

EDIT: Actually we found the problem in the editor. We'll have it fixed in 4.2.05!

    Nate using the latest Unity 4.2 branch.

      @Nate I am still running into the same bug with 4.2.05 unfortunately. JSON works fine, but binary is not animating the change in the bend direction.

      Sorry, you're right the code change was missed for 4.2.05. It'll be in 4.2.06!

      @Nate this is looking better, but in some cases I am still seeing issues with IK timelines between JSON and binary. The issue now appears to be in the mix bezier curve values that are being exported. I am seeing this issue specifically in one animation, so I am not 100% sure what the root cause is, but here is a diff printing out the values when reading in the bezier curve for the mix of this specific animation:

      binary.txt
      7kB
      json.txt
      8kB

      You can see in the binary the values for cx1 and cy1 are really huge. The strange thing is that these should be pretty simple since we are just turning the mix on/off at specific frames and there is no interpolation.

      Ah, sorry this continues to a problem. It was a different problem, we've fixed it in 4.2.08!

      Great, that looks a lot better! Thanks so much for the quick fixes, really appreciated.