I also studied the PC version. As I understand it, in the PC version the files are decompressed. This I often observe (for example, compressed graphics in Toy Story 2 and Magical Racing Tour on PS1 and uncompressed on PC). However, in the PC version of this game I see the mixed byte "FF", which is displayed on my Russian OS as "я" char in a hex editor. For example "Steяreo".
I decided to experiment roughly, and simply deleted it by replacing the FF byte in the entire file in the hex editor. Then I tried to open such a file in Tile Molester. And if earlier it opened incorrectly, now part of the image has been displayed as it should. The only point is that it seems that not all FFs should be deleted, since It seems that some of them are responsible for the image pixels, and due to the absence of such a byte, another part of the image is shifted.
Like this:
Test file:
L_Mwitch_1.bze,
582 KB from the
BZE folder
I opened it in
Tile Molester with the following settings:
15bpp BGR (555) and Canvas Size:
72 columns x
63 rows.
After removing the
FF byte, it had to be opened with other parameters:
15bpp BGR (555) and Canvas Size:
64 columns x
66 rows.
And now...
I used russian version of game. What is interesting, firstly, the picture partially began to look close to the original (especially in color). Secondly, the first half of the image (Title) and the first half of the bottom part of the image (Loading) quite began to look normal (compared to what it was). It is also interesting that the last time there were 72 columns, and after manipulating the file it took 64. It turns out that the difference of "8" is that
FF byte.
As for the sound (I also heard this noise - I listened in
MFAudio) - it looks like the same story with this byte. I think it causes this background noise. Also, I tried to open the sound of the game (like
speech00.xa) in
Audacity (well, that this program can open untyped sound files), and I want to say that if you play around with the settings, you can open the file so that there is less noise. While in theory I can conclude that if you clean the sound of the
FF byte, then there is a chance to open it correctly at least partially. I have not checked it myself yet ...
I hope I helped a little.