Emulator Issues #10931
Toy Story 3: assert on invalid CP register load
Toy Story 3
Game ID? (right click the game in the game list, properties, info tab)
What's the problem? Describe what went wrong.
The game hangs with a "Line 344 Vertex LoaderManager.cpp" error during load.
What steps will reproduce the problem?
Start the title, wait breifly for error and crash.
Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.
Is the issue present in the latest stable version?
What are your PC specifications? (CPU, GPU, Operating System, more)
Intel i7-6700, GeForce 970. Windows 10
#1 Updated by JMC4789 about 2 years ago
- Status changed from New to Invalid
Working fine for me in 5.0-7686 in single core. Also tried dualcore a bit and it was fine up until the train section. Also it's probably not a hang as much as "hey, this needs to be tested" and turning off panic handlers would get around it if you used it.
#10 Updated by kolano about 2 years ago
OK, so it does happen for you JMC when Panic Handlers are enabled. I presume this should not still be marked as questionable?
I tried to click through the errors for a while and they seemed to repeat endlessly preventing progressing into the game. So yeah, it may not be a "hang" but I'm not clear if once can click for long enough ignoring errors to get past (I understand such can be avoided with Panic Handlers disabled).
#11 Updated by JMC4789 about 2 years ago
Qt has the option to "ignore for this session" on panic handlers but it's not working.
Hang is not a great description because everyone usually think of it as a game hang. This is the UI being stupid :(
This is a valid issue, of course, we just need to figure out where to group it as other games hit this.
#15 Updated by Miksel12 about 1 year ago
I tested the game today and the error is still there, disabling panic handlers fixes the error though the fps drops (even lower, dynamic bats already lowered it from 60 to 20 fps) during the load screen in which the error would occur. I hoped it would have been fixed in the videocommon unification pr.