Timeline for Extract code from Blender Shaders
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 25 at 17:55 | comment | added | Gorgious | you can try blender.stackexchange.com/questions/267418/… | |
| Jun 25 at 13:12 | comment | added | Martin | @MarkusvonBroady Managed to extract the values and links, so the questions is solved, i think. As long as nobody know of an add-on (or similar) that could just extract the nodes-values and links directly to GLSL? | |
| Jun 25 at 12:40 | comment | added | Markus von Broady | Possibly useful: What's the most reliable way of converting a material into reusable code blocks? | |
| Jun 25 at 12:17 | history | edited | Martin | CC BY-SA 4.0 |
added 151 characters in body
|
| Jun 25 at 12:12 | answer | added | Martin | timeline score: 1 | |
| Jun 25 at 12:11 | comment | added | Lauloque♦ | So what you actually want is access your nodes' values and connections via python, please edit your question to reflect that. You could also explain why you want to do that, this sounds like a potential XY problem situation waiting to happen, people could help with it to. | |
| Jun 25 at 12:08 | comment | added | Markus von Broady | Duarte is right, the shading code is not written in Python. It's C or C++ in which Vulkan is used to convert the nodes (using a stack machine) to GLSL (openGL Shading Language). | |
| Jun 25 at 9:07 | comment | added | Duarte Farrajota Ramos♦ | What do you mean look at the code? Shaders are not written in Python, they are either C or C++. You can look at the source code of the shaders in Blender repository | |
| S Jun 25 at 9:01 | review | First questions | |||
| Jun 26 at 12:52 | |||||
| S Jun 25 at 9:01 | history | asked | Martin | CC BY-SA 4.0 |