Posts: 2
Threads: 0
Joined: Aug 2014
Reputation:
0
I can get this run on the latest Windows 64-bit build of JPCSP (3583 , ) but only if I start it from a new JPCSP instance , if I try and load it after loading something else it freezes at 0x88000000 with the same sympton (Black Screen), might be related if someone is trying to debug this.
Posts: 2
Threads: 0
Joined: Aug 2014
Reputation:
0
Did some more testing:
This game "broke" with Build v0.9.8-1054-g0f16872 when FuncReplacement was set to True by default.
This runs on the latest build if Function Replacement is turned off.
Edit memstick\PSP\SYSTEM\ppsspp.ini and under [CPU] replace
FuncReplacements = True
with
FuncReplacements = False
So under that condition it's Playable.
Posts: 5
Threads: 1
Joined: Sep 2014
Reputation:
0
09-25-2014, 10:12 AM
(This post was last modified: 09-25-2014, 10:56 AM by nicohuhuru.)
does anybody have the cwcheat for this game? thanks
can anybody please tell me what app to use to read .ini files on android?i cant seem to read it. thanks
can anybody please tell me what app to use on reading .ini files. i cant seem to read it. thanks
Posts: 3,228
Threads: 25
Joined: Nov 2012
Reputation:
98
Does turning function replacements off still fix it? Anyone with a compiler and this game willing to debug/
-[Unknown]
Posts: 35
Threads: 1
Joined: Jul 2013
Reputation:
0
Yes turning replacements off still fix it. But cant help with debug.
Posts: 3,228
Threads: 25
Joined: Nov 2012
Reputation:
98
From which memset hash it's using, I figured out the cycle counts. Apparently this also helps:
//return 10 + bytes / 4; // approximation
return 5 + 6 * bytes + 2;
(within Replace_memset()...)
But, this may just mean that something else there is incorrectly timing or is causing it to be sensitive to timing. For example, drawing may be returning too quickly or something.
-[Unknown]
Posts: 34
Threads: 1
Joined: Jan 2013
Reputation:
1
It's { 0xeabb9c1b4f83d2b4, 52, "memset", }, // Crisis Core
yes, return 5 + 6 * bytes + 2; works
Posts: 14
Threads: 3
Joined: Feb 2014
Reputation:
0
Crashes on Android.
10-07 13:29:39.271: E/WindowState(4472): The process of this window already died: Window{1c689fc7 u0 d0 org.ppsspp.ppsspp/org.ppsspp.ppsspp.PpssppActivity} : android.os.TransactionTooLargeException
Posts: 3,228
Threads: 25
Joined: Nov 2012
Reputation:
98
05-28-2016, 07:53 PM
(This post was last modified: 05-28-2016, 07:54 PM by [Unknown].)
The latest release uses the new memset timing (and I think the one before too.) Is this working now?
If it doesn't work on Android still, need more of the log. That one line isn't enough... that's after it already crashed, just Android complaining that an app crashed.
-[Unknown]