FAQ

The Beautify profile in URP cannot store scene references, so the DOF target is stored separately in the BeautifySettings component rather than in the profile itself. When undoing profile changes, the target reference may be reset as a side effect. As a workaround, you can set the DOF target through code at runtime instead of in the editor, which avoids this undo issue.

Don't use the Automatic Strip option. Instead, expand the strip settings and manually select only the features you know you won't use. This allows you to keep specific features like Depth of Field available for runtime modification while still stripping other unused features.

Change the Beautify render event to 'Before Transparents' in the settings.

Set the overrideState property for the desired effects (e.g., chromaticAberrationIntensity.overrideState, vignettingInnerRing.overrideState, etc.). If the settings don't persist after scene reload, call BeautifySettings.UnloadBeautify() before modifying the properties to ensure proper reinitialization.

Call BeautifySettings.UnloadBeautify() before modifying the property. This removes any link between the singleton BeautifySettings shortcut and a previous volume, ensuring it will modify the current profile in the scene. Then use BeautifySettings.settings.anamorphicFlaresIntensity.Override(value) to set the intensity.

For Quest 2 performance optimization: set Downscale to 2, use Depth Texture Mode = Force Prepass (most performant), disable Clear XR color buffer, enable Multi-View instead of Multi-Pass, and refer to the official performance tips guide at https://kronnect.com/guides/beautify-urp-performance-tips/. Also check Project Settings / Oculus recommendations.

Ensure the Beautify Render Feature is added to all URP assets in Project Settings > Quality. Only use the stripping options in one volume to avoid conflicts. If you want full control, you can comment out unused shader keywords directly in the code (each keyword is self-descriptive), or use the Shader Control tool to disable keywords from the inspector instead of editing code.

Increase the depth diff setting for better results. For optimal outcomes, use the Per Object Id technique to control outlines on a per-object basis rather than making large global adjustments that can cause visual instability.

Beautify follows the URP volume system. The BeautifySettings shortcut only affects the main volume. When using multiple volumes, you need to get a reference to the VolumeProfile used in each volume and update the settings directly on those profiles. See the scripting tips documentation for examples with other post-processing effects.

Disable every feature you don't need in the build settings. For features you will always use, they can be replaced by defines as explained in the documentation (https://kronnect.com/guides/build-tips-beautify-urp/). This will save unneeded shader variants. You can check how many shader variants are being generated by looking at the build log or using a tool like Shader Control.

Reducing shader variants through defines will impact build size and build time. At runtime, Beautify primarily consumes VRAM (video memory) from shader binary code, not system RAM. The RAM shown in memory profilers is from shader binary code, not from Beautify's runtime operation.

Post-processing effects don't natively support layer masking. You have several alternatives: (1) Render the object to a different camera entirely (though this impacts performance), (2) Use the Transparent render queue to render the object over blurred content without making it transparent, (3) Use a separate Gaussian blur shader with a plane positioned behind your object instead of relying on Beautify's post-processing, or (4) If you want blur behind an examined object, consider using Depth of Field adjusted to the distance of that object instead.

Checked = exclude/strip that feature from the build. Unchecked = include the feature. The stripping options are global and affect all scenes during compilation.

Check if you have multiple URP assets configured in Project Settings > Quality. During builds, a different URP asset with different stripping settings may be selected, overriding your configuration. Ensure all Quality level URP assets have consistent Beautify stripping settings.

DoF blur is gradual from the focus distance point. Objects closer to the focal point blur less, while objects farther away blur more intensely. Adjust the Focus Distance to set where the sharp focus point is, then increase both Focal Length and Aperture values to control the blur gradient. You may need to set Focal Length to a high value to achieve the desired effect. The blur strength increases with distance from the focal point.

Use the layer mask feature to specify which objects can produce anamorphic flares. If you need dynamic control, you can change the layer that the light is on via script at runtime.

Beautify 3 for URP uses the URP volume framework based on volume profiles instead of its own profile system. You can create different volume profiles with custom settings and assign them to the volume component. At runtime, you can swap between volume profiles to change effects (for example, switching to an underwater effect when the camera enters a specific area). The built-in pipeline version of Beautify still uses its own profiles, but URP uses the more generic volume profile concept.

Beautify shaders are stored inside a Resources folder, and Unity automatically compiles and includes anything inside Resources folders in builds. To reduce build size, you may need to reorganize shader placement or use conditional compilation.

The layer exclusion mask excludes sharpness from the specified layer, but it operates on a per-pixel basis rather than a per-layer basis. If another layer that is not excluded is rendered on top of excluded layer pixels, those top pixels will lose sharpening as well, since the exclusion is based on the pixel location rather than layer priority.

Some renderer is missing or invalid in the list of the URP asset. A fix was provided by the developer that prevents an error if this happens. As a workaround, try removing and re-adding all entries in the RenderList, ensuring the UniversalRenderPipelineAsset_Renderer is placed first.

Beautify does not support multiple outline colors natively. To achieve this, combine Beautify with Highlight Plus: apply Beautify before the transparent pass for the default layer, and use Highlight Plus for enemy outlines with different colors.

This issue occurs when foveated rendering is enabled. Beautify does not yet support foveated rendering. Disable foveated rendering in your Quest 3 VR setup to resolve the artifact.

Enable the Transparency support option in the Beautify settings. This option is located in the configuration panel and allows Depth of Field to work correctly with transparent or layered 2D assets.

Beautify offers two alternatives: (1) Use Eye Adaptation, which provides automatic exposure adjustment based on scene luminance with configurable min/max exposure, transition speeds, and center weighting in the inspector. (2) Use scripting with trigger colliders to change Beautify settings via the API when the player enters different zones, adjusting brightness, contrast, or exposure values dynamically.

Please visit the Support Center and use our AI Support Assistant to get answers. If the issue persists, submit a reproduction project so we can investigate further and help you.