Shader Forge is not able to reopen my shader (0.18)

I'll not be able to fix the shader, most likely, but I'll have to find out what's causing this. Thanks for the report! Let me know if it happens again :)

Sure, I will ;) in the meantime I'll be sure to commit my shader to svn every time I modify it.

Recreated my shader and now I can reopen it without problems (I used a "dessaturate" node instead of adding rgb components together)

Strange, it should have worked before anyhow

Well, you have my shader file, so you should be able to reproduce the problem when opening it.

It says it cannot find the node that links to the A entry of the Add node (I have 3 Add nodes, I don't know which one it is talking about). Nodes with id 3, 119, 219 all exist, so I don't understand what is going on.

Maybe it is not creating the nodes in the right order ? But I guess you are creating all the nodes before linking them, so ... I just don't get it :D

Oh, you get an error? Mine didn't open at all, and locked Unity completely with 100% CPU. Did that not happen for you?

No, I get an error in the Unity editor, it tells it cannot find the node that links to the A entry of an Add node, then a nullpointerexception. Unity doesn't freeze.

Shader Forge screen is gray, and then I need to restart Unity to be able to load another Shader.

One specific thing I did is an ADD node with 3 inputs, maybe the error is related ?

n:type:ShaderForge.SFN_Add,id:226,x:33479,y:32378|A-219-OUT,B-222-OUT,C-223-OUT;

Ah, interesting. That should work, but, there might be a bug somewhere. I'll have a look!

Any news on the fix for this? I'm using Beta 0.34 and I'm getting this bug as well.  I built a shader and when I try to re-open it in Shader Forge I just get a gray screen as well.

No, I don't know what caused it, and this version is way too far back to have some support. I'm afraid you'll have to remake it, or find the parts in the SF metadata that causes it not to compile properly