Known Issues

Current limitations and troubleshooting checks for the OVR Plugin for Unreal.

Current limitations

• Use Play In Editor or a packaged build for hardware testing. Simulate In Editor does not represent the normal locally controlled pawn and device lifecycle and is not the recommended validation path.

• The Fab plugin package must match the project's exact Unreal Engine version.

• Linux, WebGL, and consoles other than the listed Meta Quest Android path are not supported.

• Wine and Proton, including Steam Deck Windows compatibility layers, are not supported for Omara BLE or USB serial.

• Direct macOS BLE requires macOS 13.3 or newer.

• Android, macOS, and iOS production releases require their native toolchains, signing/permission configuration, and physical-device validation.

Common checks

• Plugin cannot be found: search for AOS: Architecture of Scent in Edit > Plugins and verify the package matches the engine version.

• Plugin assets are missing: enable Show Plugin Content in the Content Browser settings.

• Odor does not play: confirm that the device has reached the ready state. Requests made before readiness broadcast On Play Odor Not Ready and are not sent to the hardware.

• Windows serial adapter is missing: install the current Silicon Labs CP210x VCP driver and confirm the adapter appears as a COM port.

• Android BLE discovery fails: confirm the requested Bluetooth permissions and any Location Services prerequisite exposed by that Android version.

• macOS or iOS reports unsupported Bluetooth: verify usage-description keys, entitlements, signing, and the packaged application's permissions rather than relying only on an Unreal Editor permission grant.

• Companion bridge is unavailable: confirm the OVR Companion application is running and listening at the configured endpoint. The default is ws://127.0.0.1:8080.

• Win64 module/DLL load fails: use a normal Unreal build/package flow and verify BleWinrtDll.dll is staged in the plugin or packaged application's Binaries/Win64 directory. The runtime file name must match exactly.

For unresolved issues, contact OVRTechnology support.