PS2PSXe public preview (Feedback and Discussions)

@ODedinho
Nicht ferszteje paruski jazyk...

@ODedinho

As you can see, this is an english forum, so please post it in english like all we do.
And at least put the source, because it's a copy paste from EOL. Something that airam wrotes.

Como puedes ver, esto es un foro en inglés, asi que por favor postea en inglés como todos.
Y por lo menos pon la fuente, porque es un copy paste de EOL. Algo que escribió airam.

Quote:

---

Originally Posted by dlanor

If you closed the ps2client command line window after the launch, then that is what caused the freezing.

When you launch the emulator through PS2Link, with both game image, bios, and MC files being loaded from a PC, then you are dependent on the HOST protocol connection remaining active for the remainder of the session. That connection is in fact split into two parts, one of which resides in PS2Link on the PS2 while the other resides in ps2client on the PC. So closing the ps2client command line window terminates the HOST connection, which inevitably freezes the emulation.

It is like simultaneously removing the game disc, unplugging the bios chip, and jerking out both MCs from a real PS1, and then expect it to continue running the game... :lol:


You are on the right track, but not quite there.
For one thing, the partition name is never included in a PFS path. It is only used in mounting an "hdd:" partition onto a "pfs?:" device mountpoint. Then you access that "pfs?:" device as if it was the true root directory of the mounted partition. So with "gamename.img" stored in the root of that partition the PFS path would be "pfs0:/gamename.img", without any explicit mention of the partition name.

But in addition to this you must first have loaded all the necessary device drivers, like I do in the following radshell script section:

Code:

---

iopreset

load rom0:SIO2MAN
load rom0:MCMAN
load rom0:MCSERV

load int:iomanx.irx
load int:filexio.irx

load poweroff.irx
load ps2dev9.irx
load ps2atad.irx
load ps2hdd.irx -o 4 -n 20
load ps2fs.irx -m 4 -o 10 -n 40
mount pfs0: "hdd:+Test 2"
cd pfs0:/PS2PSXe

---

The last command line above shifts the current work directory into a PS2PSXe folder on that HDD partition, where I have placed all the usual files and subfolders from the PS2PSXe package (including bios files, MC files etc).

NB: Storing the above radshell script and the modules radshell needs to load on HDD will obviously not work, since there will be no way of accessing the HDD after the initial iopreset, even though the HDD drivers may have been active before that in uLE. So the initial RadShell launch, and the execution of this script needs to be started from MC. The script above is suitable for use as inital "radshell.rsh" to be launched by RadShell every time you boot it, especially if you installed RadShell specifically to use with PS2PSXe.

After executing the script above, I am then ready to run various scripts to launch games, such as the following "test_CT.rsh" script that I use to launch "Chrono Trigger" of the "Final Fantasy Chronicles" release (where CT is SLUS_013.63).

Code:

---

del mc/epsxe000.mcr
copyfile "../!_PSX_MC/ChronoTrigger_m1.mcr" mc/epsxe000.mcr
del mc/epsxe001.mcr
copyfile "../!_PSX_MC/ChronoTrigger_m2.mcr" mc/epsxe001.mcr
run pfs0:/PS2PSXe/ps2psxe.elf "-cdimage=pfs0:/!_PSX_ISO/Chrono_Trigger_US/Chrono_Trigger_US.ccd" -xoff=40 -digitizepad

---

As you can see this script starts by deleting the current MC files (too drastic, you think ?), so as to replace them with game specific MC files from another folder in the root directory named "!_PSX_MC", where I keep a collection of such MC files for all the installed games (originally I made those MC files for use with ePSXe, via ePSXeCutor).

And after setting up the MC files needed for the game, the script proceeds to launch PS2PSXe with a -cdimage path for the game, which in this case is stored in a subfolder of another collection folder in the root, named "!_PSX_ISO" and holding one folder for each of the installed games.

I do this to keep the game files separate, since a game image in CloneCD format can have up to four separate files, and this quickly gets messy if just putting all game images in a single folder. It gets messy enough anyway with the larger games, having up to four discs (thus 16 files in a full cloneCD file set of ccd, cue, sub, img).

But of course, if that was the only type of script used, the initial MC deletion would be fatal.

To avoid having all gamesaves destroyed when next launching a game this way, it is essential to also have a cleanup script, for use each time you have run a game making new saves. And this script too needs to be individual per game, as in the following "post_CT.rsh" example for "Chrono Trigger".

