Hey all,
Linux Mint 18 64 bit user here.
So I have an AMD R9 390, which I think is quite beefy, and am trying to play Skyward Sword.
I am using the latest open source mesa drivers from their git, which is version 12.1.
I am also using dolphin-git from the official ubuntu repositories.
30% of the time, Skyward Sword runs at the standard 30 fps. But in the beginning of the game, going outside into Skyloft is causing drops to 20 FPS, and that messes everything up of course.
I am trying to play at 1080p, but lowering it down to the native 640xWhatever makes the game run smooth.
This seems bizarre to me, so any help is appreciated!
OH, and it may be obvious because I'm on Linux, but I am using OpenGL as the backend renderer.
Since you say it runs at full speed when you lower the internal resolution, that means your GPU is the bottleneck. However, a R9 390 should be more than enough to handle 3x IR, so I'd guess it's the drivers.
Could you show your other graphical settings too?
(07-18-2016, 05:51 AM)leolam Wrote: [ -> ]Since you say it runs at full speed when you lower the internal resolution, that means your GPU is the bottleneck. However, a R9 390 should be more than enough to handle 3x IR, so I'd guess it's the drivers.
Could you show your other graphical settings too?
Sure, and that is my conclusion too.
The R9 290/390 have had some performance regression with drivers, so that may be it.
Attaching the OpenGL graphics settings, and the games GameConfig tap in the properties.
Yeah, it definitely seems like your performance issue is caused by your drivers. Too bad it's a GCN 1.1 card, which means it's either the open source driver or the crash-prone, buggy proprietary driver.
(07-18-2016, 06:02 AM)leolam Wrote: [ -> ]Yeah, it definitely seems like your performance issue is caused by your drivers. Too bad it's a GCN 1.1 card, which means it's either the open source driver or the crash-prone, buggy proprietary driver.
I'm not completely at a dead end yet.
I am going to install AMD's AMDGPU-Pro drivers, which is their hybrid stack. The latest release does actually work with the R9 390.
In some cases, the R9 390 is faster with those.
Problem is, it breaks with Cinnamon, so I am going to install Ubuntu 16.04 with Unity, and see how it all goes.
Will post with my results when I am done.
Oh, so their new driver finally works with older cards? That's good news
If the OpenGL performance issues are fixed, I think it would run very well.
(07-18-2016, 06:09 AM)leolam Wrote: [ -> ]Oh, so their new driver finally works with older cards? That's good news
If the OpenGL performance issues are fixed, I think it would run very well.
Yeah, it's kind of bizarre. Their supported GPU's table hasn't changed, but the support has. GG AMD.
(07-18-2016, 06:09 AM)leolam Wrote: [ -> ]Oh, so their new driver finally works with older cards? That's good news
If the OpenGL performance issues are fixed, I think it would run very well.
Welp, drivers work just fine. Problem is, now Dolphin on Ubuntu 16.04 is not properly detecting my wiimote.
It connects to Bluetooth fine, but won't connect and set off the motor on Dolphin.
Just tried it on Windows and it worked instantly.
It worked with some tinkering on Linux Mint, which shares Ubuntu software, so idk what's going on here.
Have you enabled continuous scanning?
Also, make sure your Bluetooth adapter is powered on before you start Dolphin and that any Bluetooth manager is not interfering with Dolphin and preventing it from connecting to the Wiimotes directly.
Code:
$ bluetoothctl
[NEW] Controller xx:xx:xx:xx:xx:xx Adapter_Name [default]
[bluetooth]# power on
Changing power on succeeded
Edit: also make sure you haven't paired your Wiimote and marked it as "trusted". In that case, it will be connected to your PC, but to the kernel's input driver which will use it as an input device, and which prevents Dolphin from using your Wiimote.
Code:
[bluetooth]# untrust wiimote_address
(07-18-2016, 05:33 PM)leolam Wrote: [ -> ]Have you enabled continuous scanning?
Also, make sure your Bluetooth adapter is powered on before you start Dolphin and that any Bluetooth manager is not interfering with Dolphin and preventing it from connecting to the Wiimotes directly.
Code:
$ bluetoothctl
[NEW] Controller xx:xx:xx:xx:xx:xx Adapter_Name [default]
[bluetooth]# power on
Changing power on succeeded
Edit: also make sure you haven't paired your Wiimote and marked it as "trusted". In that case, it will be connected to your PC, but to the kernel's input driver which will use it as an input device, and which prevents Dolphin from using your Wiimote.
Code:
[bluetooth]# untrust wiimote_address
One issue I'm running into is with Bluetooth Manager or 'Blueman'.
Based off tutorials I've watched, I should be able to set bluetooth to see my wiimote as something called an Input Service, but that option in blueman is gone.
I acutally got it working once last night, but it was on accident and am not able to replicate. Derp.
One of the most annoying things is that blueman kept popping up with a prompt for me to enter a PIN, which of course I can't do with a wiimote.