PCSX 1.6 beta testers wanted

[jivera]

Alright, attached is a recent build of PCSX 1.6. Anyone interested may feel free to download a copy (but be aware this is a development release so stability is not guaranteed). Just unzip it to the same directory as your current pcsx.exe executable is along with the included .dll. It's not perfect and there aren't many changes from PCSX 1.5, but I'm sure it'll be easier for anyone interested in bugtesting but without compiler access to download this.

If you can find a bug that's easily reproducable, please post it here. I will look into more advanced bug tracking methodologies if it proves necessary.

-jivera

p.s. This is a drastically different approach than PCSX has taken in the past and PCSX2 is taking now, but I still encourage you to respect their beta release policy. Please do not use this opportunity as leverage against the PCSX2 developers to make their betas available to the public. I believe PCSX can better benefit from open testing than private builds - I hope my faith in the community is not misplaced.

[Yeloazndevil]

I'll test it ;) (since I beta tested 1.5 ;))

[Razor Blade]

Damn I would but I have no DVD Rom. :p

[Chrono Archangel]

Damn I would but I have no DVD Rom. :p

why would you need a DVD Rom???.....
(nice sig....once again :D)

[Razor Blade]

Thanks. Cuz most ps2 games like 99% of them are on dvd.

[_E_]

Thanks. Cuz most ps2 games like 99% of them are on dvd.

err,..this is about the Playstation emulator PCSX, no need for DVD drives in this one. I think you are confused between PCSX and PCSX2 :p

Yours,
-Elly

[Razor Blade]

LOL. OMG I am so lame. I should have read better. LOL. Uh yea sorry bout that. :heh:

[Chrono Archangel]

LOL. OMG I am so lame. I should have read better. LOL. Uh yea sorry bout that. :heh:

:p i didnt want to directly insult you :p so i ask a simple question lol
but i knew you thought about PCSX2 lol

[Razor Blade]

I guess my mind has been on PCSX2 lately.

[jivera]

yeloazndevil: I'll test it ;) (since I beta tested 1.5 ;))

Sounds good.

It looks like at least 19 other people downloaded it too, so hopefully I can get some useful feedback. :)

-jivera

[Cyberman]

yeloazndevil: I'll test it ;) (since I beta tested 1.5 ;))

Sounds good.

It looks like at least 19 other people downloaded it too, so hopefully I can get some useful feedback. :)

-jivera

I would recomend having some critera be provided by the beta testers.
Namely
OS information
Video Card and Driver information
etc. etc.

In fact.. what might help is a little button in PCFX you click to dump there complete PCSX configuration to the clipboard.

Feed back method would be cool too. Chaos sucks and people are prone to causing it ;)

Erswhile
I'll PM my puzzling problem with the beta :)

Cyb(ie)

[fivefeet8]

Here's a preliminary report. I tried out Metal Gear Solid(US) with this new beta of PCSX and it's damn near perfect.

System specs are in my sig. Using the Forceware 52.16 drivers.

Plugins used:
Petes ogl1 gpu pluggin(PC fps Calc enabled)
PEOPS SPU plugin(MGS fix enabled)
PEOPS CDr plugin
Bios7502
Harakiri Pad Plugin

This is actually the first PSX emulator that Rumble actually works in MGS. Yes, you heard me right, Analog+rumble works in MGS in PCSX!!! I'll test some more games later. Great work on PCsx dude!!! :guitar: :thumb: :thumb:

[Dark Watcher]

jivera...we too were a PCSX beta tester...we are happy that you are continuing the project..we will post results soon

[TheGodfather]

Im testing it too.
No bugs yet.
And everything seems to be the same.

Can you tell us what did you added or fixed?

Thanks for continuing the development of this great emu.

[jivera]

TheGodfather: Can you tell us what did you added or fixed?

Ahh, sorry. Probably the only user noticable change should be that it (hopefully) supports -runcd and -runcdbios for command line arguments that a launcher or something can pass to it. I'll try to add support to allow running of .iso's and .exe's, but the Windows code for that is somewhat convoluted so we'll see.

This "release" was mostly intended to just incite some more bug testing and feedback since I'm not sure what bugfixes or feature requests the community wants out of PCSX now.

-jivera

[dukenukem]

