[Next-Gen Soft-Shadows 2] Sophisticated dynamic penumbra Shadows for Unity

I remember you mentioned NGSS 2.0 would be ready by Christmas. Is that still true?

 

@nomax5
NGSS is compatible with anything that support shadows in Unity. It's not a system that works side by side, it basically replaces default shadows. Though, there's one minor exception with shaders that uses internal _LightShadowData.r where you need to set it's value to 1 (to avoid opacity fade with point/spot shadows). Other than that it works 100% with all your effects and shaders.

@ceebeee
Yeah, sadly that won't be possible but the good news is that I'm working hard on NGSS 2.0. I will soon post some advancements on it.

 

Folks,
Update have been pushed to the store (will go live in a day or two). It contains improvements to point light shadows (performance and visuals) and Mobile shadows fix. The rest of the update will be pushed in an early January update.

 

What's going to be included in the January update? Also, what benefits enabling 32-bit shadowmaps brings? And I'm also curious if you'll be able to implement shadowmap cascades update rate when NGSS 2.0 will arrive.

 

@Kolyasisan
Benefits are more precision in your shadows. Steps to compare are smaller = less shadows artifacts and errors when shadows are extreme large.
[EDIT]
It's the same as comparing with color bit depth. The higher the more gradient transitional values you can get. The less bits, the fewer color gradient you can have (banding, fewer color tones, shades of gray, etc). For instance mapping distance to fewer bits = more prone to visual errors as the gaps between each step (or bit) cannot be fill and must be either clamped or totally skipped.

January update contains last NGSS 1.x feature update which is the cascade improvement.
I'm kinda right now working side by side NGSS 1.x and 2.0 and on our current project (which uses both of them btw). ^^
Regards,

 

NGSS Mobile shadows optimized with 16taps:

 

What do you intend to do with lookups for Spot Light? Unity shaders use native shadow sampling and make PCSS lookups impossible. I also conduct experiments with shadows. The best that I got is a texel fetch. In unity shaders correctly works Load functions from DirectX. I make PCF lookups in spotlight with it. But this path works just on Windows. OpenGL texel fetch not works. Do you use other magical tricks?

 

I totally skipped depth fetch with spot lights (same reason you described) we can't set built-in render textures types so no PCSS for them in NGSS 1.x. On NGSS 2.0 I'm doing with SRP and I can control shadows render textures types. Plus, since version 2017.2 you can do multiple samplings types per texture. For example fetch depth and fetch shadows compare without the need of a separate texture. So yeah it's not a problem there.

 

Great news!

 

Folks,
If you need the NGSS point light shadows fix for 2017.3 don't forget to email support as I think Unity team is on vacations and will probably take longer to be live on the Store.
PS: If you want extreme cheap but high quals shadows in your project try the new Mobile shadows coming in next update. It's only 16taps optimized with 8!

 

Important: Due to the recent addition (Mobile shadows) to NGSS there's a new file that gets into play, a custom AutoLight.cginc that you need to place alongside UnityShadowLibrary.cginc. Read the Documentation (always).

Release notes from the new version in review:
- Mobile directional shadows. Currently works if Cascaded Shadows are disabled (Graphics Settings). The bug remains to be fixed by Unity but still better than default mobile shadows. Once it's fixed, you will have Cascaded Shadows on top of it. There's a new option in NGSS_Directional component called "IS_MOBILE". Turn it on if you targeting low end PC or Mobile devices.
- Compatibility fix for Point Light shadows in Unity 2017.3
- Improved Point Light shadows filtering and speed. Re-implemented screen space noise stabilization algorithm, optimized a couple of maths there
- Spot Filtering now gets stabilized at screen space (you'll notice less jumping and randomness). It got also optimized the way
- Contact Shadows opacity now follows directional shadows opacity

Video demonstration of Mobile NGSS filtering (no Cascaded version):
https://s3.amazonaws.com/uploads.hi...U0vwmnLbJF0SV/NGSSMobileShadowsNoCascades.mov
PS: With cascades it will look exactly the same as in PC.

 

Hey @tatoforever,

contact shadows are broken in Unity 2017.3 with SteamVR and single pass stereo rendering. They work fine in multipass. It seems shadows are different for both eyes.

 

@daschatten
Yes, I'm working on it and the fix will be available in one of January updates.

 

Great, thanks!

 

Hello, could you add contact shadow to spotlight and point light? Like in Unreal engine 4?

 

@Danua,
Planned for NGSS 2.0 but not on initial release. The idea is to do similar to NGSS 1.x live cycle (launch with a basic set of features and add them in minor/major updates so you can get access quickly to new shadows features instead of waiting for the whole absolute thing to be ready).
Regards!

 

Ok good to go.)

 

contact shadows = screen space shadow. isnt it?

 

@zelmund,
Yes, ContactShadws both from Unreal and NGSS uses the screen depth buffer to gatter positions. The idea is quite simple, for every frag get an initial distance to light then check depth distances along a ray (light direction) for x amount of units (number of samplers). If base distance is larger than sampled ray distance it means that current frag is occluded thus should be shadowed.
The reason I din't added ContactShadows to local lights is the same as why NGSS 1.x doesn't have a component to tweak properties individually on every spot/point light = I don't have access to light indexes, so I don't know which light I'm setting properties on (that's why the hack with Shadows Strength to tweak penumbra softness). The default renderer just render meshes with the shaders located in CGInclude folder in a render loop.
This is not a problem with NGSS 2.0 as it's done with Scriptable Render Pipeline (with HD and Lightweight renderers) and I have access to their sources thus I can add any custom property I want. New shadowing techniques are coming in NGSS 2.0.

 

@ksam2
If not related to NGSS product please write to support, I'll be happy to help though.
And to answer your question yes, bake the outdoor light with shadowmasks.

 

Wait scriptable render pipeline?? Really ?But can you say when ynity implement scriptable render loop? Is this that we will have ability to tweak light parameters separately I clear it?

 

@Danua
Scriptable Render Pipeline will give you full control over the rendering process. From cameras, lights, shadows and shaders used to render your scenes. Starting in Unity 2018.

 

Something wrong this asset. I'm using this asset only for directional light with default settings. Without contact shadows. FPS is too low. I did the thing for spot light and point light.


Without NGSS:


With NGSS:


Target platform: PC
Unity version 2017.1.1
Quality settings:

Directional Light(Only light in the scene):


And The time to build the game has increased 10 times. Is this normal? Please help...

 

Try disabling PCSS filtering. The build time increase has nothing to do with NGSS though.

 

Why does it cost so much performance?

 

You should not have such perf drop unless your game was already GPU bound before NGSS.
What other effects are you using in your game?
What's the hardware you are testing?

 

any chance to get update for 2017.3 ?

 

@kurzemnieks
Email support with your invoice number.
PS: Update is being reviewed by Asset Store staff.

 

Folks,
The update is live on the Store.
Please don't forget to read the updated documentation, there's two new files you need to add to CGInclude folder.

 

never mind, got the update through asset store today! Thanks!!!

 

Hi, tatoforever.
I tried the newest ngss in unity2017.3f3, it operates good!
But, not working with some other assets.
・slightlymad's VolumetricLight script.(https://github.com/SlightlyMad/VolumetricLights)
If camera is in point light attached volumetriclight script, screen will be pink.

and I got this error.

Spoiler: error

Trying to access pass 2, but material 'Sandbox/VolumetricLight' subshader (0) has only 1 valid passes.UnityEngine.Material:SetPass(Int32)
VolumetricLight:SetupPointLight(VolumetricLightRenderer, Matrix4x4) (at Assets/VolumetricLights-master/Assets/Scripts/VolumetricLight.cs:213)
VolumetricLight:VolumetricLightRenderer_PreRenderEvent(VolumetricLightRenderer, Matrix4x4) (at Assets/VolumetricLights-master/Assets/Scripts/VolumetricLight.cs:188)
VolumetricLightRenderer:OnPreRender() (at Assets/VolumetricLights-master/Assets/Scripts/VolumetricLightRenderer.cs:319)

