Skip to content

feat(settings): add gyroscope controls toggle - #556

Merged
zortos293 merged 1 commit into
devfrom
capy/gyroscope-controls-setting
Jun 29, 2026
Merged

feat(settings): add gyroscope controls toggle#556
zortos293 merged 1 commit into
devfrom
capy/gyroscope-controls-setting

Conversation

@zortos293

@zortos293 zortos293 commented Jun 29, 2026

Copy link
Copy Markdown
Collaborator

This PR adds an experimental toggle for gyroscope controller input mapping to address issue #226.

  • Add enableGyroscopeControls boolean to shared and main Settings interfaces
  • Render toggle in Input settings with Beta badge and explanatory hint
  • index "gyro", "gyroscope", and "motion controls" for settings search
  • Add English translation strings for the setting and hint

Open OPE-231 OPE-231


Note

Low Risk
Settings and UI-only change with default off; no stream or input pipeline behavior is modified in this diff.

Overview
Adds an experimental Gyroscope Controls option under Input settings (Beta badge, hint text, English strings) so users can persist a preference for controller motion-sensor / gyro aiming when the input stack supports it.

Introduces enableGyroscopeControls on shared/main Settings, default off, with renderer defaults aligned and the Input settings search index extended for controller/gyro terms. This PR does not add runtime wiring from the flag into WebRTC or native input in the changed files—only storage and UI.

Reviewed by Cursor Bugbot for commit 0383fd9. Configure here.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
@zortos293 zortos293 added the capy Generated by capy.ai label Jun 29, 2026 — with Image Capy AI
@coderabbitai

coderabbitai Bot commented Jun 29, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: becf69ab-413e-430d-8a0c-64d56cdeaea0

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch capy/gyroscope-controls-setting

Comment @coderabbitai help to get the list of available commands.

@cursor

cursor Bot commented Jun 29, 2026

Copy link
Copy Markdown

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_f2518b28-53da-4e81-b4df-95f0c1e26912)

@zortos293
zortos293 merged commit 8b08980 into dev Jun 29, 2026
17 checks passed

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 0383fd91df

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +3455 to +3456
checked={settings.enableGyroscopeControls}
onChange={(e) => handleChange("enableGyroscopeControls", e.target.checked)}

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Wire the gyro toggle into streaming

When a user enables this checkbox and then starts a stream, nothing downstream observes the value: buildCurrentStreamSettings() only forwards the existing stream fields into the WebRTC/native paths, and a repo-wide rg enableGyroscopeControls shows only the settings defaults/types and this UI. As a result the new setting is persisted but cannot actually expose motion sensors for either input backend.

Useful? React with 👍 / 👎.

Chizuui pushed a commit to Chizuui/OpenNOW-Modified that referenced this pull request Aug 11, 2026
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

capy Generated by capy.ai

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant