Incorrect handling of full 3D side by side (3840x1080) or top and bottom (1920x2160) videos

[kiralema]

Configuration

Wolvic version: 1.7.1
Wolvic build ID: versionCode 1993652300

Hardware: Meta Quest 3 512Gb

Steps to Reproduce

1. Start playing any full SBS (side-by-side, 3840x1080, 1920x1080 per eye) or full TAB (top-and-bottom, 1920x2160, 1920x1080 per eye) 3D video, such as from Youtube or from a local video file;
2. Open the video in full screen, and choose 3D side by side or 3D top bottom option from the small menu below the main screen depending on the format of the video;
   
3. 3D video gets stretched twice either horizontally or vertically depending on the original 3D layout.
   

Current Behavior

In 3D side by side mode, video gets stretched horizontally twice its normal size. In 3D top bottom mode, video gets stretched vertically twice its normal size.

Expected Behavior

In 3D side by side mode, full 3D SBS should appear normally as 1920x1080 without stretching horizontally. In 3D top bottom mode, full 3D TAB should appear normally as 1920x1080 without stretching vertically.

Possible Solution

It seems, as of current, only half SBS (1920x1080, or 960x1080 per eye) or half TAB (1920x1080, or 1920x540 per eye) modes are supported. Perhaps, two 3D modes, 3D full side by side and full 3D top bottom could be offered in the 3D menu in addition to the existing ones.

Context

I was trying to watch 3D video media in full 1080p resolution (1920x1080 per eye), but the videos get stretched twice horizontally or vertically so viewing becomes impractical.

Error Logs and Stack Traces

[svillar]

Thanks for the report. I can confirm the bug is indeed there. For reference this video from the report is a good example of the stretching happening.

[svillar]

@felipeerias I think we regressed this with the changes we recently added to the fullscreen window size

[kiralema]

Thank you for your reply. That is unfortunate. Hopefully, there will be a solution soon. Perhaps, providing a flexible way to change the aspect ratio of the fullscreen window size could be another way to solve the issue.

@felipeerias I think we regressed this with the changes we recently added to the fullscreen window size