Dolphin, the GameCube and Wii emulator - Forums

Full Version: Dolphin runs *very* well on the OnePlus 5
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2

PCMRwill0956

I've got an issue with crashing every time I go to do something. Latest build, latest version of Oxygen OS.


No crash dump, or log.


https://www.youtube.com/watch?v=zRitPPrWixs
This is a small sample size, but it does still show progress over previous devices. The thread title is misleading but I don't think the thread itself is worthless.
(08-27-2017, 08:57 PM)degasus Wrote: [ -> ]No, it is more likely because of a JitArm64 optimization I've pushed. It speeds up by about 3%.

Sorry, I'm not an expert on these types of things as you can see. Does this optimization improve performance on every Android device? Including the Nvidia Shield TV? (Thanks for your hard work developers!)
(08-28-2017, 06:45 AM)Phozz Wrote: [ -> ]Sorry, I'm not an expert on these types of things as you can see. Does this optimization improve performance on every Android device? Including the Nvidia Shield TV? (Thanks for your hard work developers!)

Not counting devices that Dolphin won't install on, it improves the performance on every device that has an ARM CPU. The vast majority of Android devices use ARM CPUs, including the Nvidia Shield TV.
(08-28-2017, 06:50 AM)JosJuice Wrote: [ -> ]Not counting devices that Dolphin won't install on, it improves the performance on every device that has an ARM CPU. The vast majority of Android devices use ARM CPUs, including the Nvidia Shield TV.

Great! Thanks for the reply!
(08-28-2017, 02:45 AM)JonnyH Wrote: [ -> ]If the drivers have been updated for O, it would be useful to see if Qualcomm have fixed their shader_framebuffer_fetch implementation (which can be used to workaround this lack of dual-source blending support) - a build with that enabled can be found here https://forums.dolphin-emu.org/Thread-resident-evil-4-help?pid=447921#pid447921

I'm not on Android O yet, but this technically worked. There's some pretty bad artifacting, but it's definitely an improvement.

https://streamable.com/dy7ns

I first showed latest master. It renders properly, but with a very dark blue tint. Then I ran with the build you sent, which had normal colors and light, but alot of artifacting
(08-28-2017, 02:32 PM)buffsee Wrote: [ -> ]I'm not on Android O yet, but this technically worked. There's some pretty bad artifacting, but it's definitely an improvement.

https://streamable.com/dy7ns

I first showed latest master. It renders properly, but with a very dark blue tint. Then I ran with the build you sent, which had normal colors and light, but alot of artifacting

Bah, still artifacting? Balls.

*hopefully* when O gets released on qcomm devices it'll have an updated driver that fixes stuff like that.

Not holding my breath though....
(08-29-2017, 03:23 AM)JonnyH Wrote: [ -> ]Bah, still artifacting? Balls.

*hopefully* when O gets released on qcomm devices it'll have an updated driver that fixes stuff like that.

Not holding my breath though....

Well it 100% has an updated driver, even newer than the S835 launch driver.  No idea whether said driver fixes it.
Android O reportedly gives us the ability to update the graphics drivers cmiiw. At least the user space side of them. Is this useful at all for dolphin development?
(08-30-2017, 04:00 AM)Whatnoww Wrote: [ -> ]Android O reportedly gives us the ability to update the graphics drivers cmiiw. At least the user space side of them. Is this useful at all for dolphin development?

As the userspace part is by far bigger than the kernel part, such an update may include lots of improvements. However, the ability of updates doesn't tell about the update rate....
Pages: 1 2