Galaxy s7 edge crash
|
05-18-2016, 10:59 AM
(This post was last modified: 05-19-2016 08:03 PM by Jaaan.)
![]() |
|||
|
|||
RE: Galaxy s7 edge crash
Quote:To confirm, with option 1 + 0xFF (which is the 4096 + 256 option), you haven't gotten any crashes? 0xFF does not crash. I can check it out again if you like. But I haven't experienced any crashes with it as of yet. Like I said, where I could load maybe 3 or 4 on the 0x7F, 0xFF I could close and open as many as I want and let it load to the main menu. I don't see a 256 in the emitter code though, nor in the armjit. Option one only uses 4096. The other options don't have a 256 in them either ![]() Code: for (int h = 0; h < 64; ++h) { On this now! Okay did that. First time loading KH, everthing looks fine. Loads to the main menu fine. Starting a new game, also fine. Loads up to gameplay fine too ![]() ![]() Now to close the game and open another. Loaded GOW, no crash yet ![]() Now I'll try to load as much games as I can to the main menu and see if any crashes happen with that. Looks like nine games load to the main menu fine without crashes. Yup. and then starting over at game 1 won't make it crash either! ![]() I'm gonna play to the orb fight one more time and change games to see what'll happen, then I'm gonna try it with 32. 2nd time went fine too, KH performed without issues all the way up to world 1 again. This was in the same instance where I opened all those games, so PPSSPP was still in ram. Now to close it and open another game. Game opened. Loads the main menu fine, starting a new game gives gameplay ![]() ![]() Now off to try it with 32! 32 loaded up, gonna have to go do some errands, will try some stuff in the meantime and will be back soon. Seems like 32 works just as good as 64! Didn't crash once and did the same things as with 64 mostly. Now off to try 16! Fingers crossed. Alright so 16 doesn't get me gameplay. Crashes before the main menu on most games, otherwise just after. The workaround works but as soon as it gets a chance to load it crashes. Going back to 32 and see if it eventually crashes. Okay played all the way to the first boss on Aqua's story, the pumpkin car thing. Died there though. No crashes! All the way from loading up to the game to that point! Now going to switch to another game and see what happens. Ninja impact loads up to gameplay all the way fine too! Now trying out another game. Type-0 also gets me gameplay! all in the same instance too! And the performance on type-0 is somehow better than on the build with 0xFF. Anyways looking good, this one! ![]() Kizuna Drive and GOW both also loaded up gameplay fine, and was able to play around for a while. Not one crash on 32. Btw people if you are following this, which I know you are since the views keep climbing up ![]() Not trying to force anyone btw. Just saying Almost forgot: Name under CPU information = Unknown lol Still no issues with 32 For the heck of it I replaced the arm64emitter code to the original un-edited version, without the 2 lines of extra code, and with the for loop this also works! Getting gameplay on KH on first try! No crash on meteor shower. No crash after tutorial fight. No crash on orb fight and performance is good. some dips though. first map also loads fine. going to keep using this and see how it performs. It crashed upon closing KH and opening GOW, it loaded some and crashed before the main menu. Re opened PPSSPP and it reloaded GOW and it loads fine now. Nah, not as good as with the 2 lines of code. It crashed 2 times already. Well I loaded back the one with the 32 for loop and no issues. Performance is just as good as the one with the while loop. |
|||
« Next Oldest | Next Newest »
|