Hi, I feel like I have to clarify this, as I have read some wrong assumptions on forums and blendernation after this.
1) For Blender users nothing will change. Cycles will still be inside our main Blender repository, it will still be integrated via C++ into Blender. No performance or work flow loss of any kind will happen. And Cycles is and remains a blender.org project of course. 2) Cycles can be compiled as standalone executable since its first release in 2011. I just updated the code and extended the possibilities a bit. 3) The idea of this standalone project and an own git project (still on developer.blender.org) is just an *addition* for people who are interested here and want to integrate Cycles into other 3D programs. Again, for Blender users nothing will change, so time to relax... Thanks. Am 16.02.2014 18:56, schrieb Ton Roosendaal: > 2) Other projects > > - Thomas Dinges worked on Cycles standalone last week: > https://developer.blender.org/T38279#20 > He suggested to give Cycles an own git project. Is being reviewed how to > handle this efficiently. Brecht van Lommel doesn't think it's needed to > remove it from Blender's source tree, there's a way to have both. _______________________________________________ Bf-committers mailing list [email protected] http://lists.blender.org/mailman/listinfo/bf-committers
