@
damagedspline :
I am just wasting my time to first resolve
this problem. Without being able to get software player setting to work, i don't think i will get the 3D to work correctly. Its crazy. I just did a fresh windows 10 install with WinToGo USB stick, and i still see this software rendering issue on my AMD. When i had 18.2mvc running, i could only get libmfxsw64 to run when i selected software decode in the player, otherwise it would not be used.
Yes, i could not reproduce the ability to decode MVC correctly without libmfxsw64.dll installed. My mistake during testing was to use SBS output (because there is the core problem of that maybe not working on AMD because of OS-release and/or AMD driver), but then i didn't check with glasses whether there where really two pictures. Your suggestion for 'o' from prior post to diagnose was very helpful. and when i set my projector to sbs i could also see that what looked like 3D was just duplicate of a single eye.
Yes, i had to download libmfx, newer versions from intels site (Media SDK) after registering *sigh*. Annoying thing is that that site doesn't even allow to download when i am not on an intel windows system (aka: couldn't download directly from my AMD system). Had to use an Intel CPU system.
The storage of MVC on BluRay is a single SSIF file where the two set of frames, H264 for left eye and MVC for right eye are interleaved. The m2ts files then include in their UDF file-system structure only the sectors for their own eye, aka: left-eye m2ts is just the left-eye H264 sectors, so it is compatible with non-3D blu ray playback. Right eye m2ts is only the MVC sectors for the right eye. This is why a file-by-file backup tool like MakeMKV can not give you a good 1:1 copy, because you'd end up with a BD copy that has the left and right eyes non-interleaved, and if you try to play that back on a BD drive, then you will kill the head moving back and forth. Probably won't be fast enough to play back at all.
I am still curious as to which number your MFX version parameter relates to. There are various versions of libmfx, whose numbers i guess relate to the media SDK release. Is your config number some SDK API version, and if so, do you have an idea whether that is also included in the Media SDK / libmfx version number ? That would help to set the parameter right for the libmfxsw64.dll that one has installed.