From what I can tell this is going into 2.79 next revision but getting refined at the moment.
** \file BKE_blender_version.h
/* these lines are grep’d, watch out for our not-so-awesome regex
- and keep comment above the defines.
- Use STRINGIFY() rather than defining with quotes /
#define BLENDER_VERSION 279
#define BLENDER_SUBVERSION 2
/ Several breakages with 270, e.g. constraint deg vs rad */
#define BLENDER_MINVERSION 270
#define BLENDER_MINSUBVERSION 6
/* used by packaging tools /
/ can be left blank, otherwise a,b,c… etc with no quotes /
#define BLENDER_VERSION_CHAR
/ alpha/beta/rc/release, docs use this */
#define BLENDER_VERSION_CYCLE alpha
extern char versionstr[]; /* from blender.c */
#endif /* BKE_BLENDER_VERSION_H */
Right now it’s the following issue:
viewport rendering of BMW from official benchmark pack takes 12seconds on 1080TI, 20seconds on Vega64 and 16 seconds using both. With F12 render, that’s the opposite, Vega is faster with 82sec (at 128x128, best time), 1080Ti takes 93seconds (at 16x16, best time) and both take 44seconds using latest master with initial_num_samples at 5000.
To sum up:
- viewport seem really slow in latest master. OpenCL. 2.78c with selective node compilation for viewport renders nearly 2x faster on Vega 64. It’s not due to SSS or volume as those are not compiled in viewport kernel either. I can investigate on that.
- multi-device rendering is slower with viewport/progressive rendering than the fastest device alone. Logic would be to wait for the slowest half to finish, which would be around 10seconds for Vega?
I’m glad it’s not going into 2.8 first. Let us bang on it and file bugs to test, and then later roll it up into the big future release.