River edge bug?

[biddrafter2]

I'll send this to Matrix support, but in case anyone is interested in an odd possible bug in version .40 of TOAW4, please open the zipped PDF attached to this post. Short version: Seems like a specific hex in scenarios carries bad data. I have no idea if this impacts gameplay or not. If it does we probably would have heard about it by now so hopefully this is just a visual artifact. This happens on a fresh install of Steam version of TOAW4.

[biddrafter2]

Although I can reproduce the visual aspect of this bug easily, and if no bmp with the name in my OP is specified it will always throw an error in the logs, I could not find any type of game mechanic impact in my tests.

I created a 50x50 scenario to test, with no changes from plain terrain. The visual artifact was visible with my hacked bmp in place. I added supply in a diamond around the hex with the issue.

Supply was not impacted.
Unit's movement across the hex was not impacted.
Fog of war was not changed from expected behavior.

So, seems to be a nothingburger. Such an odd name though, for a game with in hex rivers [8D]

[Lobster]

This line in a scenario .gam file makes me think Norm toyed with the idea of hex side rivers <VARIABLES scenarioIsOver="0" ceaseFire="0" eventEngineVariable="0" riversAlongEdges="0"