- Feedback
-
Fejl
0
Fast
Changing the variable of a value node causes Shader Forge to constantly recompile - which takes quite some time
I've got a setup that contains a Time node which gets multiplied by a Property Value node.
Changing the float variable of the Value node causes SF to recompile the material preview. This process takes quite some time - the input box for the float variable becomes somewhat unresponsive.
Changing the float variable of the Value node causes SF to recompile the material preview. This process takes quite some time - the input box for the float variable becomes somewhat unresponsive.
Kundesupport af UserEcho
http://shaderforge.userecho.com/topic/349874-beta-...
And it looks and sounsd to me like these issues might be related to each other... let's hope for the best :)
I'm looking into this right now!
Btw.: I had an interesting bug that might be Unity devs domain/responsibility.
When I opened the example scene and started to dissect and play (aka cause some recompiles) with one of your shaders I suddenly had working refraction in my Unity Free version. That is, the refraction shader example worked... while the transmissive plant shader suddenly didn't (no cutout opacity).
After shutting down and restarting Unity Editor the materials showed up as expected ... black for the refraction shader, shaded and cutout leaves for the transmissive plant shader.
It won't be saved in a build, but you can work on it before purchasing Unity pro!
Well, at work we have Pro, at home I don't. Nice feature. Off to my bed now.