(Steam Deck) Titanfall 2 will not boot through Northstar at all after latest update

[Nannose]

Bug

Game does not boot when clicking play in Steam with Northstar proton selected and the launch command enabled. Worked fine before most recent Northstar update.

Steps to reproduce

1. Follow the setup guide here https://r2northstar.gitbook.io/r2northstar-wiki/installing-northstar/steamdeck-and-linux/installing-on-steamdeck-and-linux
2. Click play

Specifications

• Northstar version: v1.12.5
• Platform: Steam

Here is the proton log from the game trying to run with Northstar, and copied logs from running Steam through the terminal doing the same.
steam-1237970.log
terminal.txt

[GeckoEidechse]

broken wine prefix according to @Jan200101

2172.530:0118:011c:warn:seh:dispatch_exception EXCEPTION_ACCESS_VIOLATION exception (code=c0000005) raised
2172.530:0118:011c:trace:seh:dispatch_exception  eax=00000001 ebx=ffe4bcc0 ecx=ffe4bdcc edx=00000000 esi=f78b99c8 edi=ffe4bc00
2172.530:0118:011c:trace:seh:dispatch_exception  ebp=ffe4bcc0 esp=ffe4bad0 cs=0023 ss=002b ds=002b es=002b fs=0063 gs=006b flags=00210246
2172.530:0118:011c:trace:seh:call_stack_handlers calling handler at 7BC6C250 code=c0000005 flags=0
wine client error:11c: write: Bad file descriptor

[Nannose]

broken wine prefix according to @Jan200101

2172.530:0118:011c:warn:seh:dispatch_exception EXCEPTION_ACCESS_VIOLATION exception (code=c0000005) raised
2172.530:0118:011c:trace:seh:dispatch_exception  eax=00000001 ebx=ffe4bcc0 ecx=ffe4bdcc edx=00000000 esi=f78b99c8 edi=ffe4bc00
2172.530:0118:011c:trace:seh:dispatch_exception  ebp=ffe4bcc0 esp=ffe4bad0 cs=0023 ss=002b ds=002b es=002b fs=0063 gs=006b flags=00210246
2172.530:0118:011c:trace:seh:call_stack_handlers calling handler at 7BC6C250 code=c0000005 flags=0
wine client error:11c: write: Bad file descriptor

The game works fine vanilla though.

It's only when I tried running the game with Northstar proton after running it all with experimental first where it doesn't boot. Switching back to experimental without touching the prefix it still works perfect as well.

[Jan200101]

The game works fine vanilla though.

It's only when I tried running the game with Northstar proton after running it all with experimental first where it doesn't boot. Switching back to experimental without touching the prefix it still works perfect as well.

The wine prefix was generated under Proton Experimental and is in a state that other Proton versions are likely not capable of handling.

You need to manually remove the prefix, restart steam and try again

[Nannose]

The game works fine vanilla though.
It's only when I tried running the game with Northstar proton after running it all with experimental first where it doesn't boot. Switching back to experimental without touching the prefix it still works perfect as well.

The wine prefix was generated under Proton Experimental and is in a state that other Proton versions are likely not capable of handling.

You need to manually remove the prefix, restart steam and try again

Launching the game with an empty prefix though Northstar proton does not work either.

It seems to run the setup, but then the game does not launch, and trying to run it again it just exits without even opening a window.

It also throws up this error on initial setup, which doesn't happen under any other type of proton on any game I've tried.

Here are the logs from the initial empty prefix launch with Northstar proton, and then launching again after it exited without starting (where it just happens again).

steam-1237970.log
steam-1237970 (2).log

I should mention the guide explicitly says to launch and setup the game vanilla first, and that worked perfectly and the game booted fine through Northstar up until the latest update which somehow borked everything. I could even switch between experimental and Northstar with no issues or messing with the prefix.

This is error is not from anything I did.

[Jan200101]

The new logs no longer show an access violation, so thats a step in the right direction.

The guide still recommends that because in the past things were broken without it.
Since then doing it actually broke Northstar for people, without anyone knowing why.

[Nannose]

The new logs no longer show an access violation, so thats a step in the right direction.

The guide still recommends that because in the past things were broken without it. Since then doing it actually broke Northstar for people, without anyone knowing why.

Well there are the logs, I don't know what else to try. Doing it like I did it before doesn't work, and doing it with Northstar alone doesn't work, yet the game runs fine normally so it shouldn't be anything with the local files. I tried extracting the Northstar release manually instead of using Viper and that didn't change anything either.

[Nannose]

Still having this issue, game refuses to boot through northstar but works perfectly fine normally. Deleting compatdata and reinstalling northstar manually makes no difference.

Why does this keep breaking? How do I fix it?

steam-1237970.log

[GeckoEidechse]

Actually does vanilla still work?

[Nannose]

Actually does vanilla still work?

Yes, through proton experimental it runs perfectly fine.