The drivers work fine in the GUI it seems.
Art is loaded, game-settings are saved and so on.
It just fails starting a game and the most recent Betas even freeze and show weird names on original hardware, whereas PCSX2 is forgiving the TLB-Misses.
Btw.: It also already did start a game for me from SD with a new build. The annoying thing... It was a fork which started it once.
Also there is some kind of bug related to selecting a Block-device and saving settings! It doesn't get triggered every time I think.
It somehow creates a folder instead of a file and the loading-icon won't stop spinning.

conf_opl.cfg which was present before, became 0Byte.
...and the conf_last.cfg, which was not present before, became a folder.
I figure the looping of "sioWriteStart cmd: 02??" "sioWriteStart cmd:FF??" is the MX4SIO driver trying to recognize an SD via SIO?
TLB-Misses:

Art is loaded, game-settings are saved and so on.
It just fails starting a game and the most recent Betas even freeze and show weird names on original hardware, whereas PCSX2 is forgiving the TLB-Misses.
Btw.: It also already did start a game for me from SD with a new build. The annoying thing... It was a fork which started it once.
Also there is some kind of bug related to selecting a Block-device and saving settings! It doesn't get triggered every time I think.
It somehow creates a folder instead of a file and the loading-icon won't stop spinning.

conf_opl.cfg which was present before, became 0Byte.
...and the conf_last.cfg, which was not present before, became a folder.
I figure the looping of "sioWriteStart cmd: 02??" "sioWriteStart cmd:FF??" is the MX4SIO driver trying to recognize an SD via SIO?
TLB-Misses:

Last edited:


