• 3 Posts
  • 20 Comments
Joined 1 year ago
cake
Cake day: July 21st, 2023

help-circle


  • Are you me? Except I use FreeTube instead of Piped. I am so happy with this solution. Years of discontent of watching services going through the enshittification cycle… everything just becoming so underwhelming. This has given me back freedom over my own media consumption. No ads. No endless scrolling through bullshit content. Just a nicely personally curated selection of movies and TV shows (on Jellyfin) and an ad-free YouTube-experience with sponsorblock and dearrow enabled, and blocking of live chats and shorts.







  • Thanks for the link. I tried running that, but it seems to fail loading the noveau-driver (I have the proprietary Nvidia-drivers installed, as far as I know I don’t have noveau installed). Does Godot in some way depend on using noveau, and can I install that alongside the proprietary drivers?

    This is the output from running with index 0 (as you can see, I’m using a Flatpak build, if that would make a difference?). Index 1 did not use the Nvidia-card, but rather llmvpipe or something (I’m guessing CPU-emulated card?), and that was extremely slow.

    Godot Engine v4.3.stable.flathub.77dcf97d8 - https://godotengine.org
    glx: failed to create dri3 screen
    failed to load driver: nouveau
    OpenGL API 4.6 (Core Profile) Mesa 24.1.3 (git-0c49f54c76) - Compatibility - Using Device: Intel - Mesa Intel(R) Graphics (ADL GT2)
    
    Editing project: /path/to/project
    Godot Engine v4.3.stable.flathub.77dcf97d8 - https://godotengine.org
    Vulkan 1.3.278 - Forward+ - Using Device #0: Intel - Intel(R) Graphics (ADL GT2)
    

    The second block is after loading the project where it switches to Vulkan from OpenGL.

    I’ll try the on-demand thing mention in the same post tomorrow, I’ve yet to ever try running that instead of either dGPU completely on or off.





  • Depends on your budget, I guess. My setup consists of a regular Samsung Smart-TV that I have disconnected from the network, connected to a mini-PC from Minisforum running Linux Mint. The reason I got that was mainly for gaming, could get away with a significantly cheaper option if not. I run my own Jellyfin-server for media content (movies, TV and music) and use FreeTube to watch YouTube (which I sync with my laptop and mobile using SyncThing). I do use a wireless foldable and rechargeable keyboard with built in trackpad, but it’s not working as great as I imagined. Corsair used to have a nice media keyboard, but as far as I know they have discontinued it and I haven’t yet found a new one that fits my criteria, so I keep using the foldable one.

    As for gaming, I run emulation through RetroArch and Steam in big picture mode. I have four 8BitDo Ultimate controllers in case I get any friends over who are keen on a round of Mario Kart.









  • Wayland should be faster. What would you expect to happen? It should just work, while in the background EVERYTHING is changing.

    I had assumed that I would get a somehow smoother experience (such as speed, for instance) or some other perceivable benefit, but I think Ramin Honary nicely highlighted the necessity of the change on the backend side. So your point is good, maybe I should just expect a smooth transition where I don’t notice anything.

    For Freetube, it should automatically detect running on Wayland and use that. But I had one bug on Freetube only on Wayland, may be an Electron issue.

    If I run the executable after downloading from the GitHub repo directly, it launches in XWayland. The additional parameters I mentioned in the post used to work to launch it in Wayland, but not anymore.


  • Thanks for such a detailed account - it really makes sense to move on from X11 based on what you write.

    When I first heard about what X11 and Wayland was and how long the transition has been in the making, I found it a bit hard to believe that it should take so long. I am still not fully sure why it would take so long time to mature… is it a chicken-and-egg kind of situation where it cannot mature properly before it is more widely used, but it has not been more widely used because it was not mature enough? Or is it such a difficult task to get this right and that the development time reflects that?

    And why would for instance NVIDIA GPUs continue to have issues with Wayland (and what kind of issues would actually be caused by this?)? Is that a matter of closed source drivers and lack of support from NVIDIA’s side to implement required changes? Or are such issues on a more fundamental level (i.e. architectural differences that somehow factors into this - I have no idea what I’m talking about now, I’ll stop writing…)?