Hello @xRoBoTx, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

Looking at your Proton log, info: Driver : AMD open-source driver 2.0.249 looks like you're using AMDVLK, then later in the log we see info: Null hardware (RADV NAVI10): which looks like DXVK and RADV failing to find your video card. Can you test the game without AMDVLK in the mix?

Well, i there is no AMDVLK in my system. BUT, after you said it i tried to install it and figured out that actually helped me! Lol!
So its working with AMDVLK now!

I had lib32-vulkan-radeon package.

Replying to https://github.com/ValveSoftware/Proton/issues/6717#issuecomment-1653016372

Same problem here:
Nvidia 940m and same drivers, etc.

Replying to https://github.com/ValveSoftware/Proton/issues/6717#issuecomment-1653016372

Same problem:
RX 570 on latest Fedora Mesa drivers.

My guess is, the whole issue is related to this.

Replying to https://github.com/ValveSoftware/Proton/issues/6717#issuecomment-1660122424

Thanks!
I've tried uninstall completely, remove Fairlight 84 Steam folder, reinstall and use PROTON_EAC="path to Proton Easy Anti Cheat" %command and still can't load the game, just first screen, then black screen and close.

This may be some kind of GPU driver bug. I tested on 4 systems all running nobara. Steam Deck worked, laptop with 6800m worked, desktop with gnome and 7900xtx failed, media center with 7900 xtx and kde failed. The failure is the same noted in the other proton logs in this issue by others:

`[0803/182652.376:ERROR:network_change_notifier_win.cc(156)] WSALookupServiceBegin failed with: 8
[0803/182652.776:ERROR:mf_helpers.cc(12)] Error in dxva_video_decode_accelerator_win.cc on line 355
10.0.19043.1466
pid 11591 != 11590, skipping destruction (fork without exec?)`

The update released a few days ago fixed this issue, they also explicitly stated it was working with the Steam Deck.

The update released a few days ago fixed this issue, they also explicitly stated it was working with the Steam Deck.

still crashing here on two different systems, both with 7900 xtx.

even with the latest update its still wont go pass the Start Game screen.

steam-1928420.log

Also my Nvidia PC crashes also.

fixed with this patch:
farlight84_patch.txt

it's very much a hack and some debugging has to be done to figure out why USERPROFILE is not defined
if anyone wants, I can upload a build of proton-tkg with this patch applied

proton build: https://github.com/Etaash-mathamsetty/wine-builds/releases/tag/farlight84

fixed with this patch: farlight84_patch.txt

it's very much a hack and some debugging has to be done to figure out why USERPROFILE is not defined if anyone wants, I can upload a build of proton-tkg with this patch applied

proton build: https://github.com/Etaash-mathamsetty/wine-builds/releases/tag/farlight84

Not working on last update "Farlight 84 V14.4.1.5 Hotfix Notes"

looks like this is a game bug, I don't see anything crashing on wine side

I can confirm the game closes again with the latest patch.

Here is a contribution to help solving the problem. Last week, Farlight 84 was running fine on my system, until the last update, August 22, V14.4.1.5, when I now have: first screen > black screen (when the video is supposed to start) > crash. I believe the problem due to the hardware acceleration for the video player used on the loading intro, because of the dxva error I get running proton by cli:

[0825/012303.681:ERROR:mf_helpers.cc(12)] Error in dxva_video_decode_accelerator_win.cc on line 355

I am using Proton 8.0-3 as compatibility. No changes on my system since last week. It was working fine! Now it is not.

Specs:

