![]() ![]() Sudo touch memcards/epsxe000.mcr memcards/epsxe001.mcr. That way, we can call it up by typing $varname, which we'll have to do a few more times.Įxtract the ePSXe package and set up permissions: Since typing this whole path we just added is tedious and clutters up this text, we will store it in a shell variable using the export command. Sudo apt-get install unzip libgtk1.2-common libgtk1.2 You have been warned.įirst, open a terminal and install the packages that you will need: Owning the BIOS image without owning the actual console is a violation of copyright law. You may not use such a file to play games in a PSX emulator if you do not own a Sony Playstation, Sony PSOne or Sony Playstation 2 console. Legal note: The installation and use of this emulator requires a Sony Playstation BIOS file. Apparently it is possible to run it using an amd64 system, but to do that you need to install some 32 bit libraries, see this () post. An installation guide can be found in this link (). You might want to try another emulator instead, for example PCSX (). If you use powerpc it probably won't work. It is based on this guide (), which I found a bit outdated.ĮPSXe is made for x86 (common pc) only. This is a guide to install the freeware Playstation 1 emulator ePSXe () in Ubuntu. Suggest you to try the extended w/ smoothed sprites filtering, works great here.This guide is outdated and will not be updated anymore. Read the readme.txt in the pete's plugin pack for more information. It's also a (too) well-known glitch, since you are using the texture filtering and cuz' psx textures weren't supposed to receive some bilinear filtering, that makes the tiling glitch. I didn't see that was a tiling effect (thought this was some kind of black lines). ![]() Oh and untick the "keep psx aspect ratio" box.it might also solve the black lines prob w/o disabling fsaa. The crash after the first battle is due to the spu plugin, (never tried w/ eternal spu btw) just do a save state right before the crash happens, switch the spu plugin (take the epsxe internal one instead of your spu for example) and load the save state to get pass trough that glitch.Īnd I highly recommend you to play w/ the pete's ogl plugin since it's most suited for geforce cards (disable fsaa or set the framebuffer option to "black") Try disabling FSAA, I encountered several flaws w/ games displaying 2d background (strangely, not ff9 or even chrono cross).įor the big slowdown before the battle, it's a well known issue:Įnabling fsaa w/ the framebuffer effects just slows down the all. 1024x768 Fullscreen - Desktop changing They were nice and zippy with my old comp (Celly 500, GF2MX). I realize that changing the buffer can fix this, but I'd appreciate it if someone could recommend some settings.ĥ) With both Pete's OGL and D3D, battle transitions are slow: ~10 FPS in OGL and ~30 FPS in D3D. The command prompt says "ePSXe (error): recompile block too large." Huh?ģ) Also in Pete's D3D, when you try to steal something in battle, no message appears at the top stating the results of the steal attempt.Ĥ) With the Eternal 1.1 SPU, there is major stuttering in MDECs. I thought that messing with the OGL settings in the GF3 properties would help, but I can't get to them.Ģ) Using Pete's D3D solves that problem, but at the end of the first battle (between Baku and the Tantalus crew) ePSXe dies and goes back to Windows. ![]() I have a whole buncha problems getting FF9 to run nice on my new PC.ġ) In Pete's OGL 1.55 AND 1.54, backgrounds have really ugly tiling problems.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |