- Feedback
-
Bugs
0
Fixed
Shaderforge Crash - Could possibly be related to Simple Remap?
I'm using 0.31, I've yet to update because of a tight Internet data plan (Hopefully going to download it as soon as it resets), So I apologise in advance if this bug was known beforehand and has been fixed after 0.31.
I get no errors in the console, if there are any I can't see them because it causes Unity to instantly crash.
What I did was I had an Append going into a Simple Remap, behind that append was a Transform node and a View Dir. node. I attempted to break a link between the Transform and Append and it locked Unity up, I had to end process. I opened it back up and the shader loaded fine, so instead I tried breaking the connection between the Simple Remap and the Append, locked up again. This time though, I'm unable to reload my shader. Attempting to do so instantly closes Unity. Might there be any way I can recover my shader?
I get no errors in the console, if there are any I can't see them because it causes Unity to instantly crash.
What I did was I had an Append going into a Simple Remap, behind that append was a Transform node and a View Dir. node. I attempted to break a link between the Transform and Append and it locked Unity up, I had to end process. I opened it back up and the shader loaded fine, so instead I tried breaking the connection between the Simple Remap and the Append, locked up again. This time though, I'm unable to reload my shader. Attempting to do so instantly closes Unity. Might there be any way I can recover my shader?
Answer
I should probably also mention that the Simple Remap went directly into the UV part of a Texture 2D node.
0.31 has a few bugs that could have caused this. Try it in 0.33 and see if the problem persists
I should be able to download 0.33 around the start of next week, I'll get back to you on it to see if it fixed the problem or not. In the meantime do you know of any code changes I could make manually to get the Shader to load at all?
It depends on the cause of the issue. Are you getting any errors in the console when loading it?
If I recall correctly when it locked up the first time (And allowed me to reload it) it returned a caught error of something to do by multiplying by Input B. I can't remember the exact error unfortunately, but the property node is the B input of the multiply node. I can't get any more errors because Unity instantly closes without displaying anything as soon as I try to reload the shader now. Because this is probably is to do with the property node, Is there a way to manually remove that from the shader code?
Yes Unity does, not SF. So I'm unable to read any possible errors it could possibly be throwing at me.
http://pastebin.com/5cz32rab
Done. If it helps at all the property node that is probably the issue was called "Reticule Scale".
Done. If it helps at all the property node that is probably the issue was called "Reticule Scale".
Answer
Fixed
Right, it opens just fine in 0.33 :)
This one may work for you: http://pastebin.com/wK9ADTJD
If not, or if you run into it again, you'll have to update to 0.33
This one may work for you: http://pastebin.com/wK9ADTJD
If not, or if you run into it again, you'll have to update to 0.33
My apologies then for wasting your time. Unfortunately it still doesn't work, but I'll just attempt to recreate it until I manage to get my hands on 0.33. Thanks Ace!
Customer support service by UserEcho
This one may work for you: http://pastebin.com/wK9ADTJD
If not, or if you run into it again, you'll have to update to 0.33