| Age | Commit message (Collapse) | Author |
|---|
|
mouse (grab tool)
The issue was caused by SEQ_BEGIN macro modifying sequence's depth
which ruined transformation routines. Used own DFS instead which
doesn't modify sequences.
Also corrected some typos in api and comments.
|
|
tip->tooltip for custom properties
Tracked in [#31062] [2.6x] Context Ambiguity List & Discussion (keep updating)
|
|
|
|
This is apart of a code cleanup to make ED_view3d_project_short/ED_view3d_project_int/ED_view3d_project_float interchangeable. Currently they work very differently in a way thats quite confusing (and cause of bugs in blender that remain uncorrected) - fixes coming.
There are also cases where ED_view3d_project_short is used, then the values are converted from shorts into int's after because ED_view3d_project_int() behaves differently, will unify behavior of these functions after this commit.
- rather then clip/noclip versions, pass flags (for bound-box clip, window clip).
- rather then store the invalid clip-value, return success (or error value clip_near, clip_bb, clip_win, overflow).
- remove local copies of project functions from drawobject.c: view3d_project_short_clip, view3d_project_short_noclip, view3d_project_short_clip_persmat.
add functions:
- ED_view3d_project_short_global() global space projection
- ED_view3d_project_short_object() object space projection.
- ED_view3d_project_short_ex() take perspective matrix and local space option as args.
- ED_view3d_project_base() - special function to set the Object 'Base' screen coords (sx, sy), since this is a common enough operation.
|
|
|
|
label and value (these strings are a nightmare to handle in RTL languages like arabic or persian, but a bit less of a nightmare this way ;) ).
|
|
|
|
ocio configuration file failed to load
This solves issues with infinite NULL-checks to prevent crashes in
such situations. Currently only happens if there's no configuration
file at all, but could be tweaked further to fallback if this file
isn't usable by blender.
|
|
|
|
commit.
|
|
rid of this
|
|
|
|
On second thought, perhaps it is more convenient/natural if this was shown in
both places, given that many
people may only find the motion paths options through the UI now.
|
|
from selected objects and bones
|
|
debug-mode
|
|
|
|
and remove redundant NULL check there. also small changes to ui_draw_but_HSVCIRCLE().
|
|
circle.
|
|
|
|
in pre-bmesh blender version, remove MODSTACK_DEBUG, was never used.
|
|
|
|
to prevent null pointer dereference if the named color profile isn't found
|
|
|
|
BKE_mesh_do_versions_convert_mfaces_to_mpolys
Discovered when were looking into crystal_cube.blend from our regression files
collection. Now it should look the same as in 2.62 release. 2.63 release wouldn't
work correct for this file because of wrong mtface->material conversion after
bmesh merge.
|
|
(grey on grey). Patch by "ejnersan" in IRC.
|
|
Issue was happening when linking armature object and making proxy and was
caused by not copying visualization settings in BKE_pose_copy_data.
This lead to deadlocks in motion path drawing code.
After discussion with Campbell decided it is crucial fix since it fixes
bug appearing in really common scenario of using armatures.
|
|
|
|
|
|
|
|
- Bump version to 2.64
- No version char for this cycle
- This is finally release stage!
Splash would be commited in some hours from now.
Thanks everyone!
|
|
|
|
invalid memory access when freeing the blend file.
|
|
this breaks and causes bug: [#32720], where sys.stdout becomes invalid and print() does nothing.
On investigation - python is not getting the environment variable from blender (aparently because its a DLL?) so this should be resolved rather then overwriting sys.stdout.
|
|
|
|
the wrapping was resized to fit the uv map. this step was wrong and has
been deleted.
|
|
the alpha mix formula was wrong. updated it.
Be aware that the regression file does not take the alpha into account,
but it should. or at least one z combine should and the other not.
this fails in 2.63a.
- At Mind -
|
|
* Fix RNA name for "turbulence_strength" property.
|
|
|
|
V3D_CLIP_TEST_RV3D_CLIPPING'd verts. (used uninitialised stack memory)
|
|
|
|
overrun)
|
|
for face data was NULL.
|
|
then loop data. (missed with bmesh upgrade)
|
|
write wrong colors for float and crash for half-float.
|
|
with multi GPU when resolution > 128.
|
|
force fields
There was strange context changes in the Add menu... Now everything uses the EXEC_REGION_WIN one (no need to invoke here, and metaballs have a strange specific invoke func...). This fixes the problem when using Add menu from a 3D view. Obviously, it still doesn't work when used from Info window's header, but that can't be helped for now (and never worked for any kind of object).
Anyway, imho all this "add object" code could use some review/cleanup, both on py menu and C ops side, but this is obviously postponed to after 2.64!
|
|
Seems to be a regression in new compositor system -- wrong number of planes
was using for image buffer allocation.
|
|
It will
still look a bit strange since the viewport can't actually render such panorama views,
so the opengl drawn scene behind the border render will not match up.
|
|
remove duplicate -Wundef entries.
|
|
the input data was 256 length, assigning smaller values would read past the buffer.
|
