Feedback Wanted: Scriptable Render Pipelines

Combine some of the functionality of polybrush with a nice 2018 terrain shader for both pipelines and you have a great terrain system.

Top marks if you consult @jbooth because we all know the creator of mega/microsplat knows how to pack serious amounts of data into a shader (even free microsplat allows 16 texture splatmap, pretty sure megasplat allows 128 which blows my mind)

Honestly, if you think they are not already developing it your kidding yourself

Most likely its been developed for a while but is hush hush as unity seem to have really learnt lately and are only telling us about things when they are pretty certain to be released, to stop our hopes getting dashed

 

Really?? Are you aware that you are bring us hope in a matter that we are waiting soooo hard for soooo long?
Please update us on any little news

 

I tried the example on github with 3 2018.1 betas and neither has worked. There's errors on missing assemblies, shader errors when opening the sample scenes and I can't assign any .asset file into Settings->Graphics as the render loop as no file is identified as working as a render pipeline asset. Can't someone just upload a working project with this ?

 

if you have 2018.1b10 and in your package manager you update your packages for HD or LW depending and you update the shadergraph it should fix its self thats what did it for me.

 

Currently, I can only gain access to 2018.1b9. Is 2018.1b10 live on the site for download? Thank you!

 

+1 to that

 

Huh? which sample scenes are you talking about?

 

LightweightBasicScene.unity
Sample screenshot : https://drive.google.com/file/d/10JP8IA8IgSBe5Oaf4BVcy8-2dFpDMbpo/view?usp=sharing

 

This is the link i was given when i was having issues. Im not sure if its an official release but heres the link.
Edit: its live

 

Thank you, @Finepointcgi ! Yeah this link looks super underground haha thank you for the share. The main site has it live now. Cheers!

 

Unity Hub already have v2018.1.0b10 ready for download.

 

Thank you! I really appreciate it!

 

I can't find a way to remove Camera component with HDRP enabled, HDAdditionalCameraData depends on it and is hidden, so I can't remove it too.

 

Please, how can i improve the shadows in the Sample Scene of Unity 2018 HD b10?

The default one is really bad. Thanks!

 

yeah, that's the same reply I got on 2009 or 2010 I believe. Hard to remember the dates, but I remember the exact words: "yeah, we got 2 new talented programmers working on the next terrain system". And then between then and now, i even lost family members. I'm afraid I may be next before a new terrain system will come out.

 

@creat327
You should not rely on "uncertain upcoming features" unless you really see some real work in progress. I've also been there "we are working on this and that", nothing new.
Personal advice, either try to find solutions (create your own, asset store, other engines, etc) or design your project around current limitations. Indefinitely waiting will only create more frustration.

I don't want to derail this thread, let's keep it on topic (we can move to the terrain thread if you want to discuss more about it).

 

Btw any news about the HD optimization part?
- light/shadow fade distance, free from GPU rendering but still computed by CPU
- Per Object Shadow Receive/Cast, in legacy deferred shading all object always receive/cast shadow

 

From what you know, how might the new terrain system affect current plugins such as Gaia?

 

ah well, no worries. at least i know this is need to be solved to reduce cpu overhead.

Well might be usefull for lod to completely remove mesh from shadow buffer rendering

 

I know this new system trying to revamp rendering from the ground up, and break away from the legacy rendering, I'm just saying, to get a smoother transition, maybe we can have a Legacy rendering support checkbox in the Pipeline Asset settings. At least for a couple of releases of Unity, before deprecating it once and for all. I know a few fellow game developers who did not upgrade Unity for YEARS because "it broke their project" or "the models are all pink", and depending on the size of the project, or the technical skills of the developers, some people can't afford to upgrade, and this would hurt the adoption of the newer versions of Unity. So making the transition smoother by supporting legacy rendering at first, until it's time to kill it. Just my $.02

 

Just set the Scriptable Render Pipeline Settings in the Graphics Settings to Empty to stay in legacy

 

If you get the pipeline from github (rather than package manager) then there are loads of sample scenes.

You can also get just those scenes from github at this link, though I havent actually tried this myself: https://github.com/Unity-Technologies/ScriptableRenderPipelineData

 

I can't run the profiler in my project with the Lightweight Render Pipeline on as it crashes with

"Non matching Profiler.EndSample (BeginSample and EndSample count must match): After Camera Render"

I do not call any Profiler methods from my code and the problem goes away if I use the legacy render. I can't reproduce this from the template though... any ideas?

 

The Master branch normally not compatible with the current public beta release

 

