PS2 [Testers Needed] MX4SIO - WIP SD Compatibility Thread
O-P-L-Fighter
Member
I will Post it more in Detail when I have time. but what I can say in general is that I can't think of a game right now that doesn't somehow run on mx4sio.
In Kingdom Hearts (Final Mix) I get heavy fmv stutters. So for me it's unplayable.
Btw. What is your experience with .cso games? I read somewhere that mx4sio loses performance due to compression (more then USB). Is that really the case, or is the information possibly already outdated?
So far I haven't had any problems with .cso files, most games run and I only notice slightly longer loading times. But I did not tried mich games with complex fmv sequences...
In Kingdom Hearts (Final Mix) I get heavy fmv stutters. So for me it's unplayable.
Btw. What is your experience with .cso games? I read somewhere that mx4sio loses performance due to compression (more then USB). Is that really the case, or is the information possibly already outdated?
So far I haven't had any problems with .cso files, most games run and I only notice slightly longer loading times. But I did not tried mich games with complex fmv sequences...
Was that Kingdom Hearts also a .cso or was it a normal, good .iso?
O-P-L-Fighter
Member
It was an .Iso File! It's an english patched, Japanese Version of the Final Mix by Sora6645 and Crazycatz00. It works Fine when played on the internal HDD. But stutters even more when played from USB (testet on SanDisk UltraFit USB Stick (128gb)).
I used only ISO. Files on the 1tb SanDisk microSD.
Edit: yes of course Zso! CSO was it on PSP
I used only ISO. Files on the 1tb SanDisk microSD.
Edit: yes of course Zso! CSO was it on PSP
balfiere
Forum Noob
Did you turn mode 6 on? Without it I get a black screen but I was able to play until the first save point with it on.
Somehow I don't understand at all what to look for in this log. How can I learn to read the log by myself? What do I need to pay attention to and should I look for somethings and compare it?
Here is the log of the:
Kingston Canvas Select Plus 64GB (SDCS2/ 64GBSP) microSD w/o adapter.
OOTB formatted exFAT, cluster size 128K.
MX4SIO from Aliexpress (microSD variant).
OPL BDM 4.7.1 and sdcard_debugger v0.3 were used.
System is SCPH-77004 PAL.
In general, all is well with the card so far. Tried to run 'Xenosaga Episode I - Der Wille zur Macht (USA)' - the game is pretty playable, the videos plays smoothly.
It's getting interesting (to me) why this log is so different from that one:
MX4SIO memory card frustration
There's the same (at least by name) card and MX4SIO of the same origin.
Here is the log of the:
Kingston Canvas Select Plus 64GB (SDCS2/ 64GBSP) microSD w/o adapter.
OOTB formatted exFAT, cluster size 128K.
MX4SIO from Aliexpress (microSD variant).
OPL BDM 4.7.1 and sdcard_debugger v0.3 were used.
System is SCPH-77004 PAL.
In general, all is well with the card so far. Tried to run 'Xenosaga Episode I - Der Wille zur Macht (USA)' - the game is pretty playable, the videos plays smoothly.
It's getting interesting (to me) why this log is so different from that one:
MX4SIO memory card frustration
There's the same (at least by name) card and MX4SIO of the same origin.
It looks like the one used by Tailgunner is an older version. I changed the output in v0.3 to be more to the point and record everything that's sent and received via SIO2. The debuggers themselves were quickly hacked together and are really only good for debugging cards that fail to initialize to due to bugs with timing logic, which were far more common when I first started working on the MX4SIO driver. Most of the issues that remain are ones that occur during multiple block reads or during some other operation and thus will not show up in the debugger logs. if a log gets passed CMD10, it's likely a problem with multiple block reads or another later operation.
Unfortunately without someone willing to run debug builds of OPL via ps2client on their problematic cards, it's hard to address such issues. The CC tests where mostly guesswork that thankfully seemed to have good results and I have some more experimental changes planned for an upcoming build.
Last edited:
Since I'm having issues with all OPL builds out there except for CCV2 for all my SD cards, I think it's worth trying to get some debug info for you. Hopefully it'll help with zeroing-in on the issues instead of going in blind.
Could you explain what is needed for doing that? Where can I find a debug build and how do I use it with ps2client?
As for the latest grimdoomer+CCV2 build, it simply works perfectly for all my SD cards, unlike grimdoomer's official build.
Do you have any cards that don't work with CCV2 or any other builds?
I have 3 cards in total: 2 128GB (TeamGroup and Kingston) and 1 32GB card (Kingston).
All of them work with CCV2. None of my 128GB ones work with any other build. My 32GB card also works with the official 1.2.0 Beta and your BDM4.7.1 builds.
Note that when I say the SD cards "work" I mean they don't freeze in-game very soon after boot (usually on the main menu etc). All games/apps from those cards show up correctly in OPL, the issue is always when trying to...well, use them.
It would only be worthwhile to run debug builds if you had cards that were still not working with any builds. I do appreciate the offer though.
Just check for updates then. @emenesu
Once there is some new update/test which COULD improve performance, try it.
@qnox32 is working very hard on many things, so SD-Cards are a BIT on the back burner for now.
General MX4SIO performance will probably improve, once he merges all his "small" but multiple improvements (which I suppose will "stack" on each other).
Once there is some new update/test which COULD improve performance, try it.
@qnox32 is working very hard on many things, so SD-Cards are a BIT on the back burner for now.
General MX4SIO performance will probably improve, once he merges all his "small" but multiple improvements (which I suppose will "stack" on each other).
janeli
Forum Noob
A great project that runs much more smoothly than the regular version of OPL1.2.0 BETA.Support for more memory cards.although there are a few bugs.
OPL R4 version running dead or alive 2 occurs stuttering.
OPL BDM version 4.6 data read slower than other OPL and dead or alive 2 black screen unable to enter.The Japanese version and the American version of Dead or Alive 2, in different OPL versions, there will be different compatibility.
OPL BDM Version 4.7 Dead or Alive 2 Black screen failed to enter.
OPL BDM 4.7.1 and BDM4.7HOTFIX The controller cannot be operated after some console models are accessed. Or stay in the OPL interface cannot operate.
OPL BDM4.0. A random inoperable problem occurs when OPL software is accessed from the FAT console. SLIM no problem.
After testing OPL BDM 4.5 version is relatively good. But running Resident Evil 4 on the FAT console occasionally ran into CG jump stuttering issues. There is also the occasional uncontrollable occurrence after entry into OPL. Because there are no more SLIM consoles, some test data is missing for the time being.
In most games, hold the controller's SELECT START L1, L2, and R1 at the same time R2 can be reset from the game, and the reset path can be set in OPL. If the path set is the same version of OPL, you can return to the game list. For some cases where the game list disappears after restarting the PS2 console, it is not easy to reset the list in this way.
OPL R4 version running dead or alive 2 occurs stuttering.
OPL BDM version 4.6 data read slower than other OPL and dead or alive 2 black screen unable to enter.The Japanese version and the American version of Dead or Alive 2, in different OPL versions, there will be different compatibility.
OPL BDM Version 4.7 Dead or Alive 2 Black screen failed to enter.
OPL BDM 4.7.1 and BDM4.7HOTFIX The controller cannot be operated after some console models are accessed. Or stay in the OPL interface cannot operate.
OPL BDM4.0. A random inoperable problem occurs when OPL software is accessed from the FAT console. SLIM no problem.
After testing OPL BDM 4.5 version is relatively good. But running Resident Evil 4 on the FAT console occasionally ran into CG jump stuttering issues. There is also the occasional uncontrollable occurrence after entry into OPL. Because there are no more SLIM consoles, some test data is missing for the time being.
In most games, hold the controller's SELECT START L1, L2, and R1 at the same time R2 can be reset from the game, and the reset path can be set in OPL. If the path set is the same version of OPL, you can return to the game list. For some cases where the game list disappears after restarting the PS2 console, it is not easy to reset the list in this way.
Last edited:
Similar threads
-
PS2 About [Testers Needed] MX4SIO - WIP SD Compatibility Thread- Started by oraculorafa
- Replies: 0
-
-
PS2 [POC/Outdated] unofficial Open PS2 Loader (uOPL)
- Started by Ripto
- Replies: 58
-