Alright, so I’ve been wanting to play F1 2023 on my new ultrawide monitor for a while now. It’s a 3440×1440 21:9 beast, and I was pumped to see those stunning visuals stretched across the entire screen. But, boy, was I in for a surprise when I first booted up the game.
I fired up F1 2023, and bam! Big, fat black bars on the sides. Talk about a buzzkill. It’s like having a Ferrari but only being able to drive it in first gear. I mean, what’s the point of having this beautiful, expansive screen if the game won’t even use all of it? I gotta say, I was pretty bummed out.
I started digging around online, hoping there was a simple fix. I found some forum posts and Reddit threads where other people were having the same problem. Apparently, I wasn’t the only one with a fancy ultrawide monitor who wanted to immerse themselves in the world of F1 racing. Some people were saying to change it to fullscreen instead of windowed mode. I tried that, but no dice. The black bars were still there, mocking me.
I messed around with the in-game settings, trying different resolutions, and even tried some windowed fullscreen thingy, but nothing worked. I’ve got a Samsung Odyssey G9, a pretty popular ultrawide monitor, and I’m sure many of you out there are in the same boat. I even saw some folks saying this was an issue in F1 22 as well. Seriously? Why hasn’t this been fixed yet?
Then I had a thought. Maybe it’s my monitor settings? I right-clicked on my desktop and went to “Display settings,” just to make sure my PC was recognizing the ultrawide goodness. And it was, so that wasn’t the issue either.
- Checked the game resolution
- Checked if it is in fullscreen mode
- Also checked the monitor settings
It is just what it is, I think some games won’t scale to ultrawide resolutions. I guess I’ll just have to play it in 16:9 until they release a patch or something. It is not necessarily what I expected. It’s a bit of a letdown, but hey, at least the game is still playable. It’s just not the fully immersive experience I was hoping for. Hopefully, the developers will address this soon. Until then, I’ll keep tweaking and see if I can find a workaround. If any of you have figured out a solution, please let me know in the comments! I am sure lots of other people will be grateful for it too.
