[4.5.1] r.setres not working properly

Hi,

The console command r.setres seems not very reliable.

This happens when used from c++ or when entered by hand in the console.

The size is handled correctly (and the f/w option) but the resolution is not updated all the time.sometimes it works, sometimes no, and the windowed option seems more reliable than the fullscreen option. So i often find myself changing first the resolution in w mode (r.setres 1920x1080w) and then go for full screen (r.setres 1920x1080f).

I have seen similar problems in older posts but they are from previous versions of the engine, i am running 4.5.1 currently.

Cedric

Hello uced,

I have attempted to reproduce what you were talking about and I guess I am having some trouble understanding the steps you are taking. I have my own project open, which is using the ThirdPerson BP template, and brought up the console command while playing in a new window.

I typed the "r.setRes 1920x1080w which draws the screen to occupy the entire screen in windowed mode. I also tried 800x600w which set the window mode to that resolution and resized my window. As for the fullscreen mode I used the “F11” key while playing in the viewport. I tried typing the “r.setRes 1920x1080f” while in windowed and it did nothing. Is this what you are talking about?

Thanks,

Hi Andrew,

Sorry i haven’t been clear. I have a different behavior than yours.

On my computer, the F11 key only works during editor time. It does nothing during runtime.

Here is a scenario to try my problem:

  • Launch a standalone game (or a packaged game)

  • type in the console: r.SetRes 640x480w: it works well, the window becomes very small

  • now type: r.SetRes 1920x1080f: you go full screen, but the resolution remains 640x480, resulting in a blurry and pixelated screen

It looks like the f option, while triggering the fullscreen mode, prevent the change of resolution.

Hope this make things clearer.

Thanks

Cedric

Thank you for the clarification. I have since attempted to reproduce your issue and with no luck. This might be hardware or driver specific so would you mind sending me your dxdiag so I can further investigate?

Sure, here it islink text

Thank you. Quick question, what version of the engine are you using?

I am testing your issue in 4.5.1.

Same for me: 4.5.1

I have since updated my nvidia drivers (new dxdiag enclosed) but it made no difference, i still have the problem.

link text

Hello again Uced,

I have made the developers aware that this is still an issue as of recent build, and have created a new bug report so it can be addressed. I appreciate your patience with this matter as well as the documentation you provided in order for us to fix this issue.

Thanks again,

Hi Uced,

Various fixes have gone in for the resolution switching system, some of which I believe will be in the 4.6 release. With our latest code here, I can’t reproduce any of the behaviour you describe above, so hopefully it’ll all be fixed when these changes make their way to you!

Thanks,

Graeme

Hi Graeme,

Thanks a lot for the info, can’t wait for 4.6 :slight_smile:

Cedric

Hi,

Unfortunately the problem is still there in 4.6 (preview).

Here are two shots, in the first one you can see my history: i set a 800x600w windowed mode, and from that i go for a 1920x1080f.

The second shot (right after i hit enter) shows that my screen goes in full screen but still maintains a 800x600 resolution.

I’m using 4.14 and I found that r.setres sometimes not responding.

Please create a new post so we can address it there with steps and screenshots where appropriate. This post is outdated, so for tracking purposes, we would like a new post be made using the engine version you mention.

Thanks,

For me it’s not working. Maybe because the console is locked ? I tried it from the game shortcut and it always goes into 1080p instead of 1440p.