+- Dolphin, the GameCube and Wii emulator - Forums (https://forums.dolphin-emu.org)
+-- Forum: Dolphin Emulator Discussion and Support (https://forums.dolphin-emu.org/Forum-dolphin-emulator-discussion-and-support)
+--- Forum: Hardware (https://forums.dolphin-emu.org/Forum-hardware)
+--- Thread: Dolphin on the pi 4? (/Thread-dolphin-on-the-pi-4)
RE: Dolphin on the pi 4? - jdonald - 09-01-2019
(09-01-2019, 04:35 AM)bomblord Wrote: Updated to a new version of the Sakaki Gentoo 64 (1.5.1) and I'm getting noticeably smoother performance in just about everything. The update also fixed the garbled audio I was getting when running Dolphin.
It's probably the PulseAudio fix. I hadn't encountered audio problems probably because I've been using ALSA.
Some YouTube commenter pointed wrote that EXT_buffer_storage only matters for performance on GPUs with their own VRAM. Dolphin devs, is there any truth to this? If so, that wouldn't be consistent with how you guys pushed hard for support on Mali over the years.
V3D has its own L2 caches, so I imagine at the very least this extension would free up the driver from doing some unnecessary cache invalidations. Anyhow, it would be nice to get a rough idea of the expected benefit.
Without EXT_buffer_storage, another route is to eventually have Vulkan support. So far I haven't been able to tell if GLES or Vulkan gets a better framerate on my Android phones. For the Pi 4, in theory would Vulkan get us to around the same place performance-wise as EXT_buffer_storage + GLES 3.2, or could it be noticeably better?
RE: Dolphin on the pi 4? - bomblord - 09-17-2019
Buffer Storage fix could be added as soon as this week
rpi engineer Wrote:I think shader storage is already there in the version of the driverhttps://www.raspberrypi.org/forums/viewtopic.php?f=63&t=249636
available in the Rpi. It has some important bugs we have been fixing
but the feature should be exposed as an extension.
In any case, there is a public branch with GLES 3.1 here [1]. We are
constantly rebasing it etc, so it is still a development branch with
all that this means, so do let people know of this if you point them to
it. It should be noted though, that this branch requires a kernel
patch to work properly [3], particularly for buffer storage. The kernel
patch is in review process upstream at the moment and I hope to merge
it this week, but there is a delta between the upstream kernel and the
downstream Rpi kernel so I'll have to send a slightly different version
of the patch to the downstream Rpi kernel here [2] (the patch currently
sitting there is not up to date). I am planning to do that this week,
so I can ping you when the downstream kernel patch is updated in [2],
since it is probably best to wait for that before pointing people to
the gles31 Mesa branch.
As usual when installing from development versions, do advise people to
prepare backups of their cards before playing around with this stuff.
We have not seen any issues ourselves, but of course this is
development code.
[1] https://gitlab.freedesktop.org/chema/me ... v3d-gles31
[2] https://github.com/raspberrypi/linux/pull/3203
[3] Basically, we had to change the ioctl kernel interface, so if they
don't have the kernel patch, the kernel will just reject rendering
involving shader storage, shader images and other things, so things
will probably not work well, specifically if they are using shader
storage.
ARM64 rpi4 error libgl - askmewho - 09-18-2019
Hi! i was trying to get this emulator running with manjaro (it has hw acceleration), I even compiled a newer mesa to compare... non of these worked
libGL error: failed to create drawable
dont know how other people get this "working" on rpi4, but I have EGL ON... and it doesnt work at all...
and the information its too poor ? I need to enable debug to get proper info or its there any debug command??
thanks on advance, its just for testing porpise!
RE: Dolphin on the pi 4? - mbc07 - 09-18-2019
(09-18-2019, 04:23 PM)askmewho Wrote: Hi! i was trying to get this emulator running with manjaro (it has hw acceleration), I even compiled a newer mesa to compare... non of these workedMerged to "Dolphin on the pi 4?"
libGL error: failed to create drawable
dont know how other people get this "working" on rpi4, but I have EGL ON... and it doesnt work at all...
and the information its too poor ? I need to enable debug to get proper info or its there any debug command??
thanks on advance, its just for testing porpise!
RE: Dolphin on the pi 4? - bomblord - 09-19-2019
(09-18-2019, 04:23 PM)askmewho Wrote: Hi! i was trying to get this emulator running with manjaro (it has hw acceleration), I even compiled a newer mesa to compare... non of these worked
libGL error: failed to create drawable
dont know how other people get this "working" on rpi4, but I have EGL ON... and it doesnt work at all...
and the information its too poor ? I need to enable debug to get proper info or its there any debug command??
thanks on advance, i s just for testing porpise!
Is this a terminal error or an error that the Dolphin launcher is throwing?
RE: Dolphin on the pi 4? - askmewho - 09-19-2019
yeah, dolphin claims it fails to launch opengl backend
RE: Dolphin on the pi 4? - JosJuice - 09-19-2019
Did you set PreferGLES as described here? https://forums.dolphin-emu.org/Thread-dolphin-on-the-pi-4?pid=497094#pid497094
RE: Dolphin on the pi 4? - askmewho - 09-20-2019
yeah, not solving the issue. please, give me any command to get more info about whats happening.
RE: Dolphin on the pi 4? - askmewho - 09-20-2019
this is my output:
[pi@pi Binaries]$ ./dolphin-emu
qt5ct: using qt5ct plugin
qt5ct: D-Bus global menu: no
QPainter::begin: Paint device returned engine == 0, type: 1
QPainter:
etClipRegion: Painter not activeQPainter:
etClipRegion: Painter not activeQPainter::opacity: Painter not active
QPainter::opacity: Painter not active
QPainter::begin: Paint device returned engine == 0, type: 1
QPainter:
etClipRegion: Painter not activeQPainter:
etClipRegion: Painter not activeQPainter::opacity: Painter not active
QPainter::opacity: Painter not active
QPainter::begin: Paint device returned engine == 0, type: 1
QPainter:
etClipRegion: Painter not activeQPainter:
etClipRegion: Painter not activeQPainter::opacity: Painter not active
QPainter::opacity: Painter not active
QPainter::begin: Paint device returned engine == 0, type: 1
QPainter:
etClipRegion: Painter not activeQPainter:
etClipRegion: Painter not activeQPainter::opacity: Painter not active
QPainter::opacity: Painter not active
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 2365, resource id: 10577175, major code: 40 (TranslateCoords), minor code: 0
RE: Dolphin on the pi 4? - bomblord - 09-20-2019
(09-20-2019, 06:30 AM)askmewho Wrote: this is my output:Sounds like your Linux version doesn't properly support whatever dolphin is trying to do. Whether that's a missing driver, mesa/graphics library, permissions issue, or something else I don't know enough to say.
[pi@pi Binaries]$ ./dolphin-emu
qt5ct: using qt5ct plugin
qt5ct: D-Bus global menu: no
QPainter::begin: Paint device returned engine == 0, type: 1
QPainter:
QPainter:
QPainter::opacity: Painter not active
QPainter::opacity: Painter not active
QPainter::begin: Paint device returned engine == 0, type: 1
QPainter:
QPainter:
QPainter::opacity: Painter not active
QPainter::opacity: Painter not active
QPainter::begin: Paint device returned engine == 0, type: 1
QPainter:
QPainter:
QPainter::opacity: Painter not active
QPainter::opacity: Painter not active
QPainter::begin: Paint device returned engine == 0, type: 1
QPainter:
QPainter:
QPainter::opacity: Painter not active
QPainter::opacity: Painter not active
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 2365, resource id: 10577175, major code: 40 (TranslateCoords), minor code: 0
The only 2 Linux versions that I know it's been verified to work on are
1. Sakaki's Gentoo 64 build https://github.com/sakaki-/gentoo-on-rpi-64bit
2. The new experimental 64 bit Raspbian Buster https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=250730
After installing one of those make sure they are fully up to date (in Gentoo you'll need to sudo genup on Raspbian it's sudo apt-get update/upgrade) then build dolphin from source https://dolphin-emu.org/docs/guides/building-dolphin-linux/ This will take about 3 hours maybe about 1 if you turn off a safety feature that isn't required on the Pi 4.
After that, set in the folder path ~/.config/dolphin-emu/GFX.ini
Code:
PreferGLES = TrueAnd finally load your game.