Open-Source Doom 3 Running On Wayland

[dhewg]

That video wasn't about performance, its about the port running on wayland.
It was a debug build, weston was running on x11, and the capture process itself adds a significant overhead. So the on screen fps display you see in the video doesn't reflects the performance of the port itself or the open source drivers.

[9a3eedi]

This is Doom 3 running on the free software drivers (as those are the only ones compatabile with Wayland). Since they still do not have the same performance as the proprieraey blobs of course the framerate is not going to be the highest. I do not understand the confusion.

I see.. I realize that opensource drivers are lower in performance compared to the blobs, but I would think they would at least be able to handle Doom 3 since it's an old game now.

But then again, it could be a weak graphics card too..

[blackiwid]

ok libreoffice blender and co are imporatant but frist there was only talked about firefox, I could not care less about firefox ^^

Today standard is webkit its faster so go for it ^^. just use chromium... if you want a mainstream browser with many plugins... if you dont care about plugins epiphany could be an alternative soon when they ported it to the newest webit version... Who uses freely firefox today? Some people who are ultra-conservative maybe they also even hate gnome-shell ^^

[Hamish Wilson]

This is Doom 3 running on the free software drivers (as those are the only ones compatabile with Wayland). Since they still do not have the same performance as the proprieraey blobs of course the framerate is not going to be the highest. I do not understand the confusion.

[9a3eedi]

Maybe it's just me, but the framerate in that video seems pretty low for a game that's supposed to be 8 years old now. (it's not THAT low, but being a 8 year old game I would expect at least a constant 60 fps or higher)

I wonder what sort of hardware the guy is running, and what's causing the low framerate...

And it would be interesting to see the difference in framerate/performance between X11 and Wayland, that way we can know for sure if Wayland really is all what the developers seem to say it is.. a "simpler" and "faster" display protocol than X.

[DeepDayze]

Libre Office is not running yet, Blender i think is not running and quite few more of the "big ones"

On the DE front only enlightenment implemented client decorations but i have no idea if it can currently run as a whole desktop.

with X compatibility shim libs for Wayland those apps that use legacy X should still be able to run fine on native Wayland until those apps are ported to run natively under Wayland.

I for one would love to see Wayland become the default as it'll be a lighter, leaner display server that adds little overhead so that games and other intense graphical apps can run better, not to mention making it easier for driver developers to write and maintain drivers for

[bwat47]

As Shuttleworth already stated he plans to take Ubuntu proprietary some where down the road I hope they stay out of it all together.

No, he didn't. Don't make baseless assertions.

[dimko]

slow as hell

and still it's slow as hell.
I remember, I have upgrade a couple of time since moment I bought quake 4.
New video card/CPU/memory cards/MoBo never gave any performance increase(perhaps 3%).
Looks like limitation of engine.

[89c51]

Once Firefox finishes their port to GTK+3 it shouldn't be too hard to make it work on Wayland natively I believe.

But it seems like they haven't finished the port to GTK+3 yet.

https://bugzilla.mozilla.org/show_bug.cgi?id=627699

It's a good thing however that xwayland exists and that X11/GTK+ apps such as Firefox already work via xwayland. I think that we'll need to run some apps (such as Firefox) for a while via xwayland until they become native applications on Wayland, but it's a good thing that xwayland already provides this sort of backward compatibility for "legacy" applications.

I think the most important thing right now is to get the compositors to work in Wayland natively (i.e. kwin, mutter, compiz, etc) and then the whole DEs like KDE, GNOME, etc. So that users can already use Wayland instead of X for our WMs and DEs, and so that distros can already ship Wayland by default. Once we have the DEs working natively on Wayland we can use xwayland to run the usual applications such as Firefox, until they become native Wayland applications.

I think the progression to Wayland is going to be gradual, perhaps some applications will take longer to port, but since there is xwayland this shouldn't be a problem.

Hopefully we're going to see the compositors being ported now that the protocol is set in stone with the 0.95.0 release, I think Wayland/Weston 1.0 is coming soon also, and that's where the protocol is supposed to be 100% frozen/stable and we should start seeing more applications and compositors working natively on Wayland from there.

I think it's already amazing that Wayland/Weston can run on a stock Linux 3.x kernel with open-source graphics drivers, and that xwayland already exists, and the fact that most X11 applications work on Wayland/Weston, I mean, Wayland/Weston hasn't even reached 1.0 yet and it already does all this, I think Wayland/Weston has come a long way and it's amazing, I think it's going to be even more amazing once it reaches 1.0 and becomes the default windowing system in Linux and most distros.

Wayland is amazing and a much needed change for Linux. Kudos to the Wayland developers.

Libre Office is not running yet, Blender i think is not running and quite few more of the "big ones"

On the DE front only enlightenment implemented client decorations but i have no idea if it can currently run as a whole desktop.

[pq__]

Hopefully we're going to see the compositors being ported now that the protocol is set in stone with the 0.95.0 release, I think Wayland/Weston 1.0 is coming soon also, and that's where the protocol is supposed to be 100% frozen/stable and we should start seeing more applications and compositors working natively on Wayland from there.

I think it's already amazing that Wayland/Weston can run on a stock Linux 3.x kernel with open-source graphics drivers, and that xwayland already exists, and the fact that most X11 applications work on Wayland/Weston, I mean, Wayland/Weston hasn't even reached 1.0 yet and it already does all this, I think Wayland/Weston has come a long way and it's amazing, I think it's going to be even more amazing once it reaches 1.0 and becomes the default windowing system in Linux and most distros.

Just remember, that "frozen" does not mean "complete". Wayland 1.0 will lack in the protocol for anyone trying to support a full DE (or games, like you saw with that Doom 3 video). 1.0 only means, that the protocol existing so far is not going to be broken.

Also, 1.0 does not mean it can become a default windowing system in desktop distros. It means, that toolkit, DE, and application developers can now start serious work on supporting Wayland without playing continuous catch-up with protocol changes.

It is all exciting, yes, but distro migration to Wayland will be a long path. And when it's done right, you probably can't even see the difference, unless you know what to look for.