11-03-2016, 11:20 PM
PCSX2 version: 1.4.0 / 1.5.0-20161101175446 (git)
CPU options: EE/IOP defaults, VUs defaults
Speedhacks: Tested with and without SH, no changes.
Plugins: GSdx 1.1.0 / SPU2 2.0.0
HW hacks: Tried activating every single one with no results. Didn't fiddle with skipdraw.
Game patches: None, tried some, didn't help
Specs:
OS: Windows 10 Familial editiion
CPU: Intel i5 4670k x4 3.40GHz
GPU: GTX 760 GIGABYTE OC
RAM: 16GB DDR3
Description: Going underwater in Ape Escape 2 while in hardware mode causes massive drops in FPS ans graphical glitches (water overlay doesn't appear, shadows are glitched).
No problems in software mode, removing MSAA or dropping the resolution lessens the stutters to a point where MSAAx0 in native res runs at full speed on my config but it still has graphical glitches. Happens in DX11/DX9/OGL (DX9/11 appear to stutter massively after 10s near water without even entering it). Thought it came from the mipmapping in hardware mode hack from latest builds but it still happens in 1.4.0.
Video:
Hope I followed the forum instructions well enough, if it lacks details just ask and I'll add them.
CPU options: EE/IOP defaults, VUs defaults
Speedhacks: Tested with and without SH, no changes.
Plugins: GSdx 1.1.0 / SPU2 2.0.0
HW hacks: Tried activating every single one with no results. Didn't fiddle with skipdraw.
Game patches: None, tried some, didn't help
Specs:
OS: Windows 10 Familial editiion
CPU: Intel i5 4670k x4 3.40GHz
GPU: GTX 760 GIGABYTE OC
RAM: 16GB DDR3
Description: Going underwater in Ape Escape 2 while in hardware mode causes massive drops in FPS ans graphical glitches (water overlay doesn't appear, shadows are glitched).
No problems in software mode, removing MSAA or dropping the resolution lessens the stutters to a point where MSAAx0 in native res runs at full speed on my config but it still has graphical glitches. Happens in DX11/DX9/OGL (DX9/11 appear to stutter massively after 10s near water without even entering it). Thought it came from the mipmapping in hardware mode hack from latest builds but it still happens in 1.4.0.
Video:
Hope I followed the forum instructions well enough, if it lacks details just ask and I'll add them.