Judging by the screenshot, the font of the dialogs needs alignment (the letters jump around on height). And the VWF will not prevent.
hey man thats cool. Yea I definitely wasnt trying to definitively say psk was the issue. I've happily used psk for years now with out problems.@Jackafur : if other user(s) report similar problem with Pseudo Saturn Kai, then we shall conclude that something needs to be fixed there. But until that time, I guess it's only an affinity problem between your Saturn, your CD-Rs, or your drive to burn CD-Rs ... or anything else
(It took several days for me to reply about your problem to reduce the aggressiveness after reading something like "My game on CD-R game doesn't works. Please fix Pseudo Saturn Kai !" in my mail box. If more and more customer support means more people and getting interested in Saturn then that's cool, but I'm not a call center about things that can be fixed without external help ...)
I personally only turned it the TIIIINIEST bit clockwise, there's some videos out there where the people twist the thing like crazy, it makes me wince!
So I took a look at the compression algorithm used for the battle menu tiles. I rewrote the decompression in C and I'm able to decode the first image (the yellow cursor triangle) successfully. The C code isn't beautiful, but it isn't too cryptical either and I think I have gained at least a basic understanding of what's going on. Now obviously decoding the data isn't too helpful since you could just as well let the game do the work and simply dump the VDP1 RAM at the right time. I wrote the function mainly to understand the compression. I'm hopeful that I'll be able to write a re-compression function with this understanding, though it should be noted that I've no real in depth knowledge of compression/decompression so I won't rule out failure. If I can't figure it out I'll write down what I learned and publish it here.
Making the tile data isn't hard. I've done it for a few other parts already. So that shouldn't be an issue.Thanks, I've already identified, disassembled and reversed the decompression function. My function does work correctly until some position into the second tile, then it breaks and produces garbage. I've already a suspicion why this happens and I think the function will be done today. Then comes the hard part, writing the compression function.
I don't want to jump too far a head, but at some point we need the tile data from the English ps1 version. Do you already have the translated tiles?
Sometimes, if there is free space and the amount of data is small, you can place there the already unpacked data by the game itself. Thereafter you need to prohibit access to the unpacking procedure. Unpacked data will be directly read from disk to the desired address in RAM, and then written to video memory.
In this case, you do not need to spend time analyzing the algorithm for packing data and writing a decompressor / compressor.
PS: I have used this method in many games, including Linkle Liver Story.