• 3 Posts
  • 75 Comments
Joined 2 years ago
cake
Cake day: August 6th, 2023

help-circle
  • Ah, yes… if only. I’ve upgraded internally SLR 1.0 -> SLR 3.0 but we can’t deploy it until a bug is fixed in the Steam client that causes, when we enable SLR 3, all Steam Decks to run the Linux build. Yes, Steam Decks run the Proton version, solely because the save file has different letter casing (yes I know it’s so annoying haha). We’ve spent quite some time on this and there’s no way to fix this without some folks losing their saves, and that is absolutely not an option. Soooo for now desktop Linux is stuck on runtime 1.0, and Steam Deck users are stuck on Proton. “fun” :/


  • At my studio we maintain a native Linux version with a custom game engine, and it indeed takes a lot of time. I don’t consider Proton a viable option as we lost the ability to integrate with Linux-specific stuff such as Wayland APIs or better input, but I can definitely see the appeal of switching to Proton… if your team uses Windows. If you have some developers on Linux, you naturally get a Linux build (if using cross platform APIs ofc) and it’s actually faster to cross-compile a Windows build every once in a while (skip the slow ntfs I/O) and ship that. But it requires getting more of the team on Linux :)


















  • I’ve tried to match your setup, but to no avail.

    Interfaces:

    lan

    Static address (192.168.2.1) Firewall zone: lan

    wwan

    Static address (192.168.0.211) Device: phy0-sta0 (listed as the client in the dropdown) Gateway: 192.168.0.1 Use custom DNS servers: 1.1.1.1 (using root router’s IP causes DNS to stop working) Firewall zone: WLAN

    repeater_bridge

    Relay bridge Relay between: lan wwan Firewall zone: unspecified

    Firewall zones: lan ⇒ WLAN accept accept accept WLAN ⇒ lan accept accept accept

    With this, I am able to ping google.com from a openwrt ssh session, but not my laptop connected w/ ethernet (and a static ip). In the interfaces list, lan is green, repeater_bridge is grey, and wwan is red. I tried running /etc/init.d/firewall stop but still no luck.


  • When I follow this guide and get to the part where DNS server of wwan to the root router’s IP, I am not able to ping anything from a ssh session into the router (I get “bad address ‘google.com’”. So, I set the DNS address to 1.1.1.1 which restored ping’s functionality. However, with this configuration the network does not appear to be shared at all. My PC, connected to the LAN port, cannot access the internet (regardless of forcing a static IP for the pc)