I want to hopefully encourage some of you experts about helping me put together a Developer's Tutorial about PS2PSXe files and functions. This would be helpful to the average user as well as to give a shortcut to some savvy developers if they wish to help us continue with this project.
I am going to jot down some of my notes, and please chime in if you have a better understanding of them than I do.
UPDATE: August 17, 2012
I've updated my version to: ps2psxe_jay-jay_bundle_v2 -- it now supports different languages (see translation folder).
Also if you use Network/HOST: download my version: PS2LINK_to_PS2Client_by_Jay-Jay
Downloads are at: http://psx-scene.com/forums/f292/ps2...pdates-105355/ (PS2PSXe Downloads and Updates)
Game Compatibility List at: http://psx-scene.com/forums/f292/ps2...e-list-105342/ (PS2PSXe Compatibility Game List)
Attention Newbies:
DO NOT ASK QUESTIONS IN THIS TOPIC!
THEY WILL BE DELETED!
Click Here to start a new Topic and ask a question about PS2PSXe:
http://psx-scene.com/forums/official-ps2psxe-forum/
What is PS2PSXe?
PS2PSXe functions as an emulator to be run backups of PSX (PS1 Games) on the PS2. It can be used via USB HDD, Internal HDD (PHAT), or by Network (HOST).
Why do we need an emulator for PS1 Games since the PS2 can play PS1 Games?
Yes, the PS2 can play PS1 games, but only if they are original PS1 Games on discs. There is also another known method to run copies of PS1 games on discs, but doing some trickery when loading them with uLE or other disc loading methods--but we will not discuss this here.
The purpose for PS2PSXe emulator is to be able to play the games without them being on disc, instead to be able to store them as CDROM Images. So if you have a large USB HDD or Internal HDD (PHAT), you can then have the ability to store and load your PSX games (CDROM images) without the need to be changing game discs on the PS2 disc tray (the same way OPL gives you the ability to do the same thing, but with PS2 Games.)
What's the best file format to play these PSX games on PS2PSXe?
So far it's a BIN file. If you use the GUI version, you can load BIN, CUE, and even CCD files of the games. If you use the Network/Host method, it's best to just load the BIN version of the game--at least that has been my way--since I notice that the CUE or other files tend to make PS2PSXe crash.
Tutorials?
See some below.. still working on some more...
Type
_____File_Name______ Description __Directory_Placement__ ELF ps2psxe-gui-pack.elf this gives you an easy graphics user interface (GUI) for the emulator. It allows you to make some adjustments before you load a game. Some games require features to be enabled or disabled. (Read GUI Tutorial below)
This GUI still requires you to have ps2psxe.elf and ps2psxen.elf in the same directory so the GUI version can trigger these elfs for either Sound enabled or disabled. This is why it's important to not rename these ELFs and also to keep them in the same directory, since they all need to be there in order to work with the GUI version.
As far as I know, this GUI can only be used to load games if you have them on USB or Internal HDD in the PS2. I don't think it works with Network/HOST method, since when you load the GUI Version within Network/HOST with the L1+L2+R1+R2+UP command, you will not be able to load another cdrom image afterward-- at least that has been my experience with it.ROOT ELF ps2psxe.elf - this elf allows the game to have Sound. For the GUI users, it's important to keep this elf inside the same directory where you have the GUI version, since when you enable the "Emulate Sound" feature in the GUI Configuration settings, the GUI version will then run ps2psxe.elf automatically after that. ROOT ELF ps2psxen.elf - this elf disallows the game to have Sound. If you have problems running a game with Sound, then you would need to run this version--that's if you use Network or other methods to run this, without the help from the GUI (more details about this will be explained below). For the GUI users, it's important to keep this elf inside the same directory where you have the GUI version, since when you disable the "Emulate Sound" feature in the GUI Configuration settings, the GUI version will then run ps2psxen.elf automatically after that. ROOT IRX audsrv.irx ? - I am not sure if this file is necessary after r198 ROOT IRX freesd.irx ? - I am not sure if this file is necessary after r198 ROOT IRX ioman.irx ? - I am not sure if this file is necessary after r198 - plus I read that ps2client doesn't need it anymore or at least the ps2client-ps2link version I provide inside the download section with my Jay-Jay username. And I believe this file may crash radshall if you have it. Not sure, I need someone to clarify this. ROOT CFG default.cfg this is a configuration file save is created when you have the GUI save your configuration settings. (See GUI Tutorial for more info below).
Keep in mind that this cfg file can only be created and used with USB MASS / and Internal HDD -- There is a known bug that affects Internal HDD -- See Internal HDD (Phat PS2 Consoles Only) below for more info about this.
You can't use this file for HOST/NETWORK method.ROOT Folder bios
here in this folder you place the PS2 Bios. It is recomended to use only scph7502.bin - Google It -- we cannot share it here. ROOT/bios Folder mc here in this folder the files epsxe000.mcr and epsxe001.mcr exit and they are actually the emulator's memory cards so you can save your game saves into--this is done automatically when you save your game saving using USB (MASS) / Network / HDD. NOTE: When you update to a higher version of PS2PXe, be sure to not overwrite this directory, or else your game saves will be wiped out. ROOT/mc MCR epsxe000.mcr this file is inside the mc folder, and it emulates your mc0 memory card of a PS1 Console so you can save your game save. Game Saves work with USB (Mass) / Network / HDD. NOTE: When you update to a higher version of PS2PXe, be sure to not overwrite this file, or else your game saves will be wiped out. ROOT/mc/ MCR epsxe001.mcr this file is inside the mc folder, and it emulates your mc1 memory card of a PS1 Console so you can save your game save. Game Saves work with USB (Mass) / Network / HDD. NOTE: When you update to a higher version of PS2PXe, be sure to not overwrite this file, or else your game saves will be wiped out. ROOT/mc/ Folder plugins this folder is where you will find plugins to make the emulator work ROOT/plugins Folder cdr this is a folder inside the plugins folder ROOT/plugins/cdr Folder iop this is a folder inside the cdr folder. ROOT/plugins/cdr/iop IRX cdriop.irx this file is a plugin to make your CD Player work. See GUI tutorial below to learn how to enter CD Player mode -- note that this is not to play PSX games on Disc, it simply a music CD palyer. ROOT/plugins/cdr/iop/ Folder spuhw this is a folder inside the plugins folder ROOT/plugins/spuhw Folder iop this is a folder inside the spuhw folder. ROOT/plugins/spuhw/iop IRX spuiop.irx ? - not sure what this plugin is for. ROOT/plugins/spuhw/iop/ Folder snap this folder is where you game screenshots will be stored when you press this combo: press L1+L2+R1+R2+triangle+circle to save screenshot in snap folder- always using executable (slesxxxxx) with counter (always checking for files that are already there, so it doesn't overwrite files if used in multiple sessions). Screenshots are saved in tim2 / TM2 [PS2] image format. Use Tim Tool (Google It) to convert the image to JPG, PNG, BMP or other picture format ROOT/snap lng lang.lng this is the language file. by default it is in English. If you want to change it to your own language, look inside the translations folder and just replace it with one of those. (see below for translations folder). ROOT Folder translations this folder contains other languages (in folders) to use with the GUI version. Just replace the default English lang.lng in the ps2psxe launch ROOT with the translated one. If you wish to share a language file you create, please let us know, so we can include for next revisions. Look for the PS2PSXe Translation Official Thread to attach yours. ROOT/translations txt [Requirements].txt Just a readme text so you can read. ROOT txt README.txt Just a readme text so you can read. ROOT txt GUI_Readme Just a quick tutorial on how to use the GUI version. (see below for a full tutorial of the GUI functions.) ROOT
This tutorial was written by ffgriever.
PS2PSXe GUI Tutorial:
The GUI version [ps2psxe-gui-pack.elf] supports only CD/DVD, mass [USB HDD] (multiple, of course) and internal HDD. The host/Network/smb support was planned, but I didn't have time to add it. If you want these, you'll have to use ps2client, but you won't be able to do nothing with the GUI..
!NOTICE!
You can get back from emulated game to the GUI by using a combo L1+L2+R1+R2+UP. -- Also keep in mind that GUI will work only with USB (MASS) and HDD mode. It will not work with HOST/NETWORK using PS2Client and PS2Link. You will be able to launch the GUI by using the combo above, but you will not be able to save any settings nor load another game from your Network.
ONE BIG, FAT ISSUE
There is a huge bug in initialization code. If the GUI is launched through uLE (maybe some other apps), the pad behaves a little bit weird. The mode button doesn't work at all, which leads to a problem if a PSX game won't turn the analog mode on by itself (and supports analog pads). The same for digitize pad option (if it is used, the analog mode is turned off by default, but can - and should - be enabled by the user). There is a simple, temporary solution for this issue. While in main menu, just press select and navigate to the GUI directory, then launch it again. Not the pad will be fully functional. I'm not sure what causes this problems. It doesn't happen when launching directly from FMCB or through ps2link.
Start Emulation
It does exactly what it says.
If no CD image nor PSX Executable was selected, the PSX internal card manager/CD player will be launched (see image below).
Attachment 37067
If both CD image and PSX Executable are selected, CD image takes priority. If bios, CD image or executable cannot be opened, appropriate warning will be displayed and emulation won't start.
Open cdrom image
A simple explorer window will be displayed (see image below). Navigate it and select the cd image you want to emulate. Only full 2352 bytes per sector images are supported. By default only ccd, cue and bin files are displayed (case sensitive!), but pressing R2 will remove the extension mask and display all files.
IMPORTANT: It's crucial that you don't use "spaces" within the folder directories paths and titles of the games. Or else the games will not load. This is important for USB, HDD, and also Network.
Examples:
Correct: mass1:/ps1games/AceCombat2.bin
Incorrect: mass1:/PS1 Games/Ace Combat 2.bin
Attachment 37073
Open PSX executable
Just as with the above option, an explorer will be launched. By default only files with PSX and psx extensions are being shown. Pressing R2 will
let you see all the files.
Configuration
Opens configuration screen.
Hidden Menu
If you press SELECT on the main menu. You can then see all your devices and launch any ELF you have. For example if you wish to return back to uLE, simply fine your BOOT.ELF in the device you keep it in. And also launch any other ELF if you wish.
L1/R1 buttons
Scrolls 1 page up or down in the navigation of files.
L2/R2 Buttons
Enable/Disable the extension filter in the files to show only the required files, or all the files available in a device.
START button
Show credits and info about the emu.
System
Configures system options.
Video
Configures display and gfx options.
Audio
Configures sound options.
Input
Configures controller options.
Save default config.
Saves current configuration in "default.cfg" file. If this file is present in the directory the GUI is launched form, it will load it automatically
at start. It quite helpful if you're launching from hdd. After IOP reset, the pfs mount-points are not available anymore and since we have no
information on the real path (partition part is missing), you have to specify the real path in the system menu. Once saved, the GUI will load
default config at start and will not bug you for the real path anymore ;).
There is a known bug that affects Internal HDD -- See Internal HDD (Phat PS2 Consoles Only) below for more info about this.
Load default config
Loads a configuration file of your choice. The name may be a little bit misleading, as it can be any configuration you want, not just the default
config.
Save game config
If per game config is enabled, this option will save a configuration file for a currently selected CD image/executable. It will be stored in the
same directory that the image/exe and will have the same name (extension changed to cfg).
Delete game config
Deletes the per game config file, so that the selected game will use current config instead if the saved one.
PS2PSXe path
Lets you choose emulator path. Necessary if you're launching from hdd and the path is obfuscated either by fake-host or pfs mount-point. Can be left blank if launching from mass - the path of the GUI will be used by default.
Select BIOS
By default the PS2PSXe is using bios/scph7502.bin. If you want to use a different bios file, this is the option you need to use.
Per game config
This option will let you use separate config for every game. If a file "image_name.cfg" exists in the same directory as the image, it will be
loaded at launch and replace the current config.
The emulator will also use the "image_name_0.mcr" amd "image_name_1.mcr" for memory cards (in the same directory that the image file itself).
This option is not implemented yet.
Stack pointer fix
Fixes some stuff related to stack pointer optimizations (disables some stuff). Should not be needed anymore, but try it if a game crashes.
Alt. exception handling
Uses alternative exception handling method. Should not be needed anymore, but you might get it a chance if a game crashes.
Loop check
Disables most of the automatic libcrypt patching stuff. There is no real need for this until you want to test sub-channel support (it's not really
needed, the auto patcher does a great job, there is a chance that it handles pretty much every libcrypt implementation). //yup, it an auto
crack, more or less
Show FPS
FPS, resolution and mode will be displayed at the top of the screen. Might occasionally lead to some additional texture corruption (I was going to fix that, but I forgot about it ;) )
Interpreter mode
Enables interpreter CPU emulation instead of the re-compiler. Terribly slow, but fixes some games. Currently disabled, as some changes in recent versions prevent it from working (should be quite easy to fix).
Signal type
Let's you choose the video signal type. The options are:
- - PAL - obvious, default
- - NTSC - obvious
- - Auto PS2 - uses the region of your PS2 to choose between PAL and NTSC *
- - Auto PSX - uses the region of the game to choose between PAL and NTSC *
* - Auto PS2 and Auto PSX does not work yet. Keep in mind that the default setting is PAL, so if you have a NTSC TV only, make sure to change this setting before launching a game.
The recommended settings are NTSC for NTSC games and PAL for PAL games.
Frame limiter
Uses frame limiter if turned on. There are games that work at twice the nominal speed, etc. Might by quite helpful.
Depth
Lets you choose the video buffer depth. The default setting is 32bit. Use it only if you're experiencing a lot of texture corruption or great
slowdown at heavy vram usage.
Dithering
Enables dithering in 16 bit mode. Has no effect in 32bit mode.
Polygon filter
The filtering of the polygon textures (usually in-game "3D"). Can be set to bilinear for most games. Should be set to nearest for games that tend to use polygons as sprites (Valkyrie profile, star ocean second story and similar)
Sprite filter
The filtering of the sprite textures (usually in-game "2D"). Many games look much better if it is set to nearest. IMO a must for final fantasy and
similar games (though nearest filtering works fine only when using PAL mode for PAL games, NTSC mode for NTSC games and the game's horizontal resolution is either 320 or 640... If it's 256, 512 and 368, black bars might be displayed).
Screen X offset
Screen Y offset
Moves the display on the screen. It's not interactive, so you'll have to set it and launch the game to test whether the result is pleasing or not.
Use it if your TV is mis-calibrated or some menus at edges are being cut due to too big over-scan.
Emulate sound
Enables sound emulation (launches ps2psxe.elf if enabled and ps2psxen.elf if disabled).
Disable threads
Will use psx's hsyncs to transfer the execution to the audio plugin instead of letting spu be executed constantly in another thread. Threaded
mode is a little bit faster in some games, but usually (not always though) produces additional cracks in the sound playback. It's really very game dependent. You'll have to check it for yourself.
Right now threaded mode is a must if you're launching from host/smb (otherwise the game lags terribly if sound is being played and cdrom image is being accessed at the same time - IOP thread priority problem ;) )
I personally keep this setting on (threads disabled) for most of the games.
Wait for SPU IRQ
You most likely know this option from many other emulators and spu plugins. Fixes some games like valkyrie profile. It's worth a try if the
game freezes during sound playback, the sounds are played only partially, the sounds sound weird, etc, etc. There will be some additional slowdown if this option is enabled (not that big, though).
Digitize pad
When enabled, the emulator will always return to the game, that digital only pad have been connected. But, if you switch the mode button on (the little on between start and select), it will use left analog stick as if it was d-pad and right analog stick as if it was R1/L1. Quite useful for
games like FF7 that do not support analog sticks at all. This option might not worked if GUI have been launched from uLE (see paragraph 2 for a solution).
Running PS2PSXe:
There are three methods to run PS2PSXe: USB, HDD, and Network
USB HDD (FAT32)
Easy Method: Using GUI version:
Step 1: Put all the files and included folders of PS2PSXe on the root of your USB HDD. (see picture below): -- I currently recommend using the version named: ps2psxe_jay-jay_bundle-V2.rar -- it can be found attached in this thread: http://psx-scene.com/forums/f292/ps2...pdates-105355/
Attachment 37154
Step 2: make sure to create a folder in your USB HDD for your games. Simply name it games, and copy there your BIN, CUE, and CCD files.
Note: that the developer of the emulator says it's not necessary to use CUE and CCD files, that the BIN file should be all you really need--but I am not really clear on that yet, so you may want to keep that in mind.
Note2: do not use spaces within the folders and file names. It will not load the games if you do it. Also make sure you don't use long title names on the game files. (see the GUI tutorial for examples.)
Step 3: Now plugin your USB HDD to your PS2. Make uLE (or whichever way you load ELFs on your PS2) and load ps2psxe-gui-pack.elf. See the GUI Tutorial to learn how to make configurations and load your CDROM games and also save your configurations so you don't have to adjust your settings (like select NTSC if your TV doesn't support PAL and etc.) Remember that when you search for your games, you will be looking inside MASS for your USB HDD.
When you want to return to the GUI while the game is loaded, just press this combo L1+L2+R1+R2+UP -- that should return you to the GUI and then select another game and etc.
To Quit or Exit the Emulator:
You can either press the power button on your console to turn off the emulator or press SELECT button in the main screen of the GUI--it open a screen of all the devices and you can then go where you keep BOOT.ELF of uLE to quit the emu or jump to another ELF to exit.
Note: This button is described in the "ONE BIG, FAT ISSUE" section above in the GUI Tutorial, which is used also to fix the problem about the bug in the initialization code for the pad when you quit the emu and reload the GUI.
Internal HDD (Phat PS2 Consoles Only)
Tutorial by ElPatas
Internal HDD uses the GUI like the USB (MASS).
Step 1: Internal HDD requires the files to be stored differently than from USB (MASS). In USB (MASS) the files need to be placed at the root of the entire USB (mass) HDD, but, with the Internal HDD, you need to create a data partition to later put them in.
How to Create a Data Partition:
- Run uLaunchELF
- Goto FileBrowser > MISC > HDDmanager
- Press R1 and select Create
I have mine named PS2PSXe, and I created a folder inside with the name of EMULATOR where I copied all the files of the PS2PSXe with uLE. -- I currently recommend using the version named: ps2psxe_jay-jay_bundle-V2.rar -- it can be found attached in this thread: http://psx-scene.com/forums/f292/ps2...pdates-105355/
This is the route of my partition: hdd0:/+PS2PSXe/EMULATOR/
And this is all, there is no more specific things in the internal HDD to install or run the emulator with.
Step 2: You can create a folder in your Internal HDD partition for your games. Simply name it games, and copy there your BIN, CUE, and CCD files. You can also store them on the root of the partition, and simply look for them using the GUI, by selecting hdd0:/
Note: that the developer of the emulator says it's not necessary to use CUE and CCD files, that the BIN file should be all you really need--but I am not really clear on that yet, so you may want to keep that in mind.
Note2: do not use spaces within the folders and file names. It will not load the games if you do it. Also make sure you don't use long title names on the game files. (see the GUI tutorial for examples.)
Step 3: Make uLE (or whichever way you load ELFs on your PS2) and load ps2psxe-gui-pack.elf. See the GUI Tutorial to learn how to make configurations and load your CDROM games and also save your configurations so you don't have to adjust your settings (like select NTSC if your TV doesn't support PAL and etc.) Remember that when you search for your games, you will be looking inside hdd0:/ for your Internal HDD.
When you want to return to the GUI while the game is loaded, just press this combo L1+L2+R1+R2+UP -- that should return you to the GUI and then select another game and etc.
To Quit or Exit the Emulator:
You can either press the power button on your console to turn off the emulator or press SELECT button in the main screen of the GUI--it open a screen of all the devices and you can then go where you keep BOOT.ELF of uLE to quit the emu or jump to another ELF to exit.
Note: This button is described in the "ONE BIG, FAT ISSUE" section above in the GUI Tutorial, which is used also to fix the problem about the bug in the initialization code for the pad when you quit the emu and reload the GUI.
A few bugs known with Internal HDD -- thanks to member: ElPatas
http://psx-scene.com/forums/f292/ps2...tml#post992834
- You can't save more than once your configuration in the GUI when you play a game or leave the emulator, from what ffgriever said it's a problem related to check the partition for when saving the config files, and from what i remember this bug is not fixed in r202 or other older versions.
_- Another bug also related to the internal HDD and uLE, is if you use for example a custom language for the uLE stored in a partition of the internal HDD. When uLE is launched and the file is read from Internal HDD, if you launch the emulator it always freezes. Solution: You need to place the custom language for the uLE in a USB device and then it works fine.
HOST / Network (PS2Client & PS2LINK)
Difficult Method: PS2Client and PS2LINK:
(Keep in mind that running PS2PSXe on Host/Network is a bit difficult--definitely not for noobs--especially when you want to trigger settings for certain games that require special settings. This is why it's best to use the USB method above, because with Network method, you won't be able to use the GUI version above.)
Credit goes to dlanor @ psx-scene.com for providing the ps2client.exe and PS2LINK.ELF that works best with PS2PSXe
ffgriever, the developer of PS2PSXe Emulator, had provided another updated version to ps2client, but it was a bit faulty. So for best results use this version instead. Out of several tests, I found dlanor's version to be the best of the two.
So I've uploaded my modified version and called it: PS2LINK_to_PS2Client_by_Jay-Jay.rar to make sure you download the correct version and not the other one that doesn't work very well. You can find this download at: http://psx-scene.com/forums/f292/ps2...pdates-105355/
When you extract the RAR file you should have two folders:
#
Name
Definition
1 ps2link_PS2PSXe this entire folder (with all files inside) you will copy it to the root of your PS2's mc0 or mc1 memory cards. You can also put this inside your USB (MASS). (see below for tutorial). 2 PS2Client this folder contains 9 files which you will copy or move them to your PS2PSXe folder in your PC (see below for tutorial).
The 5 Files that you should see inside the ps2link_PS2PSXe folder:
#
Name
Definition
1 PS2LINK.ELF this is the ELF file that you will run on your PS2 with uLE or any other exploit you use to launch ELF files. This is the tool that will make your PS2 ready to receive data from your PC from ps2client. (see tutorial below) 2 IPCONFIG.DAT this file you must edit and make sure it has the correct IP address of your PS2 on your network as well as the Subnet Mask and also the Default Gateway of your Network. (see below for turorial) 3 icon.icn icon that will show on your PS2 Browser so it doesn't show a corrupt file on my mc cards. 4 icon.sys system info so your PS2 Browser knows what the name of that folder in your mc is. 5 README_PS2LINK.txt just instructions that I also cover in this tutorial below.
The 9 Files that you should see inside the PS2Client folder:
1 ps2client.exe this is the program that will connect with your PS2 when you a bat file from your PC. 2 pthreadGC2.dll basically the driver that needs ps2client.exe to run with (this file should always be placed next to where ps2client.exe is.) 3 PS2PowerOFF.bat turns OFF your PS2 when you run it. 4 PS2Reset.bat allows you to reset PS2PSXe, so you can then load another game. 5 run_PS1_CD_NTSC.bat use this if you have a NTSC console 6 run_PS1_CD_PAL.bat use this if you have a PAL console 7 run+log_PS1_CD_NTSC.bat use this for NTSC console at the same time it will create a logfile so you can copy and paste the information -- in case you need to share so we can troubleshoot the problem why the game doesn't work correctly. 8 run+log_PS1_CD_PAL.bat use this for PAL console at the same time it will create a logfile so you can copy and paste the information -- in case you need to share so we can troubleshoot the problem why the game doesn't work correctly. 9 README_PS2client.txt just instructions (the sames once below in the tutorial)
How to run PS2LINK?
Be sure to download: PS2LINK_to_PS2Client_by_Jay-Jay.rar http://psx-scene.com/forums/f292/ps2...pdates-105355/
credit goes to dlanor @ psx-scene.com for compiling this for PS2PSXe
Instructions:
- In order to make sure that you can make the connection between your PS2 and PC, you must edit the IPCONFIG.DAT file with notepad, that's inside the "ps2link_PS2PSXe" folder and enter the IP addresses of your PS2, followed by the Subnet Mask, and then the Default Gateway of your Network. (see picture below)
Attachment 37113
Attention OPL SMB Users!
For those that use OPL on SMB/Network, you are in LUCK! :) You already have a working copy or IPCONFIG.DAT file. You need to find it in the SYS-CONFIG folder in your main FreeMCBOOT mc0 or mc1 card and COPY it (do not move) to the ps2link_PS2PSXe folder. -- If you move it, instead of copy, OPL will fail to connect to your PC the next time you run it, so a copy needs to stay in the SYS-CONFIG folder.
If you don't know nothing about Network Configurations, I suggest to use Google and do a search to learn. After you do this Step 1, then proceed to Step 2.
_- Copy the ps2link_PS2PSXe folder to the root of your mc0 or mc1 card. -- You can also run this from a USB (Mass) if you choose to. Make sure to keep all the files inside that folder when you transfer it to your PS2 mc cards or USB. (see image below).
Attachment 37114
Note: I created some special icons so your memory cards don't show "corrupt" files when you browse your mc cards. :) (see picture below)
Attachment 37116
_- Then setup uLE to launch the file that's inside this folder: PS2LINK.ELF - If you did everything correct, you should get a black screen with white colored text and saying "ready" at the end. It's now ready to receive information from PS2Client.EXE from your PC. (see picture below)
Attachment 37115
_- Now follow the instructions for PS2CLIENT, to run it from your PC. (See Below for Tutorial)
Be sure to download: PS2LINK_to_PS2Client_by_Jay-Jay.rar http://psx-scene.com/forums/f292/ps2...pdates-105355/
How to run PS2Client?
- First open the folder "ps2link_PS2PSXe" and read the README instructions there. Once you have everything set there, proceed to step 2 below. (You can also read above the tutorial "How to run PS2LINK" above.)
_- Copy all the files inside the folder "PS2Client" and put them inside your PS2PSXe folder on your PC. It's best to be using the ps2psxe_jay-jay_bundle_v2.rar -- it can be found attached in this thread: http://psx-scene.com/forums/f292/ps2...pdates-105355/
All these files must be at the root of the PS2PSXe folder alongside with ps2psxe.elf and other files. (see image in the below) All nine files must but put in there for this to work. (I've highlighted all 9 files with red squares -- including the filelog.txt file in green--more info about this below)
Attachment 37119
_- Now it's important where you placed the PS2PSXe folder there are no spaces within the file directory path. (see the red arrow that points to my directory (image above). Also it helps that your directory path to PS2PSXe is short, so don't bury it in your hard drive with so many sub folders and etc. This can also cause a problem.
_- Now to run a PSX game. You can put a folder inside the PS2PSXe folder and call it "games" and put all your CDROM PSX games inside there or you can choose another directory in your PC to keep the games. It's up to you.
IMPORTANT: It's crucial that you don't use "spaces" within the folder directories paths to PS2PSXe and also the titles of the games and their paths. Or else the games will not load. This is important for USB, HDD, and also Network.
Example for Game Title:
Correct: AceCombat2.bin
Incorrect: Ace Combat 2.bin
Example for Directory Paths:
Correct: K:/PS2PSXe/
Incorrect: K:/PS2 PSxe/
Correct: K:/GamesCollections/PS1/AceCombat2.bin
Incorrect: K:/Games Collections/PS 1/Ace Combat 2.bin
_- Okay, so you got PSLINK running on your PS2, and you have put all the ps2client files inside your PS2PSXe folder on your PC, and your games are ready and they don't have spaces within the directory paths and folders or titles of the games.
Well all you need to do is drag and drop the GAME BIN file to the run_PS1_CD_***.bat file. Just make sure it's the correct one, according to the region of your PS2. So choose which of the two BAT files to drag and drop your BIN file into.
run_PS1_CD_NTSC.bat for NTSC
run_PS1_CD_PAL.bat for PAL
** I'd suggest to delete one of these files that you'll never use. This way you don't make a mistake. I use NTSC, so I don't have the PAL file anymore in my PS2PSXe folder. The same goes with the version that created a filelog when I launch a game.
NOTE: Also you can create shortcuts of these bat files and put then near your Games, that's if you keep your games in another directory path of your PC. As long as the main bat sits in the PS2PSXe folder, the shortcut will always point to it. You can then drag and drop the BIN files into the shortcut bat file and it will still launch PS2Client.
_- Once you drag and drop the BIN file into one of these BAT files, the game should launch. If you have a firewall, you need to make sure to accept that ps2client makes the connection to your PS2 and that's it. Once you do this a DOS window will appear on your screen and it will generate some data while you are playing the game. (see picture below) I strongly suggest you keep this window open when you are playing a game. Close after you have shut down your PS2 or when launching a new game.
Attachment 37121
_- Game doesn't work? Well there could be problems. Be sure to check out my current PS2PSXe Game Compatibility List http://psx-scene.com/forums/f292/ps2...e-list-105342/
_- Can I tweak some settings so the games work better?
Yes. I plan to add a special tutorial about this here. And I will also teach you how to make custom bat files for each game you run, this way it can have it's own tweaked settings. If you are an expert, look at the commands below for PS2CLIENT.
_- How do you create the bat files?
dlanor was the person who taught us how. See Running PS1 games by drag-drop Tutorial below...
_- I have more questions?
Please read this entire tutorial again or post a question about your problem by creating a new post at: http://psx-scene.com/forums/official-ps2psxe-forum/ be sure to list all your information about your setup and console so we can help you. Don't just write Help, that's not enough info for us to make any suggestions.. lol DO NOT POST YOUR QUESTION IN THIS THREAD - I WILL DELETE IT!
Running PS1 Games by Drag-Drop Tutorial
Tutorial written by dlanor.
Here is a small ".bat" script that you can use for simpler testing of multiple games, simply by drag-dropping ".ccd" or ".bin" files from wherever you normally keep your PS1 games onto this batch file, while PS2Link is running on the PS2. The batch will then launch ps2client with a suitable command for launching PS2PSXe on the PS2 with an argument causing it to launch the drag-dropped PS1 game from whatever storage location it has on the PC.
This allows you to test any number of games without moving a single one of them from their normal storage location on the PC (as used with PS1 emulators on the PC).
What you do need to move together into the same folder as PS2PSXe is only the PS2Client stuff (including the DLL if using my versions as made for uLE) as well as this script file. But shortcuts may be placed anywhere for the drag-drop convenience (including desktop).
The script itself is quite simple:
**By default PS2PSXe will load games as PAL, in order to prevent this, you need to add the -ntsc command. See above to notice where I placed it in the script ~ Jay-JayCode:@echo OFF
REM ------------------------------------
REM drag-drop a PS1 CD image file here, to invoke PS2PSXe for that game
REM ------------------------------------
if EXIST "%~f1" goto ArgsOk
echo Sorry, but I have no idea what you want from me.
echo I need a PS1 CD image file for PS2PSXe to launch.
goto ExitPause
REM ------------------------------------
:ArgsOk
%~d0
cd "%~dp0
ps2client -h ps2 execee host:ps2psxe.elf -cdimage=host:/%~f1 -ntsc
echo The emulation has finished (should never happen)
REM ------------------------------------
:ExitPause
pause
:ExitDirect
REM ------------------------------------
In the ps2client command above, as always for my ps2client usage, the word "ps2" represents the ps2 IP address. If you have not edited your system's 'host' file like I have then you will need to edit the batch file to use the numeric IP address of the PS2 in that position instead of the "ps2" string.
The code listing above was just to show you how simple it is, but don't bother with cut&paste here, as I've also attached it in a ZIP as well.
For more advanced testing it may be useful to make multiple renamed copies of that batch file with differing PS2PSXe options specified in its launch argument.
(Btw: This is NOT the batch GUI stuff I spoke of earlier, as that is much more complex.)
Edit:
For some weird reason that I don't myself understand, this script does not work with dropped ".cue" files, though it does work when dropping the ".bin" file of each such game. And I have no clue as yet as to why it fails for the ".cue" files...
Best regards: dlanor
PS2Client Commands
You can add more PS2Client Commands on your .bat files. You just need to add it to the line I have highlighted in red (see below). Now notice the extra commands I have added next to it in blue. You need to separate these commands with a "space" in between them. See below for a full list of commands and their description and purpose.
Basically these commands are designed to make certain games work best in PS2PSXe using PS2LINK and PS2Client. There is no need to do this if you use the GUI Version--and keep in mind that the GUI version does not work with HOST/Network.
Here is the code of a .bat file. Notice the changes: (when you are done creating this file with notepad, simply save it as a .bat file (you can name whatever you want. I would suggest to name it like your game, this way you know that's the bat file for your particular game.) For example: AceCobat3.bat - then you create a shortcut to this bat, and put it wherever you keep that game. Then use the shortcut to drag and drop the game. (see above tutorials for more details about this function).
Code:@echo OFF
REM ------------------------------------
REM drag-drop a PS1 CD image file here, to invoke PS2PSXe for that game
REM ------------------------------------
if EXIST "%~f1" goto ArgsOk
echo Sorry, but I have no idea what you want from me.
echo I need a PS1 CD image file for PS2PSXe to launch.
goto ExitPause
REM ------------------------------------
:ArgsOk
%~d0
cd "%~dp0
ps2client -h ps2 execee host:ps2psxe.elf -cdimage=host:/%~f1 -ntsc -nofps -digitizepad
echo The emulation has finished (should never happen)
REM ------------------------------------
:ExitPause
pause
:ExitDirect
REM ------------------------------------
List of PS2Client Commands
Commands provided by ffgriever.
Command Description -cdimage=PATH Path to the cd image. 2352 bytes/sector images supported. CUE and CCD cue-sheets are supported. Multiple tracks in ccd/cue are supported but only if all tracks are in a single file (no multiple files). For multiple files just point to the first track (it contains the data). PATH can be either relative to ps2psxe executable or full path. -exepath=PATH Launches PSX exe file (for intros, demos and such). -bios=PATH Bios path (bios/scph7502.bin by default) -digitizepad Internally switches pads into digital only mode (visible to PSX code). If you then manually enable analog mode (small analog switch at the center of the pad), then the left analog stick will act as D-PAD and right analog stick will act as R1/L1 horizontally. It's a nice features for games that do not support analog sticks at all (like FF7) -spfix Stack pointer fix. Try it if something goes wrong. It might be able to fix some games. It disables one of the optimizations (not many games make any use of it anyway)... -xoff=OFFSET -yoff=OFFSET Positions the screen on TV. You can use it to correct the image position if your TV leaves eg. black bars at right or left side. -sub Enables subchannel support. It is really necessary only for libcrypt protected games... For two years or so not even for them. It's kind of obsolete as the emulator has automatic patch for libcrypt, so unpatched games like FF9 PAL will work even without subchannel data. The subchannel file has to have the same name as the img/bin/ccd/cue, just with the extension being .sub (so if the image is ff9pald1.cue, then the subfile is ff9pald1.sub). It's not really necessary anymore. -excep Disables some exception stuff. Use it if a games experiences problems. I believe this one should not be necessary anymore, but I left it... Didn't see a game that would need it in year or so. -4ever Disables most of the automatic libcrypt patches (not all of them though). It's there just for testing, really. You won't have to use it until you want to test subchannel file support. -32bpp Switches into 32bpp mode. I really RECOMMEND using it unless the game has texture problems (clut problems to be exact). It's not default only because it's not native PSX format ;). So use it unless it causes problems. -nofps Disables resolution/mode/fps display (the yellow crap at the top) -nosprtf Disables filtering for sprites. (2d images, though not all 2d images are sprites). Needed for 2d backgrounds in many games (a must for all final fantasy games - all ff games).
If you specify both -nosprtf and -nopolyf, filtering will not be used at all.-nopolyf Disables filtering for all polygons that are not sprites ;).
If you specify both -nosprtf and -nopolyf, filtering will not be used at all.-nodith Disables dithering in 16bit mode. -ntsc Switches display into NTSC mode if your TV doesn't support PAL. DON'T use it unless you really have to. -limit Uses the frame limiter -nothread Disable threads for the audio -spuirq Uses the SPU IRQ for the audio
Save Screenshots Tutorial
You can take screenshots while having a game loaded in PS2PSXe. You just need to run this combo with your controller:
L1+L2+R1+R2+triangle+circleIt will save a screenshot of your game in the snap folder. Allays using executable (slesxxxxx) with counter (always checking for files that are already there, so it doesn't overwrite files if used in multiple sessions). Screenshots are saved in tim2/TM2 format. You will need Tim Tool to be able to convert the image to another image format. Google Tim Tool.
Radshell
According to our member ELPatas,
He explaisn that Radshall used to be a feature they used early on when the Emulator was being built and it did not have a GUI. So radshell was used in order to run scripts to make the games load from USB and Internal HDD. This is not needed anymore since the introduction of the GUI.
Some of the information written below was copied from the Developers preview post when he first introduced this project. Some of the information might be old or only referring to the early versions. I copied it here, since some of the information may still be helpful to complete the above tutorial....
The emu supports both PAL and NTSC display, but I REALLY RECOMMEND leaving the default PAL output. Why? Well, it's the only mode I use. Many fixes were made to make PAL games show less glitches in PAL mode... When you switch the display to NTSC it most often will show more glitches.
The PAL scph7502 bios is recommended to run games.
PAL games are recommended due to two simple reasons:
1. PAL games require only 50fps to be at 100% speed (NTSC games require 60, so PAL games are easier to emulate).
2. PAL games should look nice when using PAL display mode... NTSC games will always look much worse.
(well, I live in Europe. It's PAL region, so everything has been coded with PAL games and PAL TVs in mind. Actually, the option to switch display into NTSC mode has been added in rev163... so no fixes for that)
So use NTSC display mode only if your TV doesn't support PAL (yes I know this sucks... Most TVs in Europe nowadays support NTSC... On the other hand, most TVs in US do not support PAL... What a crap...).
Many of the parts of the emulator (like cue/ccd parser) have not been changed/updated for few years (the time I created them in 2007 or so). I focused on the most important parts of the emu... Once the time comes, everything will be replaced by proper code rather than some temporary solutions.
You shouldn't experience any problems launching it if you know what you're doing... Otherwise it might crash before even showing you anything.
The emu doesn't provide any drivers or modules other than the parts of the emu itself. But thanks to this it supports any devices that you will load modules for. I've tested it with internal hdd, usb, lan, dvd and even ps2 mc. I recommend using internal hdd or lan (host device). You can use usb, but the asynchronous cd plugin is tweaked for high bandwidth media... So when using with usb, some stuttering might occur here and there.
There is no real requirement for the modules present before the emu is launched except one. The emu REQUIRES IOMANX module to be loaded before launching it (older PS2link versions were loading it by default, but you will have to load it manually for newer ones or change it and recompile it).
Attention Newbies:
DO NOT ASK QUESTIONS IN THIS TOPIC!
THEY WILL BE DELETED!
Click Here to start a new Topic and ask a question about PS2PSXe:
http://psx-scene.com/forums/official-ps2psxe-forum/
