Press "0" in the numpad and you will see a green overlay.
#SHADOW HEARTS PCSX2 BAD LAG HOW TO#
How to get the pixel shader hashes? Search the "hunting=0" line and change it to "hunting=2".Īfter that, run the emulator and play the game you want. Set them to "=2" to not stereoize them but not making them count as HUD. New: setting them to "=1" now assumes that they are HUD shaders, so they'll be affected by the HUD hotkeys. Useful if you want to enable/disable game fixes break effects in other games. If it's "圓=0", it means it will stereoize it, the same as not writing the shader override at all.
If you write for example "z3=1", it means that regex 3 won't stereoize that specific pixel shader. They contain the hash of the pixel shader, and the value they pass to their parent vertex shader. In the ".ini" files inside "GameFixes" there are shader overrides with comments saying what they fix (sometimes).
#SHADOW HEARTS PCSX2 BAD LAG UPDATE#
The values after "Hash=" may change with future GSdx versions, but I will be able to recognize them and update the fix. "w3" is an extra option about the fix I made for the skybox in the Ratchet & Clank saga (it forces the skybox to max depth without breaking other things in those games). "x3" for regex 1, "圓" for regex 2, and "z3" for regex 3. Those are the three vertex shaders I stereoize with regexes, and their default values for stereoization. The fix includes working examples for games I own, inside the "GameFixes" folder. Even with a small library of 30 something games I found a little more than 10 conflicts between games. So fixing all games at the same time is impossible. Most of the affected games need between 1 and 3 in my experience.Ģ- Fixing something in one game can break something else in another game, or even in the same game in some cases. Still, games don't usually need a lot of these. This is where things get more complicated, for these reasons:ġ- Future PCSX2 (specifically GSdx) builds may change the hash of the generated shaders, rendering all game specific fixes useless. In these cases, you need to tell the regex to not stereoize a specific pixel shader. Sometimes, or usually, disabling some of the regex isn't enough to make a game perfect or almost perfect, because you will be disabling more things than needed. Warning: for advanced users and perfectionists A lot of times a mix of regex 3 and regex 2 will fix HUD issues, but regex 2 is usually related to other effects. And that's also their order of importance, as you'll almost never have to disable the first one. They are "j", "k" and "l", and I'll refer to them as "regex 1", "regex 2" and "regex 3". The first and most simple solution, which may be partial or fix some things and break others but it's useful many times, is using three hotkeys I offer to disable stereoization in each of the three shaders that control geometry. The regex function tries to not stereoize things that have a depth value of 0 or 1, and in some games it works (most of the HUD of the Kingdom Hearts games). The problem is that some effects of those shaders need to not be stereoized, like the HUD or some double stereoized effects (sometimes bloom, blur filters, shadows.). Instead, it uses a real time "find and replace" function for exactly three shaders that control all geometry in all games. Version right after this one has it.This fix was done without using physical shader files, for better future compatibility.
Pcsx2-v1.5.-g6e3f41f16-windows-x86 could not reproduce issue. From there on keep doing it and shortly you will see that inputs are dealyed and queued up when a battle starts, after it ends and when you open a menu and the delays will become longer. Eventually you will notice at the start of a battle that PCX2 isn't responding to inputs. Like I said inptus sort of queue up, so if you keep pressing stuff they will sort of run their course after the delay passes and then everything is normal until the next battle re-triggers the cycle and makes it longer a bit.īattle a few times and keep running away to get them over quickly. Opening a menu for the first time after exploration starts, delay. After it ends and at the start of exploration, delay. This snowballs and becomes worse and after each new battle, the delay is longer and the following cycle repeats itself: after a battle starts, delay.
After a few battles (about 4-5) the next battle introduces a problem where the game (it seems PCSX2 itself beacuse hotkeys like turbo mode don't work either during the duration of the delay) isn't responding to inputs but sort of queues them up slowly, and after 2-3 seconds it goes back to normal for the rest of the battle. Game is Shadow Hearts 2, I don't know if it happens in other games. This is very difficult to explain so please bear with me. Pcsx2-v1.5.-g9cb35a897-windows-x86 and onwards (latest as well, as of today e90c87a)ĭefault selected plugins out the gate.
0 kommentar(er)
