• 3 Posts
  • 29 Comments
Joined 1 year ago
cake
Cake day: June 3rd, 2023

help-circle
  • jlsalvador@lemmy.mltoGaming@lemmy.mlAnyone have a sudden loss in gaming?
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    1
    ·
    edit-2
    4 days ago

    Welcome. This is normal. It will be worst later (worst vision, worst reflex, laziness, etc). Just enjoy that your are alive and you will see new iterations (maybe HL3, someday) and new good games. You can not go back to your twenties or beyond, with all your over-the-top reflex, stress-free, free-time, and un-experienced view to be easy surprised. Just enjoy other things, other game types. Never play by obligation.


  • The first improvement (Media Foundation by FFMPEG) could be significant. Currently, VALVe generates large shaders to re-render those Media Foundation videos into other free codecs. These shaders can be several gigabytes in size for some games with lengthy videos. With FFMPEG, those videos could be played without being re-encoded as shaders.












  • Hahaha. Common problem with multiscreen with different resolutions. Your laptop screen is below and left of your main display, and X11 renders this black “virtual screen”.

    There are multiple solutions:

    a) Set your screen resolution and position through KDE Plasma SystemSettings and push the button “apply to SDDM configuration” (I think Plasma 6.0 removed this option, try to find it in the SystemSettings KCM SDDM section).

    b) The another solution is the old one. Create a file into /etc/X11/xorg.conf/display.conf with the proper values of position and resolution. Search in a wiki about examples (archlinux wiki?).

    c) There is a third one that I used few years ago. SDDM allows you run any command after the screen initialization. So you can exec your xrand command here. Search about /etc/sddm.conf







  • I used Tekton for the last two years, and I didn’t like it. One of the reasons is the community split around Tekton Hub between versions 3 and 4. Another reason is that it’s not very Kubernetes native. While you write YAML, there are a subset of instructions that limit you regarding mundane things you can do on Kubernetes but Tekton doesn’t support, such as mounting different PersistentVolumeClaims or setting tasks by platforms or nodes (amd64, arm64, etc).

    I was so frustrated that I created my own Kubernetes-native CI/CD solution. Currently in development phases (when it is done, I will publish it here). This one uses real native Kubernetes components (jobs). You create Webhooks that launch Workflows, and Workflows can launch other Workflows or Jobs. You can do anything in a Job with no limitations other than Kubernetes itself. Take a look if you want: https://github.com/jlsalvador/simple-cicd