| Age | Commit message (Collapse) | Author |
|---|
|
had a typo too.
|
|
Fixed as suggested by Campbell, thank you!
|
|
Problem occured when having more than one weight map available.
|
|
|
|
From: https://svn.blender.org/svnroot/bf-blender/branches/meshdata_transfer
Bachelor project at Narvik university collage (Norway).
By Ove M Henriksen (Cyborgmuppet)
Thesis will be published at Cyborgmuppets blender page.
Thanks for letting me participate!
|
|
places as well, but it's quite large change to be done before 'a' release.
For now ignore zoom inverse for 2d view to keep things consistent,
would be re-implemented for all areas after this.
|
|
|
|
|
|
engines require a limit of 4.
from Kesten Broughton (kestion)
Usage: In weight paint mode, select the mesh to have its weights culled. Click on "Limit Weights" button. A sub-panel will appear "Limit Number of Vertex Weights" with a slider field "Limit" which you can set to the appropriate level. The default level is 4, and it gets executed upon pressing "Limit Weights" so you will need to do an "undo" if your max bone limit is above 4. The checkbox "All Deform Weights" will consider all vertex weights, not just bone deform weights.
|
|
|
|
Now it uses the same color used for indicating keyframes instead of using
"error" indications.
|
|
In response to some of the feedback, I've taken a second look at the situation
when multiple views are open, and indeed in that situation having it display in
every region and blinking was quite overwhelming (admittedly, I've mainly been
testing on single-view setups). Now it only shows for the region that was used
for initiating the transform.
|
|
graph view
|
|
|
|
|
|
|
|
*Get rid of the magic numbers for median arrays, use defines instead, should make things a bit more clear and easy to edit (though there are still a bit of "array magic" on median here and there).
*Restore and extend use of RNA prop when a single (control)point of curve or lattice is selected, to allow keyframing (was added by sergey for curve radius in r41494, see [#29122], and reverted by myself in previous refactor r44599).
|
|
*Bezier points' softbody weight was called just "weight", when it is "weight_softbody" for NURBS ones, made it the same!
*Added "weight_softbody" to Lattice points as well.
|
|
by Sebastian Nell (codemanx)
The margin ignored horizontal scrolling.
|
|
* group -> group_parent
* members -> group_children
so its more clear what direction the relationship is.
|
|
from Jay Parker (battery)
|
|
|
|
|
|
|
|
By default, this is enabled, so that newbie users who are most likely to be
caught short by this will get the benefits of this option, while seasoned
animators are likely to know where to go to turn things off (i.e. the scratch-
an-itch urge is quite a powerful motivating force...)
|
|
|
|
|
|
|
|
refactoring
|
|
|
|
utf8-character conversion problem)
|
|
|
|
|
|
|
|
Final rendering is clamping tile resolution if it's too small, which was missing for viewport
|
|
The blender.config file used for local #defines in qtcreator projects is rewritten on every project update. To avoid losing user settings these can now be written to an optional blender_custom.config file, which is then merged into the main blender.config on updates.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
returning translated strings, which should never get into data. And it may generates dummy names in some situations (like all new Filter nodes were getting "Soften" as name (default option), better to always get "Filter" in this case!).
(Note for Lockal: also checked fcurves/drivers, but those names are directly taken from RNA prop name, hence they are as UI label, translated in the current language, but not stored in data. So no problem here ;) ).
|
|
then they needed to be.
update to clang_array_check.py - parse function definitions lazily for some speedup.
|
|
|
|
There are still a lot more in bmo_bevel.c and bmo_extrude.c, but those don't
seem that easy to fix.
|
|
cleanup)
* Enum tooltips will only be detected in the case that we assign that as the
default property (ot->prop) of the operator. Set all of the offending properties
to get this status, since those operators would be useless without that property
anyway
* Improved the wording/capitalisation of a few of these tooltips and labels
|
|
property
Changes:
This commit adds a second line to the tooltips (below the generic operator
description) showing the appropriate description for each enum option. This
brings it more into line enum properties in Blender which also show this sort of
information.
Rationale:
Operators such as Snap and Mirror in the Action and Graph Editors use an enum to
control their behaviour (respectively, "how to snap" or "what to use as the
mirror line"). In the menus, these options are displayed using a submenu, but
hovering over each of these items for more information from a tooltip only shows
the (relatively unhelpful) generic operator tooltip/description.
Another area where these descriptions are useful is for Keying Sets, where it's
now possible to see the descriptions for what each Keying Set
does/affects/requires. Again, this is more helpful than just the generic
tooltip, which would be something like "Insert keyframes using a Keying Set".
|
|
Thanks Julien DUROURE (julien)
|
