• aintgotnoclue117@alien.topBEnglish
    1·
    10 months ago

    A one to two percent uplift in Starfield will probably not amount to much for the Deck, but I’m interested to see how it plays on the OLED anyways when it comes in. The new drivers and the faster RAM are bound to be something interesting, anyway.

    • JPPPPPPPP1@alien.topBEnglish
      1·
      10 months ago

      the latest update broke starfield on the deck, so it’s not even playable until Bethesda experiences a drop off in players and patches the game again.

      • mytrixx@alien.topBEnglish
        1·
        10 months ago

        I had the same problem. When I deleted all the configuration files and everything was working fine.
        I investigated what could be the problem with my optimal performance settings for SD and I think I found the cause.
        See if you have bGroupRenderAllShadows=1 in StarfieldCustom.ini. This item with the value 1 causes the shadows to flash in the character menu and after a while it freezes and restarts Steam on SD. Just set it to 0 or delete it. It helped me.

      • aintgotnoclue117@alien.topBEnglish
        1·
        10 months ago

        oh really? god that sucks. you thought the new patch would’ve helped the performance if at all. ah, well.

        • JPPPPPPPP1@alien.topBEnglish
          1·
          10 months ago

          yeah. if you open up the game, go into the menu for quests, and then go back out the entire deck crashes.

    • Leopard1907@alien.topOPBEnglish
      1·
      10 months ago

      What do you mean? You would be already be able to use them with VKD3D_CONFIG=dxr , now with this release it is not needed anymore.

      • insufficient_qualia@alien.topBEnglish
        1·
        10 months ago

        Last time I tested it DXR didn’t work in UE games. I’m asking whether the stabilization is due to increased compatibility.

  • Zeioth@alien.topBEnglish
    1·
    10 months ago

    I normally set these: RADV_PERFTEST='rt,gpl,ext_ms'

    Are they still necessary?

    • Leopard1907@alien.topOPBEnglish
      1·
      10 months ago

      Lol, no

      All of them are enabled by default.

      Mesh shader support was enabled by default with Mesa 23.0

      GPL was enabled by default with Mesa 23.1

      RT was enabled by default with Mesa 23.2

      In fact, looking at Mesa env vars also reveals that.

      https://docs.mesa3d.org/envvars.html#radv-driver-environment-variables

      Env vars remained for those features are nogpl,nomeshshader,nort because they are all enabled by default so disabling needs env vars.

      • Zeioth@alien.topBEnglish
        1·
        10 months ago

        For the sake of completing your answer for other users:

        You have 3 categories of env vars.

        • Mesa: Sometimes can be used to enable experimental features in the RADV driver. Currently, nothing fancy to enable. See all env vars.
        • VK3D: For DX12 games. In new games, sometimes you might have to use VKD3D_FEATURE_LEVEL=12_x if proton doesn’t default to the newest feature level yet (because it is under development). This was necessary for Cyberpunk in the past, for example. But it shouldn’t normally be necessary. See all env vars.
        • DXVK: For DX9/DX10/11 games. The only relevant env var for regular users nowadays is DXVK_FILTER_DEVICE_NAME, which you use to decide what GPU to use when you have more than one. See all env vars.

        By general rule you shouldn’t need to set any env var at all.

        IMPORTANT NOTE FOR MULTI GPU USERS: VK3D uses VKD3D_FILTER_DEVICE_NAME and DXVK uses DXVK_FILTER_DEVICE_NAME. It’s very easy to get confused with that, so please pay attention.

        • Rhed0x@alien.topBEnglish
          1·
          10 months ago

          you might have to use VKD3D_FEATURE_LEVEL=12_x if proton doesn’t default to the newest feature level yet (because it is under development).

          You don’t. It’ll report 12_2 if your GPU supports the required features.

  • sosickwitit@alien.topBEnglish
    1·
    10 months ago

    Does this mean anything for cs2? I’m so over processing Vulcan shaders… (complete Linux Nob)

    • Rhed0x@alien.topBEnglish
      1·
      10 months ago

      CS2 doesn’t run on Proton, it’s a Linux port.

      Assuming it’s built well, you can skip the “Processing shaders” step before launch.

    • mbriar_@alien.topBEnglish
      1·
      10 months ago

      Just disable shader pre-caching in steam, it will make no difference if you use recent drivers and didn’t install amdvlk by accident.

      • Taylor_Swifty13@alien.topBEnglish
        1·
        10 months ago

        can you tell me the best setup, driver etc. wise for cs2? I have not been able to play it even one session without it feeling a bit stuttery.

        • Leopard1907@alien.topOPBEnglish
          1·
          10 months ago

          Depends on your hw and driver.

          For Radv, Mesa 23.1 and newer.

          For Nvidia, 520+ driver

          For Intel, i dunno if they have Graphics Pipeline Libraries exts yet.

          Amdvlk doesn’t have GPL exts so it will stutter.

  • t1kiman@alien.topBEnglish
    1·
    10 months ago

    Um, I’m almost afraid to ask…

    Do I have to compile this on my own or will there be usable binaries at some point?

    Because apparently I’m already using some iteration of this already? I use these launch options I got from ProtonDB in Steam to enable ray/path tracing in Cyberpunk 2077:

    PROTON_ENABLE_NVAPI=1 PROTON_HIDE_NVIDIA_GPU=0 VKD3D_CONFIG=dxr11 VKD3D_FEATURE_LEVEL=12_1 gamemoderun %command%

    Does it come with Steam/Proton or Proton-GE and will be updated sooner or later?

    Sorry for being such a noob…