Computer Information:
Manufacturer: ASUSTeK COMPUTER INC.
Model: Z170-A
Form Factor: Desktop
No Touch Input Detected
Processor Information:
CPU Vendor: GenuineIntel
CPU Brand: Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz
CPU Family: 0x6
CPU Model: 0x5e
CPU Stepping: 0x3
CPU Type: 0x0
Speed: 4000 MHz
8 logical processors
4 physical processors
Hyper-threading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Unsupported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
AVX2: Supported
AVX512F: Unsupported
AVX512PF: Unsupported
AVX512ER: Unsupported
AVX512CD: Unsupported
AVX512VNNI: Unsupported
SHA: Unsupported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported
Operating System Version:
Debian GNU/Linux 12 (bookworm) (64 bit)
Kernel Name: Linux
Kernel Version: 6.1.0-11-amd64
X Server Vendor: The X.Org Foundation
X Server Release: 12101007
X Window Manager: Mutter (Muffin)
Steam Runtime Version: steam-runtime_0.20230606.51628
Video Card:
Driver: NVIDIA Corporation NVIDIA GeForce GTX 970/PCIe/SSE2
Driver Version: 4.6.0 NVIDIA 525.125.06
OpenGL Version: 4.6
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 59 Hz
VendorID: 0x10de
DeviceID: 0x13c2
Revision Not Detected
Number of Monitors: 1
Number of Logical Video Cards: 1
Primary Display Resolution: 3840 x 2160
Desktop Resolution: 3840 x 2160
Primary Display Size: 27.48" x 15.47" (31.54" diag), 69.8cm x 39.3cm (80.1cm diag)
Primary Bus: PCI Express 16x
Primary VRAM: 4096 MB
Supported MSAA Modes: 2x 4x 8x 16x
Sound card:
Audio device: Realtek ALC892
Memory:
RAM: 15931 Mb
VR Hardware:
VR Headset: None detected
Miscellaneous:
UI Language: English
LANG: en_US.UTF-8
Total Hard Disk Space Available: 261344 MB
Largest Free Hard Disk Block: 161232 MB
Storage:
Number of SSDs: 5
SSD sizes: 480G,480G,320G,250G,160G
Number of HDDs: 0
Number of removable drives: 0

BTW I am using this script I have GTP-generated: https://pastebin.com/zHL7hLZf

Check and see if it's working on steamdeck, if not the game is broken on Linux again, and will have to wait till they fix it, so tell the dev in the steam discussion section for farlight

I know people with AMD GPUs and also crashes after loading the EAC screen. So that happened to me.
The game broke again after the 22nd August update.

Crash after EAC screen is still happening, tried proton 8.0.3 and bleeding edge
steam-1928420.log
These lines seem relevant:

[0922/195642.317:ERROR:mf_helpers.cc(12)] Error in dxva_video_decode_accelerator_win.cc on line 355
err:   D3D11VideoDevice::GetVideoDecoderProfileCount: Stub

Still crashing on the newest Proton version (8.0-4)

steam-1928420.log

I think we all have up on this game.

yeah im still convinced this is a game bug, but I have to check again

Was working just yesterday, now it isn't working after the 15.1 update. Successful booting seems to be influenced by the phase of the moon.

There are at least 2 workarounds :

1. add SteamDeck=1 envar

SteamDeck=1 %command%

1. disable RichTapWinSDKDLL.dll

WINEDLLOVERRIDES="RichTapWinSDKDLL.dll=d" %command%

Another way is by launching steam with -steamdeck argument which I think is the same as first method.

ps: only for desktop linux

I was getting black screen but after disabling RichTapWinSDKDLL.dll it works fine :)

actual fix: https://gitlab.winehq.org/wine/wine/-/merge_requests/4428

Now it works, but random freeze all computer when playing.
I've nvidia GTX 1650, Corei-10 10°

Now it works, but random freeze all computer when playing. I've nvidia GTX 1650, Corei-10 10°

Solved with Nvidia performance mode + PROTON_NO_FSYNC=1 PROTON_NO_ESYNC=1

Doesn't seem to work anymore, there is another error:

13391.062:018c:0190:err:module:LdrInitializeThunk "llhpbase.dll" failed to initialize, aborting
13391.062:018c:0190:err:module:LdrInitializeThunk Initializing dlls for L"Z:\\mnt\\games\\SteamLibrary\\steamapps\\common\\Farlight 84\\WindowsClient\\Solarland\\Binaries\\Win64\\SolarlandClient-Win64-Shipping.exe" failed, status c0000005

steam-1928420.log

Doesn't seem to work anymore, there is another error:

