Transparency errors on some .x objects

Found a route with transparency glitches I can't fix using conventional methods since all objects come in .x files which generate weird errors.

https://www.dropbox.com/s/ja218srpc60fail/Keio_dotnet.lzh?dl=0

Look at overhead cables on surface sections

It's a color pallette issue.

Specifically, the transparent color specified for X files is pure black (0,0,0) [In .x files, the transparent color is not stored in the object]
Now, the color for this in Kasen.bmp is 2,2,2
Normally, we only see this in restricted (256 color) pallette textures, which we can handle automatically by mapping to the closest color in the restricted pallette, but the author of this route seems to have saved the texture files in 24-bit color.

Short answer is to replace the transparent color in the texture with pure black.
I'll think about whether we can handle this a little better internally, but not sure.

Latest build has handling for this via the routefile patch database.
This will need to be added for any other broken files on a case-by-case basis, as it's way too disruptive to set as on by default.

Only applies in-game with the BVETSHacks enabled option, not in Route Viewer / Object Viewer.

This got fixed, but I now noticed some odd track object mismatches in some places. LU Northern line has similar issues (and I think not only track objects are affected), also it likely was there in some previous builds too