Feedback Wanted: Lightweight Render Pipeline

How is the implementation of Gizmos and LWRP different from the built-in pipeline? Gizmos seem to fade out very quickly when still very close to the scene view camera in the editor. Is this by design and is it possible to change this behaviour?

 

Same issue as above. We can turn off 3D gizmos and it makes the lines appear correctly again, but this is not ideal.

 

Hi there,

I recently upgraded my project to the latest version of LWRP and I'm getting some seriously weird rendering results once built to iOS device. Looks fine in editor.



Any ideas?

Edit: Gif wouldn't work so here's the link

 

Is 2018.3 coming next week ?

 

I kinda doubt it at this point. They were saying it would come out over a month ago, and then radio silence. Either that means they are mostly ready but keep finding "one more thing," or they found some major issues and have been reworking them.

In that case, they are keeping quiet until they have a valuable ETA or maybe it will just come out without prewarning. I don't know that I'd hold my breath, either way.

 

Hello, I have a problem, I want to use the stencil buffer or cut a hole in a mesh in Unity 2018.2.2f1, but with the lightweight renderpipeline it does not work. does anyone have an idea how to fix the problem?
Or anyone an idea how i can hide a part of a mesh?

 

I highly doubt it?

It's frustrating because my LWRP issues have been fixed a month ago, but none of them are being backported to 2018.2 branch (no new 2018.2 LWRP release since July 27).

On one hand, I empathize with Unity dev, it's a lot of work, and putting it out now would be doing everyone a disservice.

On the other hand, Unity blog has been hyping SRP since 2018.1, putting it as the flagship "feature (preview)" in both 2018.1 and 2018.2 releases. YMMV, but to me they are so broken at the moment, I cannot imagine using it for production.

Forgive me for being a bit passive-aggressive, I just want to jump off this 2018 starship and swim back to 2017 LTS boat.

(the recent lighting pipeline best practice guide put some salt my old wound.)

 

Let's not rush them, you know how rushed product is. Last time they said there's a problem with 2018.3 which they want to address before give public access

 

That said, can anyone give me a quick primer on how LWRP cull light per-object? Or more specifically, how is the culling different from Built-in Forward?

I assume there must be other optimization beyond looping over lights in a single pass?

https://github.com/Unity-Technologi...ht/LWRP/ShaderLibrary/Lighting.hlsl#L545-L553

EDIT: to be precise, the explainer blog post did say both Built-in Forward and LWRP light culling are per-object. But the best practice guide wrote something like:

> The lights are culled per-object and allow for the lighting to be computed in one single pass.

There is no connection between per-object light culling and whether lighting can be rendered in single pass, or is there?

 

Hey, found an issue on Android. Testing with LRP 3.0.0 preview and 3.3.0 preview, same issue on both.

I have a single pixel light in a scene with a bunch of meshrenderers creating shadows.
When I run in unity, it looks fine, but if I run on android the light will disable as soon as the light comes near to a meshrenderer.

I get the following errors from ADB.

Code (csharp):

1. 08-29 22:23:46.961: D/Unity(3121): fragment evaluation shader
2. 08-29 22:23:46.961: D/Unity(3121): ERROR: 0:114: '_LocalWorldToShadowAtlas' : undeclared identifier
3. 08-29 22:23:46.961: D/Unity(3121): ERROR: 0:114: 'expression' :  left of '[' is not of type array, matrix, or vector
4. 08-29 22:23:46.961: D/Unity(3121): ERROR: 0:114: 'return' : function return is not matching type:
5. 08-29 22:23:46.961: D/Unity(3121): ERROR: 0:114: 'expression' :  left of '[' is not of type array, matrix, or vector
6. 08-29 22:23:46.961: D/Unity(3121): ERROR: 0:114: 'return' : function return is not matching type:
7. 08-29 22:23:46.961: D/Unity(3121): ERROR: 0:114: 'expression' :  left of '[' is not of type array, matrix, or vector
8. 08-29 22:23:46.961: D/Unity(3121): ERROR: 0:114: 'return' : function return is not matching type:
9. 08-29 22:23:46.961: D/Unity(3121): ERROR: 0:114: 'expression' :  left of '[' is not of type array, matrix, or vector
10. 08-29 22:23:46.961: D/Unity(3121): ERROR: 0:114: 'return' : function return is not matching type:
11. 08-29 22:23:46.961: D/Unity(3121): ERROR: 0:114: 'expression' :  left of '[' is not of type array, matrix, or vector
12. 08-29 22:23:46.961: D/Unity(3121): ERROR: 0:114: 'return' : function return is not matching type:
13. 08-29 22:23:46.961: D/Unity(3121): ERROR: 0:114: 'expression' :  left of '[' is not of type array, matrix, or vector
14. 08-29 22:23:46.961: D/Unity(3121): ERROR: 0:114: 'return' : function return is not matching type:
15. 08-29 22:23:46.961: D/Unity(3121): ERROR: 0:114: 'expression' :  left of '[' is not of type array, matri
16. 08-29 22:23:46.961: D/Unity(3121): Note: Creation of internal variant of shader 'LightweightPipeline/Standard (Simple Lighting)' failed.

