(01-26-2017, 11:26 AM)OhMiBod Wrote: [ -> ]As long as it's software and no hardware issue. I hope nougat fixes it. Dolphin has too many bugs and hasn't been fixed in years
This link [removed] someone had something that sounds like same issue and a post claimed to have fixed with HUD & camea adjustment. It's older post and most likely referred to PC ver
Yeah, the issue is that the Mali GPU in Huawei devices doesn't work as well as it should. I personally don't think it'll ever be fixed (needs to be fixed by ARM, not Huawei or dolphin), so you'd only be able to use dolphin with an adreno GPU, or an nVidia gpu. Samsung is rumoured to be working on their own GPU with AMD or Nvidia, to be released in the next couple years, which may or may not have better GPU driver support.
There is a chance that it'll be fixed, but it isn't the sort of think you should expect ARM will fix over time by themselves.
(01-26-2017, 06:53 PM)degasus Wrote: [ -> ]I've just tried it now. Mario Kart Wii runs fine on my nvidia shield. So it's very likely your GPU driver.
Well, can you try the GameCube Ver? I don't think phones are strong enough to run Wii games like shield can. Plus, my phone doesn't run snapdragons and adreno. It runs kirin CPU and Mali GPU so possibly it's my phone GPU but I hope there's a work around !
Try the GC Ver and let me know
(01-26-2017, 06:53 PM)degasus Wrote: [ -> ]I've just tried it now. Mario Kart Wii runs fine on my nvidia shield. So it's very likely your GPU driver.
Also, what could possibly be missing from my GPU driver that would fix this? Is there any a new dolphin update could fix this?
(01-26-2017, 08:28 PM)Grey1213 Wrote: [ -> ]Yeah, the issue is that the Mali GPU in Huawei devices doesn't work as well as it should. I personally don't think it'll ever be fixed (needs to be fixed by ARM, not Huawei or dolphin), so you'd only be able to use dolphin with an adreno GPU, or an nVidia gpu. Samsung is rumoured to be working on their own GPU with AMD or Nvidia, to be released in the next couple years, which may or may not have better GPU driver support.
There is a chance that it'll be fixed, but it isn't the sort of think you should expect ARM will fix over time by themselves.
Funny because all Zelda game on GameCube runs fine visually on my phone. they just lag bit but this issue only happens to Mariokart...And IT ONLY HAPPENS IN RACE! NOT MENU
(01-26-2017, 08:28 PM)Grey1213 Wrote: [ -> ]needs to be fixed by ARM, not Huawei
That is a sad mistake on android. It must be fixed by both. ARM need to fix their driver, but Huawei has to pick the newer driver. Mobile manufactors usually ship one year and older drivers on their new phones, and don't update them at all. Let's hope my last statement is outdated with android Nougat.
So there is quite a good chance that ARM has already fixed the issue, but Huawei just doesn't ship it. But in the end, this makes the GPU driver problems just worse.
(01-26-2017, 08:51 PM)degasus Wrote: [ -> ]That is a sad mistake on android. It must be fixed by both. ARM need to fix their driver, but Huawei has to pick the newer driver. Mobile manufactors usually ship one year and older drivers on their new phones, and don't update them at all. Let's hope my last statement is outdated with android Nougat.
So there is quite a good chance that ARM has already fixed the issue, but Huawei just doesn't ship it. But in the end, this makes the GPU driver problems just worse.
There is light on the horizon. Google's 7.0 and 7.1 CDD's explicitly add rules that will heavily encourage, if not completely force driver updates. For example, on a snapdragon. 810 device, updating to the ES3.2/Vulkan driver version is not OPTIONAL, google will flat out deny the update certification. They are enforcing some level of parity now. The only bottleneck is google's own desire to maintain this behavior.
(01-27-2017, 01:31 AM)Nintonito Wrote: [ -> ]There is light on the horizon. Google's 7.0 and 7.1 CDD's explicitly add rules that will heavily encourage, if not completely force driver updates. For example, on a snapdragon. 810 device, updating to the ES3.2/Vulkan driver version is not OPTIONAL, google will flat out deny the update certification. They are enforcing some level of parity now. The only bottleneck is google's own desire to maintain this behavior.
Proof? Plus, does it mention other chipset aside Qualcomm?
(01-27-2017, 06:51 PM)OhMiBod Wrote: [ -> ]Proof? Plus, does it mention other chipset aside Qualcomm?
It's not chipset specific, I was merely giving an example. As for proof, the CDD documents are readily available for your viewing pleasure on google' android developer portal. Unfortunately they are PDF files so I can't do a hard link to the portion you want.
Just got emui 5 and the problem still persist. Starting to think it's a dolphin issue. Only happens in mk and not present in other engine
Doesn't necessarily mean your GPU driver was updated
Or that they fixed the bug in the newer version. Honestly though, I wouldn't bother trying to run Dolphin on anything that isn't the Shield TV.
All android devices are too buggy and too slow for anybody to care.