-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Android] Spider-Man 3 crashes unexpectedly #10196
Comments
Did this used to work in 1.4.2? Does it matter which GPU backend you use? What device? Do other games work? Since you didn't provide any detail, we can't tell if you're using some obscure MIPS Warrior CPU or what. Nothing can be done if you don't provide detail. -[Unknown] |
I don't have access to the game right now, so I can't test on v1.4.2. My GPU: Adreno 530 (Snapdragon 821 chipset) |
Update: No crashes on the PC version. I only tested the OpenGL backend. |
A few things that cause crashes have been fixed - does this still happen on the latest git build? It'd be great to find the first build it stopped working on. For example, if you knew that 1.4.2 worked, you could test somewhere around v1.4.2-475-ged602a331. If that worked, try a newer build, if not, try an older. In 8 - 10 tests you could narrow down the change that caused it. Usually this makes it a lot easier to fix the issue. If no previous version worked, it can be tricky. -[Unknown] |
@unknownbrackets |
This log was posted by @weihuoya in the above thread:
|
It's very strange that this crashes even in the interpreter, but only on Android. Just not sure what would be different between Android and Windows that would affect CPU emulation. To confirm, PC is fine even in interpreter and with fast memory enabled? -[Unknown] |
Oh, that's interesting. We definitely might not be handling misaligned sv.q the same in all jit backends... -[Unknown] |
Well, looking at the error more carefully - the fault is at 0x2300014000 right outside the scratchpad. So I guess it's not alignment... Anyway, the behavior DOES differ a bit per backend:
Though, I guess that's not related after all. -[Unknown] |
Game still crahes in the latest git build :( |
Game still crashing Im using ppsspp v1.8.0-403 gbdd9d40a1 |
This game doesn't crash in ppsspp v0.9.8 https://youtu.be/_L73ZLVJEHA and also it's performing better in my phone compare to the last gitbuild 🤔 |
@unknownbrackets after several testing Spider-Man 3 didn't crash in v0.9.8 (performance better in my phone) and v0.9.9.1 (slow on my device with graphical glitches) The game crash in area where I mentioned above tested in v1.0 - 1.4 🤔 PS: sorry for my bad english |
PPSSPP Last Build Sample Video PPSSPP Old Version 0.9.8 Sample Video *Note: ppsspp v0.9.8 has better performance without screen recording in my phone (arm32/Mali-450/octacore) |
It's possible this was caused by the hardcoded use of 0x2300000000 which was recently changed. Does this still happen in the latest git builds? Any performance issue is separate. -[Unknown] |
@Leopard20 can you test in the latest builds if this still happens for you? |
Still crashes on my phone same area where the game always crash I'm currently using v1.8.0-583-gc8730c933 🤷 |
Okay that's unfortunate, but thanks for testing! |
Can you check the CRC of your disc as well? I ask because people have reported this game as "Perfect" on mobile devices: It seems like there are various CRCs floating around, so I just want to confirm this isn't somehow related to a bad rip. Since it's supposed to crash in the first few seconds, I imagine no one would mark it "Perfect" on mobile... -[Unknown] |
Also, if the white shading on spiderman in those screenshots is wrong (it sure looks wrong, or at least not great, to me?) a GE frame dump would help. -[Unknown] |
oh i see,unlucky this is not happened in my black shark 3 phone
在 2021年1月5日週二 下午6:27,Henrik Rydgård <notifications@github.com> 寫道:
… yea this is almost certainly not a GPU-related issue.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#10196 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAQTT7H2MAAT3G6FNSQPVXLSYLSRBANCNFSM4EFMYFEQ>
.
|
@Leopard20 did you change cpu clock ? |
nope, I never change that. |
I wonder if this is because the the Memory::ValidSize improvements. -[Unknown] |
or maybe it's just working on that device ¯_(ツ)_/¯ |
So maybe there's a difference in some checking in ARM32 builds, the memory mapping we do in ARM64 not matching up perfectly with ARM32's masking perhaps? Struggling to think what the difference might be... |
Nope, not fixed for me either (ARM64) |
Another snapdragon phone ppsspp user is @Panderner can you reproduce this issue!? |
Maybe it's somehow relying on some framebuf download? -[Unknown] |
Not also crashing on Redmi 9T Qualcomm SM6115 Snapdragon 662 (11 nm) my Sister new phone |
It doesn't crash on my adreno 506 🤔 |
Well, we have two issues that are now effectively about the same thing. I'd suggest we close one, perhaps this one. Obviously something has gone wrong if the same comment is being cross posted between two issues with almost the same title. -[Unknown] |
I had a Xiaomi phone, and the game was working properly, and there was no problem, no damage, no crash |
Extra information from the user above: Device that the game crashes: According to the user, their Xiaomi Poco x3 Pro phone never had this issue. Hopefully this information is relevant. |
Closing this as duplicate of #15825 as that one has more relevant information, even though it's newer. |
PPSSPP crashes in the first few seconds of the game. Don't know why or exactly when.
(So that search for the alternate spelling works: Spiderman 3).
The text was updated successfully, but these errors were encountered: