View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000706||madVR||bug||public||2023-06-05 21:17||2023-06-10 12:11|
|OS||Windows 11 prerelease (dev)||OS Version||2305226-1341|
|Summary||0000706: Display mode switching completely broken|
|Description||Feature has no effect. |
|Steps To Reproduce||Set display modes, go fullscreen.|
It doesn't matter if it's exclusive or non exclusive fullscreen.
Does it on both monitors I have, 1 DP and 1 HDMI.
|Additional Information||Also, everytime I start MPC HC, the connected displays get a new "identification" tab|
|Tags||No tags attached.|
|Media Player (with version info)||MPC-HC (64-bit) 2.0.0 (973b644a3) MSVC v19.29.30147 Jan 11 2023|
|Splitter (with version info)||LAV Splitter 0.77.1.1-git|
|Decoder (with version info)||LAV Decoder 0.77.1.1-git|
|DXVA2 Scaling Active||no|
|Aero / Desktop Composition||On|
|Problem occurs with mode||all modes|
|GPU Model||2070 Super|
|GPU Driver Version||Studio 535.98|
I agree this area is broken. For me, I think combining SVP4 (that wants to change the video to match the current screen refresh rate) and madVR's custom modes is partially the problem.
I've never managed to trigger a mode change from madVR, other than when editing or testing modes on the custom tab. No matter how I tried to adjust my player (MPC-HC x64) or display method (windowed or full screen or attempting exclusive full screen), nor "display modes" tab options I changed.
I'd initially added custom modes for any frequency I thought might be useful. Then listed many of those modes manually. And tried to trigger mode changes at playback time. Never happened.
Also with long display modes lists I think a long string of text is a bad experience for the user (it's a hack to allow export/import, right?). Meaning why isn't there just a check box next to each custom mode that you enable/disable with instead? Then they just add any mode they want to allow to the list, and enable it.
That's all on top of the confusing and annoying "optimize" process. That I can't edit the current mode, and that if I change a setting for X hz, test it fine, then save it... I often end up with an "active" mode that's X-1 or X+1. I realize it's rounding and I'm guessing Windows cared about those values once. Now it just lists refresh rates down to 3 decimal places like "74.860 Hz"
Maybe the NVIDIA API is the issue there instead? Either way... You should hide the confusion from users. I doubt that is a new issue, but I wanted to explain more of my annoyance with this area (beyond just it never seems to activate or do anything).
In case my environment matters... Acer BE270U using DP cable 1440p@75hz native screen, NVIDIA 1080 ti x 2 (currently... the 2nd card doesn't do much for me though so I've run with 1 before and saw the same results), latest Windows 10 x64 + NVIDIA gaming drivers + SVP4 + "AviSynth+" + AviSynthFilter (not ffdshow) + "old cuda" hwdec mode in LAV Filters. Intel i7-4790k at stock, 32GB RAM, z97 motherboard.
If I was going to fix this, I'd want more automation in the testing and matching process. And personally I don't care the precise frequency results. I just wanted less extra work and changing of things if they don't need to be. To remove up/down sampling, yet fully use my hardware (use highest "good enough" and matching refresh rate). Seems more communication between the player and you might help here.
Though maybe my situation/goal is very unusual? That this won't help or be wanted by most. I can't say... Though I wish this was open source so I could see where the problem is, and maybe offer a fix.