Nice to see that you have so much faith in this community to post a build of it here instead of making it private,i will test it out on my games too when i have free time:).

[Guruma]

The CD-Rom plugin P.E.Op.S CDR Driver 1.3 Doesnt recognizes my CD drive and virtual CD :(

[Chinoz]

I'll start testing as soon as i finish d/l-ing the cdrom and controller plugins :)

edit Ok I have 2 problems.
1) Could not load CDR plugin Plugin\ (am using mooby2 plugin, and test says that it should work)

2) Couldn't detect controller plugins

[jivera]

Guruma: The CD-Rom plugin P.E.Op.S CDR Driver 1.3 Doesnt recognizes my CD drive and virtual CD :(

Does it work for PCSX 1.5 or any other emulator?

Chinoz: 1) Could not load CDR plugin Plugin\ (am using mooby2 plugin, and test says that it should work)

I've noticed plugins reporting they should work correctly and failing too, but I'm not sure if it's a PCSX or plugin specific issue (I'll try to check).

2) Couldn't detect controller plugins

Did PCSX 1.5 recognize them? Are they in your plugins/ directory?

-jivera

Edit: Upon inspection of the source code, it seems like the logic for error checking on PCSX's side is correct so it must be plugin authors unanimously decided not to actually test anything.

[fivefeet8]

Guruma: The CD-Rom plugin P.E.Op.S CDR Driver 1.3 Doesnt recognizes my CD drive and virtual CD :(

Does it work for PCSX 1.5 or any other emulator?

Chinoz: 1) Could not load CDR plugin Plugin\ (am using mooby2 plugin, and test says that it should work)

I've noticed plugins reporting they should work correctly and failing too, but I'm not sure if it's a PCSX or plugin specific issue (I'll try to check).

2) Couldn't detect controller plugins

Did PCSX 1.5 recognize them? Are they in your plugins/ directory?


The PEOPS CDR 1.4 plugin recognizes my cd drives fine. Your either gonna have to install an ASPI layer, or use a real psx bios instead of the Internal HLE PCSX bios.

Mooby2's cdr image plugin works fine as well for me. Loads up isos just fine. Check your configuration of PCsx. Again, if your using the internal HLE bios, use a real psx bios. I'm using bios 7502.

PCSX detects all controller plugins fine for me. I have 4 pad plugins listed in the pad plugin config. I'm using the Harakiri pad plugin.

[Guruma]

