WARNING: OBSOLETE
I RECOMMENDING USING DUCKSTATION!
PeteOpenGL2Tweak - Tweaker for PeteOpenGL2 plugin
WARNING: This plugin REQUIRES -ORIGINAL- Pete OpenGL2 v2.9 plugin to work ! You will get "Error 0x7e" if you do not have it !
Sources and new releases will be posted on github: Nucleoprotein/PeteOpenGL2Tweak If emulator is crashing with TextureCache and high scale setting ie. 5 or 6xBRZ download this patch and apply to -emulator- executable (ie. ePSXe.exe or PCSXR.exe): 4GB Patch – NTCore
xBRZ is compatible only with "Hi-Res Textures" option set to "0 - None"
Also make sure that "Framebuffer Effects" is set to "2 - Standard".
Requirements:
gpuPeteOpenGL2 plug-in v2.9 (425984 bytes, need to be in <emu_dir>\plugins)
- download it here: Pete's PSX GPU plugins GTE Accuracy hack requires latest PCSX-R or ePSXe 2.0+
xBRZ filter with deposterize: Usage:
Copy gpuPeteOpenGL2Tweak.dll to plugins directory, then run emulator and select "PeteOpenGL2 Tweaks" as GPU plugin.
Configuration:
Configuration file is: inis\gpuPeteOpenGL2Tweak.ini, all options can be only turn on or off so there is not much to configure, by default FixMemoryDetection and EnableVsync are off.
You are welcome to like it or hate it Thanks:
Pete Bernert
edgbla
Calb
and whole PCSXR team
I'm giving this tweak a try, but at the moment I can't make the pad plugin settings + PEC works in ePSXe 1.9.25 at all. However I manage to set all the steps on setting it up on PSCXR as mentioned on the first page.
Can anyone give a step-by-step for setting it up for the latest ePSXe? I just want the PEC and pad plugin to work.
PEC:
1. Set 'UsePEC = True' in inis\gpuPeteOpenGL2Tweak.ini
2. Run emu and set GPU plugin to PeteOpenGL2Tweak
3. Click configure, PEC configuration will appear, select Petes OpenGL2 in it
4. Click ok and run games.
PAD Plugin support hack:
1. Set 'ePSXePadPlugin = True' in inis\gpuPeteOpenGL2Tweak.ini
2. Set 'Port1 = path\to\pad\plugin' in inis\gpuPeteOpenGL2Tweak.ini
3. Do same for Port 2 if you need it
4. Run emu, goto GPU plugin select and press 'Test', this will run Pad Plugin Conguration.
5. Configure it and run games.
EDIT:
LOL apex was first ...
PS: @apex
You use LilyPad for it's advanced features or Xinput support ? If only Xinput i recommend Pokopom, it can use 'bigbutton' (Xbox big X button ) for analog switch!
PS: I'm dumb, sorry, you use SCP ie. PS3 Controller
I have XInput wrapper installed and it comes with the LilyPad plugin and "XInput1_3.dll" which I put in the same folder as ePSXe.exe. This allows me to enable "DualShock 3 native mode" in the options, so it acts exactly like a DS1, with analog toggle on the PS button on my DS3. I've tried Pokopom a few times but the L3/R3 buttons (pressing the analog sticks) didn't work so I went back to LilyPad.
Tapeq, you seem to be quite knowledgeable on these things, do you know of any way to implement per game settings as with ePSXeCutor for PCSX-R? I've wanted to try it as my main PS1 emulator but really don't want to reconfigure the settings between games. I haven't found any PCSX-R compatible frontend. One solution I tried was to set every game setting in ePSXeCutor, extract the registry keys and use a command line launch with those keys in Emulation Station and Launchbox but it's a pain in the a**.
ePSXeCutor uses same way you described - when you run setting from ePSXeCutor then it writes to registry saved setting in profile and then run ePSXe.
I tested a way to hack ePSXeCutor to run PCSXR.exe. You need to hexedit ePSXeCutor.exe and replace all "ePSXe.exe" strings to "PCSXR.exe", but this is not perfect:
NOTE1: If you rename ePSXeCutor.exe to (example) ePSXeCutorPCSXR.exe you need to rename ePSXeCutorStuff.dll to ePSXeCutorPCSXRStuff.dll and ePSXeCutorTool.dll ePSXeCutorPCSXRTool.dll.
NOTE2: It will not save/change emulator internal settings - ie. selected plugins, but will set plugin settings.
NOTE3: Command line will work, for PCSXR "-cdfile" is option to run image file
EDIT:
Ehh, I broken memory cards in PCSXR... and I think fixed it now ... re-uploaded file.
PS: Option to enable Per Game Memory Card is in "Configuration" -> "Memory Cards...". Also default extension of automatic memory cards is .mcr to be compatible with ePSXe (PCSXR and ePSXe can use same cards) ie. cards are saved to memorycards\games\<gameexename>.mcr
Hola como estas, vale ya lo estoy probando con distintos juegos y hasta ahora va bien a veces al comienzo era difícil hacerlo andar pero va bien, por lo que debo decirte muchas gracias amigo por esto... nos vemos pronto... saludos...!!!
I have a idea, hardcore mode... disable emulator save state hotkeys (F1/F2/F3) !
Some PSX games have limited memory cards save states (like Resident Evil series - you need to use "Ink Tape" to save using typewriter) and using emulator save sates is like cheating. Maybe it is stupid but save states always tempted me to use them
EDIT:
Done ! Should work for all emus because it blocks F1/F2/F3 keys in WindowProc !
NOTE: ConfigVersion updated, you config will be cleared to default values !
I have a idea, hardcore mode... disable emulator save state hotkeys (F1/F2/F3) !
Some PSX games have limited memory cards save states (like Resident Evil series - you need to use "Ink Tape" to save using typewriter) and using emulator save sates is like cheating. Maybe it is stupid but save states always tempted me to use them
EDIT:
Done ! Should work for all emus because it blocks F1/F2/F3 keys in WindowProc !
NOTE: ConfigVersion updated, you config will be cleared to default values !
Good thinking, blocked UsePEC when HardcoreMode is enabled but blocking ePSXe/PCSXR cheat menu options is not possible by plugin :/
Currently working of implementing xBRZ texture filter ! This is even more hardcore
EDIT:
Done in 95% (not all textures are rescaled).
After you will finish xBRZ could you try to implement a higher resolution multiplier currently the highest supported resolution is 3/4x IR which is pretty low. At least 12x IR would be good. By the way are you using the newest xBRZ 1.3?
Then I wonder if antialiasing like MSAA or SSAA is possible, antialiasing works with Peops OpenGL but not Pete OpemGL2. Is there a way to extract and replace textures?
Updated, Frame Buffer Effect are slow as hell and will be, I cant make it any faster without recompiling gpuPeteOpenGL2 (ie. without source code).
Removed scaling of RGB (ie. 24bit) textures (sloooow xBRZ needs 32bit textures, so conversions needed) as they only used for GUI display.
Removed automatic usage of WGL_EXT_swap_control_tear, because it crash emulator on Re-Run/Reset (black screen), seem to be AMD driver bug.
You can now set Swap Interval yourself, 0 VSync Disabled, 1 Normal VSync, -1 adaptive VSync (WGL_EXT_swap_control_tear).
PS: You can use internal 2xSal + xBRZ, but effect are not quite nice, but scaled textures + xBRZ look nice in RE.
PS2: Note that VRAM size in Configuration dialog only estimates number of usable textures in texture cache, 1024MB set 195 usable textures.
So if you scale all textures 5x, then you will require 25x more VRAM (texture size = width * scale * height * scale * (bpp/8) )!
Not stretched textures are 256x256, stretched 512x512, all 32bits so with 5x scale you get: 256 * 5 * 256 * 5 * 4 = 6553600 bytes ie. 6,25MB for single texture and 512* 5 * 512* 5 * 4 = 26214400 bytes = 25MB for single texture!
MSAA would still be nice hardware AA is always better than a software based one.
By they way tapeq there is a new Open Source PS1 emulator in the works so it'd be great if you could perhaps contribute to it in a future. https://github.com/simias/psx-rs
Not can do for now, all textures and framebuffer (in FBO mode, but who uses pbuffer today?) are in not AA compatible format and changing is complicated.
About new emu, I don't know Rust programing language...
I think Rust is C linkable so I suppose you can contribute with C/C++ but you would have to ask the author if he accepts other languages in his emulator.
I think "Frame Buffer Effects" can be much faster by using PBOs (http://www.songho.ca/opengl/gl_pbo.html) but I do not know if this will be possible by hooking this plugin more...
PS: Also this path: "E:\Users\My name\My Documents\Games\CONSOLE\
EMULATORS\SONY\Playstation\Playstation\plugins\gpuPeteOpenGL2.dll" can be too long... Move Playstation to D:\Playstation or something...
PS2: WinAPI is stupid, path is only not limited to 260 character when you use UNC prefix (\\?\) ... Most application does not use this prefix.
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Related Threads
?
?
?
?
?
Next Generation Emulation
2.2M posts
459.8K members
Since 2001
A forum community dedicated to all emulation enthusiasts. Come Join discussion on all platforms from Nintendo, Microsoft Xbox, Sony Playstation, to PC. Coding, tips, builds, specs, tricks and more.