Hey @tisis2
unfortunately the problem is not on our Wayland side. Avalonia does not support Wayland backend for now馃槗: Our own backend for Wayland 路 Issue #1243 路 AvaloniaUI/Avalonia 路 GitHub
So, when using Wayland the true for Avalonia is that you are using xWayland, that does not support OpengGL ES.
On the Avalonia Framebuffer template, there are two ways:
-
Using
/dev/fbX, actually the Linux Framebuffer, that yeah, does not support hardware acceleration: vscode-torizon-templates/dotnetAvaloniaFrameBuffer/Program.cs at 3db2727b620c2070daa42724287c397045c7af38 路 torizon/vscode-torizon-templates 路 GitHub -
And the
/dev/dri/cardX, DRM (directly rendering manager), that uses directly the GPU and supports OpenGL ES: vscode-torizon-templates/dotnetAvaloniaFrameBuffer/Program.cs at 3db2727b620c2070daa42724287c397045c7af38 路 torizon/vscode-torizon-templates 路 GitHub
So, make sure you are using DRM mode, if you are not already. And, if you are already using it let me know, because that鈥檚 the mode we鈥檝e tested with the best performance, and we have to look into it if you鈥檙e having issues.
Best Regards,