Your comments
It depends on the cause of the issue. Are you getting any errors in the console when loading it?
11 years ago
0.31 has a few bugs that could have caused this. Try it in 0.33 and see if the problem persists
Were you using any property nodes?
Great, glad it worked out :)
This has now been implemented in Beta 0.33
Deferred Lighting has now been implemented in Beta 0.33
Duplicate of: http://shaderforge.userecho.com/topic/441871-editor-dont-display-nodes/
This is due to a bug in shaders saved using 0.29. There's a property node in the node order (at the end of the SF data), that doesn't exist.
It looks like this:
21-14-4-54
One of them doesn't exist among the nodes, see if you can find which ID that isn't associated with a node, and remove the ID from the list. Otherwise you can wait for 0.33, where this is automatically done when opening one of those shaders.
It looks like this:
21-14-4-54
One of them doesn't exist among the nodes, see if you can find which ID that isn't associated with a node, and remove the ID from the list. Otherwise you can wait for 0.33, where this is automatically done when opening one of those shaders.
To control the intensity, just multiply it by a slider between 0 and 1. To control the exponent, plug in a slider with values from 1 to 8 or so, and connect it to the Exp input of the fresnel node
That's sort of the thing - plenty of things are a bit hacky, due to some pretty bad vestigial sections of code, such as the component count of the output, and so forth. But I may open it up, like you said, on a "at your own risk" basis.
I've already got custom node loading ready to go, since I had to implement it for the Skyshop nodes, thanks for the offer anyhow :)
I've already got custom node loading ready to go, since I had to implement it for the Skyshop nodes, thanks for the offer anyhow :)
Customer support service by UserEcho