| Age | Commit message (Collapse) | Author |
|---|
|
No need to call l10n stuff when it's disabled in the preferences.
Reviewed by @mont29, thanks!
|
|
There is a key conflict between grease pencil shortcuts and sculpt
shortcuts (D and ctrl D were taken by draw brush and dyntopo toggle,
respectively). Based on feedback, change dyntopo toggle to ctrl-T and
draw brush to X.
Also add missing property update for dyntopo detail size.
|
|
|
|
|
|
|
|
render layers.
Reviewers: brecht
Differential Revision: https://developer.blender.org/D346
|
|
Also fixed wrong frame number used for reconstructed object
visualization in 3D viewport.
|
|
|
|
Note that the screencast implementation is quite poor and that you may not even
get the requested FPS, the timing system here is not reliable.
|
|
Issue was caused by cycles setting scene frame which will update scene for
all the layers (not just visible ones) which confuses depsgraph making
objects which are needed as dependency are not really evaluated.
Made it so setting frame via scene.frame_set() which check whether update
need to be flushed to an invisible objects and do this if so.
Not ideal solution but seems to be safest at this point.
|
|
|
|
these would become positive on update
|
|
viewport.
|
|
Don't change user count when setting modifier objects
|
|
|
|
|
|
immediately
|
|
|
|
Poll function tried to be smart and disallow having dependency cycles,
but it didn't work properly. Further, it still possible to re-shuffle
strips stack in the way which introduces dependency cycles.
So disabled this smartness in the poll function for now.
|
|
|
|
After some discussion it seems both are valid defaults but useful for
very different purposes.
- 'free' lets you explore the scene with full 6dof (like fly mode)
- 'orbit' is closer to typical mouse view orbit, constraining to orbiting about a central location.
This doesn't effect orbit/pan which are available with modifier keys.
|
|
Useful for cases when you need to create bunch of witness tracks.
|
|
|
|
Caused by own recent changes to menu handling
|
|
|
|
it was mistake in rB50b2c78ad8b6.
|
|
causes a segfault.
Non-camera objects are not supported as cameras, and trying to use them
just causes memory errors (some bad typecasts are involved). When converting
a Scene Actuator, only use the object as a camera if it is actually a camera.
Also, the logic brick UI now filters for camera objects, which should help
avoid confusion.
|
|
This is because the sub-paths of the individual sockets are defined as
FILEPATH properties, which automatically adds the standard fileselect
operator button in the uiLists. However, that operator returns full
paths only, with no direct way to make them relative to the base path.
So for now i've turned the subpath properties into regular strings,
which removes these operator buttons but should at least avoid the
confusion.
Eventually new operators could be defined for this, which use the file-
select operator and then make the path relative.
|
|
Default Values is used on it.
The default for the socket value was always 0. Now the default value for
node socket default_value properties is chosen based on the socket
subtype to give some more sensible values.
NOTE: this may still be different from the values specified in the
socket templates! It is not possible to directly use these template
values, because all sockets share the same RNA types. At least it should
work reasonably well in the majority of cases now.
|
|
|
|
|
|
single terminator item.
Ideally no enum item function should return NULL, but since this is very
common and an intuitive mistake, better handle that case gracefully in
the RNA access function.
|
|
|
|
Deadlock between python script evaluation thread and
drivers evaluation caused by scene update invoked from
ED_screen_set_scene().
Pretty much the same as setting scene current frame
with the same solution BPy_{BEGIN,END}_ALLOW_THREADS.
|
|
|
|
|
|
|
|
This swapped translation for all ndof events.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
also increase maximum sensitivity
|
|
The "Cast Shadows" worked as expected, but it can cause problem in some cases.
For example, when using strand render, we need disabling only buffer shadows,
but the previous changes made that impossible. "Cast Shadows" should be added
as a newly created option.
|
|
ray shadows also, and rename it to "Cast Shadows".
This allows us to make materials that don't cast ray shadows.
Turning off this property can reduce the rendering time slightly.
Note: RNA path is changed to "use_cast_shadows" as well. The older
path "use_cast_buffer_shadows" still can be used as its alias, but
it will be removed after updating some addons.
Reviewed By: brecht
Differential Revision: https://developer.blender.org/D272
|
|
types
While some of these are rather rough and crude, they should be sufficient to provide
some helpful hints to (new) users when mousing over the editor type selectors
(i.e. now we can see the names of the editors; without the descriptions, the enum
item names wouldn't get shown) and also when browsing the list.
This is useful now that we have the ability to display tooltips in menus, thanks
to Campbell's earlier commit (35f62bd)
|
|
FCurve Noise Modifer now has an extra float property which offsets the noise in time.
This is useful for creating follow through in procedurally animated noise.
For example, if you've used a noise modifier on a parent bone to add additional movement,
a quick and easy way to add overlapping motion is to create copies of that modifier on
its children, and then offset the time those curves play at. See this in action at:
http://youtu.be/Ph6fk_z_k3k
Reviewed By: Joshua Leung
|
|
|
