(07-22-2018, 05:09 AM)JosJuice Wrote: [ -> ]What version of Android you have doesn't tell you what problems there will be with Vulkan. The driver version is what matters, not the Android version.
I will give some feed back if you need
Previous dolphin version :
Sonic Colors in Open GL : NO Hud Elements
Sonic Colors in Vulkan : Graphically broken and every model has black texture and boxes on it.
___
New dolphin version
Sonic Colors in Open GL : No hud elements like old version
Sonic Colors in Vulkan : The black texture issue is Fixed. The game is now perfectly visible with Hud elements too.
____________
In Harry potter chamber of secrets :
_
Old Version Vulkan : Graphically Broken
New Version Vulkan : No grahpical bugs.
_
Harry potter Sorcer stone
Old Version Vulkan : Broken black boxes every where
New Version Vulkan : No black boxes , but few noticeable graphical glitches like harry glasses and White boxes on Hud/life bar.
_
This is so far in Oreo. I will check my driver version thought. Maybe Android P that comes with new drivers broke things.
I will try to back things up with Screen shots and I will try wind waker.
(07-22-2018, 04:31 AM)JonnyH Wrote: [ -> ]Interesting - I'll certainly look into that (assuming it works...) as soon as I get a device with an updated driver.
And also it's a mistake to link android OS versions (oreo, whatever p is going to be etc.) with driver versions. They're *often* updated at the same time, but not always. It's certainly possible for different devices to be using different drivers on the same android OS version, and visa versa.
Right, obviously they tend to obtain newer revisions from the branch with major OS update, so to simplify it's P when they started to push most recent revisions with dualScrBlend starting with A630 then later to 540 and 530. But yea some OEMs could get it regardless OS version, it's just rarely happens.
So, if I've correctly understood, those newer versions would run RE4 and other dualscrBlend games with vulkan correctly ?
It's more complicated than we think.. Consider your self lucky you can run Dolphin-Emu with Vulkan API on Android Devices..
I believe someo developer have to arrange the drivers for Vulkan..I don't know if its possible.. I don't know if I'm wrong.. No offense
For Example: You can Run Dolphin-Emu on
Android-7.1.1-Oneplus 3 with older Vulkan Driver 1.0.31 I have Test it.. Working 100%
But if you upgrade the
Device OnePlus 3 to 8.0.0 or 8.1 your Vulkan Driver also upgrade to Latest 1.0.49 / 1.1.66..
Which makes Dolphin-Emu incompatible with
Vulkan API Backend
I Believe its complicated cause of
CPU-GPU Communication Vendor Drivers..
Let me explain my thoughts..
For example:
Oneplus 3 Have Adreno 530 GPU on ARM. If you upgrade the Android 8.0 or 8.1 Vulkan Driver its the same 1.1.66
Also you can have
Vulkan Driver 1.0.61 on Android 8.0 same device plus you can have 1.0.66 on Android 9.0 [color=#993333]but all that Drivers are incompatible[/color]..
The driver works only on
Android 7.1.1 which is Vulkan 1.0.31 version.
Lets talk about New Generation Device:
OnePlus 6 Vulkan Driver Range is 1.0.61 - 1.0.66
if you Go
Beta Android 9.0 which is Available for this Device the
Driver Version still remains 1.0.66.
This Device Using Different CPU-GPU but is on
ARM plaform which is still incompatible with Dolphin-Emu.
Question.. Why Devices with
SD 835 Adreno 530-540 Running Dolphin-Emu Vulkan API
My OP3 Device
SP 820 & Andreno 530 Running Dolphin-Emu Vulkan API with Older Vendor Driver older Android OS
Same drivers Vendors not running on
SD 845 GPU Adreno 630?
[color=#cc3333]Sorry not running meaning all that black boxes and black boarders..
[/color]
[color=#cc3333]I'm talking about Oneplus cause that the devices I can only Test.[/color]
(07-23-2018, 06:50 AM)BlackAngel Wrote: [ -> ]Vulkan Driver its the same 1.1.66
You confusing API version with driver revision.
API version doesn't meant to have same driver revision.
Dolphin can work perfectly fine on one 1.1.66 device and fail on other 1.1.66 (depends if GPU vendor has a regression on one of the revisions)
OEMs pull driver version from GPU driver vendors each time they feel like it, they don't use Dolphin as a bugs benchmark, it's more like Dolphin exposes weird bugs
(07-23-2018, 08:51 AM)zxcvbad Wrote: [ -> ]You confusing API version with driver revision.
API version doesn't meant to have same driver revision.
Dolphin can work perfectly fine on one 1.1.66 device and fail on other 1.1.66 (depends if GPU vendor has a regression on one of the revisions)
OEMs pull driver version from GPU driver vendors each time they feel like it, they don't use Dolphin as a bugs benchmark, it's more like Dolphin exposes weird bugs
That makes even more interesting that I thought then, if only driver version matters, then why old Vulkan Driver work with old Phon & old Adreno ARM GPU
and not working in new Adreno GPU with newest Vulkan Drivers, so the question still remain the same, API Version or Vulkan Driver Version problems still remains.
That's what i'm talking about
its dolphin-emu side problem no offense
(07-23-2018, 09:39 AM)BlackAngel Wrote: [ -> ]That makes even more interesting that I thought then, if only driver version matters, then why old Vulkan Driver work with old Phon & old Adreno ARM GPU
and not working in new Adreno GPU with newest Vulkan Drivers, so the question still remain the same, API Version or Vulkan Driver Version problems still remains.
That's what i'm talking about its dolphin-emu side problem no offense
It's never the API version really. It's not really useful comparing that.
And I'm pretty sure it's not dolphin, but actual driver bugs. This whole thread was started due to a workaround to avoid one adreno's driver bug - according to the vulkan specification the code should work, but it didn't.
It's more likely a different bug has been introduced in the newer versions, or it's exposing a new feature that dolphin is trying to use, but that too doesn't work properly due to driver bugs.
EDIT:
And this workaround only exists in the vulkan backend. It's not useful comparing openGL results, as this commit literally does nothing for openGL. The bug it is working around doesn't exist in adreno's openGL driver, so it's not needed.
(07-23-2018, 09:53 AM)JonnyH Wrote: [ -> ]It's never the API version really. It's not really useful comparing that.
And I'm pretty sure it's not dolphin, but actual driver bugs. This whole thread was started due to a workaround to avoid one adreno's driver bug - according to the vulkan specification the code should work, but it didn't.
It's more likely a different bug has been introduced in the newer versions, or it's exposing a new feature that dolphin is trying to use, but that too doesn't work properly due to driver bugs.
EDIT:
And this workaround only exists in the vulkan backend. It's not useful comparing openGL results, as this commit literally does nothing for openGL. The bug it is working around doesn't exist in adreno's openGL driver, so it's not needed.
I see so is the drivers bug it self.. Some drivers works with Dolphin-emu some other not..Too bad..
There are too many Driver Versions & too many API revisions among different Android OS Devices..
This is never gonna be run properly.. : /
Thanks for clarification~!!
Surprisingly enough, even my Snapdragon 650-based Xperia X saw improvements on this. Getting constant 28~30 FPS on Luigi's Mansion, then dropping to 20~25 FPS once thermal throttling kicks in. Before I would get 10~15 FPS and completely broken graphics on Vulkan...