## Frequently asked questions HIBIKI entertainment set a maximum target of 0.1% CPU utilisation for the autofocus solving lifetime of PBADOF. The total cost of depth-of-field rendering in Unity varies based on: - Asset quality settings - Screen resolution - 8-bit or 16-bit colour and post-processing buffers - Filtering quality - Whether the physically based lens model is enabled The autofocus solving itself is lightweight. The depth-of-field render pass cost is governed by Unity's own post-processing stack, not by PBADOF. Yes. PBADOF supports URP and works best with Bokeh depth-of-field mode. Some debugging resources are more limited in URP compared to HDRP. See the [Compatibility page](/hibiki-asset/physically-based-auto-depth-of-field/compatibility) for the full matrix. No. The Built-in Render Pipeline is out of scope and not supported. Use HDRP or URP. No. PBADOF enforces single active output ownership. Only one enabled `AutoDepthOfField` component owns the depth-of-field output at a time. Additional enabled components become passive and report that state through readiness diagnostics. No. Local split-screen is not supported. PBADOF targets a single-camera workflow. No. PBADOF is only active at runtime. The focus solver and depth-of-field output operate during play mode. You can use the diagnostic snapshot and readiness readouts to inspect behaviour during play mode sessions. Yes, through an experimental adapter. The HIBIKI adapter lets you blend PBADOF autofocus with Cinemachine 3 camera sequences. See the [Cinemachine 3 integration guide](/hibiki-asset/physically-based-auto-depth-of-field/cinemachine-3-integration) for setup and configuration. No. Setting the Volume Override exposure to Physical Camera will cause inaccurate fluctuations. HIBIKI recommends using Automatic Exposure instead of physically based camera exposure when PBADOF is active. PBADOF uses physics raycasts against colliders in the scene. There is no depth-map-based focus selection at the current stage. If an object has renderers but no colliders, use the [focus proxy component](/hibiki-asset/physically-based-auto-depth-of-field/focus-proxy) to fit a box collider around its visual bounds. Yes. Use presets to save and apply configurations across cameras, weapon optics, and override volumes. See the [Physical lens and presets guide](/hibiki-asset/physically-based-auto-depth-of-field/physical-lens-and-presets) for details. Use the [HIBIKI support](/help-center/faq/how-to-contact-support) channels to report issues. You can also use the roadmap and feedback portal to submit feature requests and track activity. Did not find your answer? [Contact support](/help-center/faq/how-to-contact-support) or browse the [Help Center](/help-center).

FAQ

Frequently asked questions