13391.062:018c:0190:err:module:LdrInitializeThunk "llhpbase.dll" failed to initialize, aborting
13391.062:018c:0190:err:module:LdrInitializeThunk Initializing dlls for L"Z:\\mnt\\games\\SteamLibrary\\steamapps\\common\\Farlight 84\\WindowsClient\\Solarland\\Binaries\\Win64\\SolarlandClient-Win64-Shipping.exe" failed, status c0000005

steam-1928420.log

Use Proton GE (GloriousEggroll). Install it using ProtonUp-Qt

Game is broken on Valve's protons, but works using Proton GE. It should not be verified for the steam deck

game is now broken

Yep, game is not working. Support is telling on discord that it is, obvious bs

WINE_DO_NOT_CREATE_DXGI_DEVICE_MANAGER=1 %command%

seems to make it work at least with GE-Proton9-7

WINE_DO_NOT_CREATE_DXGI_DEVICE_MANAGER=1 %command%

seems to make it work at least with GE-Proton9-7

I'm getting abnormal environment detected when in match instantly. But I can get to menu at least.

EDIT: Nvm, proton-ge is working, idk why mine from cachyOS isn't.

WINE_DO_NOT_CREATE_DXGI_DEVICE_MANAGER=1 %command%

seems to make it work at least with GE-Proton9-7

I thought no games need that anymore

WINE_DO_NOT_CREATE_DXGI_DEVICE_MANAGER=1 %command%

seems to make it work at least with GE-Proton9-7

I thought no games need that anymore

What's it for usually?

WINE_DO_NOT_CREATE_DXGI_DEVICE_MANAGER=1 %command%

seems to make it work at least with GE-Proton9-7

I confirm this setting works.

steam is no longer compiling shaders for this game

@SteavenGamerYT Do you mean the pop up that appears after clicking play but before the game launches? It's working fine over here. Do you have shader precaching disabled(settings > downloads)? Also note that you will only need to recompile shaders when either the game or your drivers get an update.

@SteavenGamerYT Do you mean the pop up that appears after clicking play but before the game launches? It's working fine over here. Do you have shader precaching disabled(settings > downloads)? Also note that you will only need to recompile shaders when either the game or your drivers get an update.

It's enabled and the game Is sttuering like crazy and dropping fps I have dxvk hud enabled and it keeps saying compiling shaders while playing this drops fps

@SteavenGamerYT Do you mean the pop up that appears after clicking play but before the game launches? It's working fine over here. Do you have shader precaching disabled(settings > downloads)? Also note that you will only need to recompile shaders when either the game or your drivers get an update.

It's enabled and the game Is sttuering like crazy and dropping fps I have dxvk hud enabled and it keeps saying compiling shaders while playing this drops fps

In battle royale mode it crashes after 5 seconds repeatedly.

I can confirm both Matchmaking and Ranked matches crash on loading screen or when the match starts. The other gamemodes (jetpack, deathmatch, etc) and training grounds seem to work fine.
Tested on CachyOS with proton cachyos native, tho other proton versions seem to be having the same issue, will send a more detailed report later.

Proton EM-10.0-2C has the fixes.

With some help from a friend, he found that the Unreal Engine minidump file failed with an access violation in the Agora RTC SDK.

Crash reason:  EXCEPTION_ACCESS_VIOLATION_READ
Crash address: 0x0000000000000028
Process uptime: not available

Thread 266  (crashed) - tid: 2008
 0  agora_rtc_sdk.dll + 0xfffd88
     rax = 0x00004043e24de5d9    rdx = 0x0000000000000000
     rcx = 0x0000000000000028    rbx = 0x000000009a41af70
     rsi = 0x0000000000000000    rdi = 0x0000000000000028
     rbp = 0x00000000911cd560    rsp = 0x00000000911cd400
      r8 = 0x000000009d2e21b8     r9 = 0x00000000000007d0
     r10 = 0x0000000000002e2e    r11 = 0x8101010101010100
     r12 = 0x00000000911cd6f0    r13 = 0x0000000000000000
     r14 = 0x000000009d2e21b8    r15 = 0x000000009d2e21b8
     rip = 0x00006ffff9dbfd88

This could be related to voice or game capture - I do see Farlight has a "replay" system now.

