-
Notifications
You must be signed in to change notification settings - Fork 776
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
Comments
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. |
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](https://private-user-images.githubusercontent.com/19828171/326291679-057629dd-c8ea-442e-aafc-ccd0e637ceb5.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTgzNTI0MDYsIm5iZiI6MTcxODM1MjEwNiwicGF0aCI6Ii8xOTgyODE3MS8zMjYyOTE2NzktMDU3NjI5ZGQtYzhlYS00NDJlLWFhZmMtY2NkMGU2MzdjZWI1LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA2MTQlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNjE0VDA4MDE0NlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWE0YTk4YWVlYzQ0NmI1NjI0NzI1OTEyNmVkNTBiZGJkOGVhYjI3ZTAxZTY5Yzc4ZTViODhlMjE1M2Q2YjU0YWYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.gSNR5vc3gqrR0r8ltT-MAzeVpcCWZP4rsyQzltyo904)
It's worth noting that this doesn't happen when playing in DirectX 9 mode.
Software information
System information
Apitrace file(s)
Log files
No Proton or Wine log, being on Windows, however I can provide the dxvk log:
The text was updated successfully, but these errors were encountered: