-
Notifications
You must be signed in to change notification settings - Fork 0
FAQ
Something else already owns the physical card (usually OBS Video Capture). Close/disable that source, then restart Qoresence with --streamer-device 0. Only use OBS Virtual Camera if you intentionally run legacy Pattern A.
Pad must be PC-visible. Plug USB or use Remote Play. Log lists HID candidates. Video path continues without pad.
No edges in lag band, or controller off. Press buttons; widen QORESENCE_IVC_LAG_HI_MS only if using Virtual Cam lag.
DualSense Edge report layout may still chatter; pipeline is valid — decode harden is on roadmap.
Expected for MJPEG ops glass. Theater prefers WebRTC from FrameHub. Use Retina Monitor for the local blit; LIVE / Mobile Glass for “is the path alive?”
127.0.0.1 on the phone is the phone itself. Restart with --deck-bind 0.0.0.0 and scan the Theater QR. The PC cannot find phones on Wi‑Fi or open Safari/Chrome remotely.
Pass --game-profile madden_27 (or ncaa_football_27). An explicit pin is not yanked when optics lock a stranger pair. Pause/menu is overlay-rejected (no title claim).
No InputRing events in export window (controller off or silent pad).
Use http://127.0.0.1:8765/overlay.html not file://; ensure Deck process is running.
- What is Qoresence?
- Novel Stack
- Operator Runbook
- Capture Ownership
- Retina Deck & Monitor
- Mobile Glass
- Title Presence
- Retina Monitor
- Controller-Video Sync
- Two-Speed ClutchBot
- A2A ClutchBot
- Agent Glass — spectator API
- MCP Glass — new AI agent adapter
- Streamr — experimental
- Roadmap
- FAQ