0
Under review

5.5.0f3 and 1.32 shaders work, but SF Window does not Open

Chris Tian 7 years ago updated 7 years ago 8

After upgrading to both 5.50f3 Unity then restarting. I deleted old Shader Forge folder, then installing 1.32 - I cannot open Shader Forge windows anymore. All other aspects are functional. When I click on "Open Shader in Shader Forge" a window pops up for 0.001 seconds on my 2nd monitor then closes instantly. If I go to Window>Shader Forge - same thing. Just for reference here's a totally functional Shader Forge Shader in 5.5.0f3 it looks good

works good, but I cannot open Shader Forge Window to edit the nodes. Please help or refer me to any other post where this issue has been addressed.



Just an update, it's still not working but I did notice these error logs related to Shader Forge which might give some clarity to the topic.

Under review

Can you show me the very first error?

Also, are you sure you did a 100% clean install? ( http://acegikmo.com/shaderforge/faq/?Q=erroronnewversion#erroronnewversion )

i just did it again but this time with the reset of window layout included. same problem persists. Here's errors



hello. I have the same issue, did a clean install, when opening a sample shader and push on the button 'open shader in shader forge', you see the popup of shaderforge in a split of a split of a split second and then this error shows..

I can't seem to reproduce this - any more specific data that might help?
Are you 100% sure the SF and Unity versions are correct?

What platform is active in Unity?
What platform are you running Unity in?

(I'm running Windows 8 on my end)

Running Unity on Windows 7. I'm sure the versions are correct. I've been repeatedly deleting all of Shader Forge and installing from the Asset Store. It's Unity 5.5.0f3 in Windows 7 with Shader Forge 1.32. Everyone on my project is experiencing same issue. Here's the additional details at the bottom of each error -




Unity 5.5.0f3, windows 10 pro, installed from store, shader forge 1.32



+1

Ok I managed to fix it on my end. Seems this might be a license issue or something. The project I'm on I was signed in with the other person's account (for a different asset) and I also happen to own a Shader Forge license of my own. I switched to my own account, hit "import" and that fixed everything. I'm not sure why that worked but it did. I'm still not sure why it didn't work in the first place and I'm still waiting to find out if the other person on project has the problem resolved on that end.