Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inverted stereo in `360-photos.html´ (device dependent?) #132

Open
Mikael-Lovqvist opened this issue Oct 14, 2021 · 2 comments
Open

Inverted stereo in `360-photos.html´ (device dependent?) #132

Mikael-Lovqvist opened this issue Oct 14, 2021 · 2 comments

Comments

@Mikael-Lovqvist
Copy link

When media/textures/chess-pano-4k.png is loaded it is using mode stereoTopBottom but it seems it should use stereoBottomTop. I tested this by adding this to skybox.js Mikael-Lovqvist@b4e88cb and then testing it like so Mikael-Lovqvist@99e2bbe

This was tested on an Oculus Quest 2, I saw there were earlier mentions of inversion and the jpeg was replaced with a corrected png, could this be device dependent?

@alfski
Copy link

alfski commented Apr 26, 2022

The chess-pano-4k.png (Right on top, Left on bottom) is stereo inverted on a Quest 1 as well.
The older chess-pano-4k.jpg (Left on top, Right on bottom) displays correctly.

The normal convention is "stereoTopBottom" (Left on top, Right on bottom).
I'd just go back to the older reference mage?
(additionally the original jpeg is only 2.5Mb vs 20Mb for the swapped .png!)

@Mikael-Lovqvist
Copy link
Author

I think there is a certain completeness if the API used in the sample supports all four ways (top/bottom, bottom/top, left/right and right/left) but ultimately someone from this project will have to make a decision. To just fix it by changing the image feels slightly wrong to me in case you for whatever reason want to break "normal convention" (if there even is such a thing). Just my two cents!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants