Campbell,
Maybe something about this should be posted on code.blender.org so that more
people know about the change.
Cheers,
Jonathan
___
Bf-committers mailing list
Bf-committers@blender.org
http://lists.blender.org/mailman/listinfo/bf-committers
In many tutorials from Blender 2.4x i read that it will cause problems
if you edit a mesh* with shapekeys. (* Adding or removing vertices's)
Is this also true for Blender 2.5x, that you might have unexpected
results after doing so? Or is this simply a myth? Currently i was
working on a mesh wit
Also, what about the bf-python ML ?
Cheers,
Doug.
On 11 February 2011 12:19, Jonathan Smith wrote:
> Campbell,
>
> Maybe something about this should be posted on code.blender.org so that
> more
> people know about the change.
>
> Cheers,
> Jonathan
> ___
Hi,
I don't know any of current bugs with shape keys when adding/removing
vertexes. However, what this may be referring to is that as you add
vertices, they will all simply have the same position in all shape
keys. Blender makes no attempt to cleverly set the positions of those
new vertices in oth
If new vertices will just be added/removed in the right order from all
shapekeys, then there should be no issue. (Same location: I would expect
it this way)
But thinking about the implementation: Could it be, that the order of
the indices's can go wild? If the vertices get not synchronously add
Hi,
This should all work fine, see load_editMesh for the code where it
syncs the shape keys after exiting edit mode.
Brecht.
On Fri, Feb 11, 2011 at 3:06 PM, Tobias Oelgarte
wrote:
> If new vertices will just be added/removed in the right order from all
> shapekeys, then there should be no issu
Unluckily it doesn't. :-(
I added a bugreport with an simple example to the tracker.
URL:
http://projects.blender.org/tracker/index.php?func=detail&aid=26039&group_id=9&atid=498
Greetings
Tobias Oelgarte
Am 11.02.2011 16:23, schrieb Brecht Van Lommel:
> Hi,
>
> This should all work fine, see lo
Original-Nachricht
> Datum: Fri, 11 Feb 2011 05:52:54 +
> Von: Campbell Barton
> An: bf-blender developers
> Betreff: Re: [Bf-committers] bugs?
> The reason I didn't continue to clear the dead assignment warnings is
> it would do more harm then good IMHO.
Shouldn't warnin
Patch is up:
http://projects.blender.org/tracker/index.php?func=detail&aid=26044&group_id=9&atid=127
On 10/02/2011 10:59, Tom Edwards wrote:
> Turns out that Scons isn't set up for dynamic libs: it can only copy
> them in from the /libs folder. The thumb handler residing there is
> probably for t
You suggest we should eventually make blender warning free, I'd like
this too but at the moment there are a enough false positives mixed in
with Clang's warnings.
Or, at least warnings which will never happen unless blender runs into
memory corruptions/un-thread-safe code.
In practice this isn't so
10 matches
Mail list logo
