keyframing custom properties issue #37103

New Issue

ratty redemption · 2013-10-16T13:23:18+02:00

ratty redemption commented

2013-10-16 13:23:18 +02:00

%%%--- Operating System, Graphics card ---

cpu: intel core i3 2350 2.3 ghz
ram: 4 gb
gfx: intel hd graphics 3000
os: windows 7 home premium sp 1

- Blender version with error, and version that worked ---

error found in: 2.69 r60695
was working in: ?

- Short description of error ---

key framing custom property sliders results in a stepped (integer?) curve and not a smooth (float?) bezier in the graph editor.

- Steps for others to reproduce the error (preferably based on attached .blend file) ---

[apparently happens with all blend files]

i'm trying to use custom properties in the 3d view's property panel, to blend different actions in the nla editor via the action's influence sliders.

if you look at the attached screen capture, your'll see the graph editor curves are meant to be smooth bezier curves (when set to bezier interpolation) but currently they are stepped, resulting in the animation blending stuttering horribly when played back.

if this is not a bug per se, could you guys please at least give us the option when editing custom properties to switch between integer and float outputs?
%%%

%%%--- Operating System, Graphics card --- cpu: intel core i3 2350 2.3 ghz ram: 4 gb gfx: intel hd graphics 3000 os: windows 7 home premium sp 1 - Blender version with error, and version that worked --- error found in: 2.69 r60695 was working in: ? - Short description of error --- key framing custom property sliders results in a stepped (integer?) curve and not a smooth (float?) bezier in the graph editor. - Steps for others to reproduce the error (preferably based on attached .blend file) --- [apparently happens with all blend files] i'm trying to use custom properties in the 3d view's property panel, to blend different actions in the nla editor via the action's influence sliders. if you look at the attached screen capture, your'll see the graph editor curves are meant to be smooth bezier curves (when set to bezier interpolation) but currently they are stepped, resulting in the animation blending stuttering horribly when played back. if this is not a bug per se, could you guys please at least give us the option when editing custom properties to switch between integer and float outputs? %%%

ratty redemption commented

2013-10-16 13:23:18 +02:00

Changed status to: 'Open'

ratty redemption commented

2013-10-16 18:52:40 +02:00

%%%this is looking more like a bug in my opinion.

if i load up a default scene and create a custom property on the cube (without editing the custom property) then it does output a bezier. but if i edit the "prop" with a min of 1 and a max of 20, then replace the keyframes it converts it to integers, well it's curve is stepped and no longer a bezier, even though the graph editor still says the interpolation type is bezier.

i'm attaching the simple blend file i just tested this with.%%%

%%%this is looking more like a bug in my opinion. if i load up a default scene and create a custom property on the cube (without editing the custom property) then it does output a bezier. but if i edit the "prop" with a min of 1 and a max of 20, then replace the keyframes it converts it to integers, well it's curve is stepped and no longer a bezier, even though the graph editor still says the interpolation type is bezier. i'm attaching the simple blend file i just tested this with.%%%

ratty redemption commented

2013-10-16 18:59:30 +02:00

%%%i'm having trouble attaching the blend, trying again.%%%

Bastien Montagne commented

2013-10-17 13:59:46 +02:00

%%%Note that interpolation type and "step" representation are two different things - you can have a Bezier interpolation with an integer property (and hence steped curve).

The only bug here is the "refreshing" of the displayed F-curve which is not correct when the type of the property changes…%%%

%%%Note that interpolation type and "step" representation are two different things - you can have a Bezier interpolation with an integer property (and hence steped curve). The only bug here is the "refreshing" of the displayed F-curve which is not correct when the type of the property changes…%%%

ratty redemption commented

2013-10-17 17:53:30 +02:00

%%%thanks, and i understand the first part... but if i edit the custom property to values above 1, for example a min of 1 and max of 20, then it's not just the graph editor's visual representation of the stepped curve that is buggy, if this curve is going to be used as the input of a driver, then the drivers output is also integers, and if i edit the custom property again and change the values back to min of 0 and max of 1, then the resulting curve and driver output are still integers, which requires the custom property to be deleted and new one to be created, in order to get the bezier curve working again.

so can you fix this?%%%

%%%thanks, and i understand the first part... but if i edit the custom property to values above 1, for example a min of 1 and max of 20, then it's not just the graph editor's visual representation of the stepped curve that is buggy, if this curve is going to be used as the input of a driver, then the drivers output is also integers, and if i edit the custom property again and change the values back to min of 0 and max of 1, then the resulting curve and driver output are still integers, which requires the custom property to be deleted and new one to be created, in order to get the bezier curve working again. so can you fix this?%%%

Bastien Montagne commented

2013-12-16 13:00:52 +01:00

Added subscriber: @JoshuaLeung