Graphics Problem in Barbarian Invasion regarding Screen Resolution

ViciVidiVeni483

salve, sodales!
I've just gotten back into RTW and I've been meaning to play Barbarian Invasion again too, but I've run into a nasty graphics problem for months now regarding screen resolution. This problem only happens with BI, by the way, not regular RTW for me.
Here's a screenshot, for reference:



So basically, the problem is that the screen resolution of BI does not fit the screen size of my laptop properly. I adjusted the preferences.txt file to allow me to use a 1920x1080 resolution (which is the resolution for my laptop, and I did the same thing in RTW and it worked fine), but when I selected that option the screen was far too zoomed in for the game to be playable, as basically a third of the screen was out of view. I tried going to smaller resolutions but the problem persisted with some of the screen being out of view, until I went to 1366x68x32 as you can see here, when the game just decided not to fit my screen at all, with the Steam app still visible.
I am using Windows 11 and again, my laptop resolution is 1920x1080. This problem is exclusive to BI, not regular RTW.

Could someone help me with fixing this, please?

dge1

Frankly, you might have better luck asking in the appropriate section of the Steam forum. The legacy games are no longer supported here, nor on Sega Support.

As a side note, when the Remastered Rome was issued I reinstalled the original Rome and had no issues running it. I did not try Barbarian Invasion though. You might take a look at that route also. It is part of the package, though I did not run it. I did not like the Remastered Rome so just shut it all down.

Good luck.

ViciVidiVeni483

Yeah, I've just come to know that unfortunately CA took the original off the steam marketplace. Damn shame, man.
Steam discussions can always be finicky, but yeah, I've already sent a post and hopefully they'll be a reply sometime.
I've already tried reinstalling it as well, but no dice. The regular RTW works fine, but BI still has this problem.

Either way, thank you for responding!