For the performance issues, I guess nvidia has changed the power configuration way. Here, the performance is back after two minutes playing.
If this performance issue isn't there on older builds, please check which version exactly slows down, maybe we've triggered the change ourself...
Re Vulkan backend: retroben, feel free to write a Vulkan backend. I have no interest in doing so. Dolphin is open source, so patches are always welcome...
(02-23-2016, 05:12 AM)retroben Wrote: [ -> ]No need to get snappy
You've been asked multiple times to stop making irrelevant feature requests, and not only are you still doing that, you're now setting deadlines on them for some reason?
(02-23-2016, 04:16 AM)retroben Wrote: [ -> ]The official OTA 3.0 update is rolling out and I just recieved it,so now time is of the essence if a Vulkan backend is to be made
Here you are, pretty clearly implying that not only does a thing no one wants to do needs to be done, it also needs to be done soon.
As previously said, if you'd like to apply your knowledge to the project and add these features, the devs are happy to help. Until then, if you continue to
tell the devs what to do, I'd expect "snappy" responses.
(02-23-2016, 04:16 AM)retroben Wrote: [ -> ]The official OTA 3.0 update is rolling out and I just recieved it,so now time is of the essence if a Vulkan backend is to be made to take advantage of desktop OpenGL 4.5 features and maybe some performance boosts over the limits of ES 3.1 too.
I cant believe the sense of entitlement users have on this forum. If I was a mod here there would be a lot of bans handed out.
Developer: Being nice despite my error.
Two posters right after that: Kinda being jerks to me,but I made a mistake with wording,so...
Nothing of entitlement,I just worded it weirdly typing in a hurry.
It is NOT irrelevant because what is the Vulkan API recently implemented on, "
NVIDIA SHIELD" TV!
Read the name of this thread.
I misworded one thing and came off it wrong like "and I just received it" when I was just confirming personally that the update is actually rolling out,and by "time is of the essence" I meant that since the update with Vulkan API is rolling out to all of the SHIELD TV devices officially,they can run said to-be-made backend at this point whenever it can be made.
I looked up the meaning of t-i-o-t-e and realized my error,I hate my shoddy brain.
I sure as 'ell can't make it because I am stuck with a wimpy PC that lacks the requirements to create it,let alone installing the stuff that is needed or even running anything above OpenGL 2.0 or D3D9,this old computer sucks.
Self quote you probably ignored...
Quote:I didn't mean "this instant" just eventually and literally anyone else that knows how could try to implement it,like that guy who created the DX12 backend.
Dolphin on Android might actually require use of Vulkan if the recent performance issue (caused by bugged out graphics issues) appears to be unfixable by normal means.
Though to compare,the JitARM64 performance build still works just fine.
I apologize for my stupidity from not knowing the meaning of things and my arrogance,my bad.
I've just received the OTA 3.0 and since then Dolphin can't access the USBdrive where all my games are. I tried to uninstall then re install Dolphin but it doesn"t change anything, when I try to add a new directory I can't reach the usbdrive, each time I click the "One level up" button, dolphin stops and restarts.
can someone please help me ?
EDIT : I've just seen there's a new version which fixes this problem, sorry.
So the reason Dolphin is slower on 3.0 is because Nvidia disabled the threaded OpenGLES driver after Vulkan was being implemented.
They want to give developers the option to switch from OpenGL to Vulkan because it can greatly improve performance.
OpenGLES has less priority now thats why they decided to reduce it to 1 thread only to give Vulkan a higher priority.
I'm not sure if it can be turned back on but doing so definitely requires root.
So far it seems only ARM Mali, nVidia and Intel Broadwell Mesa drivers can handle all the features in Vulkan.
There was an ADB option that requires root to enable,and I did not use it because of that,yet my speed was decent in Lollipop and sluggish on Marshmallow with master while the JitARM64 performance build still runs perfectly fine on Marshmallow.
What does certain older builds and that one do differently that makes them not bugged out on the OTA update?
Both that performance build and Mupen64Plus AE run identically to Lollipop speeds for me,though I had to re-enable the storage permission for Mupen to rectify an access issue among other apps having storage weirdly disabled.
I even tested the 3.1 variant of GLideN64 and it also ran fine,maybe because it possibly doesn't use threading due to N64 emulation constraints.
Again,sorry about that mishap of my erroneous wording earlier.
Also,the site seems to be getting really bogged down for whatever reason.
(02-24-2016, 04:23 AM)nex86 Wrote: [ -> ]So the reason Dolphin is slower on 3.0 is because Nvidia disabled the threaded OpenGLES driver after Vulkan was being implemented.
Nope. They've forced disabled it, but it was likely already disabled before. I think they've changed the power management, so it takes more time to get the GPU to get into the high performance mode. But after stuttering for a minute, it runs fine again here.
I found another issue,shader storage is not working,I checked for the files and they no longer appear in the directory where they once were before I intentionally deleted the files to avoid issues with using Lollipop created ones on Marshmallow.
I was gonna read the name of the one for Wind Waker so I wouldn't need to hunt down the Game ID manually or via WiiRD/GeckoCodes.
Neither the JitARM64 performance build or the master build will create any shader files.
(would avoid master anyway until the bug can be fixed)
Good thing Wind Waker doesn't seem to have excessive shader stutters.
The storage permission is enabled for both copies of Dolphin,so that can be ruled out I guess.