mirror of
https://github.com/hrydgard/ppsspp.git
synced 2026-04-25 06:06:03 +03:00
[GH-ISSUE #804] Android issues #227
Labels
No labels
Atrac3+
Audio
CPU emulation
D3D11
D3D9 (removed)
Depth / Z
Feature Request
Font Atlas
GE emulation
Guardband / Range Culling
HLE/Kernel
I/O
Input/Controller
MP3
Multithreading
Needs hardware testing
Networking/adhoc/infrastructure
No Feedback / Outdated?
OpenGL
PGF / sceFont
PSMF / MPEG
Platform-specific (Android)
Platform-specific (Windows)
Platform-specific (iOS)
PowerVR GPU
SDL2
Saving issue
User Interface
Vulkan
arm64jit
armjit
armv6
x86jit
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ppsspp#227
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @willyvvu on GitHub (Feb 27, 2013).
Original GitHub issue: https://github.com/hrydgard/ppsspp/issues/804
I'm using Android 4.2.2 (Nexus 4) with PPSSPP version 0.6-755-g76433a4. I'm amazed that PPSSPP is currently in a usable state, but with any new software, there are bound to be issues. I've stumbled across a few.
Interface and App itself (P.S. Nice typography and live background!)
Problems with Wipeout Pure and Wipeout Pulse
These are the two games I tried to play. The gameplay works fine, but the only thing problematic is the graphics.
Screenshots
Overbright Wipeout Pulse Menu


Overbright Wipeout Pulse Gameplay


Buffered Rendering turned off in Wipeout Pulse


Overbright Wipeout Pure


Strange glowing cube in Wipeout Pure

Look closely: It's surrounding the ship!
@unknownbrackets commented on GitHub (Feb 27, 2013):
Must say, I agree with the tap thing. I recently tried it on an iPhone and found it hard too. It needs to have a longer delay before thinking I'm doing a gesture imho, but I don't know that stuff well.
Anyway, might be better to separate this out a bit since there are feature requests and bug reports mixed together.
I will say the "super glow" issue is a new bug introduced recently, we just have to figure out how to tone it down.
And the music, it's not implemented yet. Unfotunately, the ATRAC3+ codec is not well known yet.
-[Unknown]
@hrydgard commented on GitHub (Feb 27, 2013):
Thanks for the report! Most of these are well known though and the Wipeout issues are by no means unique to Android as you could have verified by running the emu on a PC as well.
We already have an issue about the app not working when task switching away, https://github.com/hrydgard/ppsspp/issues/802 , maybe we could make it about Android app issues instead.
The issues with hard to choose games in the list is also known. Trying to write a touch-scroll list from scratch has given me new appreciation for what Apple faced when they created the first good one, it must have taken them many tries and much experimentation before they saw that what they did was awesome.
The super glow is not really a new bug, it's just that since render to texture started working better recently it's now visible, previously the super glow was being rendered but not correctly copied to screen. I think the overbrightness is caused by the game doing some trickery with the fact that destination alpha and stencil bits are shared on the PSP. They are not on the PC and it's very hard to achieve that behaviour with OpenGL ES 2.0, but it may be possible to fake.
I also have plans to make non-buffered rendering smarter which could avoid the black rectangle.
As always, patches and pull requests welcome :) All can be fixed, it's just a matter of time and work.
@willyvvu commented on GitHub (Mar 8, 2013):
I have minimal experience in C++ and Java, but I am proficient in JavaScript, CSS, and HTML. Is there any way I can contribute to solve some issues such as the touch scrolling issue? I have an idea as to how to improve it.
@hrydgard commented on GitHub (Apr 9, 2013):
This should be split up into the remaining issues one by one as it's not workable to have a huge multi issue like this, hard to categorize for releases for example.
@willy-vvu , can you please file new issues for the remaining bugs that don't already have issues?
@willyvvu commented on GitHub (Apr 22, 2013):
I am really late to reply, but sure. I'm fairly busy but I'll keep this in my head for when I get some spare time.