PCSXR-PGXP

Discussion in 'PCSX Discussion' started by iCatButler, Aug 8, 2016.

  1. nayboo

    nayboo New Member

    Messages:
    5
    Likes Received:
    0
    Instead of editing my own post, i hope it will be ok if i post a new one..

    @TheDimensioner
    I tried everything you told me. At first i saw i already had xBRZ deactivated in the .ini file, the overclocking feature was not activated too. Next, i checked the opening sequence (until you meet up with Vivi) with Eternal SPU 1.50 and your settings. But it didn't change much, sound is still weird in cutscenes and small glitches when in battle.
    I doubt there is much left to try to get better results. Still hoping there will be an update someday that fixes ffix's audio performance.
  2. TheDimensioner

    TheDimensioner New Member

    Messages:
    249
    Likes Received:
    61
    @nayboo Well, there's also the "#Disable sound plugin FPS auto limit" and the "#Enables VSync, paramater specifies the minimum number of video frames that are displayed before a buffer swap will occur" options on the .ini. Either will ultimately be related to sound, because I think there's already some kind of v-sync going on in Pete'sOGL, because I've never experienced tearing or video stuttering. So try enabling the first option, but if still stutters, set v-sync 1. Someone said it's possible to it set to "2" or even "-1", one of those sets an "adaptable" style v-sync, but I don't know if they actually do anything.

    The last resort, would be unchecking the "Psx System Type" option under "CPU...", and setting it to your game's region (NTSC or PAL). That sometimes makes framerates more stable, because the autodetect seems to be broken.

    From there, you could only try lowering video settings, like ResHack or disabling diposterize. The "OpenGL 1.78" video plugin also supports PGXP, but it has FFIX specific issues. In the "special game fixes", there's an option for FFIX to fix the yellow names highlight in the battle HUD, but that never fixed it for me.

    Another idea, maybe restarting your plugins settings, or even downloading a fresh file might help. Just use "regedit" on Windows search, browse to "HKEY_CURRENT_USER > Software > Vision Thing > PSEmu Pro". Inside are the plugin specific settings. You can try deleting just the SPU folder, or the whole PSEmu Pro folder, but you'll have to reconfigure every plugin. You could also try deleting the "Pcsxr" folder (same path before "Vision Thing"), because there could be conflicts with old PCSX-R branches. But those are just thoughts XD.
    Last edited: Feb 11, 2017
  3. nayboo

    nayboo New Member

    Messages:
    5
    Likes Received:
    0
    @TheDimensioner
    thank you again, i tried everything except getting into the registry. Will try this later this evening. Until now, nothing helped, what is quite frustrating.
  4. nayboo

    nayboo New Member

    Messages:
    5
    Likes Received:
    0
    Sorry again for double posting, but after that long time i hope its ok..

    @TheDimensioner
    You sir are my hero!! Deleting the PCSXR-folder in registry helped!!! I have almost no sound problems now, those still remaining are very very hard to notice (like screen transitions sometimes only run to 98-99%% perfectly, soundwise).
    To be honest, thought i never had PCSX-R on my system (old builds), but this could be the only explanation.
    So thanks a LOT for your help, i can finally enjoy the game in the best state possible!!!
  5. TheDimensioner

    TheDimensioner New Member

    Messages:
    249
    Likes Received:
    61
    @nayboo You're welcome! I thought about the registry thing because I myself have downloaded many different PCSX-R builds, before PGXP became my main PSX emulator. For some reason, even if the options are "ok", the registry folder is superior and will overwrite anything you set up manually. I wished someone recoded that part of PCSX-R (since it's open source) and made that all options are in a single .ini, or .cfg file, that could be easily modified without going into tons of GUIs, or inside the registry for "hidden" stuff. I guess the current configs are kinda broken for that matter, so it might be hard to change it... just guessing XD!

    But I'm glad I could help. Enjoy the best way to play PSX games!

    By the way, has PGXP been implemented in other PCSX-R builds, besides the "main" one we have here? I know someone talked about a 64-bit build that was on emucr, but I don't trust their methods... Since I've become kind of active with this emulator recently (been doing simple let's play videos), I wished to have an updated version, with at least some of the older bugs fixed. Or at least an updated audio or CD-R plugin, because those are my main problems XD. Eternal SPU is too old and P.E.Op.S 1.10 is "lazy", as in it works well only when it wants to. The CD-R plugin is also too old, and is related to audio in some ways. I can't use Mednafen HW core on Retroarch, because that doesn't run well on my system, and it's a mess to properly configure. Tried even to do custom .inis just for PSX, but it won't read my options for some reason...
  6. LuismaSp89

    LuismaSp89 New Member

    Messages:
    70
    Likes Received:
    2
    @TheDimensioner

    I found a problem with the plugin, let´s see if i can explaint it with my bad English:

    This plugin uses a different way to store the settings of the shader path. When you work with a emulator, for example like the epsxe, the shader path is stored in the registry "HKEY_CURRENT_USER\SOFTWARE\epsxe\config\GPUShaderDir" (Inside of this registry key is the directory \shaders by default) and when you set another directory, using the graphical ui of the plugin, this last one prevails. But the changes is not reflected in the registry key of the emulator.

    Example of my case:

    I have two games, the first is metal gear solid, using a default shader, the path of this shader is the default " \shaders"

    The second is Alundra, a 2D game, and i have a shader specially for 2D games, the path of this shader is "\shaders\2D"

    Now, i use the epsxe option to create a game profile "Options>save game profile" This is very useful to set the settings and load it auto for each game, and all works ok, except the shader path. I tried everything, but all the time it loads the shader path that is set using the UI. No matters if i set in the alundra configuration txt that the path is \shaders\2D, all the time it loads the default \shader, unless i set it using the ui, but in that case the metal gear solid config uses this last one, not the default.

    I don´t know if i explained it very well, but it´s annoying :( the game profiles option works like a charm, but not in this case for the shaders path of the plugin.
  7. TheDimensioner

    TheDimensioner New Member

    Messages:
    249
    Likes Received:
    61
    @LuismaSp89 Well, I'm guessing that the latest 2.0 versions of ePSXe use the same "core" plugin of Pete'sOGL 2.9 for its OpenGL 2.0.0, so some settings, like shader directory, might be in conflict with the specific "GPU" plugin settings in the registry. When I used shaders extensively, I gave up trying to make settings for specific games, so I simply entered my shaders folder and copied the folder path of the shader I wanted, and pasted on the Pete'sOGL2 shader GUI whenever I needed to.

    By the way, the current ePSXe still has some GUI issues, that I can't remember specifically right now since it's been a long time since I used it, but crazy things used to happen... not saving options correctly is one of them. One main issue that I still have, is that checking or unchecking "Screen filtering: a nice fullscreen filter" option won't take effect until I restart the emulator, ePSXe or PCSXR-PGXP. That might be specific to the plugin though.

    Again, registry settings suck for something that is not even properly "installed" (by option).

    #.ini4PSXConfig #EmulationMatters

    ...

    Don't take that too seriously :p.
  8. LuismaSp89

    LuismaSp89 New Member

    Messages:
    70
    Likes Received:
    2

    Mmm... i see... Ok, by the way i managed to solve the problem using a .bat that copys the shader of one or other game in the folder of "shaders" is too useful because i use the launchbox frontend for all my games, and i can execute the .bat before the game runs :p

    Thanks a lot for your reply.

Share This Page