Closed Bug 1419588 Opened 8 years ago Closed 3 years ago

Convergence on Samsung Odyssey seems wrong

Categories

(Core :: WebVR, defect, P3)

x86_64
Windows
defect

Tracking

()

RESOLVED WONTFIX

People

(Reporter: gfodor, Unassigned)

References

Details

Attachments

(4 files)

Attached image FF WebVR info
In testing WebVR apps with the Samsung Odyssey I've found that I have double vision after using an app for a few minutes. This does not occur when using: - WebVR in edge - Steam VR - Cliff House Attached are screenshots of the diag page for WebVR in FF (via OpenVR) and Edge.
Attached image Edge Info
Severity: normal → major
OS: Unspecified → Windows
Priority: -- → P1
Hardware: Unspecified → x86_64
We will likely need to modify the https://webvr.info/samples/00-hello-webvr.html page to start a VR presentation, as MS Edge doesn't expose all information until a VR presentation has been started.
I'll take this one, as it may potentially be related to the "Swimming" effects seen on the HTC Vive in Bug 1320616.
Assignee: nobody → kgilbert
See Also: → 1320616
The Windows Mixed Reality SteamVR preview has been updated on October 26 with a fix that may have corrected this. The patch notes include: "Fixed convergence issues" Could you please update the SteamVR app and the Windows MR SteamVR app, then advise if you are still seeing the same effects?
Flags: needinfo?(gfodor)
Yes, I confirmed this is still the case after updating today.
Flags: needinfo?(gfodor)
After verifying that the MS Edge and Firefox WebVR implementations are returning inconsistent VR display parameters, I implemented a small test app to compare the OpenVR and Windows MR API output directly. These values were captured using the HP Windows MR headset with the same IPD value and quality settings. My findings: - The Top and Bottom FOV returned by OpenVR (IVRSystem::GetProjectionMatrix) appear to be swapped. - IVRSystem::GetProjectionMatrix (OpenVR) and HolographicCameraPose->ProjectionTransform (Windows MR) are returning slightly different values. - IVRSystem::GetEyeToHeadTransform (OpenVR) returns an identity transform for the left eye and places the right eye the full IPD distance away, placing the left eye in the center. HolographicStereoTransform (Windows MR) places the eyes on each side. - The recommended viewport size returned for OpenVR was smaller than the size returned for the Windows MR API. I have filed this information in Microsoft's Feedback Hub: https://aka.ms/Cftf0y If this is found to be a bug in the Windows MR SteamVR app, then the issue may be fixed without requiring changes to FF.
Moving to p3 because no activity for at least 24 weeks.
Priority: P1 → P3
QA Whiteboard: qa-not-actionable

The bug assignee didn't login in Bugzilla in the last 7 months.
:jimm, could you have a look please?
For more information, please visit auto_nag documentation.

Assignee: kearwood → nobody
Flags: needinfo?(jmathies)
Status: NEW → RESOLVED
Closed: 3 years ago
Flags: needinfo?(jmathies)
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: