Feedback Shadergraph Somewhat Missing The Point Of Lwrp?

I've been playing a bit with the shadergraph in the LWRP, and I feel like in its current state it's quite counter productive. LWRP was meant to be targeted at low-end platforms but shadergraph pushes the user towards the least efficient way of writing shaders: no proper conditionals, everything is happening at the fragment level, no explicit control over the operation precision, and some nodes should never ever be used on mobile (i.e. noises) but the average user has no way to know it.

I understand that it's great to empower artists who would not want to dive into shader programming, but in my opinion, this is pretty much why Unreal has had such atrocious performance on mobile. Having analysed a few auto-generated UE shaders in the past (from some of their biggest games), I would be very sad to see Unity games heading the same way.

 

I would just avoid it and write by hand if you know how to write shaders. I dont think shadergraph is meant to be better than authoring a shader manually

 

There is no equivalent of surface shaders in lwrp and as far as I know you have to use the graph.

 

(OFF TOPIC) @Tartiflette Are you in Savoie ou bien ?

 

Nope, not even in France anymore, just love the word

 

While true, if you look at the generated shader code from a basic Shader Graph you'll see the LWRP's shaders are for the most part pretty simple.

 

That makes sense, I'll give it a try.