dxvk icon indicating copy to clipboard operation
dxvk copied to clipboard

Anomaly Warzone Earth aspect or resolution issue

Open Blisto91 opened this issue 3 years ago • 1 comments

Ever since commit https://github.com/doitsujin/dxvk/commit/dac7e38f4b1de439268ba28a66e11f39ba3a99dd when i start the game the screen will be missing a part of the top and bottom view.

The log file makes it appear as if it is started in resolution 1920x800, but the ingame resolution is actually set to 1920x1080. This also makes it so the cursor is offset compared to when the game thinks you are hovering over a button and i have to aim higher in the main menu. The image corrects itself i if alt tab out and in, but if you do it too quickly then you can't press any buttons with the mouse. If you alt tab out and then wait until you can hear the games music have faded away before going back in you can get both correct resolution and working buttons. Edit: Actually the issue with the mouse buttons not working if you alt tab out and in too quickly might not be a dxvk issue as that also happens with wined3d

Note that before https://github.com/doitsujin/dxvk/commit/ecc230238913d2599db276573d7590ed4a898524 the game had a issue where it will freeze in the main menu. But the issue above can be observed already at the intro videos.

Screenshot Notice the top and button black bars and cursor highlight offset

Screenshot_20221108_214151

Software information

Anomaly Warzone Earth

System information

  • GPU: R9 380
  • Driver: couple of weeks old mesa git
  • Wine version: Proton Experimental & bleeding edge
  • DXVK version: https://github.com/doitsujin/dxvk/commit/dac7e38f4b1de439268ba28a66e11f39ba3a99dd
  • DE: KDE Plasma Wayland

Apitrace file(s)

Apitrace pending...

Log files

AnomalyWarzoneEarth_d3d9.log

In this log i get to main menu and then alt tab out and in before pressing ALT F4. I think info: Setting display mode: 1920x800@60 is the first line of interest here. info: Setting display mode: 1920x1080@60 later down is when i alt tab i think.

Blisto91 avatar Nov 08 '22 20:11 Blisto91

Can you post a log file of the earlier commit that didnt have the issue?

K0bin avatar Nov 12 '22 13:11 K0bin