• 3 Posts
  • 56 Comments
Joined 4 个月前
cake
Cake day: 2025年6月8日

help-circle


  • Oh my bad, I misread the first line. In that case, I would guess that Proton on Steam might be using a different version of the DirectX translation layer. I’m not sure which that is, since im not sure which directx version the game uses.

    Very interesting that at least one person reported the same error happening on Windows.

    Edit: My guess is that wine is using WINED3D, the directx 9 to opengl translation layer, while proton is using DXVK. Since the game reportedly has this error on windows, the issue might actually be that DXVK is doing the “correct” thing and crashing the same way it would on windows.

    Did you verify that PROTON_USE_WINED3D=1 crashes with the exact same error and not a new one? Since you said the game works with vanilla wine, which defaults to wined3d, I would expect this to fix it.


  • priapus@piefed.socialto196ethernet rule
    link
    fedilink
    English
    arrow-up
    28
    ·
    7 天前

    I am aware, OP saying EoP just made me think of powerline and I wanted to share it for anybody who hasn’t heard of it since its a neat technology :)

    Appreciate you sharing this for anyone whos unaware though! I also didn’t know that plugging it into an outlet multiplier could have issues, thats interesting.



  • Steam uses the Steam runtime and can automatically apply specific settings and configurations known as Protonfixes.

    Try using Proton in Lutris and enabling the Steam runtime. Lutris has support for a tool called Umu Launcher which essentially replicates Steams method of launching games and applies Protonfixes for you. I don’t know the exact requirements to use it, but looking around in the discord (unfortunately) might get you some info.








  • I love Nushell, it’s so much more pleasant for writing scripts IMO. I know some people say they’d just use Python if they need more than what a POSIX shell offers, but I think Nushell is a perfect option in between.

    With a Nushell scripts you get types, structured data, and useful commands for working with them, while still being able to easily execute and pipe external commands. I’ve only ever had two very minor gripes with Nushell, the inability to detach a process, and the lack of a -l flag for cp. Now that uutils supports the -l flag, Nushell support is a WIP, and I realized systemd-run is a better option than just detaching processes when SSHd into a server.

    I know another criticism is that it doesn’t work well with external cli tools, but I’ve honestly never had an issue with any. A ton of CLI tools support JSON output, which can be piped into from json to make working with it in Nushell very easy. Simpler tools often just output a basic table, which can be piped into detect columns to automatically turn it into a Nushell table. Sometimes strange formatting will make this a little weird, but fixing that formatting with some string manipulation (which Nushell also makes very easy) is usually still easier than trying to parse it in Bash.