That's not the SRP Master branch, its a separate repository with the asset files from the main SRP repository without the main SRP stuff included, so just (models, textures, scenes, scripts, etc)

 

Well not sure how unity set up their repo, i assume that repo are in synced with the SRP repo. and yep you right it's not the SRP repo, but the content are the same as in the SRP repo afaik (the SampleScenes and TestbedPipeline folder).
Edit : I mean from the released version
Edit Again : Just Tested that repo it worked fine for me, no error or anything

 

I just read the latest blog about the HDRP. Does anyone know when will the system be stabilized?

1) When will HDRP be finished
2) When will volumetric lights and physically based camera be added?
3) New terrain system must be in designs
4) What else? When will the engine be complete for the new generation?

 

I'm pretty sure they arent going to be pinned down to particular timescales on most of this. It's pretty easy to imagine a lot of ongoing work carrying on for years to come. There is little doubt that 2018 is a big year on many fronts, with many new parts of the system arriving in relatively early form and likely to undergo evolution over the 2018.x cycle and beyond.

It's now so close to the GDC keynote that is likely to give us some more roadmap detail and clues, so thats when I next expect to learn something new, but I dont expect precise timescales on HD pipeline features.

 

Will Screen Space Multiple Scattering from
OCASM
(https://github.com/OCASM/SSMS)
be available in 2018.1 as part of SRP ?

 

Im thinking that for someone that plans to do an AAA graphics game might Unity not be good yet. Not until the new essentials arrive atleast.

 

isn't there a skybox fog blending in HDRP already? similar to naughty dogs fog?

 

If the HD rendering pipeline is going to be targeting high end PCs and consoles, wouldn't that mean that a good other chunk of games like VR, mobile and web games be "forced" to use the LW rendering pipeline?

That worries me a lot, as the LW pipeline is said to be a subset of the current Unity renderer. Being a VR developer, I'm not sure that I would want to upgrade, if upgrading will essentially be a downgrade instead, especially since I'm already doing fine with the current renderer. I have to say, looking at the new HD features (like decals? not sure if it's in LW) while not being able to use them in my VR project does make me a bit envious.

Are my worries justified? It just seems like the LW rendering pipeline will put people off upgrading because no one wants to downgrade their project, especially with HD being supposedly restrictive in its target platforms. I don't think scripting the LW pipeline will work either, since most people probably can't plug HD features into LW by themselves without some graphics programming knowledge.

Edit: Just seen that VR is on the roadmap for HD, that's great! I'm still not sure how one would convince mobile devs to downgrade their graphics though.

 

To answer the last question - by not looking at it as a downgrade, but rather one of those tradeoffs, some gains and some losses. eg if it performs loads better but has a couple of missing features, then how much does the particular developer care about performance vs those particular features?

Also I believe the idea is that the LW and HD pipeline are examples provided by Unity, but they expect some people to build their own, and I kind of expect some people to offer their modified or completely bespoke pipelines to other Unity developers. I doubt anybody really knows how this will actually turn out, or at what pace. But we can already see some responses from Unity that indicate the level they want to set their own LW pipeline at, and how they envisage that some features considered slightly beyond the scope of their standard LW pipeline are best added by someone else. No doubt there is almost infinite potential for disagreement about exactly where the LW limits should be set, and people are going to appeal for stuff they need to be included. Maybe sometimes it will happen, but as someone who is mostly reliant on others for graphics programming I think I will need some eager 3rd parties to help out with my own pipeline needs on many of these occasions.

 

I expect there will be optimisations to come yet if high end mobile or VR HD is supported.

 

LW seems more like "current Unity graphics" but optimized, so it's an upgrade in performance without losing much. Whereas HD is a big upgrade over existing.

 

@IgnisIncendio,
I'm currently extending LW beyond it's current limitations to suit better that middle ground. Omni directional shadows, optional pre-pass rendering (optionally using the alpha buffer == zero overhead) making it compatible with current screen depth-based effects and more.
This will make it more suitable for VR and low end device hardware while having similar features to current Forward renderer (but with the advantage of everything running in one pass).

 

Please vote for the following bug fix, so we can test SRP with PROCEDURAL models:
https://issuetracker.unity3d.com/is...try-using-graphics-dot-drawproceduralindirect

 

What is the difference in lighting in Unity 2017 compared to Unity 2018 Lightweight Render Pipeline ?

 

Hi,
not sure if is my fault or a current limitation, but it seems that there isn't proper default terrain shader with the SRP HD
When will we able to render unity terrain using the SRP HD ?