July 28, 2016, 02:00 (GMT) |
Merge branch 'master' into blender2.8 |
July 28, 2016, 02:00 (GMT) |
Use COMPAT_ENGINES instead of RenderEngine.use_game_engine for panel poll methods This mostly affects physics panels. Any engines relying on RenderEngine.use_game_engine flag to show/hide panels will need to be updated. The COMPAT_ENGINES technique is how we usually deal with this. One issue with use_game_engine is that I cannot find a way to set it; it appears only the BGE can set it. This means (without this commit) external RenderEngines cannot get rid of the default physics panels. The RE_GAME flag (the C flag behind use_game_engine) is pretty hacky and we should look into removing its usage where possible. |
July 28, 2016, 01:58 (GMT) |
Move LocalView structs to DNA_screen_types.h |
July 28, 2016, 01:48 (GMT) |
Use LocalLayerInfo struct for area visibility bits |
July 28, 2016, 01:25 (GMT) |
Fix do_versions using wrong region list |
July 28, 2016, 01:16 (GMT) |
July 28, 2016, 00:36 (GMT) |
Add comments on behavior of spacedata and regionbase lists |
July 28, 2016, 00:27 (GMT) |
Fix own mistake from c05363e8895 Didn't know slink->regionbase is removed when area is active. Don't see why this is done, but it's confusing :S |
July 27, 2016, 21:09 (GMT) |
Fix T48790: Cycles render bug with zero strength lights. |
July 27, 2016, 20:36 (GMT) |
Cycles: Fix a memory leak when cancelling a denoised render |
July 27, 2016, 19:43 (GMT) |
Cycles: Fix another cause for NaN normals and a potential divide-by-zero in the background texture |
July 27, 2016, 19:43 (GMT) |
Cycles: Add Debug build option that enables floating point exceptions By enabling the new WITH_CYCLES_DEBUG_FPE, floating point exceptions are enabled in the CPU kernels. That way, the debugger stops as soon as an invalid calculation is performed, which makes it a lot easier to track these issues. Note that the option may cause problems in combination with the --debug-fpe runtime option. |
July 27, 2016, 19:05 (GMT) |
Fix crash closing Blender while in rendered local view Happens because it was always using regionbase of active/visible area, not the correct one of the (possibly inactive) 3D view. Was pretty hidden because you had to be in local view to trigger it. Could also remove ScrArea * argument from SpaceType.id_remap now, but leaving in there to avoid bigger changes (might also be useful for some case). Steps to reproduce: * Default startup.blend * Enter local view with default cube (/-key) * Render (or open a different editor where the 3D View is) * Close Blender - should invoke crash |
July 27, 2016, 18:18 (GMT) |
Cycles: Fix a rare divide-by-zero in a fallback sampling code The issue only appeared when the random number happens to be exactly one while a fallback sampling code for shallow paths was being executed. |
July 27, 2016, 17:45 (GMT) |
Fix memory leak when closing Blender with operator popup open Steps to reproduce: * Default startup.blend * RMB-Click on "Cube" item in outliner * Select Remap Users * Close Blender using window 'x' button |
July 27, 2016, 17:08 (GMT) |
Add/use utility macro for removing object from local view And correct existing macro. |
July 27, 2016, 16:56 (GMT) |
Make move to layer OP work with new local view data And fix crash on redo. Current behavior is the same as in master, which could be improved. If in local view, the move to layer OP just opens a confirmation popup saying "Move out of Local View". Confirming only moves the object out of local view, you have to use the redo panel to move it to a different layer. |
July 27, 2016, 16:06 (GMT) |
Start using separate bitfield for local view visibility Uses BKE macros to centralize things a bit. |
July 27, 2016, 14:06 (GMT) |
Fix T48946: Blender+Tahiti+DRI3+Unity+Linux GUI corruption/not rendering Enable triple buffer by default for AMD cards on opensource driver. Should be safe now, since it was only old cards causing problems, which we don't support now most likely anyway. |
July 27, 2016, 13:56 (GMT) |
Avoid creating multiple outputs connected to the same socket when creating a node group This patch fixes the annoyance that when creating a node group where one of its nodes is connected to several other nodes, a separate output will be created for each link, even though they're all connected to the same socket in the group. Now, before adding an output for an outgoing link, the existing outputs are checked to find whether any output is already connected to the same socket. If such an output is found, it is reused instead of creating a new one. Reviewers: Severin Subscribers: Blendify Differential Revision: https://developer.blender.org/D1836 |
|
|
|


Master Commits
MiikaHweb | 2003-2021