I get these errors when loading every example shader, but it still appears to work in the preview. Additionally, whenever I change a shader setting I get the "Shader error in '': Parse error: syntax error at line 1" error every time.
Ah, it seems I was testing it under Unity 4.0.0f7. If I use the 4.2.0f4 then I only get the 'Trying to read pixel out of bounds' error upon loading any of the example shaders. I no longer get the error when changing shader settings. The call stack contains nothing else for this error.
Do you have multiple monitors? If so, try putting Shader Forge on another monitor, and see if the issue remains. Also, try docking it instead of having it free floating
I get these errors when making a new shader too, I'm not using Unity Pro, I have two monitors, putting ShaderForge on my second monitor doesn't change anything, nor does docking it.
Błędy
Which one did you load?
I get these errors when loading every example shader, but it still appears to work in the preview. Additionally, whenever I change a shader setting I get the "Shader error in '': Parse error: syntax error at line 1" error every time.
I'm unable to reproduce this it seems! Which Unity version are you running? How does the call stack say in the error message?
Ah, it seems I was testing it under Unity 4.0.0f7. If I use the 4.2.0f4 then I only get the 'Trying to read pixel out of bounds' error upon loading any of the example shaders. I no longer get the error when changing shader settings. The call stack contains nothing else for this error.
I'm also running Windows 7 64bit.
We're running the same Unity version and OS then. Odd.
Which platform is Unity set to?
Does the error actually break anything, or does it appear to be working fine otherwise?
It's set to PC, Mac & Linux. I don't think the error breaks anything, and I still get it after reimporting the packages.
Weird bug :0
Does the error appear when creating a shader from scratch as well?
Are you running Unity Pro?
Do you have multiple monitors? If so, try putting Shader Forge on another monitor, and see if the issue remains. Also, try docking it instead of having it free floating
I get these errors when making a new shader too, I'm not using Unity Pro, I have two monitors, putting ShaderForge on my second monitor doesn't change anything, nor does docking it.