Well, with NTFS, there isn’t. That’s why I said, BTRFS is definitely the better choice for games. Never had issues with two shared drives in over two years now with WinBTRFS.
I’ve been using WinBTRFS for quite some time without issues. It seems a lot of people recommend NTFS. But be aware, if you plan on using it for things like games, NTFS will absolutely break at some point. It is not compatible with Proton and will break things like updates for Steam. It always has for me up until very recently. Valve also says the same about using NTFS for games. I’m not sure this can be fixed with the NTFS driver unless they do workarounds like renaming things automatically because some things Proton does are not compatible with the filesystem spec.
!helldivers2@lemmy.ca just dropping this here to help growing smaller communities :)
Oh, interesting. In that case I misunderstood that part, I thought there were core devs of Atom involved in Pulsar, thanks :)
Oh, in that case you might like either. I think both are great in their own way!
I think Zed is quite different from Atom. But Pulsar might be your thing. A direct fork of the last release of Atom being developed by ex Atom developers :)
Definitely, she has served me like the absolute beast she is. To this day the card actually deserves very admirable even in modern titles. The next destination might actually be my roommates PC who’se still running a 960 which is pretty lackluster these days with 2 GB of VRAM.
Absolutely it’s been mostly rock solid. I do however plan on switching to Wayland. Since that will now be doable with AMD graphics it might still be a pain with Gnome 42 so depending on my impatience I might not wait till Pop!_OS 24.04.
Pop!_OS atm but hopping in the future is not out of question since this was my first and only distro on this device for a few years now. I just was too lazy so far to try out new things.
Thanks, I think I’ve read something about LACT once but it wasn’t relevant back then. Certainly looks like the tool to use to tune my card :)
Just to clarify, I use Pop!_OS and not Fedora Ublue. I looked at their Wiki because they are the only ones who had documentation on how they made hw accel work with Flatpak and Nvidia specifically. More exaclty I was led there by this Reddit post.
AFAIK it should work fine with AMD since Firefox can use the VA-API FFmpeg Flatpak to provide hw accel which should work fine with AMD GPUs. This does however not support Nvidia GPUs, which is why you have to expose the driver in the sandbox and force Firefox to try to use it etc.
Mesa drivers for opengl, vulkan, etc. are likely already installed, what you need to install are the mesa-va and mesa-vdpau drivers for video acceleration. Other than that, you just need to make sure the GPU doesn’t stay in power saving mode when you play.
Thanks, I’ll make sure to install those for sure then.
Btw, video acceleration with Nvidia mostly works if you use this.
You know, I actually tried, and I couldn’t get hardware acceleration working in the Firefox Flatpak for the love of god. I tried everything, all the guides, looked at the Ublue documentation how they did it etc. and in the end I decided it’s just not worth it because playback worked fine without, just with a wee bit higher CPU usage.
I never actually tried myself, but it seems like the documentation certainly could be improved. I saw that they provide a Docker compose, so perhaps that could be of help if you didn’t use that the last time around. They are currently in the process of cleaning up the projects to make things more maintainable and easier to get an overview, so let’s hope things might improve a bit. I think for me personally, this certainly seems like the most promising Discord replacement because it feels like a set and get solution for non-techy people trying to switch instead of relearning everything like with Matrix.
Revolt is self-hostable. It isn’t E2EE but if you’re controlling the users anyways transport encryption should be enough since you have control over the data anyway.
I reported basically this issue a few months back with another Lenovo device. Sadly there was no other activity towards resolving this.
Maybe you can bring in some new information if you can confirm, that you have the same issue.
In essence the hover recognition distance greatly reduces when touch input is present causing these jumps to happen with the palm because when writing any lifting off the pen will reactivate touch.
I looked at some info for reporting this to the kernel developers but the process is too complicated at the time. I’m currently a bit short on time but I did report it to libinput, maybe they can give pointers where exactly to report this.