- User Since
- Apr 22 2014, 6:04 PM (186 w, 6 d)
Thu, Nov 9
Aug 13 2017
After all it was my fault.
Aug 11 2017
Changing the 2.79 folder's name, or removing it completly still produces the same error in my win10/x64 machine.
It seems a python problem. I'm using Windows10/x64 and this is the output of the error with factory settings:
Jun 1 2017
simply adding SOCK_INT to the node_exec_socket_use_stack() fixes this..
return ELEM(sock->type, SOCK_INT, SOCK_FLOAT, SOCK_VECTOR, SOCK_RGBA, SOCK_SHADER);