I don't know, universe. Searching the forum and posting in the Game Compatibility section are the best ways to find out.
Edit: Making game reports is important, as it enables smegforbrain to update the Compatibility Lists, and ultimately may provide the information needed to get the game running. However, since it seems the problem may be copy protection, it's possible that making a compatibility report may provide enough responses to for you to get the game running.
Have you considered my suggestions on running copy protected games?
Last Edit: Aug 30, 2007 7:22:38 GMT -5 by patrickp
I'm a new member and just recently got wind of this emulator. I was like most of you before, I guess, using epsxe, because supposedly it was the best emulator out. It is good, but I have to say, there is no one right now who is putting the level of expertise into ANY emulator that you are. I mean, most emulators are not even updated but maybe once or twice a year, and you just keep coding away and fixing bugs! I recently downloaded this emulator and it was version 1.11, and now already you have 1.13 going!
Nice job and keep up the good work, this will be the best psx emulator ever!
That's amazing how it's just one guy working on this. And I didn't even account for the fact that it's linux too, which is great. Yeah, I'll go ahead and change my sentence: "... this IS the best pxs emulator ever!"
I just realized that I'm gonna need to retest some of the previous games I played recently (namely, Lunar 1, Lunar 2, and Musashi), since the problems I had with them were audio-related (all XA audio-related, IIRC). When I get more time... It's awesome how, even though I thought this release was less focused on compatibility and more on bug fixes (as the changelog would lead one to believe -- or at least it led me to believe as such), the one XA audio fix seems to have fixed compatibility for a nice handful of games. Thumbs up to pSX Author on that
xinx, if you want to post game reports, this is not the place: do it in the Game Compatibility thread. Also read Things to Remember when Posting Reports, prominently linked at the top of this and every other page in this forum. Remember that, apart from the required information, the amount of help you receive will depend on the amount of useful information you provide.
(pSX:22188): GLib-GObject-CRITICAL **: g_signal_handler_disconnect: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed --that appeared when main window disappeared and a dialog about bios appeared, then I choose correct one--
[src/linux/sound.cpp, line 215]: 'snd_pcm_hw_params_set_access(pcm_handle,hwparams,SND_PCM_ACCESS_MMAP_INTERLEAVED)' returned 'Bad argument' pad=0
Program received signal SIGSEGV, Segmentation fault. 0x08123fb2 in sound::linux_polled_audio_stream::next_update ()
backtrace: #0 0x08123fb2 in sound::linux_polled_audio_stream::next_update () #1 0x080eb55e in psx_spu::update () #2 0x080e20be in run_psx () #3 0x0811b223 in ?? () #4 0xb7554081 in ?? () from /usr/lib/libglib-2.0.so.0 #5 0x00000000 in ?? ()