Revision 4818b3c by Sergey Sharybin November 22, 2016, 11:34 (GMT) |
Cycles: Fix re-definition of some functions on x32 arch |
Revision 1be717d by Bastien Montagne November 22, 2016, 11:24 (GMT) |
Fix (unreported) crash when drawing armatures' poses in some cases. Was affecting armatures' pose drawing code, could try to draw with non-updated pose, which may contain NULL bone pointers (e.g. after some data-block management tool execution, like make local, remapping, etc.). |
Revision edc10f5 by Sergey Sharybin November 22, 2016, 11:11 (GMT) |
Cycles: Another attempt to fix compilation on 32bit Linux |
Revision af444e9 by Sergey Sharybin November 22, 2016, 11:06 (GMT) |
Cycles: Attempt to fix 32bit buildbot builds after recent commit |
Revision 272412f by Sergey Sharybin November 22, 2016, 11:00 (GMT) |
Cycles: Implement texture size limit simplify option Main intention is to give some quick way to control scene's memory usage by clamping textures which are too big. This is really handy on the early production stages when you first create really nice looking hi-res textures and only when it all works and approved start investing time on optimizing your scene. This is a new option in Scene Simplify panel and it acts as following: when texture size is bigger than the given value it'll be scaled down by half for until it fits into given limit. There are various possible improvements, such as: - Use threaded scaling using our own task manager. This is actually one of the main reasons why image resize is manually-implemented instead of using OIIO's resize. Other reason here is that API seems limited to construct 3D texture description easily. - Vectorization of uchar4/float4/half4 textures. - Use something smarter than box filter. Was playing with some other filters, but not sure they are really better: they kind of causes more fuzzy edges. Even with such a TODOs in the code the option is already quite useful. Reviewers: brecht Reviewed By: brecht Subscribers: jtheninja, Blendify, gregzaal, venomgfx Differential Revision: https://developer.blender.org/D2362 |
Revision 927a168 by Sergey Sharybin November 22, 2016, 10:38 (GMT) |
GPU: Consider latest Gallium driver an official ATI/AMD This will make triple buffer used by default for such configuration. Ideally we would switch to triple buffer on all platforms, but let's do it in 2.8 branch and don't open can of worms in master now. This should solve issues like T49945. |
Revision bd8cbf5 by Sergey Sharybin November 21, 2016, 20:04 (GMT) |
Glog: Fix compilation error on ppc64el This was fixed in upstream already. Time to re-bundle? |
Revision dd51ec5 by Sergey Sharybin November 21, 2016, 20:03 (GMT) |
CLEW: Workaround compilation error on ppc64el Something was conflicting here, causing C++ to consider bool as a __vector(4) bool. |
Revision 94d8e6f by Bastien Montagne November 21, 2016, 19:57 (GMT) |
Partly revert own rBb97c567c1df1e, clear_proxy is actually safe. This is very confusing, in fact, and rna tooltip was wrong, BKE_object_make_local_ex actually ensures we never have several proxies of same object, since it always clears proxy when it has to copy object to make it local... What that RNA function is probably missing, though, is same logic as in BKE_library_make_local to actually remap proxy from old linked object to new local one. |
Revision b97c567 by Bastien Montagne November 21, 2016, 14:25 (GMT) |
Fix two very bad issues in new ID.make_local RNA function. I) `clear_proxy` parameter was not assigned to parm in RNA define code, so 'pyfunc optional' flag was set to `new_id` parameter of `user_remap` func - super ugly! II) `clear_proxy` parameter itself, when set to False, would allow to leave .blend file in invalid state (more than one proxy of same object), this should never, ever be allowed in RNA API imho. Left the PAI untouched for now, just disabled any effect from this parameter (hence always clearing proxy when copying). |
Revision 2a78635 by Bastien Montagne November 21, 2016, 14:25 (GMT) |
Cleanup: get rid of unused `BKE_constraints_relink()`. Libquery/generic ID remapping code handles this now. |
Revision 25c534f by Sergey Sharybin November 21, 2016, 13:37 (GMT) |
Fix T49981: New Depsgraph - When camera is on inactive layer, it does not evaluate constraints |
Revision af7343a by Sergey Sharybin November 21, 2016, 12:32 (GMT) |
Cycles: Attempt to fix compilation error on ppc64el There is some define conflict between system headers and clew, so delay include of clew.h as much as possible.] This is something which needed to be done in the code before the refactor, hopefully such change will still work. |
Revision 5eab3b0 by Sergey Sharybin November 21, 2016, 11:00 (GMT) |
Depsgraph: Fix infinite viewport object update in CYcles render mode The issue was caused by wrong object re-tag needed to have proper dependnecies update for OpenSubdiv. |
Revision b3c8ee8 by Sergey Sharybin November 21, 2016, 10:05 (GMT) |
Depsgraph: use more explicit parenthesis |
Revision 83b1f24 by Brecht Van Lommel November 20, 2016, 17:12 (GMT) |
Fix Xcode link error, missing definitions in RNA C++ API that other compilers ignored. |
Revision b86c6aa by Mai Lavelle November 20, 2016, 16:46 (GMT) |
Cycles: Don't shadow loop variable |
Revision f68ef05 by Brecht Van Lommel November 20, 2016, 14:45 (GMT) |
Cycles: add basic backwards compatibility for device selection, move to System tab. For the multi-GPU case users still have to reconfigure the devices they want to use. Based on patch from Lukas Stockner. Differential Revision: https://developer.blender.org/D2347 |
Revision aea4ed0 by Brecht Van Lommel November 20, 2016, 14:25 (GMT) |
Cycles: refactor culling code into utility class. |
November 20, 2016, 14:01 (GMT) |
Cycles: distance culling for objects. This can be used together with camera culling to keep nearby objects visible in reflections, using a minimum distance within which objects are visible. It is also useful to cull small objects far from the camera. Reviewed By: brecht Differential Revision: https://developer.blender.org/D2332 |
|
|
|


Master Commits
MiikaHweb | 2003-2021