Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Resolved: [Bug Report] IPU1 Normal error: Fatal Frame 3: The Tormented [NTSC-U]
#1
# PCSX2 version: v1.3.1-2015222221738(git)
# CPU options: EE/IOP defaults, VUs defaults
# Plugins used: GSdx 2015222221738 (MSVC 18.00) 0.1.16 (hardware, dx11), SPU2-X 2015222221738 2.0.0
# Description: Once you start the game and select a difficulty setting, the game just hangs and the log is filled with "IPU1 Normal error!"s.
I've tried a few different ISOs, so I don't think it's a bad dump.

Sponsored links

#2
Tried software mode ?
CPU : AMD Ryzen 7 3800X
Mobo : Asus PRIME B450-PLUS
GPU : NVIDIA GeForce RTX 3070
RAM : 16 Go
#3
Just tried that, didn't work either.
#4
Give PCSX2 v1.2.1 a try. Maybe something in the recent builds broke it.
AMD Ryzen 5 3600 @ 3.60~4.20 GHz | Corsair Vengeance LPX 16 GB (2x8GB) DDR4-3200
MSI GeForce GTX 1660 Super @ 6 GB | Kingston A400 480GB SSD | Windows 10 Pro x64 (b19043.1288)
#5
Hm. That didn't work either.

Would it help if I shared my inis?
#6
also, post your emulog. and, are you using any non-default settings ?
We're supposed to be working as a team, if we aren't helping and suggesting things to each other, we aren't working as a team.
- Refraction
#7
I think I found the cause.
Apparently this game doesn't work if you use "Boot CDDVD (Fast)", you have to use Full, at least the first time. (it works with Fast after that, and I can no longer reproduce the crash?)

That said, the emulog still has quite a few error messages in it, so it might still be of use to you. Here it is: http://pastebin.com/me5vNmA3
#8
as suspected, full boot doesn't make use of the automatic game fixes in some instances so, that's probably the reason why the crash occurred.
nevermind, I was confused a little bit. there is a rule of having a interval of 5 minutes between every posts is for newbies below 5 posts.
We're supposed to be working as a team, if we aren't helping and suggesting things to each other, we aren't working as a team.
- Refraction
#9
Alright. But like I said, those errors still appear in the log even with full boot. And it's working in fast boot now for whatever reason.

Also, I doubt it was automatic gamefixes. During my testing, I disabled them and it still crashed. (Unless you meant that fast boot doesn't make use of them, and typed full by mistake?)

(PS: Why does it make me wait two minutes to post a reply?)
#10
(02-24-2015, 04:52 PM)ssakash Wrote: as suspected, full boot doesn't make use of the automatic game fixes in some instances so, that's probably the reason why the crash occurred.

He said he used Fast Boot. And only after using Full Boot once it seemed to work. He never said he used Full Boot the whole time.
AMD Ryzen 5 3600 @ 3.60~4.20 GHz | Corsair Vengeance LPX 16 GB (2x8GB) DDR4-3200
MSI GeForce GTX 1660 Super @ 6 GB | Kingston A400 480GB SSD | Windows 10 Pro x64 (b19043.1288)




Users browsing this thread: 1 Guest(s)