Guruma: The CD-Rom plugin P.E.Op.S CDR Driver 1.3 Doesnt recognizes my CD drive and virtual CD :(

Does it work for PCSX 1.5 or any other emulator?



I just checked and its probably ASPI layer. I recently reinstalled system and this plugin doesnt work in any emulator so its probably ASPI. Sorry for the problem!

-=Guruma=-

[FLaRe85]

I have another suggestion. Could a registry entry be added into the PCSX settings key giving the version number so that we front-end authors can differentiate between the new versions containing the command-line support and previous verisons that do not have the feature?

[Chinoz]

I'm using the Harakiri too. But no, it doesn't show
Any err step-by-step guide for the installation of the controller plugs?

[jivera]

ShADoWFLaRe85: I have another suggestion. Could a registry entry be added into the PCSX settings key giving the version number so that we front-end authors can differentiate between the new versions containing the command-line support and previous verisons that do not have the feature?

I'm not sure a registry entry is the best solution - there's a single registry shared by every version of the program, but the -runcd(bios) support (and any future features) is executable dependant... (people with beta and stable releases would have problems).

In the case of command-line support not existing, what do you do? I don't think PCSX 1.5 will complain if you pass it unrecognized command lines. Maybe you do some black magic to manipulate the menus so people don't have to manually click some stuff - I've never used a front-end so I don't know.

-jivera

[fivefeet8]

I'm using the Harakiri too. But no, it doesn't show
Any err step-by-step guide for the installation of the controller plugs?

Listen, The Harakiri pag plugin was designed for FPSE. So when you unzipp it's contents into the plugins folder, it actually creates a folder called "FPSE" in the plugins folder. Go into this "FPSE" folder and copy/move those files into the plugin directory. Or if you have gotten the Harakiri pad plugin to work in other emulators, you can assign the plugin directory of PCSX to point to that plugin folder. Pretty nifty to be able to assign a plugin folder instead of every PSX emu having it's own plugin folder in which case you'd need to copy every plugin into all of the PSx emulators. Nice option which definately is needed in other PSx emus.

[Xeven]

jivera, maybe you need to post a changelog on this beta? no one really knows what the changes form 0.15 are.

[jivera]

Xeven: jivera, maybe you need to post a changelog on this beta? no one really knows what the changes form 0.15 are.

I already did (http://www.ngemu.com/forums/showpost.php?postid=632426&postcount=15). Like I said, not much has changed - I'm just hoping to gather some useful feedback on what people want.

If you really want an official change log though...

2003-10-29 00:31:08 GMT Matthew Dempsky <jivera@flame.org> patch-6

Summary:
pruned unnecessary files
Revision:
pcsx--mainline--1.6--patch-6

Removed a few files generated by running configure from the Linux
port.

removed files:
Linux/Makefile.cfg Linux/config.cache Linux/config.log
Linux/config.status


2003-10-28 23:59:12 GMT Matthew Dempsky <jivera@flame.org> patch-5

Summary:
fixed array bounds
Revision:
pcsx--mainline--1.6--patch-5

Corrected the submenu array size in CreateMainMenu(). Patch submitted
by ffffff from ngemu forums.

modified files:
Win32/WndMain.c


2003-10-22 18:10:15 GMT Matthew Dempsky <jivera@flame.org> patch-4

Summary:
fixed mingw makefile
Revision:
pcsx--mainline--1.6--patch-4

Corrected the -I flags passed to the compiler to account for the
Makefile relocation.

modified files:
Makefile.mingw


2003-10-21 21:21:13 GMT Matthew Dempsky <jivera@flame.org> patch-3

Summary:
moved mingw makefile
Revision:
pcsx--mainline--1.6--patch-3

The MinGW makefile is now in the root directory of the source tree to make future transition of the MinGW port to autotools easier.

modified files:
Makefile.mingw

renamed files:
Win32/Makefile
==> Makefile.mingw


2003-10-18 09:17:12 GMT Matthew Dempsky <jivera@flame.org> patch-2

Summary:
basic win32 command line
Revision:
pcsx--mainline--1.6--patch-2

I added support for the command line arguments -runcd and -runcdbios
to the Windows port.

modified files:
Win32/WndMain.c


2003-10-16 05:58:16 GMT Matthew Dempsky <jivera@flame.org> patch-1

Summary:
fix mingw compiles
Revision:
pcsx--mainline--1.6--patch-1

Included a change to allow compilation of the Win32 release with
either MinGW or Cygwin.

new files:
Win32/afxres.h

modified files:
PsxCommon.h Win32/Makefile

renamed files:
Win32/plugin.c
==> Win32/Plugin.c


2003-10-15 23:06:42 GMT Matthew Dempsky <jivera@flame.org> base-0

Summary:
initial import
Revision:
pcsx--mainline--1.6--base-0

This is the initial import of PCSX under arch control. I have added
taglines to files when possible and otherwise used explicit tags.

new files:
CdRom.c CdRom.h Coff.h Debug.h Decode_XA.c Decode_XA.h
DisR3000A.c Docs/ChangeLog.txt Docs/CodingStyle.txt
Docs/License.txt Docs/Readme.txt Docs/Sources.txt
Docs/ToDo.txt Docs/Translating.txt Dreamcast/3dutils.c
Dreamcast/Compat.c Dreamcast/ConfigGUI.c Dreamcast/Dcast.h
Dreamcast/DcastMain.c Dreamcast/Makefile Dreamcast/PlugCD.c
Dreamcast/PlugCD.h Dreamcast/PlugPAD.c Dreamcast/PlugSPU.c
Dreamcast/Plugin.c Dreamcast/Plugin.h Dreamcast/filelst.c
Dreamcast/filelst.h Dreamcast/gui.c Dreamcast/gui.h
Dreamcast/mouse1.h Dreamcast/plugins.c
Dreamcast/romdisk/pcsxAbout.png Dreamcast/texture.c Gte.c
Gte.h Intl/Langs/fr_FR/LC_MESSAGES/pcsx.mo
Intl/Langs/it_IT/LC_MESSAGES/pcsx.mo Intl/Makefile
Intl/fr_FR.po Intl/it_IT.po Intl/pcsx.po
Linux/.pixmaps/pcsx.jpg Linux/.pixmaps/pcsxAbout.xpm
Linux/Config.c Linux/Glade2Calls.c Linux/Glade2Calls.h
Linux/Glade2Funcs.c Linux/Glade2Funcs.h Linux/Glade2Gui.c
Linux/Glade2Gui.h Linux/GladeCalls.c Linux/GladeCalls.h
Linux/GladeFuncs.c Linux/GladeFuncs.h Linux/GladeGui.c
Linux/GladeGui.h Linux/Gtk2Gui.c Linux/GtkGui.c Linux/Linux.h
Linux/LnxMain.c Linux/Makefile Linux/Makefile.cfg
Linux/Makefile.cfg.in Linux/Plugin.c Linux/Plugin.h
Linux/aclocal.m4 Linux/config.cache Linux/config.log
Linux/config.status Linux/configure Linux/configure.in
Linux/install-sh Linux/pcsx.glade Linux/pcsx.glade2
Linux/pcsx.glade2p MacOSX/Makefile MacOSX/README
MacOSX/dlfcn_simple.c Mdec.c Mdec.h Misc.c Misc.h NoPic.h
PSEmu_Plugin_Defs.h PsxBios.c PsxBios.h PsxCommon.h
PsxCounters.c PsxCounters.h PsxDma.c PsxDma.h PsxHLE.c
PsxHLE.h PsxHw.c PsxHw.h PsxInterpreter.c PsxMem.c PsxMem.h
R3000A.c R3000A.h Sio.c Sio.h Spu.c Spu.h System.h
Win32/AboutDlg.c Win32/AboutDlg.h Win32/Cdrom02.ico
Win32/ConfigurePlugins.c Win32/Makefile Win32/Win32.h
Win32/WndMain.c Win32/gnu_gettext.lib Win32/libintl.h
Win32/pcsx.dsp Win32/pcsx.dsw Win32/pcsx.rc Win32/plugin.c
Win32/plugin.h Win32/resource.h ix86/iGte.h ix86/iR3000A.c
ix86/ix86.c ix86/ix86.h pcsxAbout.bmp plugins.c plugins.h
sh4/Gte.c sh4/sGte.s sh4/sR3000A.c sh4/sh4.c sh4/sh4.h

-jivera

[Chinoz]

Tough luck getting it to work
I've done what you said, taking it from the FPSE folder, but nope, it's still blank.
I'll include a screenie of the situation

[jivera]

Can you upload one of the two plugins so I can take a look through it?

-jivera

[Foxfyre]

As far as adding support for iso's, although nice, isn't really an issue, as I'm sure everyone has a virtual drive (i.e. daemon or clone drive) that they can mount it on....

[Chinoz]

Is this what you wanted, jivera?

[fivefeet8]

As far as adding support for iso's, although nice, isn't really an issue, as I'm sure everyone has a virtual drive (i.e. daemon or clone drive) that they can mount it on....

Or they could just use Mooby's cdr image plugin to run isos with PCSX. ;)

[jivera]

Chinoz: Is this what you wanted, jivera?

Yes, thank you. *takes a look*

-jivera

[TheGodfather]

Hello Jivera
Have u already made more progress with the emu ?

[jivera]

TheGodfather: Have u already made more progress with the emu ?

Nothing significant - as I said, this is mostly a ploy to encourage some revival to bugtesting and user feedback. Windows users may notice support for -runcd and -runcdbios at the command line.

Feature recommendations or bug fixes would be appreciated.

With regards to the Harakiri pad not working, I don't know what's wrong with joy0Harakiri.dll that was uploaded, but I already had a padHarakiri.dll in my plugins directory that seemed to work - I've attached it.

-jivera

[Chinoz]

Weird....it still won't work...
Meh, guess I'm just not destined to use PCSX :p

[CloudStrife1337]

May i request 2 little features?
If so then:

1. a hotkey for quick saving/loading (like in epsxe, f1 and f3).

2. make it so it will load up from isos and zips that contain isos (if its possible of course).

Thank you ;) *goes playing ff7*

Jeez, it takes a hella load of time to load it up.
ePSXe works just fine with it, i dont know what's the problem.
Im using the same plugins as in epsxe!
P4 1.5ghz, geforce 2 mmx 400 (64mbram), 256ddram.
Or maybe, it doesnt work at all! :-/

[fivefeet8]

May i request 2 little features?
If so then:

1. a hotkey for quick saving/loading (like in epsxe, f1 and f3).

2. make it so it will load up from isos and zips that contain isos (if its possible of course).

Thank you ;) *goes playing ff7*


