Age | Commit message (Collapse) | Author |
|
values. from r60260
also correct some comments.
|
|
So now release archive will have this files included.
|
|
was regression in r59665 (fix for [#35002]).
now when checking a segment that lies on the same plane as the triangle intersects,
clip the segment by the triangle bounds so we know the points remain inside the triangle.
|
|
|
|
by applying scale). It looks that only layer brush needs this
correction.
|
|
triangulate on a fixed loop.
|
|
which need further fixes.
|
|
new geometry was initializing its original index to 0 (so all edges displayed with the first edges crease value).
now initialize to NONE.
|
|
defaults in places),
add macros for initializing BMAllocTemplate's, also add assert on invalid use of bmesh_sfme()
|
|
r60146 caused bug [#36803])
|
|
returning true,
also check deformMatricesEM callback for modifier_isCorrectableDeformed() rather then checking modifier types.
|
|
button under the mouse, and so clicking the button failed without first
moving the mouse. Similar issues could happen with popups and switching
windows.
The problem is that a notifier was being used to deactivate possible other
activated buttons, but as notifiers are delayed it could undo the correct
activation too. If anyone notices hanging tooltips or other issues after this
fix, please report them.
|
|
proxy group.
|
|
cancelled before the job, causing invalid access to op->reports in the job thread.
|
|
seems that somehow not having this is causing keyboard events to be caught by
SDL. This was removed because it broke addons that could use SDL, now set the
environment variable only temporary during SDL initialization.
This may have been causing issues with keyboard events getting missed in the
game engine, but I couldn't confirm the issue here.
|
|
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.
|
|
(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.
|
|
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).
|
|
|
|
|