Copy those two a any place you want (I like to create a subdirectory inside of epsxe directory). You need libSDL-1.2.so.0.11.4 and libSDL-1.2.so.0 (which is a symlink). If you are going to use spuEternal sound plugin (it's my favorite) you should download libsdl1.2debian_1.2.15-5ubuntu1_b and extract its contents to copy the shared libraries. Sudo apt-get install unity-gtk2-module:i386 Sudo apt-get install libcanberra-gtk-module:i386 Sudo apt-get install gtk2-engines-murrine:i386 I don't know if the next packages are necessary but there will be no harm on installing them: sudo apt-get install libgtk2.0-0:i386 Sudo apt-get install libsdl-ttf2.0-0:i386 I have a 64 bit machine and can't assure this is going to work with a 32 bit operating system. It took me some days of trial and error until I found a decent solution. So I think it should work in previous Ubuntu versions as well. And thanks again for this great piece of software so far.I can run ePSXe in Ubuntu 14.04. One last thing: Does altering the region option have any effect on compatibility at all? I noticed that leaving it at ntsc works fine for most us and european games and that setting it to pal doesn't improve compatibility for the above mentioned games.ĮDIT: Would you mind adding the possibility to map save/load state to the keypad in a future release? Would be great. Where do you do that? I couldn't find any option allowing me to use a specific bios file. Crypt Killer runs fine in PSX4Pandora.Īlso I don't get what you mean by saying "you need to enable bios". No chance of starting a game (intro runs fine and smooth though).Ģ) Resident Evil DC: Doesn't start at all (black screen)Ĥ) Myst: same as 2, did load up to the main screen in r3 though.ĥ) Tomb Raider: hangs during initialization of main screenĦ) Tomb Raider 2: main screen, screen stay black after starting a gameĪll the above mentioned games except for Crypt Killer are in bin/cue format. They didn't change at all between r3 and r5 (yes, I deleted the corresponding appdata-folder).ġ) Diablo: Still starts fine but doesn't accept any Input and plays the Intro instead. I would like to add my compatibility issues here, just to let you know. I seem to have missed r4 since I didn't know about this thread. added watchdog thread to detect emulator lockups.fixed lots of recompiler related issues (see GIT).added handling for branches in delay slots.fixed channel disable preventing irqs in P.E.Op.S.fixed remaining savestate incompatibilities between PCSX4ALL and P.E.Op.S.merged latest cdrom code from PCSX-Reloaded project.You can keep doing compatibility lists for future reference though. I'll probably stop working on compatibility now, it's really time to start my optimization efforts. There is now support for more compressed CD image formats, but before reporting bugs try. All final fantasies work now, for FF8 you need to enable BIOS and play it from the beginning (don't use old savestates with HLE, they are bad). The compatibility should go up a good deal thanks to fixed cdrom code from newer PCSX-Reloaded and my recompiler fixes. It is not as if you coded your recompiler so it may be initially reusable in another project by other coders and for another MIPS processor than the one in N64.īy the way, I can see a lot of sequence of 'if' without 'else if', is there any reason to keep them this way ? I'm not saying you must change it and I don't think you need to justify your choice. I personally think the best choice is when there is balance between efficiency and readability according to project purpose.Īnyway, it's your choice. And sure if one use only C, it limits one's imagination about how abstract and factorize one's source. Having macros helps because they name what they do instead of a long sequence of instructions and alleviates - doesn't remove - the source duplication. What I noticed is that you wrote your long sequences of instructions in C as if you are writing an assembly code (over-control on what you write instead of trying to abstract some algorithms). Deadalus has some good ideas but was pretty hard to read for the reason you stated. I don't consider PCSX source as a good piece of code, unlike gPSP. In a company, that kind development in software leads to a very bad maintenance or evolution if the program author leaves the company, because he/she rarely documents his/her source or doesn't even create a document to help to understand the layout.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |