May 1, 2017, 22:30 (GMT) |
Use DNA as a prefix |
May 1, 2017, 22:30 (GMT) |
Use DNA as a prefix, for workspace define too |
May 1, 2017, 21:20 (GMT) |
Clear win->screen pointer Caused assert when loading |
May 1, 2017, 21:03 (GMT) |
Merge branch '28' into workspaces |
May 1, 2017, 20:57 (GMT) |
Revert minor order change - wm_file_read_post This function is meant to be last and I couldn't redo any bugs after re-ordering. |
May 1, 2017, 20:52 (GMT) |
Use Main as the first argument |
May 1, 2017, 20:45 (GMT) |
Fix for crash loading a file containing a temp (maximized) screen. Not pretty, we need to remove temp workspaces after creating them because of order-of-initialization logic here, see: D2451#62433 |
May 1, 2017, 17:53 (GMT) |
Cycles integration with Draw Manager Note: This crashes very easily when building with OpenColorIO. Not sure what the problem is. |
May 1, 2017, 16:06 (GMT) |
Re-order for versioning |
May 1, 2017, 15:53 (GMT) |
Use printf instead of assert I can only assume BLI_assert wasn't configured to call real asserts, is seems this is more of a warning. |
May 1, 2017, 15:18 (GMT) |
Fix buffer overrun when setting the name Would happen on default startup file. Strings allocations were set to `but->hardmax + 1`, not `items->maxstrlen` |
Revision ded0f96 by Antonio Vazquez (experimental_gp_weight, greasepencil-experimental, greasepencil-object, greasepencil-refactor, soc-2019-npr, temp-gpencil-eval, temp-greasepencil-object-stacksplit, temp-greasepencil-vfx) May 1, 2017, 14:20 (GMT) |
Merge branch 'blender2.8' into greasepencil-object |
May 1, 2017, 14:13 (GMT) |
Odd use of BLI_strncpy (just use strcpy) |
May 1, 2017, 13:51 (GMT) |
Merge branch '28' into workspaces |
April 29, 2017, 18:53 (GMT) |
Reimplement curve smoothing in a clear way without premature optimizations. The original code tries too hard to avoid allocating more memory, which reduces clarity and is not necessary here as there aren't that many f-curve keyframes in any case. Rewriting the code with a generic solver somehow fixed the behavior of the curve in the totally unclamped case, which suggests that there was a bug hidden in the optimizations. In addition, the new solver allows treating the case when an Auto curve segment ends at a Vector handle specially as a zero acceleration boundary condition. |
April 29, 2017, 08:25 (GMT) |
Repeat the curve smoothing pass when clamping handles. When non-extreme Auto Clamped handles are clamped to prevent overshoot, it creates a discontinuity with the preceeding part of the curve that was computed under assumption of no clamping. Thus to avoid jumps in certain situations it is necessary to lock these handles and run the smoothing pass again. Handles are locked in this way only if they are clamped in the right direction; points that are trying to move against the curve are clamped to horizontal but left free to be modified by the subsequent pass. |
April 29, 2017, 08:25 (GMT) |
Fix BKE_nurb_handle_calc_smooth: no clamp 'HD_AUTO' handles. |
April 29, 2017, 08:25 (GMT) |
Fix clamping of auto handle in some rare case. |
April 29, 2017, 08:25 (GMT) |
Implement smarth algorithm to compute automatically the bezier handle that produce no acceleration discontinuities in a series of auto handle points. The result trajectory is physically as 'smooth' as possible given a set of fixed point and a start and end location and velocity. See BKE_nurb_handle_calc_smooth() |
April 29, 2017, 08:25 (GMT) |
force fcurve AUTO handlers to use 1/3 of the distance for smoothness see: http://www.blender.org/forum/viewtopic.php?p=65508&sid=02e88fe6e3a43338ec8bc354991bc402 Note: this is also used by the curve code. The magic number 2.5614f comes from review 290361776e5858b3903a83c0cddf722b8340e699 |
|
|
|


Master Commits
MiikaH:n Sivut a.k.a. MiikaHweb | 2003-2021