We consider we will need about 4 months to complete the whole integration unless unexpected things come out down the road. We already figured out a lot of things and developed not a small part of the integration but there are still a lot of things to be done. Another thing is we have no way of communicating with the development team of Blender which also slows things down. There isn’t any standardization of the source-code, so it’s basically Spaghetti code which makes things even worse. The bad news is that since the software is open-source, it doesn’t have any documentation of the changes made as well as any comments in the code which furthers complicates our job since we have to reverse-engineer basically everything. The way the old implementation of V-Ray for Blender is integrated is no longer applicable, so there is no shortcut to make support for version 2.8 - we have to build it almost from scratch. The whole concept of the software from development standpoint has been completely reworked, it’s basically a new software which operates very differently than before. There is a huge fundamental difference between version 2.8 and previous version of Blender. We already spent more than a month on this matter and here is what we have found so far.
I just want to share some information regarding the development of V-Ray for Blender and our plans for the near future.Īs mentioned before we are working very actively on the support of Blender 2.8. Hello and Happy New Year to everyone here. Here is some new interesting info about V-ray for Blender project :
0 kommentar(er)
