TFTD crash at 5120x2160

[Peter]

Starting a new game of OpenXCom TFTD at resolution 5120x2160 crashes to desktop. The menu at the resolution is fine. Starting at 3440x1440 works fine. Log attached

[Meridian]

Wow, that's an interesting one!

The log is actually useful in this case, but I can't see the problem at the first look.

I'll need to find someone with a huge monitor, or reproduce the issue by some hacking around.

Thanks for reporting, we will look into it.

[Peter]

You may be able to run at higher resolution than that of your monitor via DSR/VSR.

[Yankes]

Some workaround is reduce base resolution, with this less memory will be allocated and game would not crash.
Overall lot of logic there were designed for 320x200 base resolution, this is 100 time less pixel that on your screen.

[R1dO]

I am kinda wondering, are you using full-screen or windowed/borderless?

Reason for asking:
Full-screen requires a display that actually supports such a resolution. On some systems it is allowed to define windows that are larger than supported by the display.
If the crash occurs in windowed mode there might be no (or less) need for any hacks/workarounds.

Forcing the reported window size of 5120x2160 (on my 2560x1440 screen) i was not able to reproduce (e.g. game made it to the geoscape when starting a game).
Unfortunately i am using a different OS which makes such a 'cannot reproduce' kinda weak.

On a sidenote:
Even if able to run at this resolution you might not like the result though.
It seems that such a resolution is approaching the limit of numerical calculations (see attached '5120x2160globe_cutout.png').

For reference: the settings i used are shown in the 'settings.png' attachment.
Some further observations (valid for "being able to run" and "resulting image"):
* Displayfilters *raw/disabled/scale gave identical results
* Option "letterboxed" did not influence the result
* Globe returns to normal when using any geoscape scale bigger than "1x" (for this resolution)

[Yankes]

Can compile code you can try checkout this commit:
https://github.com/Yankes/OpenXcom/commit/2d7828f52ef36938044ee334f91f3efe653c4a70
it add new user option `globeSurfaceCache: true` that disable cache and allocation should be not problem.
(I see invert meaning of this config, should be opposite, in next version it would have more intuitive usage)

[Peter]

On a repro retry I found, the crash happens on a new game at 5120x2160p when geo/battle scales are set to Full Display. I am running in Fullscreen mode. It doesn't crash when the scales are set to 2xOriginal, which I am actually using for a playthrough. Full Display scale at such high resolution is very tiny, at least the menu is so it's not too practical for a general gameplay.

[Yankes]

did you try last build from https://openxcom.org/git-builds/ ?
I added option I previous mentioned to allow skipping some allocations for globe.

[Peter]

Yes, it crashes on 4/1 build as well

[Yankes]

Yes, it crashes on 4/1 build as well

Ok, I probably give wrong value for new config, it should be `globeSurfaceCache: false`