if any1 interested
Clearing shader cache seems to increase performance alot, but micro freezes remain (not related to proton afaik)

The other gamemodes (jetpack, deathmatch, etc) and training grounds seem to work fine.

Yeah, sticking to DM until devs fix their undertested game

Replying to https://github.com/ValveSoftware/Proton/issues/6717#issuecomment-3168182276

Yes agora tries to dereference RCX and as you can see it's value is 0x28. Adding a couple exports into iphlpapi works around the issue. It definetly is an application bug, but very simple to work around it

As for your micro freeze issue, I cannot reproduce it either.

Huh? It works fine for me (and at least one other person who asked to try)

Maybe I'm misunderstanding what issue or Proton version you're referring to.

To clarify: 10.0-2c (beta) does not fix the access violation issue causing the crash for me. My proton log shows Proton: 1753360060 proton-10.0-2c and I'm still getting the access violation and the game crashes. Please note that the crash only occurs in the regular matchmaking game modes, with players present - I had a friend play his first ever match successfully on linux, then his second match crashed.

Adding a couple exports into iphlpapi works around the issue. It definetly is an application bug, but very simple to work around it

So, are you using the workaround? Or is 10.0-2 working without the workaround?

Replying to https://github.com/ValveSoftware/Proton/issues/6717#issuecomment-3168735237

Oh I probably should not name my proton the same as valve's, wasn't aware that they also used 10.0-2C. Anyway, they are different versions you can find my 10.0-2C in my fork of Proton

Oh I probably should not name my proton the same as valve's, wasn't aware that they also used 10.0-2C. Anyway, they are different versions you can find my 10.0-2C in my fork of Proton

Ah, I see now, the "EM" refers to your forked Proton repository. TY for clarifying, and for your work fixing it. Will give it a try.

I can confirm the fork "Proton EM-10.0-2C" has the fixes and battle royale works properly.

I also confirm that unranked BR works with that version (yet to check ranked but must be the same)

Copy proton-EM-10.0-2C to /home/u s e r/.steam/steam/compatibilitytools.d/

Game freezes when playing with friends after around a hour, sometimes happens right away also when joining a match with friends

Cachyos, Mesa 25.2.1, Kernel 6.16.4, bleeding edge experimental

steam-1928420.log

@Kaiamaterasu Switch to experimental bleeding edge, add this to your game's launch parameter: PROTON_LOG=1 %command% and play the game until the issue happens, then upload the resulting steam-1928420.log file that will appear in your home folder.

Hi, somehow me and my friend have been banned from the game, i made sure my team was fully wiped out and left the game, just a warning to anyone else who is gonna play this game on linux, if this is something to do with proton or not i am not sure

Hi, somehow me and my friend have been banned from the game, i made sure my team was fully wiped out and left the game, just a warning to anyone else who is gonna play this game on linux, if this is something to do with proton or not i am not sure

@pollux78 you'll have to contact the Farlight devs - they have a discord where you can open an issue I believe.

@pollux78 I really hope its not Linux bans.... please keep us posted. Been playing for 5 days without any problems but now afraid of ban....

@pollux78 I really hope its not Linux bans.... please keep us posted. Been playing for 5 days without any problems but now afraid of ban....

3 people reporting 24hr ban today on their discord. The new update probably changed something. Got banned using Proton EM latest version.

And got ban but I did not even played... just stayed in menu......

Yea, insta "account banned", "mode unavailable" and 24h countdown.

Got a general respond from devs on discord that its "not supported" on linux so its better not to play it via linux because there were a lot of ban reports. Shame...another BR not playable

Got a general respond from devs on discord that its "not supported" on linux so its better not to play it via linux because there were a lot of ban reports. Shame...another BR not playable

Wait...so we shouldn't play farlight on linux ???

I don't know what to tell you... I played fine for 7 days and after latest patch I was in menu waiting for my friend and after few minutes account ban appeared so I was not even playing.

Respond (general) from dev in their discord:

Farlight 84 is only supported on PC (Windows). There is no official Linux version at this time. It is recommended that you use the officially supported version to avoid affecting the use of your account.

And on that discord many others reported ban also (on Linux).

