Revision c1095c7 by Sergey Sharybin March 23, 2016, 18:28 (GMT) |
Revert "Fix T47869: OpenColorIO Error with unicode path to config file under Windows" White the config itself could be loaded this way, lookup tables can not. Additionally, that's not really clear how to solve the issue with search path which is multi-byte only in the API. Reverting for further investigation. This reverts commit ab4307aa0868f2d8389cc0dd500eff38909b08f1. |
Revision 376eb77 by Campbell Barton March 23, 2016, 18:23 (GMT) |
Fix T47900: VSE adjustment crashes on blank frame |
Revision 2103e21 by Sergey Sharybin March 23, 2016, 14:42 (GMT) |
Fix T47870: Missing viewport update when material output is inside of the group |
Revision c87e655 by Joshua Leung March 23, 2016, 14:32 (GMT) |
Fix T47833: View-aligned GPencil strokes move in crazyspace when grabbed These fixes "seem" to do the right thing now... |
Revision ab4307a by Sergey Sharybin March 23, 2016, 14:09 (GMT) |
Fix T47869: OpenColorIO Error with unicode path to config file under Windows |
Revision 6a4967c by Joshua Leung March 23, 2016, 13:45 (GMT) |
AnimEditors: Fuzzy/Multi-Word Name Filtering Thanks to D1080 by @rockets, I've now been able to easily implement the ability to type multiple word snippets/partial words into the text filter field (in the Animation Editors), and have it filter the channels which contain just some of those parts (instead of having to match everything). For example, the following search strings will now work: * "loc rot" or "lo ro" will now filter all location and rotation FCurves * "col loc" will filter all location and color FCurves * "scale" will also work as before to filter all scale FCurves But, the following will not work: * "lc rt" will NOT filter all location and rotation, as the fuzzy search only breaks down the search string based on whitespace placement By default, this is not enabled when using name filtering (i.e. magnifying glass is checked, and some filtering text is specified). Instead, you need to enable the "AZ" toggle beside the name field. This fuzzy matching is not enabled by default as it could end up being quite a bit slower on really heavy scenes. (There are probably some optimisation opportunities, but that's only a future option if someone really needs it) |
Revision 21f31e6 by Sergey Sharybin March 23, 2016, 12:58 (GMT) |
Fix T47856: Cycles problem when running from multi-byte path This is a mix of regression and old unsupported configuration. Regression was caused by some checks added on Blender side which was checking whether python function returned error or not. This made it impossible to enable Cycles when running from a file path which can't be encoded with MBCS codepage. Non-regression issue was that it wasn't possible to use pre-compiled CUDA kernels when running from a path with non-ascii multi-byte characters. This commit fixes regression and CUDA parts, but OSL still can't be used from a non-ascii location because it uses non-widechar API to work with file paths by the looks of it. Not sure we can solve this just from our side by using some codepage trick (UTF-16?) since even oslc fails to compile shader when there are non-ascii characters in the path. |
Revision 6e31f4f by Campbell Barton March 23, 2016, 12:40 (GMT) |
Fix T47893: BGE crashes w/ generated mesh data |
Revision 74399e0 by Joshua Leung March 23, 2016, 12:00 (GMT) |
Radial Operator: Tweak number of digits displayed for the different property types * As requested by venomgfx, rotations now only display to 2 decimal places (more than enough for rotations in degrees) * Also, made it so that the "factor" types now show 3 dp (previously only 2, which isn't really enough when dealing with values from 0.0 - 1.0) |
Revision 9815262 by Joshua Leung March 23, 2016, 12:00 (GMT) |
Radial Control Operator: Always show the property name + value on the header The radial control operator is commonly used for setting sculpt brush Size and Strength settings. However, when using it, it can often be difficult to remember which hotkey is responsible for which setting, meaning that you can often accidentally modify the wrong setting without knowing it (or even what new value you've set it to). This commit makes it so that the property name and the current value are always shown on the header. Previously this info was only shown when the doing numeric input. (It also fixes a bug where the numeric input print would hang around even after it wasn't being used). |
Revision 0f501a7 by Campbell Barton March 23, 2016, 10:02 (GMT) |
Revision 80a7efd by Campbell Barton March 23, 2016, 07:51 (GMT) |
Revision b0a7e77 by Campbell Barton March 22, 2016, 17:47 (GMT) |
Cleanup: style |
Revision c31c539 by Campbell Barton March 22, 2016, 17:25 (GMT) |
Cleanup: style (80-width) |
Revision 46dd04f by Campbell Barton March 22, 2016, 16:54 (GMT) |
Fix incorrect strncat use |
Revision 0f1d711 by Campbell Barton March 22, 2016, 16:37 (GMT) |
Revision 84d8b35 by Campbell Barton March 22, 2016, 14:25 (GMT) |
Weight Paint: support accumulate for blur brush This re-applies smoothing based on the previous update. Can smooth more but harder to get such even distribution. |
Revision e2181c2 by Lukas Toenne March 22, 2016, 14:07 (GMT) |
Fix for crash of point density textures due to undefined `point_data` on loading. |
Revision 220a7a4 by Campbell Barton March 22, 2016, 11:37 (GMT) |
Weight Paint: blur now smooths connected weights Previously it would average all points under the brush, giving an off feedback loop that often depended on the direction of the brush stroke, giving not-very-useful smearing effect. Now blend brush smooths between connected edges. |
Revision 29acdb4 by Campbell Barton March 22, 2016, 11:07 (GMT) |
Mesh API: add BKE_mesh_vert_edge_vert_map_create Handy when you need to reference connected verts directly. |
|
|
|


Master Commits
MiikaHweb | 2003-2021