Regarding the Gooseberry meeting:
Is this a good time to finally revisit the proxy system as well? I.e.
making it useful for all object types and data, not just Armatures.
And ridding it of the weird and obscure quirks it currently has. I
could be wrong, but that seems like one of the biggest
On Thu, Feb 13, 2014 at 2:48 PM, Nathan Vegdahl ces...@cessen.com wrote:
Regarding the Gooseberry meeting:
Is this a good time to finally revisit the proxy system as well? I.e.
making it useful for all object types and data, not just Armatures.
+!
We had discussed at the time
On Thu, 2014-02-13 at 09:48 -0800, Nathan Vegdahl wrote:
Regarding the Gooseberry meeting:
Is this a good time to finally revisit the proxy system as well? I.e.
making it useful for all object types and data, not just Armatures.
And ridding it of the weird and obscure quirks it currently
I strongly rely on linked libraries but as pointed out by Bassam if you
don't carefully plan everything you have no chance to locally override
specific properties.
Unfortunately I'm always in a hurry and there's never time to cope with
complex python scripts...
The ability to proxyfy properties,
+0001 ;)
Oh one more thing:
The current system relies heavily on groups + proxies for overrides.
Among the current limitations of the system right now is that there is
no way to make an instance 'unique' with flexibility: cycles has some
tricks for shaders, but animation is copied to all
Hopefully this can also apply to point data itself so we can use
AnimAll functionality on a proxyfied group!
Daniel Salazar
patazstudio.com
On Thu, Feb 13, 2014 at 3:03 PM, Bassam Kurdali bas...@urchn.org wrote:
+0001 ;)
Oh one more thing:
The current system relies heavily on groups + proxies
On Thu, 2014-02-13 at 15:24 -0600, Daniel Salazar - patazstudio.com
wrote:
Hopefully this can also apply to point data itself so we can use
AnimAll functionality on a proxyfied group!
Daniel Salazar
patazstudio.com
+1000
we were talking about this recently and mentioned that this will make
Hi, I'm not sure if this is the right place for this proposal/discussion or
if the Cycles mail list would've been better, but I'd like to propose a
couple of feature/parameters for the cameras in Cycles. I'm posting a link
(Google Drive) to a short PDF I prepared with the proposal and interface
Hi Robin,
For your first option you may be interested on the following patch:
https://developer.blender.org/T35428
It adds the ability of adding a deformation map to your lens.
It's not as neat as a drag drop control, but it should be able to
get to the effect you are looking for.
Cheers,
+1 -though maybe 'proxy' itself doesn't need to remain, just a way of
overriding in a more generic way
Agreed. As useful as the proxy system has been, it's really time to
put it to rest in favor of something much more flexible, robust, and
generic.
I'm thinking 'more like the way' python
The barrel thing you're proposing could work fro martistics POV, but it's
not gonna to be any useful for VFX pipeline.
Currently Libmv uses third degree radial distortion, and internally it's
also capable of handling tangential distortion as well. Further, in the
future we might look into
11 matches
Mail list logo
