Closed samboy closed 4 years ago
OK, I have done it. I have added code to builder.lua
so that:
has_sky
with the value trueMAP27
, so we rebuild the entire map with a different architecture. This solves the problem in a way that the sky of a map does not look buggy.
All of the tests have been updated and pass again; only MAP27
(and the deathmatch-only items in MAP28
, MAP29
, and MAP30
) has changed. Closing ticket.
[1] I am aware that Andrew spells “neighbor” differently in the Oblige source code, but I’m American and this is how I spell this word.
This commit fixes the bug (well, it looks for the bug, and if it finds it, it remakes the map): 99eb73179a09f8086574733e2be1c43fdaae7751
This commit tries patching things so the offending sector is a sky border, but that actually looks pretty bad, so I gave up on it: adead60bcb6fd2d8598ffde136022cf28bba970f
In https://github.com/samboy/ObHack/issues/9 I “fixed” a visual gitch bug by, after failing to find anything in the very messy put-side-then-corner code which caused the bug (It looks to be an issue of having the corner in the wrong place, but fixing that may change a lot of maps, so I tread very softly even if the code is buggy), just having the writer check if this visual glitch is happening, and put in a less obnoxious texture than the pulsating
FIREBLU1
texture if so.While this improves things, the real fix should be in
builder.lua
:F_SKY1
, then make sure we make that fragment a sky border withbuild_sky_border
MAP27
via the automated tests. If not, find another fix.