[Bf-committers] [Bf-blender-cvs] SVN commit: /data/svn/bf-blender [47629] trunk/blender/intern/cycles: Cycles / Cleanup:

Thomas Dinges blender at dingto.org
Sat Jun 9 22:59:05 CEST 2012

I am not offended, but if you or someone else says that one of my 
commits broke something it's my obligation to check that and that takes 

All I did was a code cleanup, which removed some code inside Cycles, 
which simply does not affect general Texture pipeline at all.
The reorganized textures in the Cycles Shading system are there since 
Cycles was in Trunk, and the Texture UI indeed is different between BI 
and Internal, something that is also present since Cycles is in Trunk...

The Textur Workflow for that in Cycles is still WIP from what I remember 
though, Basic Color modification options for Textures still need to be 
added. For now just change back to Internal if you want to modify a 
texture and some fancy option there.


Am 09.06.2012 22:34, schrieb Daniel Salazar - 3Developer.com:
> Wait, do you feel personally offended because i might have confused a
> problem with one of your commits and failed to point to the exact culprit?
> Im the idiot then, i never attacked you! Feel free to point me to the
> correct commit, however if you want to be offended i can do better than
> that :)
> Back to business, the issue is changing the rendering context seems to
> change the texture UI in all contexts. I can not link the old procedural
> textures to a modifier when cycles is enabled. This is a problem because
> blender internal textures are extremly powerful as stand alone textures
> (can do ramps and a lot more without nodes). This helps with uses outside
> of the shading system. This is why I ask, whats the plan? Are we leaving
> the old textures forever available for this uses? Im away from my pc but
> will do demo files later
> peace
> Daniel Salazar
> patazstudio.com
Thomas Dinges
Blender Developer, Artist and Musician


More information about the Bf-committers mailing list