Revision fdb25a1 by Sergey Sharybin February 19, 2013, 09:51 (GMT) |
Fix #34249: collapse edges crash blender with a specific mesh OpenMP block was using shared variable, which for sure leads to threading issues. |
Revision 2d2164f by Campbell Barton February 19, 2013, 09:41 (GMT) |
fix [#34295] Color picker brightness to infinity simply clamp the color to the buttons softrange since color conversion can cause the value to scale outside the intended button limits. |
Revision e5a135e by Sergey Sharybin February 19, 2013, 08:37 (GMT) |
Fixes for alpha mode do_versions code Before this change only old flag "Premultiply" was used to detect alpha mode, which is not enough actually. Now the logic here is: - If "Premultiply" was enabled it is likely float image with straight alpha, which shall be premultiplied before usage. In this case image/sequence Alpha Mode is set to Straight. - Otherwise use default alpha mode for image format based on an extension. This could fail in some cases like TIFF, but this wasn't handled fully correct in older blender anyway. Initial discovered issue was that EXR images saved in older Blender versions were set to Straight alpha mode, which is obviously a straight way to lots of headache. |
Revision c68d532 by Campbell Barton February 19, 2013, 04:37 (GMT) |
fix for [#34283] wasn't working in my tests (attached to original report), made bone roll get compatible angle values with the original roll. |
Revision 926e0e7 by Joshua Leung February 19, 2013, 03:26 (GMT) |
Bugfix [#34283] armature bones losing their roll setting upon translation in edit mode My earlier fix for [#33974] (in r.54061) was causing some problems where manually specified roll values on horizontal or angled bones were getting reset. This could be nasty as you might not notice the changes for a while (especially when using stick bones without axes displayed). I've now put in place a hacky compromise solution which should catch both of these situations nicely. For z-axis (i.e. vertical) movements, the r.54061 fix is used, while for everything else (moving or just touch-n-go), the old setting is used. |
Revision 6550fb8 by Campbell Barton February 19, 2013, 02:48 (GMT) |
bpy.props.RemoveProperty() had incorrect docstring. |
Revision 098e423 by Campbell Barton February 19, 2013, 02:30 (GMT) |
minor change to own recent commit with transform fcurve centers and some style edits and typo corrections. |
Revision 4e73ff0 by Alex Fraser February 19, 2013, 02:24 (GMT) |
Fix for [#34099] Particles leaking from moving meshes This was caused by a floating point precision error. During collision detection, Newton-Raphson iteration is used to find the exact time of the collision. But when using subframes, the initial Newton step was too small. Now the initial step is given in absolute units. When subframes = 0, this should behave almost the same as before. Thanks to Janne Karhu, Lukas Toenne and Ton Roosendaal for their help with this patch, and to AutoCRC for funding. |
Revision 442d16b by Thomas Dinges February 18, 2013, 23:41 (GMT) |
Fix for [#34308] only half width of material list row is used for material name. * Issue was caused in r54393. |
Revision 47c29c1 by Pablo Vazquez February 18, 2013, 21:19 (GMT) |
Themes: disabled items on menus were using a color mix of text and text_selected, this didn't work nice with dark themes and text shadows and overall didn't make much sense. Now, disabled items use a mix of text and menu item background (inner) color. Same results, but allows dark themes with bright selected text to use shadows. Example case: http://pasteall.org/pic/show.php?id=45697 |
Revision 167dcc8 by Sergey Sharybin February 18, 2013, 19:34 (GMT) |
Force movie clips always use default alpha mode, before this straight alpha was used for them which doesn't work for cleaned footage stored in EXR file format. Perhaps we need to support configurable alpha mode for clips, but that's for later (maybe even after release), |
Revision 58c9691 by Sergey Sharybin February 18, 2013, 17:51 (GMT) |
Revision 525da1f by Brecht Van Lommel February 18, 2013, 17:39 (GMT) |
Fix wrong alpha channel for OpenGL render results with transparent textures or materials, the typical glBlendFunc(GL_SRC_ALPHA, GL_ONE_MINUS_SRC_ALPHA); blend function does not give correct destination alpha. |
Revision 9ab3d4f by Campbell Barton February 18, 2013, 16:35 (GMT) |
fix [#34303] Rotation fcurves don't work with transforming with individual centers |
Revision 4cd487d by Campbell Barton February 18, 2013, 15:47 (GMT) |
checking for V3D_LOCAL was duplicated in transform.c, and both checks not quite correct. - When checking edimode, make sure its mesh editmode. - Graph editor supports this option but wasn't being checked. |
Revision bd7648b by Ton Roosendaal February 18, 2013, 15:14 (GMT) |
Bug fix #34292 CTRL + MMB zoom in 2d editors now depends on 'max zoom' level. This makes zooms in UI (very limited) go smoother, but for fcurve or timeline it's same. |
Revision 5ba0eb0 by Brecht Van Lommel February 18, 2013, 15:08 (GMT) |
Fix some popups being too small on retina display, among them the new image dialog. |
Revision b0c6f87 by Brecht Van Lommel February 18, 2013, 15:08 (GMT) |
Fix #34290: backface culling option in 3d view was not interacting well with the option in the material in texture draw mode, now it always overrides the material. |
Revision 4ae3a28 by Campbell Barton February 18, 2013, 14:52 (GMT) |
fix bpy_extras.mesh_utils.edge_face_count_dict() helper api function. it was using tessfaces when theres no need to. |
Revision 98c5da4 by Brecht Van Lommel February 18, 2013, 14:03 (GMT) |
Fix #34276: OpenGL render not doing color space conversion to linear correctly with transparency, would show as too dark colors on edges. Found a strange issue here though, the alpha value in the OpenGL render result is not the same as the one specified in the material. It's not clear to me why this happens, color space conversions should not influence the alpha channel. |
|
|
|


Master Commits
MiikaHweb | 2003-2021