User couldn’t change the resolution in the options, the list was empty. He was able to change it only through modification of settings files. The resolution is supported, but he couldn’t change it in-game. Most users had a UHD resolution.
Methods Get Convenient Windowed Resolutions and Get Supported Fullscreen Resolutions return empty list.
Hello PixelMate,
I’ll need more information to be able to determine what is causing this to occur. Have you been able to reproduce this locally? What resolutions does the user’s monitor support? Is it a 4:3, 16:9, or 16:10 monitor? There seem to be a few references to Oculus in the logs, is VR involved in this at all? Have you had these users who were at a 4k resolution use a lower resolution to see if the problem persists?
Thank you for that information,
I tried reproducing this same issue on a TV that supports 4k but I’m not seeing the same results. You can see the resolutions I had returned in the attached picture. The Convenient Windowed Resolutions seems to vary with the UI scaling set in Windows 10 if that is being used, but the Get Supported Fullscreen Resolutions list seems fully featured.
From taking another look at the log, it seems that IDXGISwapChain::SetFullscreenState is what is returning null, not the resolutions lists. When you say that they “Can’t change it in game” is it because the numbers just aren’t being listed for them to click on or is it that clicking these numbers doesn’t change it?
The numbers are not listed. But it can be changed through configuration files.
Could you explain your method that you’re using to get these values and display them to the screen then? Could you also get dxdiag information from these users? Would it be possible to push out a version to them that includes some extra logging that outputs these lists as I have?
The method I used was as follows so I’m not convinced that it’s these arrays that aren’t being populated.
I’m going to need to get a reproduction of this before I can do anything related to reporting/fixing this issue.
We used the same method in test build. Fullscreen resolutions was empty. And convinient gave only
[2017.01.19-17.29.46:318][113]LogBlueprintUserMessages: [TestActor_120] Convenient windowed resolution: 1066x600!
We will ask the user for a DxDiag.
Was this a local reproduction or was this from the user again? Also can you provide the full log for that instance?
We made this when the problem first appeared, we sent a small app with this bp to get the logs ( you can see the log in the question). We already used practically the same loggin bp you proposed ourselves.
Hello PixelMate, is your user still experiencing this issue? Were you able to get the dxdiag information from them?
Hello, the user plugged in a monitor with standard resolution, but still had problems with the resolution, the work around with changing the resolution in config files works for him, so he didn’t want to do anything else.
Ah, well it seems like it may of been due to something else on his system. If you get any more reports of this from other users and can get some more information, I’ll be happy to look into it. In the meantime I’ll be marking this as resolved with your comment as the answer.
