ReferenceLimitations and known issues

Limitations and known issues

Understand the current constraints of PBADOF 1.4, including unsupported pipelines, runtime-only behaviour, single-camera enforcement, and experimental feature caveats.

Current limitations

HIBIKI entertainment's PBADOF 1.4.0 is a capable autofocus system with a small set of known limitations.

LimitationDetailsWorkaround
Physically based camera exposureSetting the Volume Override exposure to Physical Camera causes inaccurate fluctuations.Use Automatic Exposure instead. Do not combine PBADOF with physically based camera exposure.
Built-in Render PipelineThe Built-in Render Pipeline is not supported.Use HDRP or URP.
URP debugging resourcesURP has more limited debugging resources compared to HDRP.Use HDRP for development and debugging where possible. URP works best with Bokeh depth-of-field mode.
Collider-based focus selectionFocus targets are acquired through physics raycasts. There is no depth-map-based focus selection at the current stage.Add colliders to objects you want PBADOF to focus on. Use the focus proxy component for renderer-only objects.
Runtime-only operationPBADOF is only active at runtime. The focus solver does not operate in edit mode.Use play mode to test and verify focus behaviour. Use the diagnostic snapshot and readiness readouts for inspection.
No local split-screenLocal split-screen is not supported.Use a single-camera workflow.
Single active componentOnly one enabled AutoDepthOfField component owns the depth-of-field output. Multiple components on multiple cameras are not supported.Check CurrentReadiness to identify the active and passive components. Design around a single autofocus owner.

For renderer-only objects without colliders, use the focus proxy component. For development and debugging, HDRP provides more debugging resources than URP.

Experimental features

Experimental features are available for evaluation, but their behaviour and APIs are not guaranteed to remain stable between releases.

Experimental features are not guaranteed to always function as intended. They may change or be removed in future releases. Use them with caution in production projects.

FeatureStatusNotes
Cinemachine 3 adapterExperimentalAvailable through the optional HIBIKI adapter. Provides lens authority modes and conflict detection. See the Cinemachine 3 integration guide.
Extension systemExperimentalThe IAutoDepthOfFieldExtension interface is available for custom extensions. The API may change in future releases. See the Override volume and focus proxy API.

Known issues

No critical known issues are reported in the 1.4.0 release beyond the limitations listed above. If you encounter unexpected behaviour, report it through the HIBIKI support channels.

Reporting issues

When reporting an issue, include:

  • PBADOF version, checked in VERSION.md or the package manifest
  • Unity version and patch number
  • Render pipeline, HDRP or URP
  • Steps to reproduce
  • Expected and actual behaviour
  • Diagnostic snapshot output, if available

Next steps

For the full compatibility matrix, see Compatibility. For common questions, see the FAQ.

Was this page helpful?