Feedback Wanted: Scriptable Render Pipelines

@Zahidylin_Marat - Copy the contents of the folder into your new project.

 

@SebLagarde - Alright, fair. But in the interests of playing around with it, I still have a few questions -

What do you mean by material classification? Is there something stopping me from writing custom shaders for your loop? Assuming I follow the same standards (Pass names, Data structures, Shader macros etc.) your shaders are currently using? Don't get me wrong, picking through it all is currently a bit of a maze, but I think I have my head around most of it.

From what I can tell your light loop currently only needs a depth buffer (as a base) and a stencil buffer (as a mask?) to work with. Is there any reason I couldn't generate my own Gbuffers, resolve my own depth and write my own custom light loop shader method using the same buffers generated conveniently by the light loop?

Writing the above, I'm beginning to see your point, but I'm definitely still interested.

 

But specular map is very important to create real-world like skin shader. There is no room now or never ?

 

Is the cpu bound gonna be improved in the future?

 

Didnt help - geting error.

Code (CSharp):

1. NullReferenceException
2. UnityEditor.InspectorWindow.HasLabel (UnityEngine.Object target, System.String assetPath) (at C:/buildslave/unity/build/Editor/Mono/Inspector/InspectorWindow.cs:647)
3. UnityEditor.InspectorWindow.HasLabel (UnityEngine.Object target) (at C:/buildslave/unity/build/Editor/Mono/Inspector/InspectorWindow.cs:642)
4. System.Linq.Enumerable+<CreateWhereIterator>c__Iterator1D`1[UnityEngine.Object].MoveNext ()
5. System.Collections.Generic.List`1[UnityEngine.Object].AddEnumerable (IEnumerable`1 enumerable) (at /Users/builduser/buildslave/mono/build/mcs/class/corlib/System.Collections.Generic/List.cs:128)
6. System.Collections.Generic.List`1[UnityEngine.Object]..ctor (IEnumerable`1 collection) (at /Users/builduser/buildslave/mono/build/mcs/class/corlib/System.Collections.Generic/List.cs:65)
7. System.Linq.Enumerable.ToArray[Object] (IEnumerable`1 source)
8. UnityEditor.InspectorWindow.GetInspectedAssets () (at C:/buildslave/unity/build/Editor/Mono/Inspector/InspectorWindow.cs:663)
9. UnityEditor.InspectorWindow.DrawPreviewAndLabels () (at C:/buildslave/unity/build/Editor/Mono/Inspector/InspectorWindow.cs:679)
10. UnityEditor.InspectorWindow.OnGUI () (at C:/buildslave/unity/build/Editor/Mono/Inspector/InspectorWindow.cs:449)
11. System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) (at /Users/builduser/buildslave/mono/build/mcs/class/corlib/System.Reflection/MonoMethod.cs:222)
12. Rethrow as TargetInvocationException: Exception has been thrown by the target of an invocation.
13. System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) (at /Users/builduser/buildslave/mono/build/mcs/class/corlib/System.Reflection/MonoMethod.cs:232)
14. System.Reflection.MethodBase.Invoke (System.Object obj, System.Object[] parameters) (at /Users/builduser/buildslave/mono/build/mcs/class/corlib/System.Reflection/MethodBase.cs:115)
15. UnityEditor.HostView.Invoke (System.String methodName, System.Object obj) (at C:/buildslave/unity/build/Editor/Mono/HostView.cs:291)
16. UnityEditor.HostView.Invoke (System.String methodName) (at C:/buildslave/unity/build/Editor/Mono/HostView.cs:284)
17. UnityEditor.HostView.InvokeOnGUI (Rect onGUIPosition) (at C:/buildslave/unity/build/Editor/Mono/HostView.cs:251)
18. UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)

 

