-
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] Danganronpa compatibility broken after v0.9.1 #5403
Comments
This may possibly have to do with your "render resolution" setting. It won't be easily fixed with a range of thousands of changes, unfortunately. "Somewhere in the middle" of 0.9.1 and 0.9.5 is a very large range. It's not likely to be fixed without being narrowed down farther, unless someone can reproduce it and figure out what it is (which won't be me, since I don't have this game.) -[Unknown] |
I have tried changing the "render resolution" setting, but it doesn't solve the issue. I'm willing to try narrowing down the problem, but I can't seem to find older PPSSPP revisions. The latest one available at buildbot.orphis.net/ppsspp/ is v0.9.5-1-g3abeb62. |
Visit Orphis buildbot using old cached versions from Web archive and also by using EmuCR builds. |
All I can say for the moment is that the issues remain with the v0.9.1-1901 revision. Edit: Everything works using the v0.9.1-1473 revision, so the issue has been narrowed down a bit. Edit 2: v0.9.1-1573 works. v0.9.1-1763 doesn't. Final edit: both v0.9.1-1647 and 0.9.1-1665 revisions crash when opening the game. There is not much more than I can do with what I have. |
After some more testing, v0.9.1-1724 can load the game, but issues remain. To sum up, this issue begun shortly after v0.9.1-1573, but this is the most I can narrow it down using the revisions available at EmuCR. Could someone take a look at http://web.archive.org/web/20131220221844/http://buildbot.orphis.net/ppsspp/ and see whether there was a critical change between those versions? While it is not possible to download the apk files, the archive allows you to follow the links to see the changes. By the way, this issue has been reproduced multiple times. Anyone can read the last pages of this thread (http://forums.ppsspp.org/showthread.php?tid=940) for more information. |
Is there anything I can do to help? I've noticed that there is now more information about the last 0.9.1 revisions at buildbot.orphis.net/ppsspp/, but it is currently not possible to download those builds to test on my 2012 Nexus 7 device. I would be willing to try them in order to narrow the issue down. |
Games tested: Danganronpa & Super Danganronpa 2 my Xperia S seems to be working with examining objects while the "Read Framebuffer to CPU" was enabled. But, there are some objects that cannot be examine even "Read Framebuffer to CPU" was enabled unless if changing the Rendering Resolution to x3 or x5 will become accurate. 1x and 4x may be working but there are few objects are left that were unable to examine like the Library in SDR2 #2765 (comment), So I recommended x3 or x5 are accurate to examine objects. Unfortunately, the performance was extremely slow. |
Sadly, changing the rendering resolution doesn't seem to be working for me. (0.9.7.2 - 223). It is certainly strange, though, that some people are able to investigate objects using the Android version of PPSSPP while others can't. |
@udllpn |
Taking a look at the forums (http://forums.ppsspp.org/showthread.php?tid=940), a person with an HTC Desire 500 and another one with an HTC One were able to examine objects. On the other hand, the Samsung Galaxy S2 and the 2012 Nexus 7 are not able to make the game work correctly. I'm using Android 4.4.2, by the way. |
Most likely the game is looking for an exact color match to figure out what you're clicking on, and these GPUs where it doesn't work miscalculate slightly, could be an approximation or something. Would be interesting to see if there would be a difference when using highp (high precision) on all the variables in the fragment shaders. |
@udllpn while Samsung Galaxy S2 have 2 different models (Exynos and Snapdragon) but i think he was has the Exynos. and Nexus 7 2012 uses Tegra SoC. I just think that Android version is not the cause of the issue now. Summary: Not Working @hrydgard |
It would be interesting to know if it works on PowerVR or Mali, rather than just Exynos. I'm guessing it's more to do with the GPU vendor than the SoC. It's possible that it's not even working properly on these other chips, if no render resolution works. So it could be an approximation problem, or it could simply be an OpenGL issue. @hrydgard fwiw there is a demo (http://danganronpa.wordpress.com/downloads/, http://www.pspdemocenter.com/page.php?id=3434), and it seems like it's possible to get this problem there. -[Unknown] |
I don't know how much help this information is, but I can confirm this issue exists in a Motorola Razr D1 (Adreno 200 if I am not mistaken). While I know it is a relatively low-end device, no other game has given any problems while using the emulator. |
After testing the latest build, I'm happy to report that everything works as intended. The problem seems to have been fixed. Thanks a lot. |
Okay, great. That was what I was hoping for. If there's an issue on a specific chipset still, please comment and we'll either reopen or open a new issue. -[Unknown] |
I am afraid to inform that I have just tested the latest build (available from the Play store) and the inspection still doesn't work. I tried all the rendering options. My phone specs are in my previous comment. |
The build on Play Store is very old. Grab it from ppsspp.org/downloads |
Indeed. Just tried the latest version from the build-bot; inspection works just fine now. Thanks for the answer. |
Although issue #1686 (inability to examine objects in Danganronpa) was apparently resolved, changing from buffered rendering/non-buffered rendering to 'Read Framebuffers to Memory' does not currently work using Android.
I've been doing some testing and this is what I've found:
I have not been able to try more versions because they are not available on Github. Somewhere in the middle, compatibility was broken, so I think it might be easily fixed.
The text was updated successfully, but these errors were encountered: