| Age | Commit message (Collapse) | Author |
|---|
|
Differential Revision: https://developer.blender.org/D2522
|
|
This revision extends the functionality of the "Fill Range by Selection" button in
the "Distance from Camera/Object" modifiers so that only selected mesh vertices
in the edit mode are taken into account (instead of considering all vertices when
in the object mode) to compute the min & max distances from the reference.
This will give users much finer control on the range values.
|
|
Selection operator.
Distance calculation performed by the "Fill Range by Selection" button of the
"Distance from Camera" color, alpha and thickness modifiers was incorrect,
limiting the usefulness of the functionality.
The problem was that the distance between the camera and individual vertex
locations was calculated in the world space, which was inconsistent with the
distance calculation done by the modifiers in the camera space.
|
|
The settings.frame_start rna was clamping frame start to frame end when frame start was bigger than frame end.
The fix is simply to set frame end first
|
|
Include idea that Blender may fail to launch it even if path is correct,
in some cases (dear Windows...).
Based on idea from @lijenstina and @blendify (D2349), thanks.
|
|
This code has not been used for a long time if not ever.
Most of the code was removed in rB1d3609262704f88c9e30b2cebdb236110b25cdc9
however, this was forgoten.
|
|
compiled.
This adds a short message to the smoke, remesh and boolean modifiers' UI
when trying to use them when their compilation was turned off. This was
already implemented for the fluid and ocean simulation modifiers.
This also makes the 'quick fluid' and 'quick smoke' operator abort and
report when trying to use them when unavailable.
|
|
When major/minor segments didn't fit evenly into 4,
the UV's would move outside the UV bounds.
|
|
This is no longer needed since moving to MPoly/MLoop data structure.
Also use 3x3 matrix for transforming instead of quaternion
(slightly better performance).
|
|
|
|
|
|
selection
Previously, it was only possible to choose a single GPU or all of that type (CUDA or OpenCL).
Now, a toggle button is displayed for every device.
These settings are tied to the PCI Bus ID of the devices, so they're consistent across hardware addition and removal (but not when swapping/moving cards).
From the code perspective, the more important change is that now, the compute device properties are stored in the Addon preferences of the Cycles addon, instead of directly in the User Preferences.
This allows for a cleaner implementation, removing the Cycles C API functions that were called by the RNA code to specify the enum items.
Note that this change is neither backwards- nor forwards-compatible, but since it's only a User Preference no existing files are broken.
Reviewers: #cycles, brecht
Reviewed By: #cycles, brecht
Subscribers: brecht, juicyfruit, mib2berlin, Blendify
Differential Revision: https://developer.blender.org/D2338
|
|
Feature request during bconf, makes sense to have it even as an hack for
now, since this is probably one of the most common use cases. This should
be redone in bmesh once we have proper custom noramls handling in edit mode...
|
|
|
|
Fixes T47489.
Reviewed By: brecht
|
|
Tooltip was wrong here, it can only bake a single (active) object, 'only selected' option
is for pose bones only...
|
|
|
|
Unnecessary limit was applied.
|
|
|
|
|
|
* Added new operators to take the current transform value (loc/rot/scale or all 3)
and convert/apply that transform to a corresponding delta transform value. By default,
the transform value will be zeroed out again afterwards, so you don't end up with a
double transform.
* These operators can be found in the "Apply" menu (Ctrl-A)
* The "Animated Transforms to Deltas" (which does a similar job, except it adjusts all
existing animation data instead of the current transform) has also been moved to the
Apply menu (it was in the Transform menu instead)
|
|
This can be kept on file level but best keep out of operator functions.
|
|
|
|
Epsilon for small faces was too large.
Also suppress exception when all faces area are below the epsilon.
|
|
|
|
For cases when there are multiple matches,
find the closest match (with increasingly fuzzy tests) instead of failing.
|
|
This adds simple preset menu for unit scale scene property.
D1799 by @alm
|
|
|
|
|
|
Never used keys and better reload in same order loaded.
|
|
.blend1 file or not.
Requested by Aaron Carlisle (@blendify) over IRC.
|
|
|
|
Internally custom-id-properties used soft-limits, but there was no way to edit these.
|
|
invalid Python code/paths
The problem is that node trees (such as the Material, Lamp, and Compositor node trees)
are stored as "nested node trees" on the affected datablocks. They are particularly
troublesome to deal with, as the are not easily identified, and also cannot be easily
mapped back to the ID's which actually own them. As a result, the usual automated
methods do not work when dealing with these!
|
|
|
|
Also replace addon -> add-on
|
|
|
|
|
|
This uses selection history to select the next vert/edge/face based on surrounding topology.
Select previous just removes the last selected element.
Uses key-bindings: Ctrl-Shift +/-
|
|
Also make error handler take the exception as its argument.
|
|
The main reason for this change is this file is typically used when making bug reports,
its best if users attach this file to reports directly.
|
|
|
|
Now zooming text in the console and text editor isn't wrapping from large/small font size (annoying).
|
|
|
|
|
|
|
|
This option wasn't exposed since 2.4x.
D1622 by @candreacchio
|
|
previous version's config dir doesn't exist.
|
|
Adding/removing custom properties didn't refresh elsewhere in the UI.
|
|
|
