I did some work with the BiS mapper (fixed for hi-res), for one to clean up some maps, but mostly to learn using it. While doing so I came upon a map based on “Cafe of Broken Dreams” and it had some random SAI blockers. My first thought was that this was another “old remnant” that needs to be cleaned up, but I then tried to figure out why it was placed there, and after some time I realized that this is an attempt to fix the glitch that SW corners turn transparent when running past them or standing at them.
I never saw this anywhere else, nor used by anyone else (FoRes, Nevada etc.), and it's not the cleanest fix but it does work.
Not really sure this is interesting, but the way it works is:
The Fo2 mapper did set the two wall pieces left and right of the corner piece to “Wall Trans End: Yes”, then to avoid the glitch when approaching the corner from the inside placed the two SAI blockers. After some testing I think it needs a third one, though (just above the two along the N to S wall). Either way, after this the corner is fixed: the outside is turning transparent very little when moving and none at all when standing still, and the inside is fine, too, except that the corner is blocked, but it doesn't feel arbitrary or out of place, I'd say.
Still, it's a bit of work just to avoid a transparent glitch. Also every corner is individual. I tested a few others and it all worked the same, but eventually I found a “curved” corner, which required to set the piece left and right of the corner AND the corner piece itself to “Wall Trans End: Yes”, then it worked the same... so each case would need checking it seems.
Anyway, I thought maybe people saw these corners turn transparent when running past them and thought it odd/wrong. This old "trick" from the Cafe of Broken Dreams map seems to fix that.
Hex Marker Glitch: The marker is normally standard, however, it can be made to feature a “x” (or “1” etc.), which can be helpful when trying to click on hexes (especially when using Q). To do so, trigger the test mode (F8), then move the cursor on any blocked hex so that the “x” is featured, then end test mode (via F8), from now on the default hex will feature the “x” until closing the mapper.
This had me pretty frustrated until I finally figured out that it is a “glitch” and not a hotkey I couldn't find a second time or kept hitting by accident.
BEEP: When pressing “e” followed by “f” while having selected something that is currently not viable (i.e. wall category is open and selecting a scenery piece) it starts to beep. Going into F8 and a set of numbers is running through the display. This does not stop until pressing “e” and “f” again.
Anyway, I'm curious what those numbers are running through the display, maybe someone knows. If so let me know.
I never saw this anywhere else, nor used by anyone else (FoRes, Nevada etc.), and it's not the cleanest fix but it does work.
Not really sure this is interesting, but the way it works is:
The Fo2 mapper did set the two wall pieces left and right of the corner piece to “Wall Trans End: Yes”, then to avoid the glitch when approaching the corner from the inside placed the two SAI blockers. After some testing I think it needs a third one, though (just above the two along the N to S wall). Either way, after this the corner is fixed: the outside is turning transparent very little when moving and none at all when standing still, and the inside is fine, too, except that the corner is blocked, but it doesn't feel arbitrary or out of place, I'd say.
Still, it's a bit of work just to avoid a transparent glitch. Also every corner is individual. I tested a few others and it all worked the same, but eventually I found a “curved” corner, which required to set the piece left and right of the corner AND the corner piece itself to “Wall Trans End: Yes”, then it worked the same... so each case would need checking it seems.
Anyway, I thought maybe people saw these corners turn transparent when running past them and thought it odd/wrong. This old "trick" from the Cafe of Broken Dreams map seems to fix that.
Hex Marker Glitch: The marker is normally standard, however, it can be made to feature a “x” (or “1” etc.), which can be helpful when trying to click on hexes (especially when using Q). To do so, trigger the test mode (F8), then move the cursor on any blocked hex so that the “x” is featured, then end test mode (via F8), from now on the default hex will feature the “x” until closing the mapper.
This had me pretty frustrated until I finally figured out that it is a “glitch” and not a hotkey I couldn't find a second time or kept hitting by accident.
BEEP: When pressing “e” followed by “f” while having selected something that is currently not viable (i.e. wall category is open and selecting a scenery piece) it starts to beep. Going into F8 and a set of numbers is running through the display. This does not stop until pressing “e” and “f” again.
Anyway, I'm curious what those numbers are running through the display, maybe someone knows. If so let me know.