Game Editing > General Content Creation
[blender] keyframing custom properties?
ratty redemption [RIP]:
if i copy one of those stepped looking custom property curves, and paste it into an object's transform, the curve gets automatically converted to a bezier, so i imagine custom properties only use whole numbers/integers... i'm not at all good at maths so could misunderstanding this.
kat:
So when you copy/paste, the result is a smoother line as you would normally expect of a bezier? If that's the case then yes, there's something causing issues with the custom property you've set; ordinarily I'd say it looks like something is editing the curve but if you say there are no bezier or curve points at those kinks that would otherwise do that I've no idea what might be causing it. Very puzzling.
ratty redemption [RIP]:
yes, the copy/paste from the original key framed custom property slider results in a smooth bezier. it's as if blender knows that the keys come from one of those sliders and not an object's transform. likewise if i replace the slider's stepped curve with one from a transform then it also becomes stepped.
so i'm slowly piecing this puzzle together, but i don't understand why those sliders only appear to work with integers, while a transform's slider can use float numbers?
which when the latter is used as an input for a driver produces the desired results, i just don't want to drag around 3d sliders in the sometimes cluttered 3d view, if i can have a neater looking properties panel of sliders.
ratty redemption [RIP]:
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've reported this to the tracker.
ratty redemption [RIP]:
sorry i forgot to update this, it was eventually confirmed to be a bug which they fixed.
Navigation
[0] Message Index
[*] Previous page
Go to full version