KAMI
KAMI copied to clipboard
isJuhn
Object reference error when launching game or at random
As title says, there's an object reference error that occurs at random or when launching a game, making it impossible to play using it.
I've probably got the same error here.. haven't found a fix yet, but will let you know if I do.
found it.. turns out it's the hotkey "CTRL +S" from RCPS3 that triggers it. I played the Killzone 3 campaign for over an hour without crashes just by avoiding that combination (cause I didn't find a way to bind it to other keys). In the end I tried that hotkey and the game immediately crashed with the same error. Try it out!
found it.. turns out it's the hotkey "CTRL +S" from RCPS3 that triggers it. I played the Killzone 3 campaign for over an hour without crashes just by avoiding that combination (cause I didn't find a way to bind it to other keys). In the end I tried that hotkey and the game immediately crashed with the same error. Try it out!
That's really interesting! I'll keep that in mind, thanks for the tip! I still won't close the thread though because some of my problems are still present but I'm glad to know part of it has been resolved.
I am also getting the "object reference not set to an instance of an object" error, but it seems like it is specific to Resistance: Fall of Man. I am able to successfully load and play Resistance 3 and Killzone 2 with KAMI active. Resistance: FoM can load the main menu, but if Kami is activated it fails with the object error upon attempting to load a level.
A little further info. The error causing a crash is introduced in RPCS3 build 0.0.29-15807 (Dec 15, 2023). To fix the issue, revert to Build 0.0.29-15787 (Dec 8, 2023) . The error will still occur upon loading a level in Resistance FoM, but you can dismiss it and just press KAMI's activation button again, once the level starts.
The error occuring, without causing KAMI or RPCS3 to crash, goes back to builds that predate the most recent version of KAMI... I'm not sure what that is about, because I know I played without error at least as recently as the most recent version of KAMI... but as it stands right now, I tested all the way back to builds from January of 2023, and the error still occurs -- BUT, it's not a serious issue, until the Dec 15, 2023 build, when the crashing is introduced.