Will Vulkan performance ever get fixed?

[retroben]

I find it depressing how much of a performance gap there is now testing r5305 (latest when excluding Transifex build) Melee with four Bowsers (Training mode+ 3x CPU) on Fountain of Dreams,even with no Ubershaders.

With OpenGL I get 27fps minimum at the highest strain while Vulkan reaches single digits at a staggering minimal 7fps at one point!
I have seen a video discussing game-specific Vulkan slowdowns when compared with OpenGL while another game ran better with Vulkan so that is expected unfortunately.

Again,this is in no way directly related to Ubershaders because I disabled them for the tests.
One reason benig that Vulkan still refuses to boot with them in comparison to OpenGL booting Simpsons Hit & Run just fine using Hybrid Ubershaders after a mere 3 minutes.
I made the effort of waiting 15MINUTES for Vulkan to load in Hybrid Ubershaders but it never started.

The main reason I made this new thread is to ask this question if Vulkan performance can't be fixed to at least nearly match OpenGL's performance so I can get either one running closer to full speed on more games.

I know that XDA or GeForce Forums is the more appropriate place to ask,but those places have been fairly low on responses.
My thread in Shield TV Questions on XDA for this has yet to get a single reply but has 30 views so far,and I have a really nice reputation on XDA with a decent 62 thanks points and I don't post nearly as much there nowadays with my count being just under 500 posts since my 2014 join date for a previous device I used.

Does anyone know if Magisk works on Shield TV Pro (2015) for systemless root via flashing only into the boot image?
I want to root this "safer" way so I can then overclock the processors to their safe high levels for improved performance without needing to flash the entire rooted OTA image which has a greater chance of bricking.

Plus,flashing the full image is claimed to take ages on a Pro model Shield TV,so that is another benefit of Magisk if its compatible.
I also have to backup my stuff before unlocking the bootloader,so that will take a chunk of time in itself.

I don't want to end up backing up my stuff now if it ends up not being compatible,though it would be better safe than sorry if I did backup right away,but I want to avoid backing things up until I know that it works to begin with,then I could back up my stuff to prepare for using it.

And no,I don't merely want this method of root so I could dodge safety net legitimacy failures for the bad reasons,I mainly want it for the performance boost benefits if I can so much as have a temporary HW overclock on each boot session until I wish to update with the upcoming Android Oreo OTA (provided its stable) upon which I disable the overclocking of HW and unroot to avoid update failures via sustaining System Partition legitimacy fully.

If it overwrites the boot image then I would assume you only have to disable the stuff and unroot and maybe even revert the boot image before taking the OTA then run Magisk again to fix that as it claims you would do between OTA updates to retain everything after the OTA and without it breaking anything!

[Helios]

Same answer as always

It'll get fixed if anybody ever gets interested into tracking down the issues and implementing workarounds.

Android has none of that motivation right now

[retroben]

Well if anybody knows if rooting systemless via Magisk works on SATV (Pro 2015) please confirm that it works.
I am on the stock 5.0.2 OTA still,so I think that is the latest very eligible version that could work with Magisk.

[Guilherme]

That's not the Dolphin developers' job, Android GPUs have bad OpenGL, and even worse Vulkan support. Vulkan on Windows runs almost as good as Direct3D11 or OpenGL, the games I tested run the same.