I don't know what to tell you... I played fine for 7 days and after latest patch I was in menu waiting for my friend and after few minutes account ban appeared so I was not even playing.

Respond (general) from dev in their discord:

Farlight 84 is only supported on PC (Windows). There is no official Linux version at this time. It is recommended that you use the officially supported version to avoid affecting the use of your account.

But I have been playing since the day it was launched..I didn't get any ban....I will stop opening the game for now
Thanks for letting me know..
And i don't know why these gaming industry hates linux so much..

Did you played after yesterdays patch? BTW Its not permanent ban its only for 24h but I don't want to risk anymore.

Did you played after yesterdays patch? BTW Its not permanent ban its only for 24h but I don't want to risk

Yeah I played yesterday whole day.

And even this morning till afternoon..
I didn't get any ban

Got a general respond from devs on discord that its "not supported" on linux so its better not to play it via linux because there were a lot of ban reports. Shame...another BR not playable

Support doesn't know what they are talking about, if you open a new support ticket asking if it is supported with steamdeck they would reply with yes we are steamdeck verified. which runs under proton which means they support Linux unofficially aswell, it is the same response you get with other games, yes the game isn't natively supported on Linux but they have the anticheat enabled for proton so that it can work with Linux devices like the steamdeck.

Got a general respond from devs on discord that its "not supported" on linux so its better not to play it via linux because there were a lot of ban reports. Shame...another BR not playable

Support doesn't know what they are talking about, if you open a new support ticket asking if it is supported with steamdeck they would reply with yes we are steamdeck verified. which runs under proton which means they support Linux unofficially aswell, it is the same response you get with other games, yes the game isn't natively supported on Linux but they have the anticheat enabled for proton so that it can work with Linux devices like the steamdeck.

So the answer is yes and no both at same time.

@pollux78 I am all aware of that, but what about bans? I've even sent a email and we just go in circles "we dont support linux". I can't get into discussion with them what they support and what they don't and explaining what proton is and what native port is. They could respond we will look into it regarding proton maybe false positive bans whatever that was also happening with apex but they just respond we dont support linux . I dont know the way forward with this but will certainly not risk getting a long or a permanent ban to test "maybe it works now"

@pollux78 I am all aware of that, but what about bans? I've even sent a email and we just go in circles "we dont support linux". I can't get into discussion with them what they support and what they don't and explaining what proton is and what native port is. They could respond we will look into it regarding proton maybe false positive bans whatever that was also happening with apex but they just respond we dont support linux . I dont know the way forward with this but will certainly not risk getting a long or a permanent ban to test "maybe it works now"

it could simply be a bug with there new update, it is better to let valve's proton team handle this situation, the support team should be fully aware that the game supports the steamdeck as it is verified, lots of game studio support teams do not relies that the steamdeck is linux and is using a translation layer to play the game, and there is nothing stopping a user from playing it on linux desktop itself unless the studio enforces some checks for steamdeck only which hasn't been said by any developer from this studio.

I myself have been false banned on apex and the EA support also were unaware of linux users playing the game but respawn did know and were working with valve to solve issues with proton and i got unbanned without contacting respawn as i wasnt able to anyways, same goes with embark studios with the finals, its all the same with every support team, all you can do like you said not play until there is something officially said about it either from the game studio or valve in here.

Just to add an update there seems to be ban frenzy going on for linux, more and more people are reporting so everyone be careful

Just to add an update there seems to be ban frenzy going on for linux, more and more people are reporting so everyone be careful

Buddy...I just got banned this evening..
For 24 hours

Anyone got an update on this? I also got affected by this. Using ProtonGE latest and got handed my first account ban of 24 hours over the game crashing 3 times.

Does not matter which proton you use... the ban hammer will get you (they are banning linux folks).
They expanded the unsupportness: Linux, VM, compatibility layers etc (by their CS on discord)

EDIT: Seems there some progress but not 100% sure

Does not matter which proton you use... the ban hammer will get you (they are banning linux folks).
They expanded the unsupportness: Linux, VM, compatibility layers etc (by their CS on discord)

Based on the other discord text channels many users can play again, my friend has been playing it all day and hasn't been banned

