Stuck playing at main monitor resolution
I have a secondary monitor of 2560x1440, my main monitor is 1920x1200. I can only get 2560x1440 resolution of my main monitor is my secondary monitor. Oddly enough I can get 2560x1440 when I go into window mode.
Steps to reproduce:
- Main monitor 1920x1200
- Secondary monitor of 2560x1440
- launch game
- go into window mode
- move game to better resolution monitor
- go back into full screen mode
resolution would now be allowed to go to 2560x1440
resolution is only allowed to go to 1920x1080
I do not have any notes beyond this.
Attachments: N/A
I don’t know the game version I’m thinking this means Windows 10
System Information:
OS Name | Microsoft Windows 10 Pro |
---|---|
Version | 10.0.18362 Build 18362 |
Other OS Description | Not Available |
OS Manufacturer | Microsoft Corporation |
System Name | ******* |
System Manufacturer | System manufacturer |
System Model | System Product Name |
System Type | x64-based PC |
System SKU | ASUS_MB_CNL |
Processor | Intel® Core™ i7-9700K CPU @ 3.60GHz, 3600 Mhz, 8 Core(s), 8 Logical Processor(s) |
BIOS Version/Date | American Megatrends Inc. 1105, 6/6/2019 |
SMBIOS Version | 3.2 |
Embedded Controller Version | 255.255 |
BIOS Mode | Legacy |
BaseBoard Manufacturer | ASUSTeK COMPUTER INC. |
BaseBoard Product | ROG STRIX Z390-E GAMING |
BaseBoard Version | Rev 1.xx |
Platform Role | Desktop |
Secure Boot State | Unsupported |
PCR7 Configuration | Binding Not Possible |
Windows Directory | C:\WINDOWS |
System Directory | C:\WINDOWS\system32 |
Boot Device | \Device\HarddiskVolume4 |
Locale | United States |
Hardware Abstraction Layer | Version = “10.0.18362.752” |
User Name | Dragon-PC\Dragon |
Time Zone | Eastern Daylight Time |
Installed Physical Memory (RAM) | 32.0 GB |
Total Physical Memory | 31.9 GB |
Available Physical Memory | 25.3 GB |
Total Virtual Memory | 63.9 GB |
Available Virtual Memory | 51.1 GB |
Page File Space | 32.0 GB |
Page File | C:\pagefile.sys |
Kernel DMA Protection | Off |
Virtualization-based security | Not enabled |
Device Encryption Support | Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not Modern Standby, Un-allowed DMA capable bus/device(s) detected, Disabled by policy, TPM is not usable |
Hyper-V - VM Monitor Mode Extensions | Yes |
Hyper-V - Second Level Address Translation Extensions | Yes |
Hyper-V - Virtualization Enabled in Firmware | No |
Hyper-V - Data Execution Protection | Yes |