There is an option in Steam to allow Vulkan shader compilation in the background when you start Steam. I do that, so most times they have already compiled by the time I go to start a game

@curbstickle@anarchist.nexus

The OP’s disclosure doesn’t meet the requirements you laid out for proper disclosure. At this early stage I would suggest removing posts that only partially meet the criteria, otherwise you will spend a lot of time handholding posters. Or, if low quality disclosures are allowed, then it dilutes the effect of the rules immensely. I know you want to be patient with people, but proper enforcement now will pay off in the long run!

deleted by creator

Take a look here, it explains more about the specific configuration, such as which subvolumes are automatically snapshotted and include in rollbacks, bootloader integration, etc https://doc.opensuse.org/documentation/tumbleweed/snapper/

Basically there are many details in the setup of btrfs that are needed to get to that level where you can be confident of being able to easily rollback to a previous state. After losing some data on a manually configured btrfs setup on Fedora I went to openSUSE specifically because they have already done all the hard work for you on the btrfs config

This is what openSUSE Tumbleweed is designed to do, although config files in /home require manual setup to include. It allows you to completely rollback if necessary after a system upgrade, allowing you to use a bleeding edge distro without fear of having an unusuable system. If an upgrade goes bad, usual procedure is to roll back to the last btrfs snapshot and just wait for the fix (which usually comes in a couple days to a week, as Tumbleweed advances rather quickly).

openSUSE has a specific btrfs subvolume setup and grub/systemd-boot integration to enable this, which is not too common even today, so it really is a bit special in that you can have this functionality without excessive time spent setting it up manually.