[Bf-cycles] Cycles as Default Engine
db4tech at yahoo.co.uk
Thu Jun 19 20:50:32 CEST 2014
Have to say I definitely agree. Already made it my default a few years ago.
Skip next line if not interested in my history.
I came to Blender when Cycles development had just begun, so tried both
BI and Cycles, even at that time of early Cycles development (as a new
user) Cycles seemed so much more logical and easier to use.
Possibly raising default /Render/ and /Preview/ samples > 10? I see new
users yet to discover the /Sampling/ section wondering why their renders
Maybe two default Tiles sizes, one for GPU and CPU, rather than 64 x 64
for both? Enabling more efficient faster renders for newer users.
Can see a selection of pre-set surface node groups being very helpful
for new users. Good idea!
On 19/06/2014 17:51, Thomas Dinges wrote:
> I think it's time to make Cycles the default engine in Blender. This has
> been discussed a few times already, and the argument was to wait until
> we have Volume/Smoke etc..
> Now that we do, it's time to act. :)
> 1) Any open issues?
> Sergey fixed some remaining issues with Preview Rendering for Brushes
> etc, while Cycles is the active engine. Are there any other problems
> that need to be addressed?
> 2) Presets
> I think we should have some presets, at least a "Standard Surface" for
> Beginners. Brecht made a quick hack for that a while back, I think
> having bundled Node Groups is still the way to go.
> I would like to do the move for Blender 2.72 (upcoming Release).
> Bf-cycles mailing list
> Bf-cycles at blender.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Bf-cycles