#8908 (Bug) DisplayCal Profile Loader 3.3.4 MadVR detection

+1 0

Closed as Not A Bug
Component: 3.3.4
Created by mbze430

Last modified


I have noticed that after upgrading to 3.3.4 the Profile Loader DOES NOT detect MadVR properly anymore.  Using KODI+DSPLAYER+MADVR in 3.3.3 automatically disabled the ICC profiles.  Same with PotPlayer+MadVR.


8 comments on “DisplayCal Profile Loader 3.3.4 MadVR detection”

  1. Just to add, this happens on my Titan XP SLI computer.  Using Windows 10 build 16288.1 RS3

    I have Surface Pro 3 running Windows 10 16288.1 RS3 and it seems to detect MadVR fine.

     

    I have already using DDU to uninstall the Nvidia Drivers, but it still doesn’t detect MadVR as good as 3.3.3 was.  Also note I have a TV and a monitor on the Titan Xp SLI computer

  2. This is the system that is having problem detecting MadVR:

    System with problem detecting MadVR

     

    This is my Surface Pro 3 that is NOT having problem detecting MadVR:

    Surface Pro 3

    1. Disable either windowed overlay or Direct3D 11 (these options cannot be used together anyway, and normally D3D11 should override windowed overlay).

    1. The profile loader is not supposed to reset the gamma table. This is what madVR does if you use a 3D LUT with calibration applied to the 3D LUT itself.

Comments are closed.