search

ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
23.9k stars 1.04k forks source link

Farlight 84 (1928420) #6717

Open catemiko opened 1 year ago

catemiko commented 1 year ago

Compatibility Report

System Information

I confirm:

steam-1928420.log

Symptoms

Game crashes after launch. image

Reproduction

  1. Download the game
  2. Launch the game
kisak-valve commented 1 year ago

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?

catemiko commented 1 year ago

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!

kisak-valve commented 1 year ago

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.

catemiko commented 1 year ago

I had lib32-vulkan-radeon package.

ghost commented 1 year ago

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

System Information

I confirm:

Symptoms

The game after showing the EAC screen, shows a black screen then closes. This didn't happen before the latest Farlight update.

Reproduction

  1. Open the Game

steam-1928420.log

lucasgabmoreno commented 1 year ago

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

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

Gustavo17pacheco commented 1 year ago

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

Same problem: RX 570 on latest Fedora Mesa drivers.

wendersonp commented 1 year ago

Screenshot_20230801-082157~3 My guess is, the whole issue is related to this.

lucasgabmoreno commented 1 year ago

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.

GloriousEggroll commented 1 year ago

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?)`
ghost commented 1 year ago

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

GloriousEggroll commented 1 year ago

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.

massatt212 commented 1 year ago

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

steam-1928420.log

Also my Nvidia PC crashes also.

Etaash-mathamsetty commented 1 year ago

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

lucasgabmoreno commented 1 year ago

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"

massatt212 commented 1 year ago

It's down again, you tried with proton experimental?

Etaash-mathamsetty commented 1 year ago

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

ghost commented 1 year ago

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

lucasgabmoreno commented 1 year ago

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.
Etaash-mathamsetty commented 1 year ago

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

fde-capu commented 1 year ago

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

lucasgabmoreno commented 1 year ago

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.

massatt212 commented 1 year ago

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

jorgicio commented 1 year ago

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.

simifor commented 11 months ago

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
ghost commented 11 months ago

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

steam-1928420.log

massatt212 commented 11 months ago

I think we all have up on this game.

Etaash-mathamsetty commented 11 months ago

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

JupiterSky11 commented 10 months ago

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.

rezzafr33 commented 10 months ago

There are at least 2 workarounds :

  1. add SteamDeck=1 envar 
    SteamDeck=1 %command%
  2. 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

davispuh commented 10 months ago

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

Etaash-mathamsetty commented 9 months ago

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

lucasgabmoreno commented 9 months ago

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

lucasgabmoreno commented 9 months ago

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

rezzafr33 commented 9 months ago

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

lucasgabmoreno commented 9 months ago

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

wendersonp commented 6 months ago

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

SteavenGamerYT commented 3 months ago

game is now broken

ziomek64 commented 3 months ago

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

xpander69 commented 2 months ago

WINE_DO_NOT_CREATE_DXGI_DEVICE_MANAGER=1 %command%

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

ziomek64 commented 2 months ago

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.

Etaash-mathamsetty commented 2 months ago

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

ziomek64 commented 2 months ago

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?

jorgicio commented 2 months ago

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.

simifor commented 2 months ago

farlight should work with the current proton experimental bleeding edge, and without extra environment variables.

ziomek64 commented 2 months ago

farlight should work with the current proton experimental bleeding edge, and without extra environment variables.

Etaash-mathamsetty commented 2 months ago

farlight should work with the current proton experimental bleeding edge, and without extra environment variables.

  • What changed?

Gofman added the workaround to the proton script

ziomek64 commented 2 months ago

farlight should work with the current proton experimental bleeding edge, and without extra environment variables.

  • What changed?

Gofman added the workaround to the proton script

I see, will this come to proton ge if eggroll updates it?