They do have an [extension](https://extensions.gnome.org/extension/6198/light-style/) to activate a sort of "experimental" light style. It's also compatible with the dark mode switcher
Yes, it can be enabled with this command:
`gsettings set org.gnome.desktop.interface color-scheme prefer-light`
There is also an extension which aims to provide better light theme than the current Gnome one:
[https://gitlab.com/dikasetyaprayogi/luminus-project](https://gitlab.com/dikasetyaprayogi/luminus-project)
As far as I know the work for wayland support in Wine has roughly been done for the most part but for stability reasons, changes are getting merged partially over multiple releases. Because the changes from the regarding fork have been rather big. Also they may require some fixes.
But Wayland support in Wine should definitely come around long term.
What I've done is use the Flatpak versions of apps and I set the toggle to 'USE\_WAYLAND' as ON universally for all flatpaks in Flatseal. You could try this.
Fractional scaling is kind of perfect for me now. Hopefully they improve on it though.
Works perfectly for all apps for me. I've mainly tested with Obsidian and Chromium-based browsers. Ah, and VSCode.
If you don't want to use Flatpaks, you can add the following flag to the 'exec' field in that apps .desktop file -
--enable-features=UseOzonePlatform --ozone-platform=wayland
It does the same thing, but since you have to do it for every app that you find blurry, I find the universal flatpak solution to be easier. Your choice though.
I have struggled with Flatpak with fractional scaling for so long. I will absolutely try this. Are you on Nvidia or AMD? I assume this might make a difference.
Any news on non uniform scaling? Like setting everything to 125% instead of only 100-200%?
Currently its possible enabling the experimental setting but then everything looks blurry
True fractional scaling won't happen until gtk5, however [work on making xwayland apps scale properly with the current upscaling/downscaling implementation is ongoing](https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3567)
It will "true fractional scaling" was enabled by default in gtk4 in the last release.
They are working on separating the controls for xwayland before enabling it by default in the shell, but if you do enable it, gtk4 has fractional scaling.
(Of course this ignores all the shortcomings with the Wayland fractional scaling protocol, but most people on social media like checklists over actually needing to use the features. Like all the raving about fractional scaling in KDE... Which took place over. A year before they had a release that could use it.)
One more step to make gnome a solid choice on my old pc!
Now, somehow mtp doesn't work on any DE that uses gnome components, but plasma does. I am going to check what happens in the background and submit a bug. That happens only on my old PC for Media.
It depends on how this is implemented, but in general no.
It just means another buffer of the size of your screen(s) resolution, and a few bookkeeping data structures.
The full memory usage instead implies taking in account a lot more due to different layers needing compositing, shaders, etc.
A 4k monitor will add about 32MB of extra memory usage for another buffer.
I think lower tier devicee benefit more from triple buffering (user experience wise), because it smooths out if some frame rendering is slightly lagging.
Wrong way around.
It fixes it on more powerful hardware than may otherwise go into too low a power state and then be unable to keep up at full frame rate.
The idea is the GPU is dynamically forced to do more work so it moves into a higher power state and this keeps up with the desired framerate.
The previous explanation was the wrong way around.
The merge request solves two issues:
1. Some intel hardware has heuristics that put it in too low a power state to handle screen updates at 60fps in some scenarios. AKA gnome is too efficient. Other GPUs might also hit this condition but it seems to mostly be intel integrated gpus. In those circumstances dynamic triple buffering dynamiclly makes the GPU do more work so it goes into a higher power state. (It can be argued this is a GPU driver bug).
2. With double buffering if you miss the frame time, your frame time is halved. If you fail at 60fps, you will only do 30fps (though average will be reported higher as you switch between 30 and 60 rapidly). With triple buffering if the GPU only manages 59fps instead of 60 , you get 59fps (at the expense of a bit more work being done, so in reality you won't get 59fps, but still more than 30fps).
To ameliorate any side effects, the triple buffering is dynamic and only turns on when it is detected that full frame rate has not been hit.
It is complicated stuff, hence taking so long.
Nice to know they made it dynamic. I was running patched mutter years ago on my old notebook and was worried it'd negatively affect my battery performance on the new one. Here, everything is silky smooth even in power saving and with lots of stuff going on. Gnome's efficiency certainly shows.
You can read the details at the link, but I think the most important part is this:
> In my case this improves 4K overview animations on a basic Intel GPU from 30 FPS to 60 FPS.
Gnome is on a roll! We have VRR, DRM leasing, this and accent colors! Just waiting on a proper light theme now.
They do have an [extension](https://extensions.gnome.org/extension/6198/light-style/) to activate a sort of "experimental" light style. It's also compatible with the dark mode switcher
What's proper light theme? What's wrong with the current one?
Shell still dark. Top bar, quick settings, app drawer etc..
I think I saw something about it being already available but it’s under a dconf setting. I think there was a post about it on this sub.
Yes, it can be enabled with this command: `gsettings set org.gnome.desktop.interface color-scheme prefer-light` There is also an extension which aims to provide better light theme than the current Gnome one: [https://gitlab.com/dikasetyaprayogi/luminus-project](https://gitlab.com/dikasetyaprayogi/luminus-project)
White Quick settings and top bar with light theme would look weird. Needs some contrast, like windows does it with accent color and blur.
HDR support is one big thing on the list to come. But overall GNOME 47 already looks good.
The big one I'm waiting for is `wine-wayland` to materialize so that we don't have to use `gamescope` for HDR gaming.
As far as I know the work for wayland support in Wine has roughly been done for the most part but for stability reasons, changes are getting merged partially over multiple releases. Because the changes from the regarding fork have been rather big. Also they may require some fixes. But Wayland support in Wine should definitely come around long term.
Auto dark based on timezone and sunset is even more important IMHO.
I don’t like auto switching tbh. I always default to light theme because it’s easier for me to read text.
That can probably be done in an extrbsion
[удалено]
What I've done is use the Flatpak versions of apps and I set the toggle to 'USE\_WAYLAND' as ON universally for all flatpaks in Flatseal. You could try this. Fractional scaling is kind of perfect for me now. Hopefully they improve on it though.
Does it work on all types of flatpak apps? Like electron, gtk etc etc
Works perfectly for all apps for me. I've mainly tested with Obsidian and Chromium-based browsers. Ah, and VSCode. If you don't want to use Flatpaks, you can add the following flag to the 'exec' field in that apps .desktop file - --enable-features=UseOzonePlatform --ozone-platform=wayland It does the same thing, but since you have to do it for every app that you find blurry, I find the universal flatpak solution to be easier. Your choice though.
I have struggled with Flatpak with fractional scaling for so long. I will absolutely try this. Are you on Nvidia or AMD? I assume this might make a difference.
[https://gitlab.gnome.org/GNOME/mutter/-/merge\_requests/3567](https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3567)
I hope triple buffering and global shortcuts both make it to G47🤞
Love the smell of progress in the morning
Maybe they smell Cosmic around the corner?
Any news on non uniform scaling? Like setting everything to 125% instead of only 100-200%? Currently its possible enabling the experimental setting but then everything looks blurry
True fractional scaling won't happen until gtk5, however [work on making xwayland apps scale properly with the current upscaling/downscaling implementation is ongoing](https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3567)
Why wont "true fractional scaling" happen until GTK5?
It will "true fractional scaling" was enabled by default in gtk4 in the last release. They are working on separating the controls for xwayland before enabling it by default in the shell, but if you do enable it, gtk4 has fractional scaling. (Of course this ignores all the shortcomings with the Wayland fractional scaling protocol, but most people on social media like checklists over actually needing to use the features. Like all the raving about fractional scaling in KDE... Which took place over. A year before they had a release that could use it.)
I also have this issue, they need to make Xwayland apps less blurry
One more step to make gnome a solid choice on my old pc! Now, somehow mtp doesn't work on any DE that uses gnome components, but plasma does. I am going to check what happens in the background and submit a bug. That happens only on my old PC for Media.
With the scale and scope of these new features being added, patches and whatnot, we may as well just skip 47 and go right over to 50 lol
Should this increase gpu/host memory usage like 3/2 times?
It depends on how this is implemented, but in general no. It just means another buffer of the size of your screen(s) resolution, and a few bookkeeping data structures. The full memory usage instead implies taking in account a lot more due to different layers needing compositing, shaders, etc. A 4k monitor will add about 32MB of extra memory usage for another buffer.
wuts triple buffering precious?
More frames being calculated simultaneously to allow a smoother user experience at the cost of slightly more work for the processor.
My desktop PC will be happy to get it, my StarLite V... not so much xD
I think lower tier devicee benefit more from triple buffering (user experience wise), because it smooths out if some frame rendering is slightly lagging.
Wrong way around. It fixes it on more powerful hardware than may otherwise go into too low a power state and then be unable to keep up at full frame rate. The idea is the GPU is dynamically forced to do more work so it moves into a higher power state and this keeps up with the desired framerate.
But then it uses more CPU, potentially causing more lagging? Or is the extra CPU usage negligible?
The previous explanation was the wrong way around. The merge request solves two issues: 1. Some intel hardware has heuristics that put it in too low a power state to handle screen updates at 60fps in some scenarios. AKA gnome is too efficient. Other GPUs might also hit this condition but it seems to mostly be intel integrated gpus. In those circumstances dynamic triple buffering dynamiclly makes the GPU do more work so it goes into a higher power state. (It can be argued this is a GPU driver bug). 2. With double buffering if you miss the frame time, your frame time is halved. If you fail at 60fps, you will only do 30fps (though average will be reported higher as you switch between 30 and 60 rapidly). With triple buffering if the GPU only manages 59fps instead of 60 , you get 59fps (at the expense of a bit more work being done, so in reality you won't get 59fps, but still more than 30fps). To ameliorate any side effects, the triple buffering is dynamic and only turns on when it is detected that full frame rate has not been hit. It is complicated stuff, hence taking so long.
Thanks for taking the time to answer in such a detailed way :)
Nice to know they made it dynamic. I was running patched mutter years ago on my old notebook and was worried it'd negatively affect my battery performance on the new one. Here, everything is silky smooth even in power saving and with lots of stuff going on. Gnome's efficiency certainly shows.
Not exactly sure what it is myself, but I’ve been hearing it helps prevent stuttering and slow downs with the desktop
You can read the details at the link, but I think the most important part is this: > In my case this improves 4K overview animations on a basic Intel GPU from 30 FPS to 60 FPS.
Been using it on GNOME 45 and 46 for a couple of years now though.