And performance is even more important for real time applications. The results are quite good already, if you use a proper roughness map. You can also set the specular intensity of the material in the SSS settings (although it's global and not a map).

 

Ok, I'm not expert - but if we wait so long for sss in Unity why this is worse than f.e. UE4 ?

 

Actually I like the implementation more in Unity, albeit the differences are negligible.
As far as I know, specular color doesn't vary that much. Occlusion in the pores are better handled by the ao map, normals and roughness.
Even the official UE material guide reccomends to leave the specular input alone.
https://docs.unrealengine.com/latest/INT/Resources/ContentExamples/MaterialNodes/1_3/
It should be used only for microshadowing, but as I said, it's handled by the AO map.

 

Maybe you have right, but textures for skin always have a specular map.
For simply games with small characters - sss is not important - but for cut scenes with close up - that's matter.
Of course skin with standard lit shader SRPHD looks very impressive - but I would like to see it with specular map.
That guide in UE is not applicable to skin or anything has a specularity.

 

Works great until you start adding pretty much any other asset that I own to the project....and I have some of the best and most popular assets out there. You are going to have to get on that if you want this to succeed, because lets see you broke my mapmagic you broke my megasplat, you broke my voxeland, you broke my Aquas.

When I just straight follow the instructions, which is run the script you provided, make a new scene, import those 2. It works but theres no textures to play with so I bring in my textures/land tools so I could give it a run for its money. Welp you broke them all grats haha. I copied my real project and tried to just import those assets and woah wanna talk about disaster, glad it was a backup, for fun I tried to fix everything, took me 18 hours, and I had to delete the Shader and Post Processing Stack 2 to even make that time

Don't get me wrong it was fun, I am only reporting my first impressions. Sadly I have no opinion on how it works because it came with like a couple textures. When I tried bringing in standard assets many of them broke too lol. Been laughing all night.

Windows 10 creators, i7 7700k, 32 gigs ram, Nvidia Geforce 1060, Driver 390.77, Unity3d 2018.1.0f5

I havn't given up hope I will come back and try again when you get some more polish on it.

 

Yes, it is applicable. The metallic workflow exist solely because most non-metal materials have similar specular intensity and very little variance in that. The magic happens in the roughness maps.

Xype: It'll break anything custom shader related, it is expected.

 

I think everyone is getting this particular want some feedback item wrong. It works on the lower end new framework. This isnt the ultra high def PBR system. This is a system they designed so that devs grabbing unity out of the box can have something that looks great and performs extremely well with little overhead so they can use the overhead somewhere else.

I mean if you wan't skin I think Unity knows how to do Skin. They walked everryone through that 2 years ago.



Basically I am sitting here even though it did not work for me, ABSOLUTELY HAPPY. Here we have 2 Unity folks interacting with us actually supporting and delivering on their promise.

DONT RUN THEM OFF OMG

 

This means you should stay with the classic pipeline. SRP with HD is the future of Unity rendering in an experimental phase. It is not designed to be compatible with the past at all, and I doubt it ever will be. Instead your assets need to update to work with SRP/HD instead.

 

Its all good man, I was just trying to get some textures in to play with. I reported my findings, my thought is next time they might toss in some textures so I can give it a good whirl

And I know thats why I am tinkerin with it. I am looking forward to it. I had a blast breaking things. Its just script incompatabilities and the beta, I wish I had more time to hammer into it, but I got code to write

 

Just wanted to make sure I'm not missing anything...
Right now to get started there are very basic pipelines - say BasicRenderPipeline - and the built-in ones like HDRenderPipeline, but the contrast in complexity is ridiculous. While the Basic is very easy to understand and get along, but HD seems like a complete framework of it's own.
Are there any intermediate pipelines out there or used internally, like Deferred only with basic feature support (shadows, lightmapping, ...), to learn from?

 

@SebLagarde Are the Optimization constraints because of current builtin pipeline or that's a choice to get the most out of hardware?

 

Ah, alright. So shaders made in the shader graph will have these material classifications automatically applied.

 

Yep, I was talking about the developer side of things, not the user. I know for production the complexity of HD is needed.
But to get started creating a pipeline, IMO, Basic is too simple and HD is too much at once.
What I asked is if there are any special intermediate pipelines with less flexibility and less features, that may or may not be production ready, to learn from? Anything that bridges the gab between basic and HD is fine for me
If there are none, ok with me, I'll try to grasp the HD. I understand that in the beta phase there's not much learning material, but later on I hope you'll have

 

is it possible to provide mini pack just for using HDR lit tessellation and lit tessellation layer shaders on unity 2017?

 

yup ... i mean provide this framework as mini unitypackage for using on 2017

 

Baked indirect lighting is not working with the lightweight srp. If I select any low end pipeline asset and bake lightmaps, no light has any indirect bounces at all, no matter the intensity and light type (mixed and baked show the same results) in both Enlighten and progressive. It works just fine if I remove the pipeline asset. Is this expected behaviour?

Created an empty project and it's working now. No clue what caused the problems.

 

Terrains itself are not supposed to work, or are they?

 

Anyone knows if HD pipeline will be available with 18.1 release?

 

No, it is not due for 18.1 - Check roadmap.
(Even lightweight is experimental status at the moment).

You can experiment with it of course and give feedback (I think most of us are playing with it in this thread). Just don't expect an easy time.

 

I tried but got error so dumped it. Is it going to give better graphics, or is it just a faster approach?

 

Graphics quality is up to the artists. However, there will be tools provided to achieve better graphics, like the Shader Graph. What SRP will provide (Built-in pipes to be specific) is better rendering/shading PBR wise. Custom pipelines will do whats needed for specific projects and such.

(At least to my knowledge and understanding. I'm just an artist messing with this stuff)

 

It looks subjectively better (far less camera shaking at extreme positions, less flickering, more light options [soft borders] ...) and it is frickin' fast. My unoptimized project went from around 40 fps to 145.

 

https://imgur.com/a/QtbHX

Incorrect visualization rendering of NavMesh Surface component.

 

Interested what has changed about floating precision?

Myself (and it seems a few others) are noticing far better floating precision when moving far from the origin (less shake, stutter etc), which is a very nice addition I didnt know was getting worked on

 

Maybe camera relative rendering?

Taken from this post: #2

 

Yep, I’ve encountered the same- the lighting is gorgeous but I can’t quite put a finger on why it’s qualitatively better. Better tonal range out of the box, without so much need for post colour correction.

And I’m seeing a fantastic performance increase, particularly after beta 6.

I’m finding I’m developing out of the branch I made to test 2018.1 / SRP and ignoring the main 2017.3 project, seems to work ok and I’m happy enough if future SRP updates break features.