2016-01-28, 16:49
Ok, some progress from further testing!
So by changing the 3D type in the OSD to SBS, and restarting the file, it switches to hardware based 3D ok.
With the 3D type in OSD back to Auto, and by adding .sbs to filename (so avatar.3d.sbs), it switches to hardware based 3D ok.
However with 3D type in OSD set to auto, and having only .3d in filename (so avatar.3d), it doesn't switch to hardware based, and instead switches to 4k 3840x2160.
When testing previously, i've only ever used .3d in the filename as the 3D flag (no .sbs), so maybe an issue with auto detecting the 3D type with just the .3d flag?
I can upload some debug logs if it's help, just let me know what circumstances you'd like me to test and log. That was all tested in Jarvis RC1 by the way.
Many thanks
So by changing the 3D type in the OSD to SBS, and restarting the file, it switches to hardware based 3D ok.
With the 3D type in OSD back to Auto, and by adding .sbs to filename (so avatar.3d.sbs), it switches to hardware based 3D ok.
However with 3D type in OSD set to auto, and having only .3d in filename (so avatar.3d), it doesn't switch to hardware based, and instead switches to 4k 3840x2160.
When testing previously, i've only ever used .3d in the filename as the 3D flag (no .sbs), so maybe an issue with auto detecting the 3D type with just the .3d flag?
I can upload some debug logs if it's help, just let me know what circumstances you'd like me to test and log. That was all tested in Jarvis RC1 by the way.
Many thanks
