Ultrawide (3440x1440) problems

[Pong [Linux]]

Since I upgraded from a FullHD to an 34" Ultrawide Monitor, several games have problems. Sometimes keys don't seem to work, sometimes graphics are corrupt und sometimes F12 (screenshot) makes steam freezing!

Are these known problems and why does Steam freeze often on screenshot key F12? This never happened with my old monitor (nothing changed on computer, i.e. same OS, same video driver, etc. - just swapped the screen.

[Pong [Linux]]

Yes, in preparation for the monitor I bought an RX460 that can handle 4K resolution - about 2 months ago. And it worked flawlessly with the old monitor. The strange thing about those key problems is, that they occur only in some games (that worked without problems with the old monitor). Other games have no problems with keys and F12 work well with them.

[ɣ𝖆𝖍˛𝖔٥ˀ𝖊ю҉]

-=-

[Snapjak]

An RX 460 is not an ultrawide gaming gpu. It's a budget card that can "do" ultrawide on the desktop but will very severely struggle with remotely demanding games.

You have more than doubled the number of pixels that need to be rendered.
2,073,600 vs 4,953,600

[Pong [Linux]]

Hello? I don't care about the performance of the card - it's even better with the Widescreen than previously my internal AMD APU Kaveri on FullHD. But this is irrelevant as I have problems with the keys - not with performance.

[cSg|mc-Hotsauce]

please post here... http://steamcommunity.com/discussions/forum/11/

[Snapjak]

Wurzelzweig Linux님이 먼저 게시:

Hello? I don't care about the performance of the card - it's even better with the Widescreen than previously my internal AMD APU Kaveri on FullHD. But this is irrelevant as I have problems with the keys - not with performance.

Wurzelzweig Linux님이 먼저 게시:

Sometimes keys don't seem to work, sometimes graphics are corrupt und sometimes F12 (screenshot) makes steam freezing!

Two of these point to the 460 either being bad or just not up to the task. If it's always in game, then it all could point to the 460 not being enough, or just bad.

But firstly, did you uninstall and reinstall your graphics drivers.

[Pong [Linux]]

You don't get it: it only occurs on some games - other games work flawlessly - e.g. demanding Tomb Raider works great with all keys and F12 screenshots. Other like Dirt Rally have problems with keys.

[Pong [Linux]]

This NOT ABOUT PERFORMANCE. It's just that some games have problems with keys - especially F12 (screenshot).

[Pong [Linux]]

Well I had 2 games that had some polygon flickering. But people, forget it. I found it out myself: launching those problematic games with the option "-opengl" fixes the problem - also with F12 key. So, this seems to be a driver problem (already using the lates AMDGPU-PRO 16.60) probably with vulcan (no idea).

[Snapjak]

Wurzelzweig Linux님이 먼저 게시:

Well I had 2 games that had some polygon flickering. But people, forget it. I found it out myself: launching those problematic games with the option "-opengl" fixes the problem - also with F12 key. So, this seems to be a driver problem (already using the lates AMDGPU-PRO 16.60) probably with vulcan (no idea). :seriouspewpew:

Which is why...

Snapjak님이 먼저 게시:

But firstly, did you uninstall and reinstall your graphics drivers.

I said that...

[Pong [Linux]]

I didn't reinstall the drivers - I just set "-opengl" in the game properties of Steam.

[Snapjak]

Right. I thought not. Whenever you change graphics cards, you should DDU the old drivers and install new ones. Even if it's the exact same driver or the same generation of card or same AMD/Intel.

[Pong [Linux]]

Okay: when I bought the graphics card, I installed the AMDGPU-PRO drivers because the old (open source) drivers didn't support hardware acceleration with this card. So, after mounting the new card, I installed the drivers.

[Snapjak]

Oh it's a linux driver issue? Should post in the linux section and get proper help.

Otherwise you fixed it and hopefully new OS drivers come out that do support the 4xx series.

[Berzerk]

Never had issues with it