Age | Commit message (Collapse) | Author |
|
when they shouldn't be.
|
|
|
|
from UI inputs.
normal and point parameter types of OSL shaders are creating SOCK_VECTOR sockets in the script node. When these sockets are in turn used to define the fixed input values for these parameters they get
converted as OSL vector always, losing the distinction of vector/normal/point. To prevent OSL rejecting the value due to type mismatch, explicitly define the parameter defaults in the OSL script node
compiler function as vector, normal and point (unused types will simply be ignored).
|
|
functions where missing the ntreeMakeLocal entry, was still marked as 'not implemented'.
|
|
|
|
|
|
|
|
pointer" to console.
|
|
consideration
(which is also "[#36749] Joining objects with more than one uv map depends on list order")
Thanks Bastien Montagne and Brecht van Lommel for reviewing and some advice.
|
|
even if no 3Dmouseware was detected
|
|
|
|
(added Ctrl+P as a toggle to show Properties)
|
|
It already had deprecated comment, but now it also uses
compiler flag just to be sure no one uses this guy.
|
|
Suggestion by Jonathan Williamson, and thanks to
Walid Shouman for noticing that the existing code
worked if a test to prohibit it were removed.
Limitation: treats segments > 1 the same as
segments == 1 in this case; a TODO to do
something more intelligent.
|
|
Added object and world space for normal map in GLSL view.
|
|
In fact, the issue was that names of mloopuv/mtespoly layers could very easily get out of sync (a simple rename was enough), while most tools (such as the UVProject modifier) expect matching layers to have the same name!
Now matching names are check on load, and renaming of a layer through RNA is guaranted to be synchronized with its counterparts.
Thanks to Brecht & Campbell for reviews.
|
|
Seems to be a regression since BMesh merge.
|
|
This makes more sense to have no displacement if baking
non-normalized displacement map or have mid-level displacement
(which is likely be close to no displacement as well) when
baking normalized displacement.
In any way it's better than using default black color.
|
|
|
|
Issue was caused by missing NULL-pointer check in user-data
initialization.
This issue might have lead to wrong displacement map being
baked.
|
|
When setting keymap properties to values equalling the RNA default, they will
get "unset" and automatic operator behavior is used. There is no way to
explicitly set the default value as a user.
1) To allow distinguishing uninitialized (not set) properties in the keymap
items, a few changes to the RNA struct comparison function are needed: Instead
of allowing only strict/non-strict comparison of 2 properties A and B in a
struct, this now has 3 modes:
* STRICT: compare only the actual property values (same as 'strict' before)
* UNSET_MATCH_ANY: if either A or B is unset, consider them a match (same as
non-strict before)
* UNSET_MATCH_NONE: if one property is set and the other not, consider them a
mismatch.
The new UNSET_MATCH_NONE mode is useful for keymaps, because it allows keeping
user-defined property values in the keymap even if they match the default
property value (see wm_keymap_diff function in wm_keymap.c)
2) A new operator is added for unsetting ID properties in the RMB context menu
and in user preferences next to keymap properties. This only works on ID
properties and deletes the ID property storage, so that the default value is used.
In the user preferences for keymaps the properties are shown in an inactive
layout to indicate that the default value is used (which some operators such as
the "select linked" op from the report use to trigger automatic behavior). When
the user sets a property it gets set and stays that way until explicitly "unset"
using the new operator.
|
|
also set_source_files_properties() wasn't working for rna_*_gen.c files,
set dna.c and generated data files with generated property too.
|
|
mask function ignoring the name argument from RNA-api.
|
|
|
|
|
|
view3d_operator_offset_lock_check()
|
|
more of a usability issue then a bug, now dolly switches out of camera view, like view-rotate does.
|
|
* Update links to release logs, now pointing at http://www.blender.org/development/release-logs/blender-269
* Update readme, also remove FreeBSD from it, we don't have official releases for that anymore.
|
|
|
|
|
|
defined as 2 (2D coordinates).
|
|
|
|
It seems sometimes a knife edge with the same
vertex on both ends was created sometimes.
|
|
A crash was reported but without info to reproduce.
This is a likely crash introduced by previous fix
to allow linehits to snap to vertices.
The function to find connected linehits can't
assume all linehits have edges any more.
|
|
ldconfig immediately after lib compile (looks like OSL compile process needs boost libs...).
|
|
After discussion with Brecht decided that automatically updating the sockets of the node based on externally modified data (removed EXR file passes) is not desirable behavior. But at least making sure
the correct passes are assigned to the output sockets of the Image node is possible. Now the passes are matched by name instead of using the faulty index stored in the socket data, which is more
reliable. Still may break if changing pass names externally, but an image reload is highly recommended anyway and will fix that.
|
|
MultiEXR mode, because it matches sockets and EXR layers by index and was skipping unconnected sockets. Simply create EXR layer info
for all sockets now and then ignore unconnected layers when finally writing to file in deinitExecution.
|
|
doing the full intersection check.
with 500 verts gives approx 2x speedup.
|
|
|
|
in fact this failed for all nested dupli types except for dupli-groups, (which ignore the 'par_space_mat' object_duplilist_recursive()).
|
|
call,
(indirectly referenced Python define of ~30 lines, most were optimized out but still caused some code bloat).
|
|
|
|
|
|
I also replaced all EVT_TWEAK_L by EVT_TWEAK_S
- and replaced B by the gesture mouse for the clip keymaps
|
|
ERROR: Image not available. Keeping packed image
This was due to recent bugfix for #36639, the image should only be reloaded if
the path actually changed and it's not a packed file.
|
|
Blender versions, previous fix only solved it for newer versions.
Fix a memory leak in packed files.
|
|
Depsgraph would only consider one level, now it works recursive.
|
|
poly/loop ones.
|
|
also move foreach_get/set examples into their own py example files (prefer not to have example code built into blenders binary).
|
|
also use __slots__ for classes.
|