You're blocking ads, which pay for BlenderNation. Read about other ways to support us.

Blender developers meeting notes: 18 March 2019

2

Brecht writes:

New Features and Changes

About 130 bugs were fixed in the last week.

  • Subdivision surface performance when transforming in edit mode was improved. The topology is now cached for faster updates. Performance of editing topology is still not as fast as before, however. (Sergey Sharybin)
  • Cycles CUDA render performance has been improved by 5-20% on production scenes, due to better thread scheduling. (Stefan Werner)
  • Cycles OpenCL viewport render now shows an ambient occlusion preview render until the kernels are fully compiled, to keep the viewport interactive. Kernel re-compilation on changes is needed less often as more features are always enabled. (Jeroen Bakker)

  • Shader node editor: panels with light and world settings in the sidebar, as was already available for materials. (Brecht Van Lommel)
  • Preferences: new settings to display factors as percentages throughout the user interface. (Jacques Lucke)
  • Help > Report Bug now automatically fills the bug reporting form with system and Blender info, we recommend users to use this for complete and accurate info. (Ray Molenkamp)
  • Windows builds now include batch files for easily running Blender with debug log output. The resulting log files can be attached to bug reports. (Ray Molenkamp)
  • X3D add-on: now available in 2.8 again. (Bastien Montagne)
  • Python API: there is now an API for add-ons to register tools in the toolbar. Example code is available as a template in the text editor. (Campbell Barton)
  • Python API: ShaderNodeCustomGroup was added to define custom node groups for Cycles and Eevee. Works the same as existing NodeCustomGroup. (Miguel Porces)

Development

  • Cycles now uses CUDA toolkit 10.1 as the officially supported version, we recommend upgrading for best performance and stability.
  • In the bug tracker, developers are encouraged to look also at older reports marked as Need Information or Need Triangle. Also to mark important older bugs as high priority so they get attention.

Weekly Reports

About Author

Bart Veldhuizen

I have a LONG history with Blender - I wrote some of the earliest Blender tutorials, worked for Not a Number and helped run the crowdfunding campaign that open sourced Blender (the first one on the internet!). I founded BlenderNation in 2006 and have been editing it every single day since then ;-) I also run the Blender Artists forum and I'm Head of Community at Sketchfab.

2 Comments

  1. "Cycles CUDA render performance has been improved by 5-20% on production scenes, due to better thread scheduling. (Stefan Werner)"

    *Foams at the mouth*

    Yesss
    YESSSSSS!

  2. The last paragraph: "In the bug tracker, developers are encouraged to look also at older reports marked as Need Information or Need Triangle. Also to mark important older bugs as high priority so they get attention."

    Should "Need Triangle" instead read "Need Triage"?

Leave A Reply

To add a profile picture to your message, register your email address with Gravatar.com. To protect your email address, create an account on BlenderNation and log in when posting a message.