URP Render Feature to do full-screen transition effects, like iris-wipes.
Go to Package Manager, and click "+", then "Add from git URL". Paste the following in:
https://github.com/hunterdyar/Unity-Transition-Effects.git
If you wish, click on the "Samples" tab and import the basic usage examples.
First, Add the render feature to your URP Render settings. By Default for a 2D URP Project, these settings are Assets/Settings/Renderer2D.
At the bottom of the Renderer settings object is an "Add Renderer Feature" button. Select "Transition Effect Render Feature".
That's it. Now you're ready to use it!
The settings for the transition are stored right here.
- Active must be checked for the effect to be on. It's a convenient way to bypass an extra render pass when not needed, to minimize overhead. My utility coroutines turn this on and off, so be aware you may need to set it enabled if using your own code in addition to mine.
- Transition Type the type of visual transition. For the Circle transition, the "0-1" can be thought of as the radius of the circle. Transitions cannot be mixed together.
- Transition is a float where, at "0", the game will be visible, and at "1" the transition will cover the game entirely. We make a transition happen by smoothly sliding this value in a coroutine. You can, and will likely, want to do this yourself.
- Color the RGB color of the circle. Alpha is ignored completely.
The scriptable object settings are all editable at runtime. You can simply write a script that holds a reference to an serialized variable of type "TransitionEffectRenderFeature", and uses it's SetTransition, SetColor, SetTransitionType, and SetActive functions. You can assign the feature in the inspector from your renderer settings, and you're good to go.
It's good practice to set SetActive to false when not transitioning. The performance impact may be negligible, but why do extra render passes when we know we don't need to? You don't need to use my UseActive, RenderFeatures can be disabled from code at runtime, but I find this a hassle.
But, there are a number of utility scripts to make your life easier, in the "Transition" class. The simplest example is as follows:
using Blooper.TransitionEffects;
public class FadeInOnStart : MonoBehaviour
{
void Start()
{
StartCoroutine(Transition.TransitionInToScene(TransitionType.Fade,0.1f, 0.85f, Color.black));
}
}
If you have the ability, you can change your Canvas from "Screen Space - Overlay" to "Screen Space - Camera" (then assign the appropriate camera). For many users, this will work fine; and now the effect will happen on top of the UI.
If you have to use Overlay, then I can't help you. This is how the render features work. I don't really consider this a bug.
This is a tricky issue, and I'm researching for something better. Like the camera feature, it's not really a bug. Theyre called POST processing effects for a reason. In the meantime, There is a hacky workaround. Add a second Camera to the scene. Remove it's audio listener and be sure post processing is unchecked. Set it's Culling Mask to "Nothing", and it's Environment Background type to "Unititialized". Having a second camera in the scene is not ideal, and the effect is applied to both cameras (so it won't work well with the Fade transition). The camera only needs to be enabled during the transitions.
I don't recommend this workaround, but instead just rolling with it. When the transition color is black, a lot of the post processing effects don't do much. The feature I need to fix this is apparently a closed PR with no progress, but maybe there are other ways about it I just don't know about.
The textures are getting sampled such that they are being stretched to fit the game window. You will want them to have the same aspect ratio as your final project. Be sure to look at the filter mode in the import settings of the texture you want, and try different ones. Point will keep pixels sharp will bilinear will blur them, and either might be desired depending on your texture.