-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a global transform property on meshes #5
Comments
I was thinking, if a Transform property is attached to inputs, we'll have to have one attached to the output. By default it'll be the main input one, but if a plugin writer wants to change this it makes the effect become a constraint rather than a modifier. In blender it is not possible to do both at the same time. |
Added
|
So, if I understand correctly, we have:
where |
Correct! |
I think we should change this a bit and add a way for the effect to request the transform first, a bit like what we intend for attributes. Because as it is now the effect should theoretically be recomputed every time the object's transform change, in case the effect uses it, which is stupid for many cases! |
I was thinking about adding In the same vein, we may want |
I agree with the fact that there is little use in knowing the location of only one of the inputs but these unimaginable edge cases would really suffer from it when they will exist and the overhead for adding input-level switch is reasonnable, so I'd lead toward a
I should check out again how they do in Image Effects, but I agree that time mostly is a parameter like any other as long as we don't allow "solver"-type modifiers that read the previous frame to generate the next (I don't think that image effect allow this neither). |
It would seem handy for video (denoising, warp stabilization, etc.) and apparently OpenFX does have support for this: https://openfx.readthedocs.io/en/master/Reference/ofxRendering.html#rendering-sequential-effects In terms of Open Mesh Effect, one way it could be useful would be with the "generator" context - you could use a plugin for reading animated data in some format, without needing direct support for the format in the host application. |
Fixed with |
As pointed out by @tkarabela in eliemichel/OpenMfxForBlender#35 there would be a fair need for a
kOfxMeshPropTransform
to provide a global transform matrix. So also we need a way to have matrices in properties maybe.The text was updated successfully, but these errors were encountered: