You’re very welcome! I’m glad it could save your project!

Yeah it was a little tricky to figure out 😅

@@LlamAcademy Thanks for the hard work, just wanted to ask if this also works with details that are painted with unity's detail paint brush like trees and such

I don’t think this will work out of the box with Unity Terrain with trees, grass, and other details placed.

Thank you 🙏 I appreciate that

Glad it could help you!

Great! 🙌 I don't fully understand what all of the things we're toggling do either so 🤷‍♂️sometimes just have to just accept some magic :)

😅 I don’t know about that, but thank you! I’m glad it helped you!

🙌

did change it to SphereCastNonAlloc with a radius of 1 for my game

That's why it's available :) Glad it helps you

Awesome to hear! 🙏 I appreciate that

Hmm……. I will check that out maybe I pushed some incorrect code after doing the editing on the video. Let me get back to you. The idea is this supports as many objects blocking view as you allow RaycastHit array size to be.

Glad you think so! Thanks!

To debug this I like to make an editor script that draws the raycast for me with Handles.DrawLine() based on the direction and start position of the camera. Somehow a lot of times I mess up the raycast and it's not hitting what I expect. If you see the line going through all the objects, double check the layer mask you're raycasting on and the layers of the objects you expect to be hitting to see if there's something wonky going on there.

@@LlamAcademy Thanks so much, I got to work! Looks like it was the layers of the objects and the layermask that was making everything wonky!

Hi! Sorry for the delay in response, it's been a crazy few weeks for me lately. For your issue... I'm not sure how you could have that happen. Because the FadingObject script finds all child renderers and we iterate over all materials, I can't imagine a scenario where you could run into that if FadingObject just pulls all children. There's no magic material properties on the Standard Lit Shader in URP that would prevent it from fading out. Some ways I could imagine that would result in what you described would be: 1. If there are overlapping objects, some without colliders, that are not parented under the object that has a collider + FadingObject. The secondary object would not be considered and not fade out 2. If FadingObject has Renderers assigned in the inspector that are not the full set of Renderers to consider. If you can send a video of your scene setup and the issue maybe I could spot something funny? Or if you have a small reproducible repository I could check it out as well

The objects that can obstruct the camera need a reasonable collider or it won’t work! Do you have colliders on your objects?

​@@LlamAcademy Yes, i use the same sense , the starter 3th person

Works with any target

Thanks for the feedback! When I go back in time and review my older videos I see a lot of room for improvement. One of those (many areas 😅) is the too loud background music that obviously loops. I hope in more recent videos you find the music choice and volume less distracting.

@@LlamAcademy Thanks for the response! Unfortunately, once you've focussed on the music it's really hard to just ignore it - I have tried :). The content of the tutorial was very helpful though. I only really wanted the bit about fading a 3D object with URP, but I found much more than that, which I am sure will be very useful in the future.

Thank you for sharing your update 🧡! I'm sure someone else will run into the same issue and appreciate that

@@LlamAcademy So I did a build and run test on my project and the fade function doesn't work. Works great in the editor but fails to implement in the build. Any thoughts where to begin debugging this issue?

Sometimes in the build Unity will strip shader variants that are not used. That’s configured in your project settings / graphic settings. If you aren’t using any transparent materials sometimes this variant doesn’t get included in the build. You can add that variant as a preloaded shader to ensure it’s always included.

You’re very welcome! ☺️

Honestly, I haven't looked into Render Features. When I implemented this effect, URP and Render Features were not out yet. This video was a direct URP translation from what I implemented in the Built-In Render Pipeline.

Hi! Yes this is specifically for URP. In the description of the video I have a link to the video showing how to do it with the Built-in render pipeline. The process is the same, but I give you the specific properties and values over there.

If you have a static list of items that need to be checked, I think the simplest solution is to attach multiple of the same script with different targets. If it's dynamic, then I would expect you're doing it conceptually correct on the CheckForObjects. Could you send me a gist or something with the code? Maybe it's just a small tweak that needs to be made to what you already did.

@@LlamAcademy yeah it'll be a dynamic list: I have a script on the targets that adds them to the list when they enter camera view and removes them when they exit camera. What would be the best way for me to share my code with you? Discord?

Actually I believe I solved it myself. For other people's reference: essentially when doing the raycast check for each consecutive target, it overrides the array of the previous. And since the function which fades back in objects that are no longer being hit uses this Hits array, it only takes into consideration the last target checked. You need to save all the objects hit in a new array/list and use that in the FadeObjectsNoLongerBeingHit function

Oh! Great to hear. I like to use GitHub Gists to share individual scripts: gist.github.com/starred

That’s right. The terrain uses a different shader and does not use the standard rendering with a MeshRenderer

Hmm...I am not 100% sure you can achieve that very easily. Transparent objects usually are not included in the SSAO pass. Maybe you can tweak the settings of SSAO to go after opaque and change the render queue to something like Opaque + 1 to see if that works? Otherwise it might require custom implementation of SSAO to consider these objects.

@@LlamAcademy Thank you for the answer! I'll see what I can do!

Yes! A Raycast is an “infinitely thin” line. You can use a boxcast or spherecast if you need a wider area. You can check out this video to see how all types of “casts” work: kzfaq.info/get/bejne/nLCpnJqdl9q7e6M.html

@@LlamAcademy Thank you very much for answer! But in your case you are actually using RaycastNonAlloc and i don't know how to feet it exactly to your script because each Raycast have different settings allocation and i think using non alloc is better isn't that?

Yes, the NonAlloc is the most performant option since it doesn’t generate garbage. You can feed the BoxCastNonAlloc very similarly to RaycastNonAlloc. The video linked above has examples of how to feed each “cast” along with links to the documentation pages!

@@LlamAcademy Yes i already watched these video before

I will review this in the morning and get back to you

😎

Thank you, I figured it out myself))

Could you explain your solutions for this? I got the same issues.

@@chuozt I'll answer you a little later!

@@chuozt it was so long ago that I don’t remember what was there, here is the entire coroutine: private IEnumerator FadeObjectOut(FadingObject FadingObject) { float time = 0; while (FadingObject.Materials[0].color.a > FadedAlpha) { foreach (Material material in FadingObject.Materials) { if (material.HasProperty("_Color")) { material.SetFloat("_FloatAlph", 1f); AlphaStep = FadingObject.InitialAlpha; // AlphaFloat = Mathf.Lerp(FadingObject.InitialAlpha, 0.4f, time * FadeSpeed); for (int i = 0; i < 3; i++) { AlphaStep = AlphaStep - 0.2f; material.color = new Color( material.color.r, material.color.g, material.color.b, AlphaStep ); yield return new WaitForSeconds(FadeSpeedOn); Debug.Log(AlphaStep); } } } time += Time.deltaTime; yield return null; } if (RunningCoroutines.ContainsKey(FadingObject)) { StopCoroutine(RunningCoroutines[FadingObject]); RunningCoroutines.Remove(FadingObject); } }

@@qqqwwwwq Your objects' surface types are set to Transparent initially right?

♥

Hmm..... you can safely delete that file. It was just carried over from the Third Person Starter Assets from Unity. Which version of Unity are you on?