Like I said before in this thread, PCSX also has savestates. Just like epsxe. It uses the same F1 - F3 keys as well.

If you use mooby's cdr image plugin, you can load isos and zipped/rarred isos with PCSX.

[sxamiga]

Just found this thread jivera. I've downloaded it and will test it for you also. I'm a beta tester for ePSXe and I'll be happy to beta test PCSX for you as well. PCSX is one of the three PSX emus that I use all the time. Between the three, ePSXe, PSXeven, and PCSX I am able to properly play all my PSX games.
sincerely,
sx/amiga

[jivera]

Okay, I haven't had much time to make any more updates to PCSX yet... I installed Linux a few days ago to find out that Windows corrupted my source code archive so I had to restart the archive (luckily I still had the source code at least). This Friday I have two rather important tests at school that I haven't spent much time until now studying for, so I'll have to make up for that really quickly before I can get back to work on PCSX.

Just thought I'd make a quick contact so nobody was afraid PCSX was abandonned again.

Btw, sxamiga, thanks for the additional support. :)

-jivera

[Takmadeus]

Hmmmmm I will not beta test PCSX (I think I don't fit the requirements).... but at least I can congratulate you for continuing the project, thanks to it, I was able to play at decent fps when I used my old sis 630.....

I have a suggestion.... why don't you add a debugger window (like the one that epsxe has), as sometimes, a game commits an error (say, an opcode error), then the emu just shows the blank screen..... leaving you wondering if it had an error, or it just crashed, or whatever.... if not a debugger, at least a popup window telling you there was an error... plus, it would help a lot with feedback and all...

[jivera]

takmadeus: Hmmmmm I will not beta test PCSX (I think I don't fit the requirements)....

I wasn't aware of any requirements. :)

I have a suggestion.... why don't you add a debugger window (like the one that epsxe has)

I'm not familiar with ePSXe's in particular, but this is, in fact, something I'm interested in (and believe I've mentioned else where in this forum, if not this thread).

-jivera

[Takmadeus]

yeah.... why don't you give epsxe a chance, so you know what I am talking about.... anyway... I don't think it is very hard to figure what I am meaning.... as for the requirements.... nah, i meant I am not fit to be one.... i mean, if you are a beta tester, you should at least understand so coding concept (ie, when an opcode error pops up) besides, a beta tester has to have a very precise eye, in order to recognize when something isn't going well...

[jivera]

takmadeus: yeah.... why don't you give epsxe a chance, so you know what I am talking about....

ePSXe runs on Linux, right? I'll give it another try to see that in action. I've seen a number of other emulators with debugger consoles and memory viewers so I have an idea of what you're talking about.

i mean, if you are a beta tester, you should at least understand so coding concept (ie, when an opcode error pops up) besides, a beta tester has to have a very precise eye, in order to recognize when something isn't going well...

I don't think that's true. Granted, if you understand how the program works it makes it easier to beta test and debug the code, but that doesn't mean you can't run the program and identify problems with it. (Though, too, at the moment there aren't that many changes so you might as well bug test with 1.5 and anything you find would probably still be applicable.)

-jivera

[FLaRe85]

I'm pretty sure Takmadeus is referring to the console window that is displayed along with ePSXe. Since I don't have mine enabled atm, I'll go ahead and post an image from PSXeven to give you an example. It's basically the same thing.

[Takmadeus]

>ePSXe runs on Linux, right? I'll give it another try to see that in action. I've seen a number of other emulators with debugger consoles and memory viewers so I have an idea of what you're talking about.


that's a good thing Jivera, thanks

>I don't think that's true. Granted, if you understand how the program works it makes it easier to beta test and debug the code, but that doesn't mean you can't run the program and identify problems with it. (Though, too, at the moment there aren't that many changes so you might as well bug test with 1.5 and anything you find would probably still be applicable.)

perhaps you are right, I might as well give it a try later ;)

[zenogais]

If you'd like some help Jivera, I've actually been working on a debug system for NeoPSX. I have a screenshot of the CPU register output window, I can easily adapt the code to PCSX as I'm fairly familiar with the source code, and I'm also working on a memory debugger for NeoPSX as well but that may take longer, but I also have a screenshot of the layout for that as well. Hope I can help.

Sincerely,
-zenogais-

[Takmadeus]

hey Zenogais, btw.... willing to release a public beta? :p (not that I would test it, but I'd like some progress report on it ;))

[FLaRe85]

hey Zenogais, btw.... willing to release a public beta? :p (not that I would test it, but I'd like some progress report on it ;))
All of his releases are downloadable from his site. ;)

[Takmadeus]

oops! didn't know that, I'll try to be more careful from now on ;)

[zenogais]

Actually that release isn't available to anyone right now, I really need to update my CVS. I really wanted to have something good for the next release. I'll see what I can do though.

[jivera]

Alright, exams for today are over (*whew*), so I'm free to do some more PCSX hacking again. I took a look at the ePSXe debug console image ShADoWFLaRe85 posted, and I understand what you mean now and, while I misunderstood your original sentiment, that's still something I'm interested in adding. :)

I've been at a bit of a low for development progress at the moment, but I'm just trying to setup my Linux install so it can cross-compile the Windows programs (cygwin + mingw just wasn't cutting it on Windows).

-jivera

[jivera]

Alright, I just finally successfully cross-compiled pcsx under Linux! :D

Well... successfully in a rather limited sense of the word - it compiled but I don't know if it runs correctly. If a few people wouldn't mind downloading and just taking it for a quick spin to see if it runs okay, I'd really appreciate it. Now, I don't need any thorough testing for this - just a few responses from people with either "yeah it runs fine" or "no, it gives {insert error} at start time." (To run it, just put pcsx--test.exe in the same directory as the other pcsx.exe files.)

Assuming you can get this to run, all I need you to test is if the CPU configuration menu works correctly (particularly with a Spanish version of... something). I'm not familiar with .rc files so I made a quick hack based on some code I found for VNC to get it to compile.

Many thanks!

-jivera

Edit: I just tested this file under Wine and it seems to work okay (except for the way some of the plugins are compiled, but oh well). I'm still interested in hands on Windows feed back though.

[Takmadeus]

okie... downloading, so I'll give it a test... if something, I'll edit this post kthx :p

edit: worked just fine... no probs at all

[Guruma]

Here on win98 se it works corectly!

[jivera]

Guruma: Here on win98 se it works corectly!

Good to hear. In case anyone else tests it out, I am aware there was a bug with native language support (e.g. not being able to change the menus to Italian), but that has been corrected.

-jivera

[jivera]

zenogais: If you'd like some help Jivera, I've actually been working on a debug system for NeoPSX. I have a screenshot of the CPU register output window, I can easily adapt the code to PCSX as I'm fairly familiar with the source code, and I'm also working on a memory debugger for NeoPSX as well but that may take longer, but I also have a screenshot of the layout for that as well. Hope I can help.

That'd be great (I've finally moved past the stage where I'm still learning the code and ready to add more). If you want, you can email me at jivera (at) flame (dot) org.

-jivera

[zenogais]

zenogais: If you'd like some help Jivera, I've actually been working on a debug system for NeoPSX. I have a screenshot of the CPU register output window, I can easily adapt the code to PCSX as I'm fairly familiar with the source code, and I'm also working on a memory debugger for NeoPSX as well but that may take longer, but I also have a screenshot of the layout for that as well. Hope I can help.

That'd be great (I've finally moved past the stage where I'm still learning the code and ready to add more). If you want, you can email me at jivera (at) flame (dot) org.

-jivera

You've got mail Jivera. Also I've posted some screenshots of the completed NeoPSX debugger, I actually finished it this weekend with a little help from PsYcHoJaK ;). Hopefully the pictures are pretty self-explanatory.

Sincerely,
-zenogais-

[Violineb]

gah! Every time I try to run this emu I get this when I run CD.

After I click ok the game continues to run but of course I can't control it at all.
:( I remember something about pad null but I can't find it on google.

[jivera]

Violineb: gah! Every time I try to run this emu I get this when I run CD.

Which version of PCSX are you using? 1.5, the 1.6 linked at the beginning of this thread, or the version built under Linux (linked most recently)? (Hm, maybe I should dedicate a part of my website to hosting the latest versions or something so people have an easy way of checking.) If you tried with a version of than the one attached a few posts ago, try that one (post by me at November 22nd, 2003 at 03:29).

-jivera

[Alex/AT]

Looks like memcards are not working in beta PCSX 1.6. Tested on Grandia, it hangs when "reading memory card".

[Imperial999]

i tried the new beta version, unfortunatly just like version 1.5 i cant load any games. I get a black screen if i use Run CD. If i use Run CD through bios, i see the bios splash screen but it doesnt go any further. I think it my be a GPU Plugin setting but i dont know what.

[Alex/AT]

i tried the new beta version, unfortunatly just like version 1.5 i cant load any games. I get a black screen if i use Run CD. If i use Run CD through bios, i see the bios splash screen but it doesnt go any further. I think it my be a GPU Plugin setting but i dont know what.

If you see the splash screen, your GPU plugin is probably working fine. The problem may be related to your CDR plugin, try to change or tweak it a bit. I got the situation with almost all CDR plugins, since my CD drive does not support RAW reads, nor it supports subchannel reads :( .

[Imperial999]

If you see the splash screen, your GPU plugin is probably working fine. The problem may be related to your CDR plugin, try to change or tweak it a bit. I got the situation with almost all CDR plugins, since my CD drive does not support RAW reads, nor it supports subchannel reads :( .


i have 3 cdr plugins, one is mooby2.dll so i can load image files. other 2 are cdrSaPu.dll cdrPeops.dll. I fiddled a bit with the cdr settings and i can load some parts of a PSX CD, on Resident Evil 3: Nemesis and Dino Crisis i can the screen that says "This game contains some scenes of violance and gore", but it stays on the screen. On Tekken 3 it starts to load but its slow, if i press start i hear the noise you would hear when you skip the into, but the menu doesnt load.

My system uses:
AMD AThlon XP2100+
GeForce FX 5600 Ultra 256MB
1GB 266mhz pc2100 RAM

[Alex/AT]

i have 3 cdr plugins, one is mooby2.dll so i can load image files. other 2 are cdrSaPu.dll cdrPeops.dll. I fiddled a bit with the cdr settings and i can load some parts of a PSX CD, on Resident Evil 3: Nemesis and Dino Crisis i can the screen that says "This game contains some scenes of violance and gore", but it stays on the screen. On Tekken 3 it starts to load but its slow, if i press start i hear the noise you would hear when you skip the into, but the menu doesnt load.

1. What plugins do you use except CDR?
2. Do games load normally from image files? If you haven't tried, make an BIN image, preferably using Alcohol 120%, and try.
3. Do you have some unusual software (DX tweakers, graphic card accelerators, etc. in your system)?
4. What OS and DX versions you run?
(edit) 5. What CD-ROM drive do you have?

My system uses:
AMD AThlon XP2100+
GeForce FX 5600 Ultra 256MB
1GB 266mhz pc2100 RAM

Yo! You have a good system (for me). Mine is Athlon XP 1600+/GF2MX400 64Mb/384Mb 333mhz pc2700 Samsung RAM. So you see our configurations are almost alike (just except GFFX5600 which IS C00L). I run PCSX v1.5 pl1 under Win2003 Enterprise using either PeOPS DX GPU or Lewpy Glide GPU (yes, I have Voodoo2!), Eternal SPU and Mooby Image CDR. For input, I use N-Rage. It works just fine.

Another optin will be to download 1.5 pl1 and try it. 1.6 is merely a beta and some features in it are probably overtweaked unto death (e.g. memory cards).

[Imperial999]

1. What plugins do you use except CDR?
2. Do games load normally from image files? If you haven't tried, make an BIN image, preferably using Alcohol 120%, and try.
3. Do you have some unusual software (DX tweakers, graphic card accelerators, etc. in your system)?
4. What OS and DX versions you run?
(edit) 5. What CD-ROM drive do you have?



Yo! You have a good system (for me). Mine is Athlon XP 1600+/GF2MX400 64Mb/384Mb 333mhz pc2700 Samsung RAM. So you see our configurations are almost alike (just except GFFX5600 which IS C00L). I run PCSX v1.5 pl1 under Win2003 Enterprise using either PeOPS DX GPU or Lewpy Glide GPU (yes, I have Voodoo2!), Eternal SPU and Mooby Image CDR. For input, I use N-Rage. It works just fine.

Another optin will be to download 1.5 pl1 and try it. 1.6 is merely a beta and some features in it are probably overtweaked unto death (e.g. memory cards).

I use Win XP PRO OEM Edtition, direct x 9.0b. i use the following plugins:
gpuPeteD3D.dll
spuPeteDSound.dll
padHarakiri.dll

I am unable to load image files, haven't tried a bin file.

cd rom i use is acer2010 CD-RW or Sony DW-U10A DVD-RW+RW

no unusal software running.

[Cyberman]

I use Win XP PRO OEM Edtition, direct x 9.0b. i use the following plugins:
gpuPeteD3D.dll
spuPeteDSound.dll
padHarakiri.dll

I am unable to load image files, haven't tried a bin file.

cd rom i use is acer2010 CD-RW or Sony DW-U10A DVD-RW+RW

no unusal software running.
Got the black scream huh?
I can run games with PCSX 1.5 that I can't with EPSXE, that being said give me a few of the IDs of the games you are trying to run? Some won't work in PCSX but do in ePSXe. Diablo won't run in ePSXe for example but does under PCSX. Etc. So let me know I'll tell you if it works or not and what my settings are if it works.

Cyb

[Imperial999]

Got the black scream huh?
I can run games with PCSX 1.5 that I can't with EPSXE, that being said give me a few of the IDs of the games you are trying to run? Some won't work in PCSX but do in ePSXe. Diablo won't run in ePSXe for example but does under PCSX. Etc. So let me know I'll tell you if it works or not and what my settings are if it works.

Cyb

well i have tried using epsxe and psxheaven but they not got the games workign either, and on my old pc i have had these games working before.

C12 - Final Resistance.img
Crash Bandicoot 3 - Warped.img
Destruction Derby 3.img
GT2- Arcade.img
GT2- Gran Turismo.img
Metal Gear Solid - CD1.img and CD2.img
Road Rash Jailbreak.img
Tony Hawks Pro Skater 4.img

Resident Evil 3 - Nemesis original CD
Tekken 3 Original CD
Dino Crisis Original CD

thanks for trying to help btw

[Cyberman]

well i have tried using epsxe and psxheaven but they not got the games workign either, and on my old pc i have had these games working before.

C12 - Final Resistance.img
Crash Bandicoot 3 - Warped.img
Destruction Derby 3.img
GT2- Arcade.img
GT2- Gran Turismo.img
Metal Gear Solid - CD1.img and CD2.img
Road Rash Jailbreak.img
Tony Hawks Pro Skater 4.img

Resident Evil 3 - Nemesis original CD
Tekken 3 Original CD
Dino Crisis Original CD

thanks for trying to help btw
I have
MGS
RE3
I can try those two under PCSX for you.
Are you using Moby to run the images?

Cyb

[Imperial999]

I have
MGS
RE3
I can try those two under PCSX for you.
Are you using Moby to run the images?

Cyb

yeah i am using cdrmooby2.dll to run the image files.
Hope your tests work.. i could used to play all my image files when i had my old pc which was a dell D300 quite old to say the least... now i've built my own and it doesnt work.

[Cyberman]

yeah i am using cdrmooby2.dll to run the image files.
Hope your tests work.. i could used to play all my image files when i had my old pc which was a dell D300 quite old to say the least... now i've built my own and it doesnt work.
Ok Both Games work fine.
The sound skips a bit on MGS for some reason but otherwise it works just fine.
RE3 works too.. So what do you need to know?

Cyb

[Imperial999]

Ok Both Games work fine.
The sound skips a bit on MGS for some reason but otherwise it works just fine.
RE3 works too.. So what do you need to know?

Cyb


why they dont work with me... is it my pc hardware, pcsx plugin settings i've done wrong or what. like i said i used to use pcsx fine without errors with my old pc, but cant with this one