https://discord.com/channels/795501514730635305/1413224155498676366

Does not matter which proton you use... the ban hammer will get you (they are banning linux folks).
They expanded the unsupportness: Linux, VM, compatibility layers etc (by their CS on discord)

Based on the other discord text channels many users can play again, my friend has been playing it all day and hasn't been banned

https://discord.com/channels/795501514730635305/1413224155498676366

Is it confirmed?

Yea it seems, was not aware of that since I've left discord but rejoined

Yea it seems, was not aware of that since I've left discord but rejoined

...
I will be waiting for someone to play and say here..
That it works

I've played one now but firstly stayed in the menu about 20min... so far works ¯_(ツ)_/¯

Yea it seems, was not aware of that since I've left discord but rejoined

...
I will be waiting for someone to play and say here..
That it works

I have played some matches with that friend now in ranked and have not been banned, as another user said I think it's ok for now, the support team continues to deny supporting Linux or even the steamdeck but someone is allowing it in the studio it seems, gotta love support who are uninformed 👍

played 5-6 matches SEEMS fine™

Crashes sometimes after a fight. It started after the 2025-09-11 update.

steam-1928420.zip

Also, no launch parameters were used during those matches.

Also, no launch parameters were used during those matches.

So right now at present is it safe to play farlight at linux right now.
And based on your observation which proton is better.
.and is there any recommendations or suggestions u would love to give..
And thank you so much for this help as fellow linux guy

No suggestions from me sadly.

No suggestions from me sadly.

It's okey...thank you so much for the information.

It was very valuable

No suggestions from me sadly.

It's okey...thank you so much for the information.

It was very valuable

You are very welcome

Scratch that, I am now suffering from consistent crashes

Got the logfile containing the crash.

Archived due to the log file exceeding Github's maximum allowed file size.

steam-1928420.log.tar.gz

I'd encourage the ones who can debug Wine issues to apply for the current Farlight beta test. The application link is in the in-game mailbox.

Maybe we'll catch more crashes before the actual release.

I'd encourage the ones who can debug Wine issues to apply for the current Farlight beta test. The application link is in the in-game mailbox.

Maybe we'll catch more crashes before the actual release.

On it.

Registration got sent over, awaiting a response.

Update on the Beta Test, I sadly did not get accepted. Let me know how well it goes.

My closing comment: Because of the unfair ban handed to my account, I am automatically not allowed to participate in the Beta Tests, so I wish those who do get accepted goodluck and let us know how it goes.

Replying to https://github.com/ValveSoftware/Proton/issues/6717#issuecomment-3411131089

Well buddy.. because I have exactly the same issue....right now...

I am also hoping for a solution..or atleast i wanna know what's the reason...are we not allowed to play this game anymore as linux users .

Well buddy.. because I have exactly the same issue....right now...

I am also hoping for a solution..or atleast i wanna know what's the reason...are we not allowed to play this game anymore as linux users .

They are open about the fact they do not support Linux in one of their videos, which makes me wonder how they even got SteamDeck verified 🤔

Replying to https://github.com/ValveSoftware/Proton/issues/6717#issuecomment-3411247916

I have the same question...they say linux isn't allowed...and they don't support steam deck..but behind the scenes they do ..
But what did it go wrong this time..
Can we expect repair from their side.
Or do we have to figure our way out...

I got some bad news, the new Season of Farlight 84 now instantly crashes when you launch it.

I believe this to be the final nail in the coffin for Linux support.

They actually call out Linux as being bad in this video https://www.youtube.com/watch?v=hdo8vCJU0gw

The actually call out Linux as being bad in this video https://www.youtube.com/watch?v=hdo8vCJU0gw

This is.....................heartbreakingly not the news I wanted to hear.

I cant believe I actually called it. This is a complete nightmare.

They actually call out Linux as being bad in this video https://www.youtube.com/watch?v=hdo8vCJU0gw

I guess that's it...we are done with farlight 84

Yes, the video. But did they actually manage to block Linux or it's just another crash of a new update?

Yes, the video. But did they actually manage to block Linux or it's just another crash of a new update?

Nice question to be honest

