[Warner306]

You have enable refresh rate switching in madVR or MPC (I would recommend madVR). Kodi's internal refresh rate controls do not affect MPC.

[Eddie Strike]

You have enable refresh rate switching in madVR or MPC (I would recommend madVR). Kodi's internal refresh rate controls do not affect MPC.

 I have madVR set up doing the switching, and it works great, but only if I manually load the movie.

Kodi will switch it to 24hz, then instantly back to 60hz before playing the movie in 60p.

[Warner306]

Hmm, that sounds odd. I wonder if this is a new bug introduced by Kodi? What version of Kodi are you using? The last time I tried this method was Jarvis. 

Try turning off Kodi refresh rate switching to see if that is to blame.

[fullsun]

there are a fix for playerfactory, if you don't it Kodi keep the hand and also can crash if you have disable the fullscreen window:
<hidexbmc>true</hidexbmc>

no issue after MPC close, Kodi back.

[Warner306]

there are a fix for playerfactory, if you don't it Kodi keep the hand and also can crash if you have disable the fullscreen window:
<hidexbmc>true</hidexbmc>

no issue after MPC close, Kodi back.

 Should only be an issue if you use Kodi in fullscreen rather than a fullscreen window. Most users should use a window if using external players for a more seamless integration.

[fullsun]

disable all settings targeting the display or just put this value.

And xysubfilter is good with MadVR but don't support 10bit, for HDR 10bit there are no subtitle or crash.

[Warner306]

disable all settings targeting the display or just put this value.

And xysubfilter is good with MadVR but don't support 10bit, for HDR 10bit there are no subtitle or crash.

I wonder about XYSubFilter. I asked DSPlayer users and they are having no problems. DSPlayer uses XYSubFilter.

Are these external subtitles?

[neo2018]

I followed the instructions on this topic, but although MPC-BE opens correctly, it displays a warning "Cannot render the file".
If i use the MPC-BE window, and select "Open File", the file plays correctly.

I'm using:
- Kodi 18.0 ALPHA1
- Windows 10 Professional
- MPC-BE 
- Files on an external NAS server, accessible by NFS.

playercorefactory.xml:

xml:
<?xml version="1.0" encoding="UTF-8"?>

<playercorefactory>

   <players>

      <player name="MPC-BE" type="ExternalPlayer" audio="false" video="true">

         <filename>C:\Program Files\MPC-BE x64\mpc-be64.exe</filename>

         <args>"{1}" /fullscreen /close</args>

         <hidexbmc>false</hidexbmc>

         <hideconsole>false</hideconsole>

         <warpcursor>none</warpcursor>

         <playcountminimumtime>1140</playcountminimumtime>

      </player>

   </players>

    <rules action="prepend">

        <rule filetypes="mkv|mp4|avi|divx|mpg|wmv|flv|ts" player="MPC-BE">

        </rule>

    </rules>    

</playercorefactory>

I tried to check the Kodi logs, but couldn't found anything.

Anyone knows what could be the problem?

[brazen1]

What is the file extension?

[neo2018]

Its a .mkv file (and it happened with all .mkv's i tried).

[neo2018]

This is the error i'm getting:

[brazen1]

Your NAS is most likely streaming ok since you can open the file via Explorer but try copying the file local and see if it opens correctly.
Right click the mkv file and select open with MPC-BE instead of using MPC-BE 'open file'.
If this works, imo KODI v.18 is at fault.

"failed to render file" usually means the external player simply fails to read it.  In my case, I see this when trying to play full rip iso's before automating a mount via scripts.  I have seen one other post that MPC players do not need to mount an iso before they can play it but I don't see how this could be possible.  This is why I ask to check the NAS stream because failed to render sounds like MPC just doesn't see the file.  This could be a miscommunication from KODI and the playercorefactory though?

 I have been trying v.18 for some time now including todays latest nightly.  While I can open a file with an external player launched from KODI, no amount of selecting WHICH external player obeys the playercorefactory or the KODI 'open with' menu performs.  Reverting to v.17.6 all is well.  You might give the revert a try as it should perform as expected until a Windows developer joins the KODI team and desires to tackle playercorefactory.xml and external player hurdles.

[neo2018]

^^
Thank you for your help, i'm going to try this, and will report back as soon as possible.

[Warner306]

^^
Thank you for your help, i'm going to try this, and will report back as soon as possible.

I think the file system you are using is to blame. It may not be compatible with external players and Kodi.

To check, copy a file locally and add it as a source in Kodi. Play it through MPC-BE. It shouldn't produce the same error.

If that doesn't fix it, try reverting to 17.6. I'm sure external players will eventually be addressed in v18 but not until the internal player is working correctly and the bugs have been addressed in the new 64-bit build. Team Kodi will have to help Windows this year to address bugs if they want to release a Beta.

[neo2018]

^^ 
I've made a quick test with 17.6 using NFS, and i got the same error.

I then mapped the NAS on Windows, and it worked.

I've always used NFS in the past (Oppo 203, Mede8er 600x, Zidoo X8) as it was fast than Samba.
Anyone has any ideia on the performance on NFS vs Windows Mapped driver?