Now, I'm not confident with shaders, but in the file "com.unity.render-pipelines.lightweight@3.0.0-preview\LWRP\ShaderLibrary\Shadows.hlsl" has the following line:

Code (csharp):

1.  
2. float4 shadowCoord = mul(_LocalWorldToShadowAtlas[lightIndex], float4(positionWS, 1.0));
3.  

It seems to be the issue. If I remove "[lightIndex]" it works, no errors, but no shadows show.
Any clues?

 

Use 2.x for 2018.2, afaik what you are now looking at are meant for 2018.3

 

You were right, I was using Unity 2017.2.5f1 and LWRP 3.0.0-preview.
I swapped the LWRP and CoreRP both to 2.0.8-preview, still appear to be getting the exact same issue though.
I even tried deleting the 3.0.0 packages, library and temp and reimporting the whole project, no luck though.

 

@Tim-C , as of now, is current state of HDRP 18.3 production ready (without the new terrrain)?

 

I one could like something twice. this is the post.

(Okay threes times, just for your hat Tim, and I waited YEARS to say that)

 

Okay - so stupid question time.

Which tag/branch/commit/revision of https://github.com/Unity-Technologies/ScriptableRenderPipeline/tree/

is for 5.6.6? So i can test LWRP on 5.6?



(5.6.6 is solid as a rock, surely Unity appreciates that many professional developers not only own this outright, but would use it preferentially for just this reason )

 

Shader graph is for 2018.1 onward so you won't be able to use that and older versions of LWRP you won't want to use since they have fewer features naturally. If you really want to mess use a 5.6 version then you can find it here
(You will be missing a lot)
https://github.com/Unity-Technologies/ScriptableRenderPipeline/releases?after=Unity-2017.3.0b2

I would advise to get 2018.2 latest and use LWRP with that since it seems you just want to see how it is

 

Even the 2018.2 branch are in need of heavy patching, you will very well drive yourself crazy.

 

Another shoutout to my previous question, appreciate any answers

 

Has anyone figured out a workaround for having directional light culling mask yet? We need this feature to be fixed...

 

Just wondering if Lightweight pipeline has support to work with ProBuilder selection materials on 2018.2.x? It seems that with the lightweight pipeline active, the face selection rendering in ProBuilder doesn't work. (I assume this is because the probuilder selection materials are using internal probuilder shaders and not the lightweight ones?)

 

Just checking in to see what the status is on LWRP working with the UWP.

https://issuetracker.unity3d.com/is...weight-rp-on-uwp-platform-trigger-an-exeption

 

thanks for the feedback.
Pipeline in 5.6.6 feels like abandonware now. Salt rubbed in wound everytime I open "graphics"

pfft. lameness. and kinda unprofessional

 

I don't know, I was always under the impression that it was a 2018 feature. That was how they framed it at all their keynote speeches and blogs. You can't expect a company to backport every new feature (or any new feature really).

 

I don't. Just everytime I open "graphics" it irks the hell out of me.
Anyway. I'll shut up

And you are totally wrong about it being a "2018" feature.
At the rate they are going more like 2020, but it started in 5 and then they just ditched it for each new wonky beta along the way

 

I can't update to v3.0.0 in unity 2018.2.6f1 , Amplify shader editor supported version render-pipeline.high-definition v3.0.0.

Error with package details: Package has invalid dependencies:
com.unity.render-pipelines.core: Version [3.0.0-preview] is incompatible with the selected version [2.0.6-preview]
UnityEngine.GUIUtilityrocessEvent(Int32, IntPtr)

 

Hi, we are working on SRP project, we modify the legacy speedtree shader to work in SRP, but we still can't make the wind work with speedtree, I can't find any information in the github project, can you tell me something about official speedtree support plan?

 

Hi!

Any chances to get an AO Post-processing effect functional with the LWRP soon? Do you have an ETA for a version for the pipeline that's ready for production?

Thanks!

 

