Retroarch android psx beetle hw wont download

When trying to load any game with the hardware renderer, I get a black screen and the message "Unable to find or open hardware renderer for frontend".

Both gl and Vulkan produce this. Software renderer works fine. It started a week ago. I heard from ggdrt that this area of the code was changed recently. I'm on the latest version as far as I know 1. The text was updated successfully, but these errors were encountered:. For the "Renderer Restart " core option, what do you have it set to, and importantly what does your frontend's video driver set to?

Sorry, something went wrong. I just tried it with Hardware OpenGL and the backend as gl, and I got a different error: "attempted to force opengl renderer, but core was built without it".

Doing the exact same thing but with Vulkan actually makes the game boot up, but has the usual Vulkan graphical bugs that we've had for a while now. Like rz5 mentioned in that previous closed issue, the core is not built with GL support on Android. The new Hardware Auto option is the same as the Hardware option in previous versions of the core.

It attempts to run a hardware renderer for what your frontend requests. Because your frontend is requesting the GL renderer but the Android core does not have support for it, you will receive the warning in your original post. Similarly, forcing the GL renderer through the core options when the core is built without GL support will give you the second warning that you mentioned. So the core options are working as expected.

If you're unsatisfied with the Vulkan renderer you could alternatively run core in Software mode instead. The Vulkan renderer does have bugs, but the issues are typically much less severe than the GL renderer. How is that possible? I spent a lot of time with this core, and the performance was clearly better with the hardware renderer than the software, and I didn't have any bugs, so it didn't fallback to Vulkan. I used to get 60 fps most of the time, now with software I'm getting 40 fps, and with Vulkan I get bugs.

Clearly, there used to be a third option that is no longer available. MegaDeox - Specifically about this bug: you CAN get something other than a black screen and you do NOT get the "unable to find hw renderer for frontend" message, correct? Please consider opening a new bug report about whatever bugs you currently have with the Vulkan renderer on Android and go into as much detail as you can.

Just be aware that we already know of About this core being slower: there's several moving parts to verify first before making that statement. But despite those moving parts, you now also have access to a CPU dynarec option that should get you back into fullspeed. Test that out as well. I really don't think anything changed on my end. The core worked fine, I updated it, and It stopped working. I think I already opened a bug for the Vulkan thing a few months back, I'll try to find it.

MegaDeox - I need you to be specific on this: does it still not work for you on your end? You're still getting the black screen and error message as described on your original post?

What happened was I had the renderer set to hardware there used to be just one hardware option with gl, and everything worked fine.

Then I updated. The aforementioned scenario gives me the error in the OP. Setting the backend to Vulkan gives me graphical glitches, like before the update. Setting the renderer to software gives me poor performance, like before the update. Playing around with the dynarec does not help the performance with the software renderer. You didn't use to get that error because the fallback handling wasn't even working properly back then. Prior to 2efd the Hardware setting would always force the Vulkan renderer.

Between 2efd and d4f8 , the Hardware setting would force the Vulkan renderer in any case where the frontend driver was not OpenGL. Because the Android build does not even have the checks for initializing a GL renderer built into it, I am highly certain that you were falling back to either the Vulkan renderer or software renderer at 1x resolution , depending on whether or not your frontend at the time had support for requesting a specific renderer from the core. I was even able to bump to 2x in some games.

There had to have been a difference. MegaDeox - In , tabnk did say he had lower performance when using the Vulkan renderer. If I need to change any other settings, or even open a new issue for this here, let me know. Regardless, thanks again for your help, much appreciated. MediEvil, from what I played, hovers around 60fps with some dips here and there, and the graphics look great here as well. Maybe THPS2 itself is problematic. Still, I think we should be able to achieve 60fps here. I've used the frame duping feature but that doesn't seem to help much.

Not sure this is relevant to this bug anymore but try disabling software framebuffer for a speed up. Still, you're not going to get 60 fps in most games, not even close in some. I also have a phone with a SnapDragon EDIT: Maybe better to create a new issue regarding performance if you think it's needed. I warn you, I created one about the same issue a couple of months ago and was closed almost straight away It's a shame.

Mine doesn't even have the SD, it's the Exynos model. Still, pcsx for example seems work fine on 1x no other option , so I'll even take that in Beetle HW, but that doesn't seem to achieve 60fps either. Like kikeminchas said, if you can't get fullspeed at 4x upscaling, drop it down till you can. If you still can't get stable framerates Frame duping and disabling the 'software fb' option will give you a very small perf increase.

The hardware renderer is only really faster at upscaling graphics. At 1x, it shouldn't be any faster versus the software renderer. For a true boost in performance, we need a dynarec like in pcsx-reARMed.

As for your graphics issues in THPS2, maybe open an issue if you can't get it fixed, maybe it's a bad dump, who knows. Use that instead of this core;. Reopening this because fdd reverted the fix.

That literally only ruins what you've done! Skip to content. Star New issue. Jump to bottom. Copy link. Description When you update the HW core via online updater on android, on either version of RA, the downloaded core is actually the normal version. Actual behavior The core appears identical to the normal, non HW version. I'd appreciate you contacting the devs. Thank you! The litmus test is if you see the PGXP and overclock options as new core options. Linking the commit for reference.

Don't forget to close the issue if it's working. I tested it now, and even with Vulkan and 4X, I'm getting 40fps and weird graphics, seen here: If I need to change any other settings, or even open a new issue for this here, let me know.

Alright so the reported issue is fixed, good. It's back in. TA already re-added it. Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment. Linked pull requests. You signed in with another tab or window. Reload to refresh your session.