nodes disappeared!

Are you getting any errors in the console?

No, unfortunately.  I'm getting nothing.  The weird thing is, if I blindly right-click around, I'll be able to "find" a node where the contextual popup offers "Edit Comment" and "What does Texture2D do?" (for example).

This is an amazing tool so far.  I applaud your efforts so far.  If you need I can send you the source output if that would help.

That's really strange... Are you 100% sure you aren't getting any errors? As in, when you open the shader

100%.  I've tried reloading it now just to make sure I wasn't hallucinating.  Nothing.  According to Shader Forge, all is well.

Did you check the Unity console? (The one outside SF)

I've loaded your Lightwrap example shader, then the console had this to say about my own shader suddenly...

"Shader error in '': Parse error: syntax error at line 6"

And yes... the Unity console is the one I assumed you were talking about.  I honestly didn't think there was a console in SF.  (??)

There's no console in SF, just wanted to make sure you were looking at the right place :)
Put the shader up on pastebin and I'll have a look

I've never used Pastbin.  Is this something I need another login for?  Can I email it to you instead?

I've "pasted" it there now.  How will you get it?

Just checking in to see if you got the shader.  If not, please help me get it to you.  I really need to continue on this today.  (Sorry for the urgency!  I'm using SF at work.)

Thanks!  :-)

Update...

So I tried starting from scratch and created a new shader.  As soon as I press 'T' the workspace goes blank.  I can't even create the node.

... that goes for ANY hotkey.  I can create nodes with right-click.  I can create nodes by drag-drop from the bin on the right.

Now it seems like any key press at all will blank out my workspace.  If I try to enter a number in Value, boom... gone.

(???)

I installed Unity 4.5 and tried loading the problematic shader.  Here's what ended up in my console:

Serialization depth limit exceeded at 'ShaderForge::SF_PreviewSettings'. There may be an object composition cycle in one or more of your serialized classes.
UnityEditor.Undo:RecordObject(Object, String)
ShaderForge.SF_Editor:AddNode(SF_EditorNodeData, Boolean)
ShaderForge.SF_Editor:UpdateKeyHoldEvents(Boolean)
ShaderForge.SF_EditorNodeView:OnLocalGUI(Rect)
ShaderForge.SF_Editor:OnGUI()
UnityEditor.DockArea:OnGUI()

Thanks.

update:

I was using Unity 4.3.4f1 with SF 0.34.  I installed Unity 4.5 and tried loading the broken shader again but it still didn't display... however, I was able to create NEW shaders with the hotkeys again.

So...

I regressed to SF 0.33 and "fixed" my broken shader by doing the following:

I looked at the source shader code generated from SF.  I noticed several nodes that had x-coordinates in the minus two billion range!!!  I carefully edited them to be within your standard 33,000 range and saved it as a new version.  I was then able to open it up, then delete all the unattached nodes I created during the debugging process.

Our company is still using Unity 4.3.4f1 so in the interest of keeping everything compatible here, I will be using Unity 4.3.4f1 with SF 0.33 and go from there.

I lost a day of work because of this.  :-/

Ah, I had that problem a while back as well. I'll need to look into that soon

Are you using multiple monitors?
Any obscure mouse solution?
Anything else that I should know about?

Yes, I'm using multiple monitors.  We wondered about that being a problem as well.  I have two 24" and a 13" Cintiq plugged into the Macbook Pro Retina.  (Amazing that it can even handle all of it!)

The mouse is a standard three button mouse.  Middle button is a wheel.  It's a USB mouse, nothing fancy, although it's being routed through the Cintiq's USB throughput port... but I can't imagine THAT would be an issue.

I'm curious to know as to why this would suddenly start misbehaving like this after using it for a week?  I thought it was because I had too many applications open, so I shut down Maya, Modo, Photoshop and some tabs I had open in Safari so I could attempt to free-up the gfx card.  I tried rebooting too.  Nothing stopped SF from misbehaving on key-press, except for when I tried using it in Unity 4.5.

The devs here know about the plethora of bug fixes in 4.5 so are trying to update our core system, but as you're aware this can take time to trickle down to the production team.  So I'm stuck using Unity 4.3.4 and SF 0.33 until you can spot the problem.  In the meantime, I can keep working.  If this happens again I know where to fix it in the shader source output.  Not convenient, but not a show-stopper either.

Thanks for the response and all of your hard work.  :-)

Ahhh yes it has.  Sorry... didn't clean up after myself here.  ;-)  thanks again!