[Bf-committers] bake-cycles merged in master

[Thomas Beck]

Hi Dalai,
as I wrote on several platforms now: Awesome work and incredibly useful for
my work! Will test that extensively in the coming weeks...

One thing is hindering my workflow though (generally, not Cycles baking
fault): You always have to select the image datablock in the UV/Image
editor whenever you want to see the baking result (because selecting a
texture node is not changing the associated texture automatically). I
disliked the functionality right from the start (I know Andrew, we
introduced it on your request)... but it is even more apparent now that we
have baking in trunk and need to select many objects one after another to
see the result. It would be much more clear to the user when we would
automatically change the UV/Image whenever we select an image texture node
- what is to be said against that? ... What do you guys think-should we
open up a UI topic for this on b.d.o?

Other than that - thanks so much for your work!
Many greetings, Thomas


2014-05-03 12:45 GMT+02:00 Dalai Felinto <dfelinto at gmail.com>:

> Dear all,
> Just a note to say that the bake-cycles branch is fully merged in master.
>
> I split the commits in 3 categories:
>  1. Blender core new utility functions, independent of baking,
> separate commits (BLI_, IMB_, ...).
>  2. Bake API - generic API structure to be implemented by interested
> external render engines
>  3. Cycles Baking - Cycles implementation of baking, independent of Blender
>
> Since I did a lot of squashing and I forgot to reset the date of the
> commits,the emails in bf-cvs show them in a strange order. git log
> shows them as intended, regardless of the commit timestamp, so we
> should be fine.
>
> I still need to include Cycles baking in the release logs for 2.72,
> but the documentation is online:
> http://wiki.blender.org/index.php/Doc:2.6/Manual/Render/Cycles/Bake
>
> If someone needs help to integrate an external engine (LuxRender, ...)
>  with the Baking API let me know. The Cycles Baking commit [eec3eab]
> should have all you need though.
>
> For the records: 56d8aff 198f5e5 97641a0 3312b20 eec3eab :
>
> * https://developer.blender.org/rB56d8aff
> * https://developer.blender.org/rB198f5e5
> * https://developer.blender.org/rB97641a0
> * https://developer.blender.org/rB3312b20
> * https://developer.blender.org/rBeec3eab
>
> Thanks everyone for all the help, and thanks for the contributors of
> Blender Development Fund. And let the tests begin.
>
> [cross posted on bf-gamedev (tests/workflow/usability related replies)
> and bf-committers (other Blender dev related replies)]
>
> Best regards,
> Dalai
> --
> blendernetwork.org/dalai-felinto
> www.dalaifelinto.com
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>
>


-- 

------
Plasmasolutions
Design | Development | Training

Website: Http://www.plasmasolutions.de <http://www.plasmasolutions.de/>
Blog: Http://blog.plasmasolutions.de <http://blog.plasmasolutions.de/>

Telefon: 0176 2017 9565