ValveSoftware
Farlight 84 (1928420)
Compatibility Report
- Name of the game with compatibility issues: Farlight 84
- Steam AppID of the game: 1928420
System Information
- GPU: AMD Radeon Graphics (AMD Ryzen 5 5500U)
- Driver/LLVM version: Mesa 23.2.0
- Kernel version: 6.2.12-zen1-1-zen
- Link to full system information report as: Gist
- Proton version: 8.0-1
I confirm:
- [x] that I haven't found an existing compatibility report for this game.
- [x] that I have checked whether there are updates for my system available.
Symptoms
Game crashes after launch.
Reproduction
- Download the game
- Launch the game
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?
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.249looks like you're using AMDVLK, then later in the log we seeinfo: 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!
Your system information from 15 minutes ago disagrees: https://gist.github.com/xRoBoTx/aeb07ff835bc42533584b4f04d21566c#file-steam-sysinfo-log-L290-L306 and https://gist.github.com/xRoBoTx/aeb07ff835bc42533584b4f04d21566c#file-steam-sysinfo-log-L431-L460 shows 32 bit amdvlk most likely from the lib32-amdvlk system package.
Looks like today's update broke the game on Linux (Game windows open with a black screen, then closes after a couple of seconds)
Compatibility Report
- Name of the game with compatibility issues: Farlight 84
- Steam AppID of the game: 1928420
System Information
- GPU: NVIDIA GeForce RTX 3060
- Video driver version: nvidia 535.86.05
- Kernel version: 5.19.0-50-generic
- Link to full system information report as Gist: https://gist.github.com/gabuch2/fc563715f85daf89e2761238a3e8ab84
- Proton version: Proton Experimental / Same behavior with Proton GE
I confirm:
- [x] that I haven't found an existing compatibility report for this game.
- [x] that I have checked whether there are updates for my system available.
Symptoms
The game after showing the EAC screen, shows a black screen then closes. This didn't happen before the latest Farlight update.
Reproduction
- Open the Game
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.
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.
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
Proton 8 and Experimental, same error:
[0822/200715.624:ERROR:network_change_notifier_win.cc(156)] WSALookupServiceBegin failed with: 8
[0822/200719.085:ERROR:browser_gpu_channel_host_factory.cc(103)] Failed to launch GPU process.
Proton 8 and Experimental, same error:
[0822/200715.624:ERROR:network_change_notifier_win.cc(156)] WSALookupServiceBegin failed with: 8 [0822/200719.085:ERROR:browser_gpu_channel_host_factory.cc(103)] Failed to launch GPU process.
huh I don't get that second error
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
Proton 8 and Experimental, same error:
[0822/200715.624:ERROR:network_change_notifier_win.cc(156)] WSALookupServiceBegin failed with: 8 [0822/200719.085:ERROR:browser_gpu_channel_host_factory.cc(103)] Failed to launch GPU process.huh I don't get that second error
Must be my Nvidia.
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
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 :
- add
SteamDeck=1envar
SteamDeck=1 %command%
- 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
