I’m trying out Bazzite again after about a year with CachyOS because I don’t have time for tinkering anymore and only play games maybe once a month or so. Anyway, I’m playing some Hitman tonight and noticed this lighting bug a few times. I remember seeing it in Cyberpunk 2077 when I was using Bazzite about a year ago too, shortly before I switched to CachyOS. Does anyone know what’s causing it and how to fix it? If it’s a big deal to fix I won’t bother as I don’t have much time for computers, and don’t want to spend most of that fixing a bug. I took a couple more pictures too, I’ll show below.

If it’s important at all, this is pretty much a clean install, I haven’t done any tinkering at all and have barely downloaded anything either. I downloaded a VPN, a password manager, and otherwise I think everything else is what came with the distro. I have the game running from an external HDD if that makes a difference. I played the game a couple months ago on CachyOS with zero issues.

  • Static_Rocket@lemmy.worldEnglish
    72·
    9 days ago

    DXVK cache lingering between driver versions has occasionally gotten me similar effects. You can delete the shader cache in the proton prefix and see if that helps.

      • sp3ctr4l@lemmy.dbzer0.comEnglish
        2·
        3 days ago

        Home/.steam/steam/steamapps/compatdata

        That should be, if you are on Bazzite, the dir that houses all the Proton data for each game.

        Home/.steam/steam/steamapps/shadercache

        And that should be the … basically the shaders assembled by Proton.

        Unfortunately, the individual folders in those dirs, per game, are all named with an ID number that Steam uses internally.

        You probably can figure out which specific game is which number, or, you can just wipe out everything in the compatdata and shadercache folder.

        Doing that will essentially clear out Proton, Steam will then redownload Proton and rebuild game specific shader caches, as per your settings as to if that is automatic or on game launch.

        You might need to shutdown and restart Steam, or reboot the system, or jump in and out of deck-game mode or something like that, to fully kick Steam into realizing you just performed surgery on it and it should start healing.

        If that doesn’t work, in Bazzite terminal:

        ujust fix-reset-steam

        This is a much more thourough reset process though, read up on it.

          • sp3ctr4l@lemmy.dbzer0.comEnglish
            2·
            2 days ago

            No prob!

            Did any of this work out… or problem still perists?

            EDIT

            Oh shit… actually read your full initial comment.

            Yes, if the entire game… or Steam… is running from an external HDD… including the shaders and such?

            Shaders generally are used many times, every frame.

            Having those on an internal SSD could make a difference, and possibly be part of the problem you’ve shown, depending on your total hardware setup.

            Generally speaking, more graphically complex 3D games that make substantial usenof shaders should be run from an internal SSD.

            You can do HDD for 2D or less complex 3D games and its usually fine, but if fancy pants shaders are involved in many more modern games, use an SSD if you can.

            • BurntWits@sh.itjust.worksOPEnglish
              2·
              2 days ago

              That makes a lot of sense actually. Maybe I’ll try installing it on the internal ssd first before doing anything else. As mentioned I don’t spend much time on my pc so it might be a bit before I actually try anything to fix it, but I’ll start with installing it on ssd first and then your other solution after if it doesn’t work.

    • Natanael@slrpnk.netEnglish
      4·
      8 days ago

      I think that’s an error with prebaked lighting effects, because it’s hard to see why it would give those square texture error style glitches otherwise