Revision c707b91 by Sergey Sharybin January 12, 2015, 09:49 (GMT) |
Cycles: Optimize leaf splitting code by avoid vector allocation Use variables allocated in the stack and avoid heap allocation which should make leaf splitting code a bit faster. |
Revision b56f590 by Sergey Sharybin January 12, 2015, 09:49 (GMT) |
Cycles: BVH params option to split leaf node by primitive types The idea of this change is make it possible to split leaf nodes by primitive type, making leaf containing primitives of the same type. This would become handy when working on a single ray to multiple triangles intersection code, plus with careful implementation it might give some extra benefits on BVH traversal code by avoiding primitive type fetch and check for each primitive in the node. But that's a bit tricky to have benefits on this change only because depth of BVH increases. This option is not exposed to the interface at all and not used even secretly, the commit is only needed to help working further in this direction without messing around with local patches and worrying of them running out of date. |
Revision d8fc404 by Campbell Barton January 12, 2015, 07:56 (GMT) |
Cleanup: style |
Revision bae5826 by Campbell Barton January 12, 2015, 07:30 (GMT) |
Fix T42069: Fonts /w non-ascii paths fail in win32 Workaround freetype's use of fopen by swapping FT_New_Face for our own version which uses BLI_fopen. |
Revision f9c7cbd by Campbell Barton January 12, 2015, 00:46 (GMT) |
revert part of 7a1dc20 These warnings are false positives & confuses intended logic to set dummy values. |
Revision 1864253 by Antonis Ryakiotakis January 11, 2015, 20:29 (GMT) |
Fix T43208 material flickering in edit mode. Happens because material setting now occurs in the derived mesh drawing routine as it should. However that means that it also happens during selection and that influenced the drawing state somehow. In 2.72 this did not occur because material setting happened during draw setting (skip or draw) instead of after the draw setting passed (so selection would skip it by use another draw setting function). Of course this violated design but worked. Made it now so backbuffer selection does not enable materials (it's redundant in those cases anyway). This could be ported to a possible 'a' release but as is classic with display code there may be some other places that it could backfire. Tested fix with texture/vertex painting and selection which use backbuffer for both subsurf and regular meshes and it seems to work OK. |
Revision 0a5ad65 by Bastien Montagne January 11, 2015, 20:23 (GMT) |
Modifiers shall be listed in alphabetical order in UI... |
Revision 7a1dc20 by Bastien Montagne January 11, 2015, 20:14 (GMT) |
Cleanup: quite some harmless but noisy warnings from gcc... |
Revision 1b3b011 by Bastien Montagne January 11, 2015, 17:33 (GMT) |
Transfer data: cleanup: Remove 'vertex_group_transfer_weight' operator. We can now use 'generic' data transfer instead. Note new one is not an exact replacement, it should be able to do everyting old op could do though, and more. |
Revision a628a82 by Bastien Montagne January 11, 2015, 17:32 (GMT) |
Data transfer: make operator able to work 'reversed' (i.e. transfer from selected objects to active). Needed to replace weight transfer modifier in WeightPaint mode... Note this is not exposed to users in UI, shall remain technical intern parameter imho. Esp. since behavior when several sources is a bit 'random' (merely uses each source in selection order...). Also, this correct a bug, where 'lib' linked objects/meshes could not be used as source... |
Revision 599c8a2 by Bastien Montagne January 11, 2015, 13:59 (GMT) |
Fix T43204: Shrinkwrap constraint, project mode: Space ignored in bone case. Own fault in rBb154aa8c060a60d to fix T42447... Reverted that commit, and added kind of not-so-nice hack instead. Note root of the issue comes from the special case we are doing here re 'Local' space of parent-less objects. In that case, local space should be the same as world one, but instead we apply the object rotation to it... This is inconsistent with all other cases and could very well lead to other issues as T42447, but afraid fixing that properly would be rather hairy - not to mention it would likely break all existing riggings etc. :( Should be safe for a 2.73a, shall we need it. |
Revision cd2d84d by Bastien Montagne January 10, 2015, 21:54 (GMT) |
Fix three issues reported by coverity in own recent code. Including two potential crashers. |
Revision 5357474 by Bastien Montagne January 10, 2015, 18:15 (GMT) |
Fix building with very strict flags, use size_t rather than int for string length. Reported on bf-committers. |
Revision ab3f037 by Joshua Leung January 10, 2015, 13:15 (GMT) |
GPencil Editing: FKEY now controls the eraser size when in Stroke Edit Mode |
Revision 9590e77 by Campbell Barton January 10, 2015, 01:40 (GMT) |
cleanup: style & warnings |
Revision dec523d by Campbell Barton January 10, 2015, 01:32 (GMT) |
Fix for regression in bmesh connect-pair T42563 fix wasn't right, fortunately this doesn't fail in most cases. |
Revision 79d8617 by Bastien Montagne January 9, 2015, 23:04 (GMT) |
Transfer data: add modifier. Not much to add, modifier uses same code as operator basically, only key difference is that modifier will never create data layers itself, you have to use dedicated operator for that. |
Revision 8615977 by Joshua Leung January 9, 2015, 22:20 (GMT) |
Fix: Delkey didn't activate the Grease Pencil strokes delete operator like XKEY does |
Revision ee4453f by Bastien Montagne January 9, 2015, 18:32 (GMT) |
Transfer Data: add main core code and operators. This add code needed to map a CD data layout from source mesh towards destination one, and code needed to actually transfer data, using BKE's mesh remap generated data. This allows to transfer most CD layers (vgroups, vcols, uvs...) as well as fake, boolean ones (like smooth/sharp edges/faces, etc.). Some types are not yet transferable, mainly shape keys, this is known TODO. Data transfer can also use some advanced mixing in some cases (mostly, vgroups and vcols). Notes: * New transfer operators transfer data from active object towards selected ones. * Modifier will be committed separately. * Old weight transfer code (for vgroups) is kept for now, mostly because it is the only usable one in weightpaint mode (it transfers from selected object to active one, this is not sensible in Object mode, but needed in WeightPaint one). This will be addressed soon. Again, heavily reviewed and enhanced by Campbell, thanks! |
Revision 67b1412 by Antonis Ryakiotakis January 9, 2015, 18:23 (GMT) |
Radial operator number angle input should use angles. Much more lenient if you are a human. |
|
|
|


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