I've been using W10 and this method since the day it was released. What do you mean by "I don't see the same options"? Same as what? I can only assure you, this method and W10 indeed work perfectly for me or the guide would not be here.
I was told madVR controls stereoscopic ON/OFF and no further scripts would be necessary. In my testing, I found madVR only controls stereoscopic at O/S level. It does not control stereoscopic at driver level in my testing (which is also crucial). I was then told a script could be launched from madVR instead of the KODI playercorefactory.xml to control stereoscopic additionally at driver level. This was the script Warner and Manni often refer to. While this script controls at driver level by editing registry settings, it seems rather complicated to simply turn 3D OFF/ON. I assume this is because it was created for JRiver users, not KODI users who can launch from a playercorefactory.xml unlike other front ends, thus its need for advanced code and flexibility it offers.
I created a simple 3D Enable.bat and a 3D Disable.bat to test madVR's script launching and left it at that. That is what's referenced in the pictures. It doesn't matter if they remain or are removed thus why I see no need to include them in this guide. I need more functionality. Indeed madVR launches the scripts and they work. These files would be sufficient for exclusive .mkv users but not for iso users since iso's additionally need to be mounted. The method guided here is for diverse collections that have a mix of anything and not just mkv's exclusively. So, the code here needs to be more involved to include mounting and stereoscopic controls as well as other actions. These involved codes cannot be launched from madVR like the two simple 3D Enable/Disable scripts. The involved codes need to be sorted and assigned based on content which is defined by 'Rules' in the playercorefactory.xml. (Player assignment, virtual ROMS, 3rd party .exe, 3D control, file type and name sorting for example) MadVR cannot assign like the playercorefactory can. However, it can control one player and one simple rule such as 'is the file 3D or not?' which is partly why a couple Enable/Disable 3D scripts would suffice a single player, single file type (mkv) user.
Here is the 3D Enable.bat code:
@
echo OFF
"C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvstlink.exe" /enable
EXIT
and the 3D Disable.bat code:
@
echo OFF
"C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvstlink.exe" /disable
EXIT
Perhaps they are of some use to you and you can avoid the additional scripts as you deem worthy.
As stated elsewhere, you only use one player for everything. You stated you only use one file type, mkv's. I doubt you would find any benefit using the methods here for your simple requirements. This isn't to say it will not work for you. You can read the thread and find similar users who had code tailored for them that should apply to you as well. You've determined the method here is only ample for player selection, iso usage and too complicated to be 3D.mkv friendly besides stating it doesn't work. Perhaps another method would be best for you. This guide is not going to change to only satisfy mkv users. That's what partly makes this guide unique. Keep in mind, driver level stereoscopic still needs to be controlled and what you consider not useful and too complex applies to simple mkv users as well. I will say I have a few 3D.mkv's TAB and SBS along with iso's. I can assign playback through capable players (automated or manually) and 3D mode switches on/off on demand as well as corresponding resolution and refresh rate switching with zero intervention or complications. Your faux k PJ may behave differently and be better served by another method although your help requests elsewhere suggested alternate methods were not working either.
If you'd like to pursue the method here, provide your playercorefactory.xml and any related bat files along with pertinent madVR settings as well as NCP stereoscopic switch position during playback. Maybe there is something obvious preventing you from perfect playback that can be diagnosed. I need to know exactly what you are telling software to do, how you go about it, and how your hardware responds. The more details, the better. Other than that, your particular PJ may be hampering you above and beyond what any software and code should do for you but that hasn't been determined imo.