when i ran proton log there was a few things that popped out to me feel free to pop in here if any of these are unimportant at all.

597.440:0164:0390:err:dmo:create_placeholder_file Creating tag file h264-used.
0:00:00.020915783 12839 0x7fe7a01b5200 ERROR aacparse gstaacparse.c:358:gst_aac_parse_sink_setcaps: Need codec_data for raw AAC
0:00:00.020939017 12839 0x7fe7a01b5200 ERROR aacparse gstaacparse.c:358:gst_aac_parse_sink_setcaps: Need codec_data for raw AAC
597.572:0164:02ac:err:sync:RtlLeaveCriticalSection section 000000000122D8E8 "?" is not acquired
597.572:0164:02ac:err:sync:RtlLeaveCriticalSection section 000000000122D8E8 "?" is not acquired
602.948:0110:0140:err:service:device_notify_proc failed to get event, error 1726

when i ran proton log there was a few things that popped out to me feel free to pop in here if any of these are unimportant at all.

597.440:0164:0390:err:dmo:create_placeholder_file Creating tag file h264-used.
0:00:00.020915783 12839 0x7fe7a01b5200 ERROR aacparse gstaacparse.c:358:gst_aac_parse_sink_setcaps: Need codec_data for raw AAC
0:00:00.020939017 12839 0x7fe7a01b5200 ERROR aacparse gstaacparse.c:358:gst_aac_parse_sink_setcaps: Need codec_data for raw AAC
597.572:0164:02ac:err:sync:RtlLeaveCriticalSection section 000000000122D8E8 "?" is not acquired
597.572:0164:02ac:err:sync:RtlLeaveCriticalSection section 000000000122D8E8 "?" is not acquired
602.948:0110:0140:err:service:device_notify_proc failed to get event, error 1726

These are just warning at most

Yes, the video. But did they actually manage to block Linux or it's just another crash of a new update?

I am hoping it's a codec issue or something as I believe the video they play after the splash screen has always been glitchy and I believe they have changed it. They also mention something about animation issues in their patch notes.

Due to an issue affecting the intro animations of certain hero skins (Mission Express, Ultimate Weapon, Starry Wander, Venus, Vanguard Commander), we have temporarily disabled the related animation display feature. The issue is currently being fixed, and the animations will be re-enabled once the fix is complete.

🤞🏼

Ok I can confirm that it works without forcing any proton version (and if you do) if you use SteamDeck=1 %command% in launch options.

Ok I can confirm that it works without forcing any proton version (and if you do) if you use SteamDeck=1 %command% in launch options.

ok why does this just work.

Ok I can confirm that it works without forcing any proton version (and if you do) if you use SteamDeck=1 %command% in launch options.

ok why does this just work.

Maybe their anti-cheat is checking to see if you are playing on steamdeck, and this launch option fools it?

Ok I can confirm that it works without forcing any proton version (and if you do) if you use SteamDeck=1 %command% in launch options.

Will try on my end and report back when I can. These install sizes drives me nuts XD

Ok I can confirm that it works without forcing any proton version (and if you do) if you use SteamDeck=1 %command% in launch options.

Yea, no dice on this one. Still instantly crashes and refuses to launch.

Running without problem with proton-EM-10.0-30 and Launch options SteamDeck=1

Replying to https://github.com/ValveSoftware/Proton/issues/6717#issuecomment-3418421226

Oh? I was double checking if I miss-typed the launch flag. I always thought it is STEAMDECK=1 %command%

