Clocknova
Member-
Posts
102 -
Joined
-
Last visited
Clocknova's Achievements
Garrulous Glaahk (8/17)
-
I posted about this issue back in 2015 when Avernum 2 was re-released, and I'm pretty pissed I still have to post about it now, but has anyone figured out how to hack either Avernum 2 or Avernum 3 to display higher resolutions in widescreen the way Avernum 1 did? Specifically, at 2560x1400, the game refuses to display in widescreen. Jeff gave some vague answer three years ago about the engine doing weird things at higher resolutions, but I don't recall that ever being a problem with his earlier games. And since he clearly has no intention of removing this limitation, I was hoping that in the years since this became an issue that someone had documented a way to force the games to display at the proper resolution. I've been waiting three years to play Avernum 2, and will apparently have to keep waiting to play both that and Avernum 3. Hoping someone can help.
-
This is a screenshot of what the game screen looks like: http://static01.gog.com/upload/forum/2015/01/79ad0e9e60e2c2525e26ee5f2e653aec17e119a2.jpg And for comparison, here is what the previous game looks like on the same machine with the same settings: http://static04.gog.com/upload/forum/2015/01/78ad2c148c07d8da0cdc3fb33015ae048f053d44.jpg
-
I mean the game area will not fill the screen. There are black bars on all four sides that the mouse cursor will go into, but the playable area will not extend into it. I'm in fullscreen mode, and the initial Spiderweb logo will display across the entire screen. The previous games called the largest game area size setting "whole window," but in Crystal Souls it is simply called "large." I wonder if he changed the way the game calculates this and inadvertently broke it for certain resolutions (namely mine.)
-
I don't get a 1920x1080 option. However, 1600x900 will fill the screen, but my native res of 2560x1440 will not. But, as I said before, all other recent Spiderweb games since Avernum 6 will properly will the screen at my native resolution, so there's clearly an error in this release. I'm running this on a late 2013 27" iMac, 3.5 Ghz i7, NVIDIA GeForce GTX 780M 4096 MB, 24 GB RAM, OS X 10.10.1.
