January 26, 2018, 22:42 (GMT) |
Speed up a little drawing of UVs in the Image Editor In my tests the previous loop was running in 200 ms. With this change it now runs in 17 ms. The difference in the end is still not great because the `draw_uvs_lineloop_bmface` function is called for each face and has an ImmBegin and ImmEnd in the function itself |
January 26, 2018, 22:06 (GMT) |
Code refactor: make mixed small/large BSSRDF radii more robust. |
January 26, 2018, 21:42 (GMT) |
Collections: As it turned out, this is quite harmless to have accessible everwhere I think ultimately we may move these operators from the outliner space to scene. Partial revert of a08f687b91a2a7880889. |
January 26, 2018, 21:37 (GMT) |
Make outliner new collection operator work via viewport too Technically this revert b3bcbc9e85aa. This however doesn't seem to be needed any longer. |
January 26, 2018, 19:10 (GMT) |
Outliner: If a collection is empty and you drag something inside it, it opens up. Idea by Pablo Vazquez. |
January 26, 2018, 17:47 (GMT) |
Fix mixed BSDF + BSSRDF sampling bug in path tracing, after 095a01a73a35. Spotted by Ha Hyung-jin, thanks! |
January 26, 2018, 17:47 (GMT) |
Code refactor: store RGB BSSRDF in a single closure. Previously we stored each color channel in a single closure, which was convenient for sampling a closure and channel together. But this doesn't work so well for algorithms where we want to render multiple color channels together. |
Revision 634e269 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) January 26, 2018, 17:19 (GMT) |
Apply onion opacity factor when fade disabled If the fade option is disabled, the opacity of the onion strokes is defined by opacity factor and not fixed as before. |
Revision bc1f587 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) January 26, 2018, 15:29 (GMT) |
Rename new GP monkey object to "Suzanne" (Same as we do for mesh monkey) |
Revision e3c802a by Pablo Vazquez (experimental_gp_weight, greasepencil-experimental, greasepencil-object, greasepencil-refactor, soc-2019-npr, temp-gpencil-eval, temp-greasepencil-object-stacksplit, temp-greasepencil-vfx) January 26, 2018, 15:16 (GMT) |
Rename empty Grease Pencil object from "GP Object" to "Blank" Also, name the Monkey palette "Suzanne" (same as we do for mesh datablock/object name) |
Revision e38b5ad 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) January 26, 2018, 15:07 (GMT) |
Change minimum alpha value for Onion Sometimes is necessary to make transprarent and before it was not possible using opacity slider. |
Revision de56355 by Bastien Montagne (blender-v2.79a-release, blender-v2.79b-release, fracture_modifier, fracture_modifier-master, temp-fracture-modifier-2.8) January 26, 2018, 14:18 (GMT) |
IMB: Add asserts that returned fps and fps base are strictly positives. Forgot to add that in previous commit, also related to T53003. |
Revision 3ee1a79 by Bastien Montagne (blender-v2.79a-release, blender-v2.79b-release, fracture_modifier, fracture_modifier-master, temp-fracture-modifier-2.8) January 26, 2018, 14:18 (GMT) |
Related to T53003: tweak scene fps range. Move restricted 'reasonable' range to ui_range, and allow wider values for manual settings. |
Revision a73b390 by Bastien Montagne (blender-v2.79a-release, blender-v2.79b-release, fracture_modifier, fracture_modifier-master, temp-fracture-modifier-2.8) January 26, 2018, 14:18 (GMT) |
Fix T53003: IMB: Invalid framerate handling due to short integer overflow. FFMPEG uses int for the numerator, while Blender uses a short. So in cases people gave weird exotic framerate values and we cannot reduce enough the numerator, we'd get totally weird values (even negative frame rates sometimes!) Now we add checks for short overflow and approximate as best as possible in that case (error should not matter unless you have shots of at least several hundreds of hours ;) ). |
January 26, 2018, 14:14 (GMT) |
IMB: Add asserts that returned fps and fps base are strictly positives. Forgot to add that in previous commit, also related to T53003. |
January 26, 2018, 14:12 (GMT) |
Related to T53003: tweak scene fps range. Move restricted 'reasonable' range to ui_range, and allow wider values for manual settings. |
January 26, 2018, 13:59 (GMT) |
Fix T53003: IMB: Invalid framerate handling due to short integer overflow. FFMPEG uses int for the numerator, while Blender uses a short. So in cases people gave weird exotic framerate values and we cannot reduce enough the numerator, we'd get totally weird values (even negative frame rates sometimes!) Now we add checks for short overflow and approximate as best as possible in that case (error should not matter unless you have shots of at least several hundreds of hours ;) ). |
January 26, 2018, 12:37 (GMT) |
fix:T53271 now using the context scene layer as requested |
January 26, 2018, 11:16 (GMT) |
Fix Collada importer (crash) We were not tagging depsgraph to update its nodes after importing new objects. |
January 26, 2018, 11:15 (GMT) |
Make object_update comment about lack of ID even more clear |
|
|
|


Master Commits
MiikaHweb | 2003-2021