Proton working for anyone else?

[Boothy]

I've played the game for a long time via Proton (i.e. same as Steam Deck, but on PC), no issues at all, many hours.

I had a break for a few months, and decided to jump back in, but the game no longer works! At least no for me. Another post on protondb shows someone else having the same issue 2 months back.

The game launches fine, I can pick a map, start the game etc. But there is no 3D view at all! The 2D elements work fine. So menus, buttons etc all that works fine, but no actual map view!

As an example, I created a new game, and get to the initial placing of the camp. I can move the camera around, and see the red marker moving on the mini map, but the screen where the view would be is just solid background colour, no 3D view. But all buttons etc are there as expected, and work. i.e. Anything 2D is fine, just no 3D content at all!

I can even place the initial camp, with the screen showing invalid locations if I try to place over say a river, I just can't actually see the placement! Also once placed, all the build buttons appear (housing etc).

So basically the game itself seems to be running fine, it's just not rendering anything other than the 2D elements! So I am basically playing blind. No 3D view of any sort.

I've tried switching Proton version, used GE Proton etc. but it seems like something was changed in the 3D rendering part of the game around 2+ months back, that has just broken the 3D visual parts of the game.

I know the game is still beta, so Proton and Steam Deck compatibility is not exactly high priority, but just wanted to get this out.

Anyone else running okay via Proton?

Edit: Typo.

[Thagarr]

Linux Mint Cinnamon here, Proton works perfect for me on every game I have tried it on, including Ostriv. I did have an issue when I first ran the game and was only able to see the menu, but not the game it's self. I am running a Radeon 550 graphics card from 2017.

I solved that problem by unchecking the Borderless Window option in the Options menu. The game has run flawlessly since then, with the exception of some of the bugs fixed in previous patches. I would try playing around with some of the graphics options, changing resolutions.

[Boothy]

Thanks! Hadn't thought to switch from borderless! Just switched it off, and now working fine, very odd!

Only played for a little while (after midnight here, got work in the am) but so far so good.

Also Mint with Cinnamon, so don't know if that's common, or just a coincidence in this case.

Cheers :-D

[Thagarr]

Glad it worked for you mate! I am not sure exactly what the issue is with the borderless window. I run dual monitors though, and have had issues with some programs not liking that.

[Boothy]

Ha, I've been dual monitor since the 90s with CRTs, showing my age :-D

Current home setup, is a 3440 x 1440 144 Hz (Gigabyte) for the main, and an older regular 2560 x 1440 60Hz (aka 1440p) for the secondary (an old Dell from many years ago now).

I always game on the UW, and use the regular 1440p for web browsing etc.

Only game I have real dual monitor issues with is War Thunder, and that's native Linux!

Issue there seems to be it doesn't automatically pick the primary display, and won't let you pick one manually! As far as I can tell, it uses the primary display resolution, but uses the left most monitor to actually display. So if your main monitor is the left one, it works fine, but if not, like me, it doesn't. I have a little script to disable the left monitor that I use before launching War Thunder (and another to turn it back on afterwards). It's so far the only game I've ever needed to do this with!

[rowdog]

On X11 you can use xrandr to designate a primary monitor. I use
xrandr --output DVI-D-0 --auto --primary --output HDMI-0 --auto --rotate right --left-of DVI-D-0
That sets my DVI as primary and sets up my HDMI on the left and rotated to be tall.

[Boothy]

Thanks, although my primary is already set to the main display, it's just that War Thunder ignores the setting, or at least has some sort of bug there.

All other games work fine. On the rare occasion I get a game opening on the not primary display, there has been an option in those game to set the specific display in the settings.

Unfortunately War Thunder doesn't have this as a setting, and I've never found a way to force it to open on the primary display.

War Thunder seems to pick up my primary displays resolution, 3440 x 1440, (or perhaps just remembers it from last time), but then opens on the left most monitor (my primary being to the right). It actually squashes the display, i.e. the game is outputting at 3440 x 1440, but is showing on the 2560 x 1440 display, all squashed in.

My work around is a couple of shell scripts sat on my desktop next to my War Thunder icon (I use the native install, not via Steam). These use xrandr, one turns off the second display output, and the other turns it back on.

So it's run one script, launch the game, play. Then once done, exit game, run the other script.

Just means I can't have the second display on while playing (which I typically have Youtube or something on), but it's not really an issue as it's a competitive game, so I need to concentrate anyway :-)

[rowdog]

Yeah, changing the primary seemed to fix it for me but that's pretty annoying about War Thunder needing you to turn the monitor off. A really wonky kludge might be to have the script turn off the monitor and use a racey sleep. Uh, something like
./turn_off_monitor
(sleep 30 && turn_on_monitor)&
./warframe

Then it ought to turn on the monitor after letting War Frame claim the intended primary. That's a terrible way to do it but with a long enough sleep you might get your side monitor back ;^)

Just to get back on topic a bit... Ostriv works great for me with borderless fullscreen on Gentoo Linux with Nvidia 1070 (570.86.16 and before on 550) + AMD 3900xt. I tend to suspect your original issue has more to do with video drivers than Linux itself. FWIW, I did switch to "proton hotfix" but mainly because I never saw the hotfix version before and I did have to change away from the 4.x default I set some years ago.

[Boothy]

I tend to use GE Proton by default these days (as a default in Steams settings). Simply due to GE being a little more cutting edge and just seems to work out of the box first time with new games, more than the default Steam Proton versions. At least for me anyway. If I have issues, I'll then try one of the default Protons, or the experimental.

As for drivers, I'm on full AMD (so 5800X3D + 6900 XT), so I just use the regular open source drivers that come with Mint 22.1, e.g. mesa for GFX. Mint isn't exactly cutting edge on mesa, but they are usually only about 8 weeks or so behind for mesa releases.

The only time I've had mesa issues in the past, (might have been when CP 2077 first came out) I switched to a customer PPA mesa build, which resolved the issues. But I was still on Mint 21 back then, and removed the PPA when I upgraded from 21 to 22, and everything just worked, so never bothered adding the PPA back, so I'm basically on vanilla Mint currently (latest 22.1 now).