・At build time shader error with AFS(https://www.assetstore.unity3d.com/jp/#!/content/68907)
But I can not get this errors after reinstall ngss.

Spoiler: error1

Shader error in 'Afs_Internal-DeferredShading': 'UnitySampleShadowmap': no matching 1 parameter function at Assets/Advanced Foliage Shaders v5/Shaders/Resources/Afs_DeferredLibrary.cginc(105) (on d3d11)

Compiling Vertex program with SPOT SHADOWS_DEPTH
Platform defines: UNITY_ENABLE_REFLECTION_BUFFERS UNITY_USE_DITHER_MASK_FOR_ALPHABLENDED_SHADOWS UNITY_PBS_USE_BRDF1 UNITY_SPECCUBE_BOX_PROJECTION UNITY_SPECCUBE_BLENDING UNITY_ENABLE_DETAIL_NORMALMAP SHADER_API_DESKTOP UNITY_HARDWARE_TIER1 UNITY_LIGHTMAP_RGBM_ENCODING

Spoiler: error2

Shader error in 'Afs_Internal-DeferredShading': 'UnitySampleShadowmap': no matching 1 parameter function at Assets/Advanced Foliage Shaders v5/Shaders/Resources/Afs_DeferredLibrary.cginc(111) (on d3d11)

Compiling Vertex program with POINT SHADOWS_CUBE
Platform defines: UNITY_ENABLE_REFLECTION_BUFFERS UNITY_USE_DITHER_MASK_FOR_ALPHABLENDED_SHADOWS UNITY_PBS_USE_BRDF1 UNITY_SPECCUBE_BOX_PROJECTION UNITY_SPECCUBE_BLENDING UNITY_ENABLE_DETAIL_NORMALMAP SHADER_API_DESKTOP UNITY_HARDWARE_TIER1 UNITY_LIGHTMAP_RGBM_ENCODING

・At build time shader error with UBER(https://www.assetstore.unity3d.com/jp/#!/content/39959)

Spoiler: error1

Shader error in 'UBER - Specular Setup/ Core - simple (no normalmap)': 'UnitySampleShadowmap': no matching 1 parameter function at Assets/UBER/Shaders/Includes/UBER_AutoLightMOD.cginc(101) (on d3d11)

Compiling Vertex program with SPOT SHADOWS_DEPTH _WETNESS_NONE
Platform defines: UNITY_ENABLE_REFLECTION_BUFFERS UNITY_USE_DITHER_MASK_FOR_ALPHABLENDED_SHADOWS UNITY_PBS_USE_BRDF1 UNITY_SPECCUBE_BOX_PROJECTION UNITY_SPECCUBE_BLENDING UNITY_ENABLE_DETAIL_NORMALMAP SHADER_API_DESKTOP UNITY_HARDWARE_TIER1 UNITY_LIGHTMAP_RGBM_ENCODING

Spoiler: error2

Shader error in 'UBER - Specular Setup/ Core - simple (no normalmap)': 'UnitySampleShadowmap': no matching 1 parameter function at Assets/UBER/Shaders/Includes/UBER_AutoLightMOD.cginc(106) (on d3d11)

Compiling Vertex program with POINT SHADOWS_CUBE _WETNESS_NONE
Platform defines: UNITY_ENABLE_REFLECTION_BUFFERS UNITY_USE_DITHER_MASK_FOR_ALPHABLENDED_SHADOWS UNITY_PBS_USE_BRDF1 UNITY_SPECCUBE_BLENDING UNITY_ENABLE_DETAIL_NORMALMAP SHADER_API_DESKTOP UNITY_HARDWARE_TIER2 UNITY_LIGHTMAP_RGBM_ENCODING

Spoiler: error3

Shader error in 'UBER - Metallic Setup/ Core': 'UnitySampleShadowmap': no matching 1 parameter function at Assets/UBER/Shaders/Includes/UBER_AutoLightMOD.cginc(101) (on d3d11)

Compiling Vertex program with SPOT SHADOWS_DEPTH _WETNESS_NONE
Platform defines: UNITY_ENABLE_REFLECTION_BUFFERS UNITY_USE_DITHER_MASK_FOR_ALPHABLENDED_SHADOWS UNITY_PBS_USE_BRDF1 UNITY_SPECCUBE_BOX_PROJECTION UNITY_SPECCUBE_BLENDING UNITY_ENABLE_DETAIL_NORMALMAP SHADER_API_DESKTOP UNITY_HARDWARE_TIER1 UNITY_LIGHTMAP_RGBM_ENCODING

Spoiler: error4

Shader error in 'UBER - Metallic Setup/ Core': 'UnitySampleShadowmap': no matching 1 parameter function at Assets/UBER/Shaders/Includes/UBER_AutoLightMOD.cginc(106) (on d3d11)

Compiling Vertex program with POINT SHADOWS_CUBE _WETNESS_NONE
Platform defines: UNITY_ENABLE_REFLECTION_BUFFERS UNITY_USE_DITHER_MASK_FOR_ALPHABLENDED_SHADOWS UNITY_PBS_USE_BRDF1 UNITY_SPECCUBE_BOX_PROJECTION UNITY_SPECCUBE_BLENDING UNITY_ENABLE_DETAIL_NORMALMAP SHADER_API_DESKTOP UNITY_HARDWARE_TIER1 UNITY_LIGHTMAP_RGBM_ENCODING

Please give me an answer how to fix it.

 

Hello. Unity 2017.3p1
Shader error in 'Standard': 'unitySampleShadow': no matching 1 parameter function at /Programs & Games/Unity 2017.3.0p1/Editor/Data/CGIncludes/UnityStandardCore.cginc(437) (on d3d11)

 

Hi,

I think NGSS is not working properly in my situation. The shadows looks very noisy, not soft like your example and the only working option is PCSS_GLOBAL_SOFTNER parameter. Changing the other variables does nothing. Unity 2017.3.0p1 - Mobile (Android) Platform, NGSS 1.6.1v.



Thanks!

 

I had this problem too. I think it's a 2017.3.0p1 problem and not a NGSS problem. I rebaked my lighting on all my scenes and that fixed it for me. <3

EDIT: I take it back. I can't compile either. Damn!

EDIT 2: OK Shader issues resolved. Reinstalled with 1.6.1 from the asset store and solved my problems and allowed me to successfully build. 1.6.0 had only 2 files but 1.6.1 has 3 that needed to go into CGincludes. Aces now!

 

Hi, I realize I can't build my project after I update to use latest version of NGSS, everytime I try to build and it fail with a bunch of shader error. I attached the error and I using Unity 5.6.5

 

Awesome asset.


This implement in our scene pretty well, destroy every problem with shadow. Awesome.

 

But I have only one Issue with custom shader made with:

Spoiler

'UnitySampleShadowmap': no matching 1 parameter function
Compiling Vertex program with SPOT SHADOWS_DEPTH SHADOWS_SOFT LIGHTMAP_OFF DIRLIGHTMAP_OFF DYNAMICLIGHTMAP_OFF
Platform defines: UNITY_ENABLE_REFLECTION_BUFFERS UNITY_USE_DITHER_MASK_FOR_ALPHABLENDED_SHADOWS UNITY_PBS_USE_BRDF1 UNITY_SPECCUBE_BOX_PROJECTION UNITY_SPECCUBE_BLENDING UNITY_ENABLE_DETAIL_NORMALMAP SHADER_API_DESKTOP UNITY_LIGHT_PROBE_PROXY_VOLUME UNITY_LIGHTMAP_FULL_HDR

And some warning to every custom shader. Also made with amplify as well. What does it mean? And how to solve this?

Spoiler

'i': loop control variable conflicts with a previous declaration in the outer scope; most recent declaration will be used
Compiling Vertex program with SHADOWS_CUBE
Platform defines: UNITY_ENABLE_REFLECTION_BUFFERS UNITY_USE_DITHER_MASK_FOR_ALPHABLENDED_SHADOWS UNITY_PBS_USE_BRDF1 UNITY_SPECCUBE_BOX_PROJECTION UNITY_SPECCUBE_BLENDING UNITY_ENABLE_DETAIL_NORMALMAP SHADER_API_DESKTOP UNITY_LIGHT_PROBE_PROXY_VOLUME UNITY_LIGHTMAP_FULL_HDR

 

Красиво

 

Hey guys,
I'm back from holidays, I'm gonna start answering more closely your questions/issues tomorrow.
Did you guys read the updated documentation? There's now three new files that you need to place in the CGInclude folder. Btw, do not Hit Build n Run as sometimes produces unwanted results, try first Build and then Build n Run.

 

Folks,
To all of you having build errors with v1.6:
Apparently there's too many custom shaders calling UnitySampleShadowmap and unitySampleShadow functions with default parameters set (which is only one) and in version 1.6 I've added a second parameter for screen space noise stabilization which is computed in the vertex shader (saves lot of instructions as before it was done in the pixel shader).
Turns out it was a bad idea as most of custom shaders call those methods with only one parameter thus I'm reverting it back to how it was so you can keep using your custom shaders with NGSS as before. Though, we might lost the quality improvement on noise stabilization introduced in v1.6 (hopefully not).
This issue have nothing to do with the new mobile shadows addition to NGSS. Was only the noise quality improvement part added in v1.6.
If you need to build your project, try reverting back to default CGInclude files otherwise keep working normally. I'm working on the fix and will let you know when it's ready.
PS: Happy new year (quite late though).

 

Having to replace default unity files is a really annoying workflow, particularly with large teams and unity updates - it would definitely be preferred to have changes to unity default include files optional

 

Hello please say what kind fix need write to restore custom shader work? I've got error

'UnitySampleShadowmap': no matching 1 parameter function
Compiling Vertex program with POINT SHADOWS_CUBE LIGHTMAP_ON SHADOWS_SHADOWMASK DIRLIGHTMAP_OFF DYNAMICLIGHTMAP_OFF
Platform defines: UNITY_ENABLE_REFLECTION_BUFFERS UNITY_USE_DITHER_MASK_FOR_ALPHABLENDED_SHADOWS UNITY_PBS_USE_BRDF1 UNITY_SPECCUBE_BOX_PROJECTION UNITY_SPECCUBE_BLENDING UNITY_ENABLE_DETAIL_NORMALMAP SHADER_API_DESKTOP UNITY_LIGHT_PROBE_PROXY_VOLUME UNITY_LIGHTMAP_FULL_HDR

It's mark this line below:
////// Lighting:
float attenuation = LIGHT_ATTENUATION(i);

 

@Danua
You can add "screenPos" as a second parameter to UnitySampleShadowmap and unitySampleShadow functions in your custom shaders. But keep in mind you will have to remove it again once you get the fix.

 

Hello,

Some advice about the noisy shadows? I've already replaced the three new files in the CGInclude folder, that's not the problem, maybe I'm doing something else wrong...

Comparison between your example(image_1) and mine(image_2). Unity 2017.3.0p1 - Mobile (Android) Platform, NGSS 1.6.1v.



Thanks!

 

@danix,
Hey man, sorry I completely forgot your post. Yes, you can disable the noise filtering to obtain the same result as the left image by commenting the #define NGSS_USE_POISSON_SAMPLING_MOBILE in UnityShadowLibrary.cginc at line 31. You need to delete your project ShaderCache after that modification in order to apply the change.
PS: Notice that as your kernel varies you will notice banding.

 

@Carpet_Head
Unfortunately it's the only way to improve shadows on current default renderer and keep it compatible with all custom shaders available.
This will change with NGSS 2.0 which is done with SRP where you only have to load the SRP asset in your project once and voila.

 

I'm having an issue where no shadows appear in builds at all, version 1.6, trying the latest version now. The builds complete, no errors, but in game there are no shadows whatsoever. Anything you've heard about?

 

@_M_S_D_
Are you targeting mobile platforms with spot/point light shadows? If so, then that's normal, Unity does not render spot/point shadows on mobile platforms, only directional. If your target platform is other than mobile then yes, try with the latest version (1.6.1)
PS: Don't do Build and Run. Try with Build first, then build and run afterwards.

 

Nope, not mobile. Windows 32 and 64 bit builds with directional lights as the only shadow casters.

 

Try with the last NGSS version and do a normal Build (not Build and Run) and see how it goes?