04-15-2013, 03:03 PM
(This post was last modified: 04-15-2013, 03:05 PM by VIRGIN KLM.)
(04-15-2013, 06:02 AM)c0nK3R Wrote: I don't really see how cpu state can determine or cause a savestate to work or not.
This break is caused by pgd decryption according to
[Unknown] Wrote:PGD doesn't properly save state, so unfortunately that's expected right now.
-[Unknown]
I only mentioned the video because it shows two thing interesting.
the break happens in a different room than the save state.
And the 2nd one you spawn out of bounds and rendered correctly
It's because more than half of the data of the nearest rooms is cached on the RAM to speed up Loading times. When it will reach something that it will need to read more data like collisions, textures etc, the CPU has no clue what has been loaded already and what not and it fails to call it again. It's the same story on all Kingdom Hearts games across all emulators and I'm pretty possitive it belongs actualy to a majority of games that do that and have simmilar bugs easily covered up by missleading signs.


