I remember that there's a Boolean keying issue in the custom param and we should have fixed it. Not sure whether it's the same issue.
Let us know whether you still can repro it in 2014. Chris On 7 Sep, 2013, at 7:50 AM, "Jeremie Passerin" <gerem....@gmail.com<mailto:gerem....@gmail.com>> wrote: Oh and it's XSI2013. I would have to check in 2014 On 6 September 2013 16:49, Jeremie Passerin <gerem....@gmail.com<mailto:gerem....@gmail.com>> wrote: The new layer is the current layer on my test. So I vote for a bug too ;-) thanks On 6 September 2013 16:45, Matt Lind <ml...@carbinestudios.com<mailto:ml...@carbinestudios.com>> wrote: Edit: Just thought about it – depends on whether or not the new animation layer is defined as current or not. If the new layer is not set to be the current layer, then the behavior you’re experiencing is correct as your last key from the base layer is set to false. If the new layer is the current layer, then it’s a bug as the last key was set to true. Matt From: Matt Lind Sent: Friday, September 06, 2013 4:43 PM To: 'softimage@listproc.autodesk.com<mailto:softimage@listproc.autodesk.com>' Subject: RE: Animation layers and Boolean parameters Sounds like a bug to me, but of the small annoyance kind. Matt From: softimage-boun...@listproc.autodesk.com<mailto:softimage-boun...@listproc.autodesk.com> [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Jeremie Passerin Sent: Friday, September 06, 2013 4:41 PM To: softimage Subject: Re: Animation layers and Boolean parameters just tested and yeah I have the same issue with the viewvis parameter On 6 September 2013 16:21, Matt Lind <ml...@carbinestudios.com<mailto:ml...@carbinestudios.com>> wrote: Do you get the same behavior when keying a native Boolean parameter instead of a custom parameter? CustomParamSets are kind of the wild west in terms of behavior. I would test a Boolean parameter like viewvis and compare with a Boolean on a self installing customproperty. Under the hold the animation layer system is actually the animation mixer which has it’s own rules and logic. Perhaps some of that is bubbling up. Matt From: softimage-boun...@listproc.autodesk.com<mailto:softimage-boun...@listproc.autodesk.com> [mailto:softimage-boun...@listproc.autodesk.com<mailto:softimage-boun...@listproc.autodesk.com>] On Behalf Of Jeremie Passerin Sent: Friday, September 06, 2013 4:08 PM To: softimage Subject: Animation layers and Boolean parameters Before I log a bug report, I want to make sure I'm not doing something stupid. Here is what I do. - New Scene - Create a null - Create a custom property on that null with a boolean parameter - Set a key on the parameter ( value = False ) - Now create a new animation layer - Set the param to True and Key - Move to another frame and key again BAM ! The parameter is set to False without asking ! Am I doing anything wrong there ? You can also reproduce the bug with this script : Application.NewScene("", "") Application.GetPrim("Null", "", "", "") Application.AddProp("Custom_parameter_list", "", "", "CustomPSet", "") Application.SIAddCustomParameter("null", "Param", "siBool", 0, 0, 1, "", 2053, 0, 1, "", "") Application.SelectObj("null.CustomPSet", "", "") Application.SetValue("null.CustomPSet.Param", True, "") Application.SetValue("null.CustomPSet.Param", False, "") Application.SaveKey("null.CustomPSet.Param", 1, "", "", "", "", "") Application.AddAnimationLayer("Scene_Root", "", 1) Application.SetValue("null.CustomPSet.Param", True, "") Application.SaveKey("null.CustomPSet.Param", 1, "", "", "", "", "") Application.SetValue("PlayControl.Key", 10, "") Application.SetValue("PlayControl.Current", 10, "") Application.SaveKey("null.CustomPSet.Param", 10, "", "", "", "", "")
<<attachment: winmail.dat>>