Replying to [#6717 (comment)](https://github.com/ValveSoftware/Proton/issues/6717#issuecomment-3418421226)

Oh? I was double checking if I miss-typed the launch flag. I always thought it is STEAMDECK=1 %command%

thats what im using proton EM 10.0-30

Would this be a Proton issue or a game issue as that is not my GPU?

Would this be a Proton issue or a game issue as that is not my GPU?

I installed Proton EM-10.0-30 with ProtonPlus application.

@MyNamesTee the video is working on my end, do you have shader precaching enabled? As for the black strip, if it only appears for a few seconds it must be what appears alongside the signin notification, it's not specific to your setup

@MyNamesTee the video is working on my end, do you have shader precaching enabled? As for the black strip, if it only appears for a few seconds it must be what appears alongside the signin notification, it's not specific to your setup

I do not have Shader Pre-caching enabled as I never needed it.

I dont think this game is a Vulkan/OpenGL game

@MyNamesTee shader precaching isn't specific to those apis, and it's not specific to actual game shaders. Proton transcodes videos it can't play otherwise, this is delivered through the same mechanism.

@MyNamesTee shader precaching isn't specific to those apis, and it's not specific to actual game shaders. Proton transcodes videos it can't play otherwise, this is delivered through the same mechanism.

Ahhh I see

Replying to https://github.com/ValveSoftware/Proton/issues/6717#issuecomment-3168585829

Yes agora tries to dereference RCX and as you can see it's value is 0x28. Adding a couple exports into iphlpapi works around the issue. It definetly is an application bug, but very simple to work around it

@Etaash-mathamsetty could you please explain more in detail where to add the workaround? A custom Wine build needs to be made?

Hi all!
I could run this game via PROTON-EM-10.0-37, It can connect and playable.
But one big problem: There is a Blank area in the upper 20% section, which created while the game notify me about Steam Connections in the login screen. I tried with SteamDeck and without SteamDeck options, but no chance.

@PPFHD on my desktop I see that the upper area becomes black under the notification, but it clears up after a few seconds, before the main menu of the game is done loading. Is this not the case for you?

@PPFHD on my desktop I see that the upper area becomes black under the notification, but it clears up after a few seconds, before the main menu of the game is done loading. Is this not the case for you?

Mine isnt clear, Its an graphical bug, because i alt+tab-bing with different windows, Its shows the full screen about the game.. I use fedora kde plasma with wayland. Gpu is amd.

Replying to https://github.com/ValveSoftware/Proton/issues/6717#issuecomment-4425389804

Mine is looks like too, than yours. But in menu and under game is black area visible too.

@PPFHD videos work on experimental, maybe you have shader cache disabled? steam settings > download
That said, After first connecting my account to the game it's never asked me to login manually

@PPFHD on my desktop I see that the upper area becomes black under the notification, but it clears up after a few seconds, before the main menu of the game is done loading. Is this not the case for you?

Which Linux you use?

Farlight 84 works fine with Proton 10.1000-105

Steam launch command:
SteamDeck=1 %command%

╭───────────────────── System ───────────────────────╮
│       Fedora Linux 43
│       7.0.5-cachyos1.fc43.x86_64
│       zsh 5.9
╰────────────────────────────────────────────────────╯
╭──────────────────── Hardware ──────────────────────╮
│       AMD Ryzen 7 5700X3D 8-Core Processor
│       Radeon RX 9070XT 16GB
│       8 GB / 31 GB
╰────────────────────────────────────────────────────╯
╭──────────────────── Session ───────────────────────╮
│       WAYLAND
│       niri
│       noctalia
│       kitty
╰────────────────────────────────────────────────────╯

@PPFHD turns out this game uses h264 for videos, it's likely you don't have support for that enabled, you can get that sorted by running this in your terminal: steam steam://unlockh264/.

As for the crash itself, as you'd been swapping proton versions around, it's best if you wipe the game's prefix. Assuming it's in the default disk, it will be in /home/youruser/steam/steam/steamapps/compatdata/1928420, just delete that folder.

If crashing persists after that, change the game's launch parameter on steam to PROTON_LOG=1 %command% then attempt to run the game again, this will generate a text file called steam-1928420.log in your home folder, upload it here, and zip it if it happens to be too big for github.

@PPFHD that's just the header for the proton log, if it ends there it means the didn't even get to run thus there's no log. Given that it's generally working for people, I'd first try moving the game to your main drive to avoid any potential filesystem shenanigans (specially if the partition it's in right now happens to be ntfs) and see if it that makes a difference.

When there's no proton log populated there's also a chance you might get some explanation why in ~/.steam/steam/logs/console-linux.txt.

Also, given that the proton log is empty that should mean that the behavior isn't what you described before, with the game starting but getting a color pattern, if it was getting that far currently then the logs would show something