Code:

---

del "../!_PSX_MC/ChronoTrigger_m1.mcr"
copyfile mc/epsxe000.mcr "../!_PSX_MC/ChronoTrigger_m1.mcr"
del "../!_PSX_MC/ChronoTrigger_m2.mcr"
copyfile mc/epsxe001.mcr "../!_PSX_MC/ChronoTrigger_m2.mcr"

---

As you can see this does not involve the emulator itself in any way, but merely ensures that the MC files in the collection folder are updated (by replacement) with the newest gamesaves for the game that was just used.

With this method it is the responsibility of the user to recognize which was the last game used and when it is necessary to use a 'post_xxx.rsh' script to preserve the saves. But it is simpler to implement this way.

I have also done some experiments where the scripts themselves can keep track of such things by various methods, but it gets rather complex and prone to failure if the user makes any errors in script preparation. I think the above should do for most immediate needs anyway.

Best regards: dlanor

---

dlanor, thank you very much for your reply. :) I will go try now what you have posted.
I appreciate your answering as I know your not feeling well.
Hope you get better soon!!!:)

@ffgriever you are neither a liar or an idiot in my, or a lot of other peoples eyes. please keep up the great work you do. as you said, this is not a final release but just a preview. I patiently await the final release, as i have for some time. your past work is priceless as will this be when its done...cheers mate.

toozit

Quote:

---

Originally Posted by ffgriever

I'm just curious about one thing. How do things look on PS3 side? I mean, the ones with backwards compatibility... Are there any special requirements to make anything work on it? How well is PS2 emulated on PS3? Is it full emulation or it's just a general one made to make most of the games working but nothing more? PS2PSXe relies heavily on TLB and exceptions... Do these work properly on PS2 emu included in PS3? How's the hardware access? Do mass devices work fine or are there some ps3 specific fixes necessary? Do things like uLE or radshell work on it?

Because I'm quite curious, I would be glad if someone could help me test it. I can provide all the PS2 and project related support, though the PS3 related stuff is totally beyond me (I don't have one and know barely anything about it). It's not a priority, I'm just curious... If the changes required are not big, I think it could be done... If there is a lot of work required, I'll pass. The backwards compatible PS3s are obsolete now, no longer in production, so it would ba a waste of time. Then it would be simply easier to wait until some exploit is available and write native ps3 app (well, there is one, but they're selling it with every game through psn, and this sucks... why to pay for a game you already own...).

PS. Emulator running emulator... How perverse! ;) .

---

Sorry the english!
ffgriever, thank you for everything you have done to us!

I was able to run on a ps2slim trough mass and host.
I have a PS3 PAL 60gb firmware 3.15
and I do not was able to make it run neither trough mass or host.
I use SM 3.6 to load ulaunchelf 3.41. It is the version I Know that can detect mass (USB devices)

Trough host on ps3 enverioment I can make ping with response, but when I load SM 3.6 I can't longer make ping with response. And PS2LINK crash.

Trough mass, I don't know what happens but after load radshell shows logo of playstation 2 and stays there.

If you want a can make a video.

About the emulation of ps2 on ps3. I have both consoles, and I prefer play PS2 games on PS3 I have component cables on both consoles and the image quality is better on PS3. About homebrew of ps2 on ps3, lot of them work like ps2 usbloader, other don't.

gracias ODedinho funsiona perfecto :D

thanks ODedinho it works :D

Quote:

---

Originally Posted by docyoe

I tried it out its not working that way I copied everything in usb root.
But I get in radshell the error "Not an elf file: mass:/ps2psxe.elf" any help?

---

I had also experienced the same problem with you, it turns out the problem on my console (30001), I try to use another type (70012) that apparently works well.

Make sure the usb modules are loaded and mass device is working (the hardware is properly detected).

Then read what berion wrote and you should have no problems using usb devices.

Quote:

---

Originally Posted by ffgriever

Make sure the usb modules are loaded and mass device is working (the hardware is properly detected).

Then read what berion wrote and you should have no problems using usb devices.

---

Now is working, Master, but no sound
Thanks....good job.

No sound you say? There must have been some kind of mistake...

Get as close to your TV as possible. Now put your ear to the speaker. Take a deep breath and listen. Can you hear it? The static... Pure noise... Isn't it the most beautiful sound in the world?

But seriously - there is no sound support, sorry to disappoint you ;).