Hi.
As recommended by Sergey i kindly request for help from platform
maintainers for updating the Collada libraries:
OpenCOLLADA had a bug that was discovered in this blender report:
https://projects.blender.org/tracker/?func=detail&atid=498&aid=36325&group_id=9
The bug has been fixed by now. So
Hi;
Sergey has mentioned that building the OpenCOLLADA libraries
on linux is troublesome and always needs manual tweeking.
However i believe if there are such issues, then the openCollada
maintainers would be more than happy to get informed about
these problems and how they have been fixed by the
I have already asked for an alternative to the "#frame" driver for
rendering animation in Cycles.
It is realy not a good aproach anymore due to new security policies.
Seed should always vary per frame. Static seed is an exception, it is only
usefull in very rare situations when you need to compare
Not sure if we're supposed to respond to these, but I've been meaning to
ask: Why can't we bake to level 0?
On Tue, Jul 30, 2013 at 11:35 PM, Sergey Sharybin wrote:
> Revision: 58752
>
> http://projects.blender.org/scm/viewvc.php?view=rev&root=bf-blender&revision=58752
> Author: nazgul
> Date:
Hi,
The answer it that during sculpting, the sculpt stroke does not propagate
on the data on the zero level. This means that the mapping between
displaced and base mesh breaks on this level and the algorithm that does
the multires baking breaks there. My guess is that this is an architectural
issu
"Either make the strokes touch mesh data directly, or use an apply base
modifier prior to baking, maybe with a warning that baking will alter the
mesh data."
Make that an "Apply Base operator" instead of modifier, sorry for the
confusion
___
Bf-committe
Hi,
- If renders are useless it should do this by default?
- the #frame tag shouldn't be using python, and work always.
I'm quite sure more expression shortcuts can kept working...
-Ton-
Ton Roosendaal - t...@blender.org - www.blend
Hi,
I understand the pain... apparently this header notice is not communicating,
even when people already expressed disagreement and knew the feature was coming.
However, you can set this all in user preferences to have things work forever
as you want. It'swell documented in release logs:
http:
On Sun, Aug 11, 2013 at 3:35 AM, Ton Roosendaal wrote:
> Hi,
>
> I understand the pain... apparently this header notice is not communicating,
> even when people already expressed disagreement and knew the feature was
> coming.
>
> However, you can set this all in user preferences to have things
I just wanted to say I think that sounds like a great idea.
Cheers,
Morten.
On Sat, Aug 10, 2013 at 10:26 AM, Antony Riakiotakis wrote:
> "Either make the strokes touch mesh data directly, or use an apply base
> modifier prior to baking, maybe with a warning that baking will alter the
> mesh
10 matches
Mail list logo
