| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
from Andreas Schwab (schwab)
modified to use code from BLI_endian_switch.
|
|
temp char (approx 18x speedup on my system).
|
|
from Sunny Gogoi (darkowlzz)
|
|
should have been optional.
|
|
api, for better control over groups and instances" by Martin Sell (moerdn). This patch adds a member and a group property to KX_GameObject:
* KX_GameObject.member returns the list of group members if the object is a group object, otherwise None is returned
* KX_GameObject.group returns the group object that the object belongs to or None if the object is not part of a group
|
|
|
|
forced ON, but this change was not cached yet. Thanks to Jens Verwiebe for providing this fix.
|
|
* The minimize() function, which solves a least-squares problem, is
only needed for sharp remesh mode, but was being calculated for
smooth and blocks modes as well. Disabling this calculation when
it's not needed gives a big performance boost.
|
|
* Move InternalNode operators from Octree class into InternalNode
struct
* Constify various member functions
|
|
Note that this is just an RNA change, underlying dualcon octree
already supports even higher values.
|
|
* OSL UI message did not show up when device type was GPU, but User Preferences were None. Also remove experimental check, more convenient for testing.
|
|
Separate vertex copies are now made for flat-shading, such that the
normal is correctly flat-shaded. The element index buffer is not
created in this case.
|
|
* De-duplicate GPU code to check if VBO should be used.
* Add a flag to indicate if the buffer should be drawn smooth or not,
rather than checking each time the node is drawn.
|
|
The parameter lists are using OIIO::TypeDesc static standards, which are also static variables. With static OSL libraries these are not initialized when the closure parameter lists are initialized, so OSL rejects the closure types.
Putting static initialization into functions works just as well, but ensures the OIIO::TypeDesc access is delayed until initialization is complete.
|
|
order to provide the osl_allocate_closure_component function for LLVM.
|
|
Warns if an array is passed to a function where the array is declared larger, eg float[2] argument is passed function defined as float[3], (or a greater size).
Existing free static checkers dont do this from what I can tell.
|
|
also correct array sizes in othere areas.
|
|
draw_tracking_tracks().
|
|
|
|
This adds cmake code for LLVM on linux and updates the cmake code used for OSX.
LLVM is linked like other external libraries now, by using the setup_liblinks and setup_libdirs macros instead of the PLATFORM_LINKFLAGS variable.
The use of llvm-config for getting a list of libraries can also be simplified quite a bit.
Caching the LLVM_DIRECTORY and LLVM_VERSION strings could be nicer though.
|
|
Used the same hack as BLI gzip is using -- calculate short path and
send it to OCIO library.
|
|
definition (EDBM_selectmode_convert())
Cheers to Sebastian Nell (codemanx) for catching this.
|
|
the mouse about to see the result).
also remove print from last commit.
|
|
bmesh is empty
was missing set typecheck
|
|
utility metaball functions to (de)select all.
|
|
|
|
which DNA ignores.
tag operator callbacks as needing their return values used. These are not directly called in many places so the inconvenience is minimal.
|
|
As suggested by Campbell on the IRC gave grease pencil its own notifier type (NC_GPENCIL) and made the makesrna notifier functions actually update properly.
Also got the #ifdef'd GreasePencil.layers.[new/remove] functions working.
|
|
|
|
|
|
also add boundbox checking for lasso select.
|
|
|
|
radius-squared for circle select comparisons.
edge_fully_inside_rect() & edge_inside_rect() args were shorts when all callers were passing ints.
|
|
* Added/fixed some comments
* Swapped order that invoke/exec calls are defined in the operator definitions
to reflect flow better
|
|
|
|
Added a convenience operator to the Follow Path constraint which adds a F-Curve
for the path (or the operator's "fixed position" value if no path is assigned),
with options for setting the start frame and length of motion. This makes it
easier for common users to just set up a quick follow-path animation where the
camera (e.g. flying around a set over certain number of frames).
A key advantage of this is that it takes care of the underlying math required
for setting up the generator curve accordingly (I've got some plans for making
this a bit friendlier to use later). Now, animating the paths is a one-click
operation, with the start and length properties able to be controlled using the
operator properties.
|
|
|
|
Recently on the bf-funboard list, there have been some requests for clearer
indications for animators that autokeying has been enabled when transforming so
that corrective action can be taken sooner if this wasn't expected. This is
especially important in distributed+collaborative environments where multiple
artists may work on a single shot file: someone working on a shot from
another animator may not be aware that autokeying was enabled, thus accidentally
setting a whole bunch of extra keyframes.
In this current incarnation, we display using red (not hardcoded, but using an
existing theme color) a solid 1px border around the 3D view while transforming
with autokeying enabled. In addition to the border, a blinking indicator (record
icon + "Auto Keying On" text) appear in the top right corner, as inspired by the
traditional recording indicator icons on camcorders.
|
|
with
have all rotation axes disabled.
|
|
"bone" instead of "curve"
|
|
* Get rid of ED_object_add_generic_invoke() and all invoke callbacks using it, it was doing nothing exec() callbacks would not do. In fact, its only action (setting part of common add ops properties, like loc, layers, etc.) was needed too by direct exec call, so it was done twice in case of using invoke()!
* Replace custom invoke code for metaballs by WM_menu_invoke helper (as already used by lamps).
* Add a new OBJECT_OT_empty_add op, to allow direct addition of empties of a given drawtype.
* And some general code cleanup (like trailing spaces, empty lines, ...).
Did quite a bunch of tests/verifications, but obviously could not tackle all possible scenarios... Anyway, if any, bugs should arize quite quickly (but I don’t expect any! :p ).
|
|
objects.
|
|
sure I want to recommend anyone doing this, but the fix is simple.
|
|
|
|
ED_view3d_project_short_global() with ED_view3d_project_int_object() in some places.
|
|
Was caused by mixing up own C-API typedefs with OCIO's
|
|
precision math
This could solve issue #32748: Boolean Modifiers Making unneeded edges?
|
