madshi bug tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000477madVRbugpublic2017-04-18 21:502018-01-21 21:36
Assigned Tomadshi 
StatusclosedResolutionnot fixable 
PlatformOSWindowsOS Version10 x64
Summary0000477: Switching display modes with madVR ignores custom res/refresh rate
DescriptionWhen using madVR to automatically change the display mode, it seems to switch to the default Nvidia profiles and ignores the custom resolution/refresh rate I set via the Nvidia Control Panel.
Steps To Reproduce1. Create custom refresh rate with a refresh rate of 23.976 and resolution of 1920x1080 with the Nvidia control panel.
2. Add it to the madVR display modes for automatic switching
3. Launch a video, CTRL+J shows it is still running at ~23.970 and ignoring the new resolution made.
TagsNo tags attached.
madVR Version0.91.8
Media Player (with version info)MPC-HC 1.7.11 x86
Splitter (with version info)LAV Splitter 0.69.0
Decoder (with version info)LAV Video Decoder 0.69.0
Deinterlacingauto mode
DXVA2 Scaling Activeno
Aero / Desktop CompositionOn
Problem occurs with modeall modes
GPU ManufacturerNVidia
GPU ModelGTX 1080
GPU Driver Version381.65
Attached Files

- Relationships

-  Notes
3S5U (reporter)
2017-04-18 22:37

Just to add: it seems like this issue is only present when using DX11. It switches to the proper refresh rate in DX9.
madshi (administrator)
2017-04-18 23:24

I'm not sure if there's much I can do about this. In D3D11 I can't just request e.g. 23p or 24p. I have to request 24000/1001 or 24000/1000, and maybe the driver skips the custom resolutions in that situation? I'm not really sure, though. I'll have a look at that later, when I find some time.
3S5U (reporter)
2017-04-20 00:07

No prob. Thanks for looking into it, it's much appreciated. I've switched back to D3D9 in the meantime and haven't noticed much difference to be honest.
madshi (administrator)
2018-01-21 21:36

In the latest Windows 10 Fall Creator's Update version, Microsoft fixed some bugs in the refresh rate switching. Maybe the problem is solved now. Make sure you have the "hack Direct3D to make 24.000Hz and 60.000Hz work" option unchecked in madVR.

If the problem is still not solved, then there's really nothing I can do about it. So I'm closing this bug report, because ultimately it's the GPU driver or the OS which decides these things, so it's out of my hands.

- Issue History
Date Modified Username Field Change
2017-04-18 21:50 3S5U New Issue
2017-04-18 22:37 3S5U Note Added: 0001632
2017-04-18 23:24 madshi Note Added: 0001633
2017-04-18 23:24 madshi Assigned To => madshi
2017-04-18 23:24 madshi Status new => assigned
2017-04-20 00:07 3S5U Note Added: 0001634
2018-01-21 21:36 madshi Note Added: 0002199
2018-01-21 21:36 madshi Status assigned => closed
2018-01-21 21:36 madshi Resolution open => not fixable

Copyright © 2000 - 2012 MantisBT Group
Powered by Mantis Bugtracker