Well, based on Unity @Andre_Mcgrail s post on this forum from August 1st it does not look too promising :-(

"....AO is a tricky one, it's definitely on our 'nice to have' list right now, but as we are trying to focus on stabilisation and documentation this most likely will be pushed to 2019.x due to LWRP only having Colour and Depth, this leaves little room to make something both performant and passable visually..."

Its really pitty as AO is almost must for interactive visualizations etc...

Another useful/needed thing is matte aka shadow-on-fully-transparent-plane - good for product vis, indispensable for AR etc (old implementation see Matte Shadow Drawer made by Unity own Keigiro Takahashi), but that is probably also just a dream for LWRP at this stage...

 

The original unity blogpost about SRP (like what? in 2016?) was vaunting the new pipeline ability as great because anyone could write their own. And now the mere mention of coming up with ones own solution seems to be utterly derided as foolish.

Oh well. I guess I really missed the point of all of this work. Or perhaps that point changed.
Glad you are finally managing to get something potentially "useable" after all this effort.

 

Is it likely this bug with realtime shadows will be fixed soon? https://issuetracker.unity3d.com/is...rectional-light-shadow-maps-exhibit-artifacts

 

Thanks Andre for your answer, my mistake for not searching in deep of this post.
I haven't played (yet) BoTW , nevertheless I understand what you're saying. Better at least to keep a minimum of visual quality. Meanwhile I will use the LWRPAO from Shindo-san. Let's hope it will be ready for 2019.1

 

No, I dont see it that way at all, there is nothing foolish about people developing their own pipelines, so long as they have the right resources/abilities and it makes sense in their situation to do it. It will also make sense for some people to customise one of the pipelines that Unity are providing, although there are risks to attempting such things when the pipelines are still changing quite a lot.

A somewhat different but sometimes related issue is the state of the SRP feature within different versions of Unity itself. Clearly Unity first started going on about the scriptable pipeline feature long before it was really ready, and during the development of their own scriptable pipelines they have found things that needed to be changed or added to the core of Unity. The large amounts of progress seen with the pipelines during 2018 are what I was originally hoping to see in 2017, with 2019 looking more like the timeframe when things start to stabilise and mature. I know that is extremely annoying for someone such as yourself who was hoping for stuff that worked with Unity 5.6 or whatever, but I dont see how these annoyances and lengthening timescales actually make a material difference to the ultimate potential of scriptable render pipelines.

 

Oh okay. that is actually good news then. I will simply hang around and see what the (very sagacious) Unity team comes up with. Thanks for this ray of hope

 

Minor request for Unity devs: change the protection level of a lot of the ShaderGUI editor code from private to protected. As it is, if I want to extend the LWRP standard shaders and add a few properties, I have to copy and paste essentially an entire editor class.

For example, overriding ShaderPropertiesGUI() seems to be the logical way to insert new property fields, but it references a bunch of private fields and methods. Here's what I get when I paste the ShaderPropertiesGUI() method from LightweightStandardSimpleLightingGUI into a custom class which inherits from it:


For now, I'll just call base.ShaderPropertiesGUI() and add my property fields at the beginning or end, but... it's so unnecessarily sloppy!

 

Finally!

Did a bit of test, my upgrade from a 2018.2 test repo isn't quite successful (package manager ui not working), but I re-created a new repo and try my previous demo again. LWRP PBR is finally working.



However I am seeing an interesting complication, I am not able to see any 3d model in my actual build (tried il2cpp and mono), only skybox:



Since this was working in 2018.2 builds (and certainly in 2018.3 editor), I am wondering what else has been added that lead to my problem...

 

macOS + Metal, but I think it's actually a case of 2018.3 not upgrading scene file properly. Because I just tried creating a new scene file and it certainly works in build.

Then I tried duplicating the scene file and build with it, again the camera position and rendering is correct. So it's just the original scene file (created in 2018.2) appear to be affected.

Both original scene file and the clone one look the same in editor (render fine in game view and play fine), but building them result in different camera position.

(I think it's unlikely to be a LWRP issue.)

 

I there currently a bug with the object node (which outputs the world position and scale of an object)? I works fine in hdrender pipeline projects but in a lightweight project it doesnt.

 

Thanks @Andre_Mcgrail for AO-related info.
Maybe even "generic" AO Post-Processing solution would be good, so we could use it in our developing projects as a kind of "placeholder" while looking forward to future improvements.

Regarding matte/shadow shader - thanks, will try to convert. Its pity though that such useful (for many, particularly VR cases) shader is not included in standard Unity installation...

Anyway, thanks, and wish a lot of endurance in further development

 

My lights just turn off in LWRP when there are more than 1 light visible so only 1 lighsource stays active the whole time and while the camera is moving new lights appearing just turn off or on depending if there are more nearby visible. No matter if i set max pixel light to 4 or 8. Is this a Bug and how do i fix this?