April 8, 2021, 16:43 (GMT) |
Merge branch 'master' into temp-gpencil-bezier-stroke-type |
April 8, 2021, 16:19 (GMT) |
Cleanup: |
April 8, 2021, 16:12 (GMT) |
Fix previous commit: wrong `is_mesh_verts_only` check |
April 8, 2021, 16:07 (GMT) |
Fix T86762: Inconsistent show of result of modifier Screw in edit mode To check if an "is_mesh_verts_only" mesh, the overlay engine checks if the mesh has no "totedge" and has "totvert". However, sometimes this engine can check the wrong mesh since editmesh works on `embm->mesh_eval_final`. Reviewed By: fclem Differential Revision: https://developer.blender.org/D10917 |
April 8, 2021, 15:45 (GMT) |
April 8, 2021, 15:44 (GMT) |
Fix: Dragging a modifier to the same index recalculates modifier stack The fix is to simply check if the final index is the same as the start index and not call the "reorder" callback in that case. |
April 8, 2021, 15:42 (GMT) |
Cycles: Fix threading issues in the PathTrace render cancel The actual flow is a bit of a mystery to me, but there were cases when `PathTrace::cancel()` was waiting for the `PathTrace::render()` to finish, but the `render_cancel_.is_requested` was cleared so that the render_pipeline was not quitting. The new code seems more logical to me, but really wouldn't mind a second pair of eyes here. |
April 8, 2021, 15:35 (GMT) |
Spreadsheet: support showing data of specific node Previously, the spreadsheet editor could only show data of the original and of the final evaluated object. Now it is possible to show the data at some intermediate stages too. For that the mode has to be set to "Node" in the spreadsheet editor. Furthermore, the preview of a specific node has to be activated by clicking the new icon in the header of geometry nodes. The exact ui of this feature might be refined in upcoming commits. It is already very useful for debugging node groups in it's current state though. Differential Revision: https://developer.blender.org/D10875 |
April 8, 2021, 15:26 (GMT) |
Add ability to get a selection list of bones This adds the ability to get a selection list for both edit mode bones and pose mode bones. To do this the selection menu list logic had to be reworked a bit. Before it only stored the names of objects. This might work will of objects, however as stated in the code, it might fail for linked objects (so multiple object can have the same name in some corner cases). For bones it is a very common occurance where you can have multiple armature that has the same bone names. So now it also stores the object and bone pointers for this case. Reviewed By: Sybren Differential Revision: https://developer.blender.org/D10570 Fix T85796 |
April 8, 2021, 15:09 (GMT) |
EEVEE: Ensure Reflection: Use new implementation Use same implementation as Cycles. Is also a bit faster. Should also fix T86578 at the same time. |
Revision d18e74d by Clément Foucault (eevee-rewrite, temp-eevee-gpencil-rewrite, viewport-compositor) April 8, 2021, 14:22 (GMT) |
DRW: Fix debug print of error in shader lib dependency. |
Revision 8c753a2 by Clément Foucault (eevee-rewrite, temp-eevee-gpencil-rewrite, viewport-compositor) April 8, 2021, 14:22 (GMT) |
GPUTexture: Fix max FBO attachement in panoramic view + dof + eevee |
Revision 2a7d9d4 by Clément Foucault (eevee-rewrite, temp-eevee-gpencil-rewrite, viewport-compositor) April 8, 2021, 14:17 (GMT) |
EEVEE: Depth Of Field: Add back post process depth of field. Pretty much identical to the previous implementation. With the exception of a temporary noise function and some simplification of the CoC computation. This also fixes issues with the Ortho depth of field. Most of the files were modified to comply to new shader codestyle. This also adds partial support of panoramic cameras (bokeh and anamorphic is still buggy). |
April 8, 2021, 13:52 (GMT) |
Fix T81707: Spline IK Joints "Floating" above curve The issue was that where_on_path uses a resampled curve to get the data from the curve. This leads to disconnects between the curve the user sees and the evaluated location data. To fix this we simply use the actual curve data the user can see. The older code needed a cleanup either way as there were hacks in other parts of the code trying to work around some brokenness. This is now fixed and we no longer need to clamp the evaluation range to 0-1 or make helper functions to make it do what we actually want. Reviewed By: Campbell, Sybren Differential Revision: https://developer.blender.org/D10898 |
April 8, 2021, 13:51 (GMT) |
Cleanup: modernize-use-equals-default This was missing from rB19dfb6ea1f6745c0dbc2ce21839c30184b553878. |
April 8, 2021, 13:31 (GMT) |
GPencil: Bake Armature modifier for Bezier type |
April 8, 2021, 13:29 (GMT) |
Merge branch 'master' into temp-gpencil-bezier-stroke-type |
April 8, 2021, 13:06 (GMT) |
Cycles: Improvements for the resolution divider calculation * Do not report render and denoising time if render has been cancelled. It is not possible to estimate full rendering time from a cancelled state, and reporting wrong time gives the scheduler the wrong idea about how fast render is. * Use timing of the first sample to calculate start resolution divider. This timing is more accurate, because in viewport is known to include a single sample, and it resembles performance better because later on multiple samples might be scheduled, making it seen that render is faster. * Add some tolerance to the desired timing, so that if the higher resolution gives close enough timing we use higher resolution. This solves resolution divider bouncing between two values on a boundary values of render time (however, it does not eliminate requirement of hysteresis to really ensure this). Some utilities became public, so that they can be covered with the tests. This is mainly to verify own mental math, but also to allow to play with analytical formulas without breaking things. |
April 8, 2021, 13:06 (GMT) |
Cycles: Fix wrong OpenGL context manipulation in some cases When the BlenderSession is destructed from an initialization of a temporary are the current active context is window, not the draw manager. Made it so context release/activation goes correct in this case. Steps to reproduce an original issue: - Compile in debug mode, so that asserts are active. - Start Cycles viewport render. - Hit shortcut to open file (Cmd-O / Ctrl-O). |
April 8, 2021, 13:06 (GMT) |
Cycles: Stop rendering as quickly as possible The goal is to make it so stopping viewport render will happen as quick as possible. For example, when existing render mode or when opening a file browser. There is no need to wait for the viewport to be uniformly sampled in those cases. |
|
|
|


Master Commits
MiikaHweb | 2003-2021