Tomato Cycles: use actual number of tiles for viewport rendering
authorSergey Sharybin <sergey.vfx@gmail.com>
Sun, 12 Aug 2012 11:58:34 +0000 (11:58 +0000)
committerSergey Sharybin <sergey.vfx@gmail.com>
Sun, 12 Aug 2012 11:58:34 +0000 (11:58 +0000)
commit711b97c2acbdda30e325df561907bf86bd8c7e6b
treea07d38e20ee9aff5c3b420696d383a38f2397c5f
parent8aeba8ec8b94d65d53f00b072f47812baa0c4c56
Tomato Cycles: use actual number of tiles for viewport rendering

Before this debug_tile_size was used as a size of tile, which
became hidden property since tile-based rendering implementation
and couldn't have been controlled.

This resolves the issue with single thread used for viewport
rendering in some cases. Also it makes possible to control tiles
for CUDA viewport rendering, which still behaves much faster when
using the single tile.

Also fixed issue with minimal tile size which was used to calculate
divider of final resolution to be used for initial rendering. Now
it's a Resolution Divider property in Performance tab. This option
could be used to tweak initial resolution of viewport for faster
navigation or faster refresh when changing some properties.
intern/cycles/blender/addon/properties.py
intern/cycles/blender/addon/ui.py
intern/cycles/blender/blender_sync.cpp
intern/cycles/render/session.cpp
intern/cycles/render/session.h
intern/cycles/render/tile.cpp
intern/cycles/render/tile.h
source/blender/editors/space_view3d/view3d_draw.c