Closed IPv6 closed 3 years ago
Answering my own question - seems to be path casing problems. current beta of blender (on windows) has problems (at least with OSL) IF path to executable has disk char in lower case. after changing path casing in addon settings - everything started to work again.
broken: "blender.executables": [{"path": "c:\\_WPLabs\\Programs\\blender293\\blender.exe", ...
fixed: "blender.executables": [{"path": "C:\\_WPLabs\\Programs\\blender293\\blender.exe", ...
I am using 0.015 and it works very well with 2.91. But there is a problem with 2.93 beta: when blender is up and running from inside addon, it can not compile external OSL scripts. This is only on windows, using the same setup (vscode+blender 2.93) on MacOs and everything is fine
I made a bug request initially in Blender bugtracker: https://developer.blender.org/T88323 Turns out the problem mainly exist when blender is started from inside VSCode, and not from command line. Concole output (when executing steps from blender issue tracker blend file):
Seems like this addon replaces some paths that are used by OSL during compilation. When blender is started from inside vscode thereis a line " 'scriptsFolder': 'c:\_WPLabs\Programs\blender293\2.93\scripts' " and the error message gives '"c\_WPLabssProgramsmblender29322.932scriptsraddonsacycles\shader\stdcycles.hd' - slashes arise right after overloaded path... may be coincidense, but could it be the reason?
Does anyone had the same problem?