On what version of Cycles is Bricklink Stud.io's Eyesight renderer based?

Archive User Feedback
1

I’ve been writing a lot of new custom colors for Stud.io. As such, I use the Blender Cycles Manual a lot for reference. However, the online manuals available for Cycles only go back to version 2.79. I think Eyesight is based on some version of 2.78 because even using the older versions of the manual there are still parameters listed that are not available in Eyesight.

So…I’d like to know on which version of Cycles Eyesight is based, and if there is a Cycles manual available for that particular version.

2

You’d have to ask them, we make the code available, what 3rd parties do with it is up to them.

1 Like
3

Got bored, did some digging in their binary, they built using some of our our svn libraries (I know it’s our libs since the paths embedded for some of the source files are local to my computer :slight_smile: ) which makes it easy to track down

they ship openimageio 1.7.15 which means the code is likely from somewhere in between 2017-06-04 and 2018-08-27 which is indeed around the 2.79 time frame.

It would have been nice if they kept the code opensource, so it could get all the improvements blender makes easily, but they seemingly chose not to go that way. which is somewhat strange since they clearly lifted the GPL licensed bf_blenlib [1] so the closed source nature of eyesight is odd to say the least.

[1] the executable contains strings like Error! Could not get the Windows Directory - Defaulting to Blender installation Dir! , Error! Could not get the Windows Directory - Defaulting to first valid drive! Path might be invalid! and BLI_dynstr_append text too long or format error. that can only could have come from bf_blenlib

6 Likes
4

Excellent information! Thank you!! I’m sorry you were bored, but I DO appreciate you doing a little digging. And the Cycles online manual DOES go back to 2.79.

2 Likes
5

Doesn’t that mean we can force them to open-source it? I think that sounds like a good idea.

1 Like
6

they built using some of our our svn libraries

Doesn’t that mean we can force them to open-source it?

There’s nothing wrong with using our SVN libraries, many libraries in there have a more permissive license than blender has.

I think that sounds like a good idea.

I certainly won’t stop you from executing what you deem a good idea.

I will stop you from necromancing a 2 year old thread though

7