Skip to content
This repository has been archived by the owner on Jul 22, 2024. It is now read-only.

Set correct Oculus WebVR device name #1032

Merged
merged 1 commit into from
Mar 20, 2019
Merged

Conversation

MortimerGoro
Copy link
Contributor

@MortimerGoro MortimerGoro commented Mar 18, 2019

We are using "Oculus" instead of "Oculus Go" for the WebVR device name.

I found that this affects Sketchfab performance (with "Oculus Go" it uses a lower quality model/shader). Could this affect other engines @fernandojsg, @cvan?

@daoshengmu Please review the correct name.

@ghost ghost assigned MortimerGoro Mar 18, 2019
@ghost ghost added the in progress label Mar 18, 2019
Copy link
Contributor

@cvan cvan left a comment

Choose a reason for hiding this comment

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

thanks for changing this. which sites in your testing (or which issue) does this in particular fix? also, see my comment about WebXR vs. WebVR v1.1.

Sketchfab performance is already unusable on the Oculus Go. we won't be displaying Sketchfab models for the Oculus Go, so hopefully not a huge issue. but users navigating directly to https://sketchfab.com/ and enter VR on the Go will likely be confused. (but, that's a larger issue we should accommodate for in a separate issue and PR.)

@@ -988,7 +988,11 @@ DeviceDelegateOculusVR::RegisterImmersiveDisplay(ImmersiveDisplayPtr aDisplay) {
return;
}

m.immersiveDisplay->SetDeviceName("Oculus");
if (m.IsOculusQuest()) {
m.immersiveDisplay->SetDeviceName("Oculus Quest");
Copy link
Contributor

Choose a reason for hiding this comment

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

to prepare for the WebXR Device API (which intentionally does not expose identifier strings for devices), shouldn't we begin deprecating VRDisplay#displayName?

Copy link
Contributor

@daoshengmu daoshengmu Mar 18, 2019

Choose a reason for hiding this comment

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

It looks correct compared to Oculus browser.

Copy link
Contributor

Choose a reason for hiding this comment

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

👍 good to know that we have parity with the Oculus Browser. in that case, we can defer deprecating the device string until WebXR is implemented (in both browsers) and web-compatibility isn't affected.

@@ -988,7 +988,11 @@ DeviceDelegateOculusVR::RegisterImmersiveDisplay(ImmersiveDisplayPtr aDisplay) {
return;
}

m.immersiveDisplay->SetDeviceName("Oculus");
if (m.IsOculusQuest()) {
m.immersiveDisplay->SetDeviceName("Oculus Quest");
Copy link
Contributor

@daoshengmu daoshengmu Mar 18, 2019

Choose a reason for hiding this comment

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

It looks correct compared to Oculus browser.

Copy link
Contributor

@cvan cvan left a comment

Choose a reason for hiding this comment

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

per @daoshengmu's comment, this looks good to go.

@cvan cvan added this to the v1.1.4 milestone Mar 18, 2019
@MortimerGoro MortimerGoro merged commit b1ba6ae into master Mar 20, 2019
@ghost ghost removed the in progress label Mar 20, 2019
@bluemarvin bluemarvin deleted the oculus_device_name branch March 20, 2019 15:57
@cvan cvan modified the milestones: v1.1.4, v1.1.3 Apr 15, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants