New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Socom 3: U.S. Navy SEALs (NTSC-U) - Slowdown when looking at the sun. #3049
Labels
Comments
piau9000
changed the title
Socom 3 (NTSC-U) - Slowdown when looking at the sun.
Socom 3: U.S. Navy SEALs (NTSC-U) - Slowdown when looking at the sun.
Jul 30, 2019
Do you tried the EE Timing hack and delay VIF1 stalls? |
Yes. But it had no effect. |
Fixed in #3402 |
Forgot that i removed the patch for the sun slowdown completely oops, it does improve it overall. |
Reminder that this is a workaround for now, needs a proper fix later. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
PCSX2 version: 1.5.0-dev-3212
PCSX2 options: Tried several combinations of round and clamping, and also several gamefixes. No effect.
Plugins used: Default. Happens in both HW and SW mode.
Description of the issue: When looking around, the game works fine and no message appear on the log. But when looking at the sun, the game becomes sluggish and the following message keeps popping up in the log:
sceGsSyncPath: VIF1 does not terminate
<D1_CHCR=10000045:D1_TADR=00121e50:D1_MADR=00121e50:D1_QWC=00000000>
<D2_CHCR=70000045:D2_TADR=00b3daf0:D2_MADR=00b3db10:D2_QWC=00000000>
<VIF1_STAT=00000043:GIF_STAT=00000004>
The VU and GS drops to 0%, but the EE does not change, maintaining the average of 37%. Also, the speed does not change too (100% - 60FPS). My CPU usage drops from 40% to 10%.
How to reproduce the issue: Right at the beginning of the game. Skip all cutscenes and, when you gain control of the character, look at the sun.
Last known version to work: --
PC specifications: CPU: Intel Core I5 4690 - GPU: EVGA GTX 750Ti - OS: Windows 7 64-bit
The text was updated successfully, but these errors were encountered: