Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[d3d11] Vindictus: Wrong Aspect Ratio in Multiple Screens Setup #3975

Open
kin-patsu opened this issue Apr 28, 2024 · 1 comment
Open

[d3d11] Vindictus: Wrong Aspect Ratio in Multiple Screens Setup #3975

kin-patsu opened this issue Apr 28, 2024 · 1 comment

Comments

@kin-patsu
Copy link

kin-patsu commented Apr 28, 2024

When playing Vindictus in DirecX 11 mode in a setup with more than one screen, if one of those is connected through DisplayPort and the second one through HDMI then the aspect ratio of only the DisplayPort screen will be used, regardless of which screen is being used as the main one.

In my case, my main screen is 16:9 connected through HDMI, with another side monitor, also 16:9, used vertically and connected through DisplayPort. This causes Vindictus to default its resolution to windowed 1024x768 when started with dxvk, and to only show vertical resolutions when choosing a custom one, as shown here:
image
It's worth noting that this doesn't happen when playing in DirectX 9 mode.

Software information

System information

  • GPU: NVIDIA GeForce RTX 4090
  • Driver: 552.12
  • Wine/Proton Version: NA (Windows)
  • DXVK version: v2.3.1

Apitrace file(s)

Log files

No Proton or Wine log, being on Windows, however I can provide the dxvk log:

@doitsujin
Copy link
Owner

doitsujin commented Apr 29, 2024

We currently don't really support rotated displays, in part because I have no idea how DXGI reports display modes for them and whether or not apps have to be aware of the rotation.

I'm also not sure what the expectation here is though, the game is not aware of multi-monitor setups and only queries display 0, and I don't know if changing the "main" display at an OS level has any effect at all on the way EnumDisplayMonitors / EnumDisplaySettings report things.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants