December 18, 20205 yr With most games, when you switch from full screen to windowed mode, the window will be resized accordingly to the resolution that you have chosen. I play on a native 4K display. For example, when I play Battlefield V in full screen and then change my resolution down to 2560x1440 and select 'windowed mode'. The game will switch to window mode and set it to the proper size and I won't be able to drag the corners to resize the game window. That's how it's meant to be. But in MSFS when I switch from a full screen 4K mode to a windowed 2560x1440 mode, the window takes about 85% of my screen, and I am able to drag the corners to resize it down. It should automatically resize the window to 2560x1440 and not let me be able to resize the window by dragging the corners. Why is this??? This is extremely frustrating because I expect the window to be sized exactly at 2560x1440. By me having to manually drag and resize, I'm not even sure if my resolution is exact or not and the proportion can go out of whack if I'm not eyeballing it correctly. Edited December 18, 20205 yr by captain420 ASUS ROG Maximus Hero XII ▪︎ Intel i9-10900K ▪︎ NVIDIA RTX 3090 FE ▪︎ 64GB Corsair Vengeance RGB Pro ▪︎ Windows 10 Pro (21H1) ▪︎ Samsung 970 EVO Pro 1TB NVME SSD (OS Drive) ▪︎ Samsung 860 EVO 2TB SATA SSD ▪︎ Seagate 4TB SATA HDD ▪︎ Corsair RMx 850W PSU
December 18, 20205 yr Just now, captain420 said: With most games, when you switch from full screen to windowed mode, the window will be resized accordingly to the resolution that you have chose. I play on a native 4K display. For example, when I play Battlefield V in full screen and then change my resolution down to 2560x1440 and select 'windowed mode'. The game will switch to window mode down to the proper size and I won't be able to drag the corners to resize the game window. That's how it's meant to be. But in MSFS when I switch from a full screen 4K mode to a windowed 2560x1440 mode, the window takes about 85% of my screen, and I am able to drag the corners to resize it down. It should automatically resize the window to 2560x1440 and not let me be able to resize the window by dragging the corners. Why is this??? This is extremely frustrating because I expect the window to be sized exactly at 2560x1440. By me having to manually drag and resize, I'm not even sure if my resolution is exact or not and the proportion can go out of whack if I'm not eyeballing it correctly. Yes, it is a bit frustrating. My workaround is to set it to "Fullscreen", but with the resolution you want the window to be in. When you click OK it will look stretched and horrible, but then you change it from "Fullscreen" to "Windowed" and it should resize to the correct size. // 5800X3D // RTX 3090 // 64GB RAM // HP REVERB G2 //
December 18, 20205 yr Author I see, that it's not only me then. I really wish Asobo would make it behave like other games. I do not like how the window can be resized when going from fullscreen to windowed mode. It should be locked to whatever resolution you picked. But in the meantime I'll try your workaround. Thanks. ASUS ROG Maximus Hero XII ▪︎ Intel i9-10900K ▪︎ NVIDIA RTX 3090 FE ▪︎ 64GB Corsair Vengeance RGB Pro ▪︎ Windows 10 Pro (21H1) ▪︎ Samsung 970 EVO Pro 1TB NVME SSD (OS Drive) ▪︎ Samsung 860 EVO 2TB SATA SSD ▪︎ Seagate 4TB SATA HDD ▪︎ Corsair RMx 850W PSU
December 18, 20205 yr Oh, I think I have the more or less same frustration with my UltraWide monitor. When I'm going back from fullscreen to window mode, the window position is always not - at least - centered and I have to resize + put the frame inside my Windows desktop. MSFS doesn't save the its starting position. Thread to vote: https://forums.flightsimulator.com/t/windows-position-not-remembered-window-size-not-saving/318893 Edited December 18, 20205 yr by vbazillio Vincent B. Check my free MSFS sceneries : https://flightsim.to/profile/vbazillio/trending and my hardware configuration.
December 18, 20205 yr I had the impression that "fullscreen" in MSFS was actually borderless full screen window mode.
Archived
This topic is now archived and is closed to further replies.