-
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
Forced close and decreased OpenGL performance on latest builds #11715
Comments
Any chance you can test a few intermediate builds and see when the problems started happening for you? I haven't noticed anything like that, but it'll likely be device-dependent. |
I also noticed that in Tekken 6, Need For Speed Underground Rival and GoW Chain Of Olympus. Phone Quick Specs: |
OK, I'll do it. |
If it's just about the timer hack, maybe try downclocking instead? Although, it's well known that that won't work with Tekken. |
@Emulatorer There's a CWCheat that allows to use custom clocks with Tekken 6, but I don't know if it works properly. Also you can use a cheat to run GoW at 30 FPS (if your phone can't handle 60 FPS), it worked fine for me. Check this link: https://forums.ppsspp.org/showthread.php?tid=22787 @hrydgard the both issues started with the build 332, the first build available after 321, so might be some revision between them. |
So that's #11694 . Very strange, wouldn't expect anything in there to affect perf, but hey ... I've said that before :) @unknownbrackets this seems rather strange.. |
This may explain the force close, but I don't understand how a Vulkan workaround could affect OpenGL performance. But it reminds me that sometimes when I tried to switch to Vulkan the app crashed too. |
Do you have an Adreno? Which one specifically? Can you get a logcat of the crash? That range also includes #11695. So the possible GLES effects are:
I think the first one is the most likely by far, at least for perf impact. I don't know about crashing. -[Unknown] |
@unknownbrackets I have Adreno 509 (Snapdragon 636). I'll try to get the log later. |
Here is the zip file: https://drive.google.com/open?id=1ja0i_mVi-jLTXqdL5E4K6Covj2R-iaJ_ I played the game for a while, then I got back to the PPSSPP main screen and pressed the home button, tried to open emulator again and the app crashed. |
That link doesn't work, did you share the file? Ok, so yet another task switching issue to track down. I know from Google Play reports we have one or two really weird ones left... |
That's weird, the link was working then suddenly don't. I uploaded to another server: https://www.mediafire.com/file/5v75z3kkgbd4ehg/ppsspp.log/file |
Maybe a buffer not being cleanly reinit? -[Unknown] |
How is stability now? |
The performance decreased (OpenGL) continuesly happen in the latest git build I notice 5 fps frame drops in Tekken6, GoW chain of olympus & ghost of sparta compare to v1.7.5 🤔 |
That is still surprising, need to figure out what it might have been (in that test, did you disable Timer Hack on 1.7.5?) |
Nope I always enable it in GoW & Tekken 6 😅 |
Well that could be your speed difference then. Maybe removing it was a little hasty, although it is a really gross hack heh. If you compare performance of 1.7.5 without Timer Hack with current performance, how does it look? |
v1.7.5 timer hack off still better compare to the latest git build that occasionally frame drops from 1-5 fps v1.7.5 timer hack on only give me 1-2 fps increase though 🙂 *Sorry for my english |
@cheding09 can you also test if you experiencing occasionally frame drops using the latest git build as we both have same unit 🙂 |
Aperently MC3 is running better now with OpenGL, and I haven't noticed any crash. But I'll still need a better CPU or better Vulkan drivers to run at 60 FPS. |
So at this point this is just about performance loss, potentially due to shaders that were compiling wrong but not causing any obvious visual issues? Let's not lump in other settings changes (timer hack, disable slow effects, etc.) that have changed in behavior here. If that made sense, we would just have one issue - "PPSSPP is not perfect". But that's a horrible way to fix issues, it's better to break them up and look at each one separately. -[Unknown] |
v1.7.5 without timer hack enable still perform better than the current beta build in my device :v |
UP NFS: Most Wanted run smoothly on v1.7.5-471-g8090c3db5 build Now v1.7.5-473-g4d8f3c48a up to 1.7.5-504 makes the game choppy Also what do you call this little squares on tint ? Unit Specs : |
Those squares are a known driver or hardware bug in that GPU. It happens in a bunch of other games too. There is no 1.7.5-472. v1.7.5-471-g8090c3db5 changed Qt, and v1.7.5-473-g4d8f3c48a changed Windows. Neither of these would affect Android. Can you double check which version changed performance? If the version is actually v1.7.5-479-ga0d4abae2, then you probably have the sync real clock setting on, which was broken before but is expected to reduce performance (it basically improves input lag at the cost of performance.) Note also that there are two "v1.7.5-477" for example, so best to just copy and paste the entire thing. -[Unknown] |
@cheding09 the little square is a normal My only issue is the performance of the current build is decrease in OpenGL compare to v1.7.5 🤔 |
@unknownbrackets The graphic bug does not affect performance though, I was just hoping to make it perfect graphics and gameplay😁 I will try to record test on the versions you said, maybe later or soon👍 @odrac Yalisad Anayla |
@unknownbrackets |
I think we can close this thread 😅 (imo) |
Yeah, I don't think there's much to do here. I hope to find time to work more on overall performance after 1.8.0. |
Using the latest builds I have random forced close's, sometimes when I exit a game and go to menu, or when I exit to home screen directly I receive the forced close message. I also have been trying old version and noticed that OpenGL performance is better with 1.7.4 (downloaded from official page) than it's with latest builds. Midnight Club 3 runs 50-60 FPS on 1.7.4, on latest builds it runs 40-50 FPS.
The text was updated successfully, but these errors were encountered: