Revision 298d311 by Thomas Dinges June 2, 2012, 21:04 (GMT) |
Cycles / Object Info Node: * The random output had a range from -0.5 to 0.5, added an offset of 0.5 to bring it into the 0.0 / 1.0 range, which is in alignment with Shader Node Guidelines. Patch by Agustin Benavidez, thanks! |
Revision 64039bd by Bastien Montagne June 2, 2012, 19:58 (GMT) |
Fixing most (if not all) remaining issues with nodes UI i18n. Note that I had to script-tag all sokets' names, as they are currently completely unknown from bpy.types (and hence unreachable for our po generating scripts). |
Revision d6128ae by Thomas Dinges June 2, 2012, 19:25 (GMT) |
Cycles / OSL: * Forgot to rename Gradient OSL file. |
Revision a5b2d2a by Thomas Dinges June 2, 2012, 19:14 (GMT) |
Cycles / OSL: * More OSL fixes for r41599, removed marble and wood texture and ported Wave Texture to OSL. |
Revision cf929c7 by Thomas Dinges June 2, 2012, 17:44 (GMT) |
Cycles / Wave Texture: * Found an issue in the shader code, it used the x coordinate twice. |
Revision d61e6e1 by Thomas Dinges June 2, 2012, 17:10 (GMT) |
Cycles / OSL Fixes: * OSL textures were never updated after the refactor in november 2011. * Remove stucci texture and renamed blend to gradient. |
Revision fea490c by Peter Larabell June 2, 2012, 00:16 (GMT) |
small code cleanup in rasterizer |
Revision db7fd6b by Peter Larabell June 2, 2012, 00:01 (GMT) |
small code cleanup in inner loop of rasterizer |
Revision 0dc84e6 by Campbell Barton June 1, 2012, 20:38 (GMT) |
experenental manual linking from the UI. realize this is an issue which is not agreed on so probably this will be disabled for release. the data is stored here so more dev can commit: ./release/scripts/addons/modules/rna_wiki_reference.py |
Revision e94e7b4 by Campbell Barton June 1, 2012, 20:28 (GMT) |
code cleanup: rename bool --> do_tint, confused qtcreator |
Revision 4fa34b5 by Bastien Montagne June 1, 2012, 17:47 (GMT) |
Commenting out unused var, prevents my debug Blender to build... ;) |
Revision 14b1c40 by Bastien Montagne June 1, 2012, 17:28 (GMT) |
Make "Match Movie Length" into an operator (must be called inside a context having either a "texture" Tex, an "area" SpaceImage, or both "edit_image" Image and "edit_image_user" ImageUser). Thanks to Campbell who pointed me to uiLayoutSetContextPointer() func! |
Revision 9efc294 by Daniel Genrich June 1, 2012, 16:50 (GMT) |
Followup fix Bugfix [#31629]: Cloth simulation collisions used still too high repulsions. |
Revision 3ea554e by Daniel Genrich June 1, 2012, 15:49 (GMT) |
Smoke Bugfix: Velocity of moving objects was too high after scaling patch. Spoted by MiikaH. |
Revision abc1a27 by Lukas Toenne June 1, 2012, 15:16 (GMT) |
Fix #31673, File Output node forgets about socket names. Was checking for wrong file version for do_versions. |
Revision 0446617 by Campbell Barton June 1, 2012, 15:05 (GMT) |
fix for crash when loading a file while rendering. |
Revision 392ee8f by Joshua Leung June 1, 2012, 15:00 (GMT) |
Tweaks for Pasting Keyframes in DopeSheet/Graph Editors In response to [#31670], I've reviewed the way that the Paste Keyframes tool for the DopeSheet and Graph Editors works. Previously, it required you to always select the F-Curves to paste the keyframes into before allowing you to paste keyframes. This was because it is quite difficult to infer which ID-block's set of curves is intended if more than one ID-block has similar curves (e.g. a scene with two materials, and both have their diffuse color animated). The underlying assumption and intention of the feature here was that the copy+paste were only being used by animators to copy animation between similar curves, to transfer and offset animation across block boundaries. However, it turns out that many people were by far more familiar with the simpler copy/paste paradigm from everywhere else (i.e. instead of trying to use duplicate to copy keyframes around within their respective F-Curves). Furthermore, in most cases there is only going to be a single character being animated at a time (vs multiple), which means that most of the time the matching problem is much simpler. Hence, the Paste now works as follows: - If there are selected F-Curves, we limit the paste-matching to only consider those in the selected F-Curves. This makes it possible to still explicitly specify where to paste. - In the more general case (no prior selections), pasting will try to match anything relevant it finds. TODO: - Check on whether the strictest matching level needs adjustments to limit the number of false positives - Testing and feedback of the new behaviour needed <--- ANIMATORS! PLEASE TEST |
Revision 07ce209 by Campbell Barton June 1, 2012, 14:59 (GMT) |
code cleanup: warnings |
Revision 341a991 by Sergey Sharybin June 1, 2012, 14:42 (GMT) |
Ignore track's disabled channels when requesting for pattern used in keying screen node |
Revision 32fe2d7 by Lukas Toenne June 1, 2012, 14:42 (GMT) |
Theme color for frame nodes. The alpha value from this theme color is also used when drawing frames with a custom color (which is just RGB). |
|