Not 100% sure, but it looks like the problem may be with

10517.884:0034:0037:fixme:wlanapi:WlanEnumInterfaces (00000001, 00000000, 06A6D800) semi-stub
10519.055:0034:0035:warn:seh:OutputDebugStringA "QObject::connect: No such signal QNetworkReplyHttpImpl::error()\n"
10519.055:0034:0035:trace:seh:raise_exception code=40010006 flags=0 addr=0x7b00dd67 ip=7b00dd67 tid=0035

which seems to involve Qt code (QNetworkReplyHttpImpl). Since Qt is garbage with Wine https://appdb.winehq.org/objectManager.php?sClass=version&iId=37891 I wonder if the problem is that Wine needs fixes for Qt applications since it throws a fixme just before this error?

https://github.com/wine-mirror/wine/blob/ba9f3dc198dfc81bb40159077b73b797006bb73c/dlls/wlanapi/main.c

Looks like in the best case it may return ERROR_SUCCESS whatever a successful error means. That error was a success lol. Funny people.

Might not be playing this game anytime soon.

On another note, that problem appears to affect wifi so I wonder if Newbytee is using wifi? The gist doesn't have that info.

That might fix that issue (using wired lan port) or that the code gets called anyway wifi or not.

On another note, that problem appears to affect wifi so I wonder if Newbytee is using wifi? The gist doesn't have that info.

That might fix that issue (using wired lan port) or that the code gets called anyway wifi or not.

I'm using Ethernet.

This game apparently uses a kernel driver for anticheat (xigncode), so even if the current issue isn't related (and were to be fixed), I doubt it would run until kernel drivers are properly supported in wine (as far as I understand, they aren't).

any news ?

Same problem here with latest version of Black Desert Online as of today;

Processor Information:
    CPU Vendor:  AuthenticAMD
    CPU Brand:  AMD Ryzen 7 2700 Eight-Core Processor          
    CPU Family:  0x17
    CPU Model:  0x8
    CPU Stepping:  0x2
    CPU Type:  0x0
    Speed:  3200 Mhz
    16 logical processors
    8 physical processors
    HyperThreading:  Supported
    FCMOV:  Supported
    SSE2:  Supported
    SSE3:  Supported
    SSSE3:  Supported
    SSE4a:  Supported
    SSE41:  Supported
    SSE42:  Supported
    AES:  Supported
    AVX:  Supported
    AVX2:  Unsupported
    AVX512F:  Unsupported
    AVX512PF:  Unsupported
    AVX512ER:  Unsupported
    AVX512CD:  Unsupported
    AVX512VNNI:  Unsupported
    SHA:  Unsupported
    CMPXCHG16B:  Supported
    LAHF/SAHF:  Supported
    PrefetchW:  Unsupported

Operating System Version:
    Unknown (64 bit)
    Kernel Name:  Linux
    Kernel Version:  5.7.15-100.fc31.x86_64
    X Server Vendor:  Fedora Project
    X Server Release:  12006000
    X Window Manager:  Xfwm4
    Steam Runtime Version:  steam-runtime_0.20200720.0

Video Card:
    Driver:  NVIDIA Corporation GeForce RTX 2060/PCIe/SSE2
    Driver Version:  4.6.0 NVIDIA 450.66
    OpenGL Version: 4.6
    Desktop Color Depth: 24 bits per pixel
    Monitor Refresh Rate: 29 Hz
    VendorID:  0x10de
    DeviceID:  0x1f08
    Revision Not Detected
    Number of Monitors:  2
    Number of Logical Video Cards:  1
    Primary Display Resolution:  3840 x 2160
    Desktop Resolution: 6400 x 2160
    Primary Display Size: 24.45" x 13.43" (27.87" diag)
                                            62.1cm x 34.1cm (70.8cm diag)
    Primary Bus: PCI Express 16x
    Primary VRAM: 6144 MB
    Supported MSAA Modes:  2x 4x 8x 16x 

Sound card:
    Audio device: USB Mixer

Memory:
    RAM:  32118 Mb

VR Hardware:
    VR Headset: None detected

Miscellaneous:
    UI Language:  English
    LANG:  en_CA.UTF-8
    Total Hard Disk Space Available:  1048276 Mb
    Largest Free Hard Disk Block:  60531 Mb

Problem persists here my log and system info:
steam-hardware-info.txt
steam-582660.log

Unfortunately Black Desert uses Xigncode3 as anti-cheat and it leads a lot of problems for Linux users. I hope some update fixes that.

Black Desert changed to Easy AntiCheat about 6 months ago, better hopes for it now.

After the release of the new version of Easy Anti-Cheat, tried to run the game. As a result, the Launcher did not even start. The logo appears and then closes.

steam-582660.log

This title switched to Epic's Anti Cheat service, which to my knowledge looks to be the same as used in the AVA CBT which ran like a charm for that game. Could this game please be reinvestigated for issues?

steam-582660.log

EDIT: All I can detect from the logs is that there's a null pointer exception somewhere, if I need to run this with any special features please let me know. The proton versions tried were experimental and tkg.

If I remember correctly, the launcher does a bunch of web request before even starting. It feels/looks like that is failing.

Here are some more log files:
steam-582660.log
update.log
debug.log

If I remember correctly, the launcher does a bunch of web request before even starting. It feels/looks like that is failing.

This is the case, and if you use a custom launcher you are able to play the game using DX9 mode apparently (You can't use the Steam version of the game). If it could be implemented where the check succeeds then this game should start working in some capacity. This project here is the workaround that I've seen talked about. https://github.com/jsoctocat/BDO-Launcher

This project here is the workaround that I've seen talked about. https://github.com/jsoctocat/BDO-Launcher

I use this launcher on Windows for OTP reasons, and it cannot download or update the game. How do you update the game every Wednesday with this workaround method? I've to try it and give more feedback.

This project here is the workaround that I've seen talked about. https://github.com/jsoctocat/BDO-Launcher

I use this launcher on Windows for OTP reasons, and it cannot download or update the game. How do you update the game every Wednesday with this workaround method? I've to try it and give more feedback.

It requires you to move the files from Windows every week in order to make use of it. Less than ideal, if work could be done to get the official launcher working that would be great. Here's a link to someone talking about the process. https://www.reddit.com/r/blackdesertonline/comments/yg1isl/comment/iu6msod/?utm_source=share&utm_medium=web2x&context=3

If I remember correctly, the launcher does a bunch of web request before even starting. It feels/looks like that is failing.

This is the case, and if you use a custom launcher you are able to play the game using DX9 mode apparently (You can't use the Steam version of the game). If it could be implemented where the check succeeds then this game should start working in some capacity. This project here is the workaround that I've seen talked about. https://github.com/jsoctocat/BDO-Launcher

Dx9 is being removed on February 1st: https://www.naeu.playblackdesert.com/en-US/News/Detail?groupContentNo=4595

Dx9 is being removed on February 1st: https://www.naeu.playblackdesert.com/en-US/News/Detail?groupContentNo=459

Even if that's the case, at least we have 2 solid issues now telling us what we need to get the game running.

1. Initial launcher web requests that fail
2. DXVK not working with BDO's DX11 implementation.

We know it's not the anti-cheat that's at fault, so it's actually a possibility to get running. (Unless the reddit users used a workaround for the anti-cheat)

You can get past the client now. "Failed to init Auth."

@Hourija which version of Proton did you use? Did you use special command line parameters?

All Versions (Experimental, Hotfix, 8.0-2) I tried to start Black Desert show me the Launcher Icon and after that I get a black window which the cursor changes if I hover over it. If I click in certain spots my browser opens the links in the launcher. Sadly I cannot start the game by clicking in the lower right corner (where the play button is supposed to be). The launcher itself looks like this:

I use Manjaro with an Ryzen R5 5600 + RX 5700XT

@dominik-code
Proton experimental and ge got me to the same point.
The client for me is a black window aswell. The play button works after selecting eu or na to play on. It is a bit tricky to do without seeing but doable. I did this by looking at pictures of the client.

Black Desert moving back to Xigncode, has already changed on the public test server.

Black Desert moving back to Xigncode, has already changed on the public test server.

I've heard mixed reports about xigncode. How well does it work on proton?

Black Desert moving back to Xigncode, has already changed on the public test server.

I've heard mixed reports about xigncode. How well does it work on proton?

As far as I know, it doesn't. I became very interested in trying out Scarlet Blade, which implements XIGNCODE as well, and even though the game does install successfully and the game launcher works like a charm, the game itself does not even start with WINE, and we all know that Proton is a slight modification of WINE's codebase but for Steam.

At least according to long time BDO players, XIGNCODE also tends to lead to false-positive bans that Kakao was reluctant to overturn. If PA implements it in a similar way to the prior use, it will have a higher chance for account bans than I would be comfortable with (at least hopefully PA would be more responsive...)

Today BDO switched from EAC to XIGNCODE. The Game is working now on Linux. The only Problem left is that the Launcher is completely black and you've to type in your Account-Data blind.

If you use the Steam version of the game (authenticates using your Steam ID), does that skip the launcher entirely or do you still have to click on the "play" button?

I dont have the Steam Version. Just added the Launcher as non steam game.

I haven't yet tried post EAC, however thus was the case before. After the first launch and having to click the server and whatnot, you only needed to click play after (albeit with the window blacked-out).

It's not just the launcher being black. The central market/warehouse is unusable as well. (Plus the game loads zones too slowly as if it's running on an HDD despite being on an nvme.)

The 3rd party launcher seems to work as a workaround (just have to install it as a non-steam game, then point it to your BDO install folder), but requires you to have successfully launched the game at least once via the normal launcher, which almost defeats the purpose.

Are there no leads at all on how to fix the rendering of the launcher?

I wanted to share my experience with running Black Desert steam version on the Steam Deck using Proton GE 8-27. I've managed to launch the game successfully, despite encountering a couple of issues.

The launcher appears completely black, but I've been able to navigate blindly and enter my OTP and select the region blindly. Surprisingly, the "Play" button works as expected. However, once inside the game, it crashes after a few minutes without any error messages.

Has anyone has encountered a similar problem or has insights on how to debug or fix this issue? any assistance would be greatly appreciated.

Start steam via CLI and add following Launch Option for BDO: PROTON_LOG=1

I've tested BDO for a few Hours and didnt have any crashes with following Specs:

CPU: 7945HX
GPU: 4090 Mobile (545.29.06 driver)
Distro: Arch Linux
DE: KDE Plasma 6 RC 1
Proton: Proton-Cachyos
Using x11

I haven't had any crashes as of yet, but I'm running the game via Lutris with ge-proton 8-25. The biggest issue right now is getting the Market Place to work. Without it you face some pretty big limitations, can't move items from/to market etc. I've been trying to debug some traces, but no luck yet.

CPU: 5800x3d
GPU: 7900xt
Distro: Fedora 39
DE: Gnome 45
Proton: GE-Proton 8-25
Using Wayland

Start steam via CLI and add following Launch Option for BDO: PROTON_LOG=1

I've tested BDO for a few Hours and didnt have any crashes with following Specs:

CPU: 7945HX GPU: 4090 Mobile (545.29.06 driver) Distro: Arch Linux DE: KDE Plasma 6 RC 1 Proton: Proton-Cachyos Using x11

I changed to ge-proton 8-25 and it seems and it seems to work now, but it doen't work the central market and the black spirit's adventure and can't reopen the game when I do a minimize to tray

Here is the error from the bdo client regarding the market:

"Failed to load the information from the Central Market. Please try again later.","Log":"WorldMarket processJSON Fail size(1006) != originalsize(0), type(8)" }
"Failed to load the information from the Central Market. Please try again later.","Log":"WorldMarket processJSON Fail cant process type : , type(10)" }
"Failed to load the information from the Central Market. Please try again later.","Log":"WorldMarket processJSON Fail size(162) != originalsize(-256), type(18)" }
"Failed to load the information from the Central Market. Please try again later.","Log":"WorldMarket processJSON Fail cant process type : , type(26)" }
"Failed to load the information from the Central Market. Please try again later.","Log":"WorldMarket processJSON Fail size(162) != originalsize(0), type(18)" }
"Failed to load the information from the Central Market. Please try again later.","Log":"WorldMarket processJSON Fail cant process type : , type(26)" }
"Failed to load the information from the Central Market. Please try again later.","Log":"WorldMarket processJSON Fail cant process type : , type(26)" }
"Failed to load the information from the Central Market. Please try again later.","Log":"WorldMarket processJSON Fail size(162) != originalsize(0), type(18)" }
"Failed to load the information from the Central Market. Please try again later.","Log":"WorldMarket processJSON Fail cant process type : , type(26)" }
"Failed to load the information from the Central Market. Please try again later.","Log":"WorldMarket processJSON Fail size(162) != originalsize(1701978624), type(18)" }
"Failed to load the information from the Central Market. Please try again later.","Log":"WorldMarket processJSON Fail size(162) != originalsize(1701978624), type(18)" }
"Failed to load the information from the Central Market. Please try again later.","Log":"WorldMarket processJSON Fail cant process type : , type(26)" }
"Failed to load the information from the Central Market. Please try again later.","Log":"WorldMarket processJSON Fail cant process type : , type(26)" }
"Failed to load the information from the Central Market. Please try again later.","Log":"WorldMarket processJSON Fail size(162) != originalsize(0), type(18)" }
"Failed to load the information from the Central Market. Please try again later.","Log":"WorldMarket processJSON Fail cant process type : , type(26)" }
"Failed to load the information from the Central Market. Please try again later.","Log":"WorldMarket processJSON Fail size(162) != originalsize(1701978624), type(18)" }
"Failed to load the information from the Central Market. Please try again later.","Log":"WorldMarket processJSON Fail size(162) != originalsize(1701978624), type(18)" }
"Failed to load the information from the Central Market. Please try again later.","Log":"WorldMarket processJSON Fail cant process type : , type(26)" }
"Failed to load the information from the Central Market. Please try again later.","Log":"WorldMarket processJSON Fail cant process type : , type(26)" }
"Failed to load the information from the Central Market. Please try again later.","Log":"WorldMarket processJSON Fail size(162) != originalsize(0), type(18)" }
"Failed to load the information from the Central Market. Please try again later.","Log":"WorldMarket processJSON Fail cant process type : , type(26)" }
"Failed to load the information from the Central Market. Please try again later.","Log":"WorldMarket processJSON Fail size(162) != originalsize(1701978624), type(18)" }
"Failed to load the information from the Central Market. Please try again later.","Log":"WorldMarket processJSON Fail cant process type : , type(26)" }
"Failed to load the information from the Central Market. Please try again later.","Log":"WorldMarket processJSON Fail size(162) != originalsize(1701978624), type(18)" }
"Failed to load the information from the Central Market. Please try again later.","Log":"WorldMarket processJSON Fail cant process type : , type(26)" }
"Failed to load the information from the Central Market. Please try again later.","Log":"WorldMarket processJSON Fail size(162) != originalsize(1701978624), type(18)" }
"Failed to load the information from the Central Market. Please try again later.","Log":"WorldMarket processJSON Fail size(1006) != originalsize(0), type(8)" }
"Failed to load the information from the Central Market. Please try again later.","Log":"WorldMarket processJSON Fail size(162) != originalsize(0), type(18)" }
"Failed to load the information from the Central Market. Please try again later.","Log":"WorldMarket processJSON Fail cant process type : , type(26)" }
"Failed to load the information from the Central Market. Please try again later.","Log":"WorldMarket processJSON Fail size(162) != originalsize(0), type(18)" }
"Failed to load the information from the Central Market. Please try again later.","Log":"WorldMarket processJSON Fail cant process type : , type(26)" }
"Failed to load the information from the Central Market. Please try again later.","Log":"WorldMarket processJSON Fail size(69) != originalsize(0), type(18)" }

"JSON parsing failed. The JSON data is irregular.","Log":"pa_json::parse()" }

I've tried debugging winhttp, which is used to make the calls but haven't seen anything specific yet.

Is there a way to look at the JSON responses directly using a packet sniffer? They might contain more information on the nature of the error. It looks like it's almost always the same error, with 2 extras thrown in there.

Start steam via CLI and add following Launch Option for BDO: PROTON_LOG=1

I've tested BDO for a few Hours and didnt have any crashes with following Specs:

CPU: 7945HX GPU: 4090 Mobile (545.29.06 driver) Distro: Arch Linux DE: KDE Plasma 6 RC 1 Proton: Proton-Cachyos Using x11

Finally, I reproduced the crash:

wine: Call from 00000002C73AC5E5 to unimplemented function win32u.dll.NtGdiDdDDINetDispQueryMiracastDisplayDeviceStatus, aborting
wine: Call from 00000002C73AC5E5 to unimplemented function win32u.dll.NtGdiDdDDINetDispQueryMiracastDisplayDeviceStatus, aborting
wine: Call from 00000002C73AC5E5 to unimplemented function win32u.dll.NtGdiDdDDINetDispQueryMiracastDisplayDeviceStatus, aborting
wine: Call from 00000002C73AC5E5 to unimplemented function win32u.dll.NtGdiDdDDINetDispQueryMiracastDisplayDeviceStatus, aborting
wine: Call from 00000002C73AC5E5 to unimplemented function win32u.dll.NtGdiDdDDINetDispQueryMiracastDisplayDeviceStatus, aborting
wine: Call from 00000002C73AC5E5 to unimplemented function win32u.dll.NtGdiDdDDINetDispQueryMiracastDisplayDeviceStatus, aborting
[string "FromClient_ChatUpdate"]:1: '=' expected near '<eof>'
wine: Call from 00000002C73AC5E5 to unimplemented function win32u.dll.NtGdiDdDDINetDispQueryMiracastDisplayDeviceStatus, aborting
wine: Call from 00000002C73AC5E5 to unimplemented function win32u.dll.NtGdiDdDDINetDispQueryMiracastDisplayDeviceStatus, aborting
[string "FromClient_ChatUpdate"]:1: '=' expected near '<eof>'
wine: Call from 00000002C73AC5E5 to unimplemented function win32u.dll.NtGdiDdDDINetDispQueryMiracastDisplayDeviceStatus, aborting
wine: Call from 00000002C73AC5E5 to unimplemented function win32u.dll.NtGdiDdDDINetDispQueryMiracastDisplayDeviceStatus, aborting
pid 24337 != 24336, skipping destruction (fork without exec?)
Game 582660 created interface STEAMAPPLIST_INTERFACE_VERSION001 / AppList
Game 582660 created interface STEAMAPPS_INTERFACE_VERSION008 / Apps
Game 582660 created interface STEAMHTMLSURFACE_INTERFACE_VERSION_003 / HTMLSurface
Game 582660 created interface STEAMHTTP_INTERFACE_VERSION002 / HTTP
Game 582660 created interface STEAMINVENTORY_INTERFACE_V001 / Inventory
Game 582660 created interface STEAMMUSICREMOTE_INTERFACE_VERSION001 / MusicRemote
Game 582660 created interface STEAMMUSIC_INTERFACE_VERSION001 / Music
Game 582660 created interface STEAMREMOTESTORAGE_INTERFACE_VERSION014 / RemoteStorage
Game 582660 created interface STEAMSCREENSHOTS_INTERFACE_VERSION003 / Screenshots
Game 582660 created interface STEAMUGC_INTERFACE_VERSION009 / UGC
Game 582660 created interface STEAMUNIFIEDMESSAGES_INTERFACE_VERSION001 / UnifiedMessages
Game 582660 created interface STEAMUSERSTATS_INTERFACE_VERSION011 / UserStats
Game 582660 created interface STEAMVIDEO_INTERFACE_V001 / Video
Game 582660 created interface SteamController005 / Controller
Game 582660 created interface SteamFriends015 / Friends
Game 582660 created interface SteamMatchMaking009 / Matchmaking
Game 582660 created interface SteamMatchMakingServers002 / MatchmakingServers
Game 582660 created interface SteamNetworking005 / Networking
Game 582660 created interface SteamUser019 / User
Game 582660 created interface SteamUtils008 / Utils
Game 582660 method call count for IClientNetworking::IsP2PPacketAvailable : 5349
Game 582660 method call count for IClientUtils::RecordSteamInterfaceCreation : 24
Game 582660 method call count for IClientUtils::GetAppID : 26
Game 582660 method call count for IClientUser::GetSteamID : 2
Game 582660 method call count for IClientUser::BLoggedOn : 1
Uploaded AppInterfaceStats to Steam

GLib-GObject-CRITICAL **: 16:22:55.779: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

this person on the forums says:

0b14:fixme:winhttp:set_cookies unhandled attribute L"expires"
0b14:fixme:winhttp:set_cookies unhandled attribute L"HttpOnly"
0b14:fixme:winhttp:set_cookies unhandled attribute L"Secure"

Which I don't see on my log or anywhere. Just throwing that out there in case it's relevant.

I've been trying to debug the Market issue and here is what I know so far:

• I have made some modifications to winhttp.dll source to show POST data response/request
• The game will make a POST request to /Trademarket/GetMyWalletList. It's POST data is something like: {"userNo":"12345","certifiedKey":"","type":"0"}
  The response is not ascii, it seems like possibly it's encrypted. Interestingly the retrieved bytes is the same size as the log complains about:
  winhttp:read_data retrieved 486 bytes (1012/1012)
log: WorldMarket processJSON Fail size(1012) != originalsize(0), type(8)"
• I'm wondering if the process is unable to decrypt the payload properly and that is why it's complaing about invalid json. There are a few crypt errors:

  0280:fixme:cryptasn:CryptDecodeObjectEx Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4
  0280:fixme:cryptasn:CryptDecodeObjectEx Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4
  0504:fixme:bcrypt:BCryptGenerateSymmetricKey ignoring object buffer
  0504:err:bcrypt:BCryptGenerateSymmetricKey no encryption support

• Followup requests to /Trademarket/* seem to have a valid key:
  winhttp:send_request POSTDATA: {"userNo":"12345","certifiedKey":"FFF1CB84-4C12-4922-1ED3-4556138ACB7A","type":"0"}

Maybe this certifiedKey value is created by the first request. That's currently where I'm at. I'll try to debug further, but I'm not sure what else to look into, possibly the bcrypt issues.

@Daktyl198 does the 3rd party still works got it with an error, trying to use it :

@Daktyl198 does the 3rd party still works got it with an error, trying to use it :

It's working perfectly fine for me. Just launched a second ago. Make sure your game client is actually up to date by launching the patcher first and manually check the Paz folder for how many items it has.

welp i ran out of spirit perfumes and my stash is in central market. Is there a way to take them with black desert+ or something?
i already contacted the support and ask them to move the perfumes to my inventory but it has been 2 days and i got no answer.

Replying to https://github.com/ValveSoftware/Proton/issues/3620#issuecomment-1902116652

"Fixme's are for code that is missing to implement functions that exist
in the Win32/Win64 APIs that are partially implemented and need further
work to become fully implemented."

welp we need to wait for wine devs to implement it i guess. I have been messing around with dependencies like 'winhttp, wininet, xna etc etc' aaand nothing yet

Edit: (i don't wanna send notification to people for nothing so im editing this comment)

for the leauncher;
it was giving gl shader errors, just passed 2 env variables (__GL_SHADER_DISK_CACHE 1 - __GL_SHADER_DISK_CACHE_PATH $GAMEDIR ) and seems like the gl shader errors are gone but now im getting this

"[0121/173647:ERROR:network_change_notifier_win.cc(153)] WSALookupServiceBegin failed with: 8
[0121/173648:WARNING:cert_verify_proc_win.cc(108)] Unknown error -2146762482 mapped to net::ERR_FAILED
[0121/173651:WARNING:cert_verify_proc_win.cc(108)] Unknown error -2146762482 mapped to net::ERR_FAILED
[0121/173653:WARNING:cert_verify_proc_win.cc(108)] Unknown error -2146762482 mapped to net::ERR_FAILED
[0121/173654:WARNING:cert_verify_proc_win.cc(108)] Unknown error -2146762482 mapped to net::ERR_FAILED
[0121/173654:WARNING:cert_verify_proc_win.cc(108)] Unknown error -2146762482 mapped to net::ERR_FAILED"

@psychomantium seems I need to accept the terms of service, that's why I'm running into this error.

Not sure if it's possible from the website as I see nothing in the launcher on Linux.

@LexaproDelirium I would like to first investigate the black launcher issue, I'll reach out to wine devs in order to further debug what's going on and hopefully fix that first.

The marketplace will come in second.

Wine devs are focusing on finishing a wayland driver at the moment and probably are squashing some bugs but if we can help it would be better I guess.

Tried a few stuff in an attempt to fix some issue but so far, no significant progress, using wine 8.0.2 and some winetricks (winhttp webio ie8 wininet), I cannot get the launcher to launch, I get either this error :

wine: Call from 7BC2BC10 to unimplemented function urlmon.dll.414, aborting
wine: Unimplemented function urlmon.dll.414 called at address 7BC2BC10 (thread 0418), starting debugger...
04a0:fixme:imm:ImeSetActiveContext (000900AC, 1): stub

Or this error (with no winetricks involved) :

Unhandled exception: page fault on write access to 0x00000000 in 32-bit code (0x10644ca0).
03c4:fixme:dbghelp:elf_search_auxv can't find symbol in module
Register dump:
 CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b
 EIP:10644ca0 ESP:0022e088 EBP:0022e0bc EFLAGS:00010246(  R- --  I  Z- -P- )
 EAX:00000000 EBX:0022e2bc ECX:3fa04000 EDX:3fe10380
 ESI:3e902980 EDI:3e8aa9a8
Stack dump:
0x0022e088:  0022e2b8 3e809530 3e809530 1051b765
0x0022e098:  0022e298 3e809530 00000000 10986637
0x0022e0a8:  00000000 3ff00000 00000000 3eac41c0
0x0022e0b8:  00000000 0022e0d8 1051bd72 0022e2b8
0x0022e0c8:  3e809530 0022e298 3eac41c0 00000000
0x0022e0d8:  0022e0f8 1097d2cd 0022e0f0 0022e2b8
Backtrace:
=>0 0x10644ca0 in libcef (+0x644ca0) (0x0022e0bc)
  1 0x1051bd72 in libcef (+0x51bd72) (0x0022e0d8)
  2 0x1097d2cd in libcef (+0x97d2cd) (0x0022e0f8)
  3 0x1095f3b2 in libcef (+0x95f3b2) (0x0022e11c)
  4 0x104bc3fa in libcef (+0x4bc3fa) (0x0022e14c)
  5 0x104ed654 in libcef (+0x4ed654) (0x0022e184)
  6 0x104ecc0f in libcef (+0x4ecc0f) (0x0022e1b0)
  7 0x104ebcde in libcef (+0x4ebcde) (0x0022e238)
  8 0x104ea146 in libcef (+0x4ea146) (0x0022e990)
  9 0x103e4897 in libcef (+0x3e4897) (0x0022e9b4)
  10 0x1032636b in libcef (+0x32636b) (0x0022e9d4)
  11 0x1039a20b in libcef (+0x39a20b) (0x0022e9f0)
  12 0x1039a1dd in libcef (+0x39a1dd) (0x0022ea34)
  13 0x103e1525 in libcef (+0x3e1525) (0x0022eab4)
  14 0x10368b80 in libcef (+0x368b80) (0x0022ead4)
  15 0x10325e56 in libcef (+0x325e56) (0x0022eb0c)
  16 0x10368b80 in libcef (+0x368b80) (0x0022eb2c)
  17 0x10325e56 in libcef (+0x325e56) (0x0022eb64)
  18 0x10368b80 in libcef (+0x368b80) (0x0022eb84)
  19 0x10325e56 in libcef (+0x325e56) (0x0022ebbc)
  20 0x10368b80 in libcef (+0x368b80) (0x0022ebdc)
  21 0x10325e56 in libcef (+0x325e56) (0x0022ec14)
  22 0x10368b80 in libcef (+0x368b80) (0x0022ec34)
  23 0x10325e56 in libcef (+0x325e56) (0x0022ec6c)
  24 0x10368b80 in libcef (+0x368b80) (0x0022ec8c)
  25 0x10325e56 in libcef (+0x325e56) (0x0022ecc4)
  26 0x10368b80 in libcef (+0x368b80) (0x0022ece4)
  27 0x10325e56 in libcef (+0x325e56) (0x0022ed1c)
  28 0x10368b80 in libcef (+0x368b80) (0x0022ed3c)
  29 0x10325e56 in libcef (+0x325e56) (0x0022ed74)
  30 0x10368b80 in libcef (+0x368b80) (0x0022ed94)
  31 0x10325e56 in libcef (+0x325e56) (0x0022edcc)
  32 0x10368b80 in libcef (+0x368b80) (0x0022edec)
  33 0x10325e56 in libcef (+0x325e56) (0x0022ee24)
  34 0x103267e0 in libcef (+0x3267e0) (0x0022ee5c)
  35 0x1032654f in libcef (+0x32654f) (0x0022ee88)
  36 0x10340902 in libcef (+0x340902) (0x0022eef4)
  37 0x1034061a in libcef (+0x34061a) (0x0022ef44)
  38 0x105795ad in libcef (+0x5795ad) (0x0022ef70)
  39 0x10578f2a in libcef (+0x578f2a) (0x0022efa8)
  40 0x1054bc9c in libcef (+0x54bc9c) (0x0022efdc)
  41 0x11147b8f in libcef (+0x1147b8f) (0x0022efe8)
  42 0x11132b26 in libcef (+0x1132b26) (0x0022f01c)
  43 0x1152a357 in libcef (+0x152a357) (0x0022f19c)
  44 0x10dbb0cf in libcef (+0xdbb0cf) (0x0022f1bc)
  45 0x100bfd54 in libcef (+0xbfd54) (0x0022f230)
  46 0x115e8a9e in libcef (+0x15e8a9e) (0x0022f2dc)
  47 0x115e858f in libcef (+0x15e858f) (0x0022f3e4)
  48 0x1159158c in libcef (+0x159158c) (0x0022f3f8)
  49 0x1145e02a in libcef (+0x145e02a) (0x0022f40c)
  50 0x100bfd54 in libcef (+0xbfd54) (0x0022f480)
  51 0x1007d9e5 in libcef (+0x7d9e5) (0x0022f4ec)
  52 0x1007e388 in libcef (+0x7e388) (0x0022f620)
  53 0x100bc8d6 in libcef (+0xbc8d6) (0x0022f64c)
  54 0x1007d775 in libcef (+0x7d775) (0x0022f670)
  55 0x10099a29 in libcef (+0x99a29) (0x0022f698)
  56 0x1007d022 in libcef (+0x7d022) (0x0022f6c4)
  57 0x1212fb3f in libcef (+0x212fb3f) (0x0022f7d4)
  58 0x11a3ba5a in libcef (+0x1a3ba5a) (0x0022f7e8)
  59 0x11a3b9b8 in libcef (+0x1a3b9b8) (0x0022f834)
  60 0x11a3b375 in libcef (+0x1a3b375) (0x0022f844)
  61 0x10fafdbd in libcef (+0xfafdbd) (0x0022f920)
  62 0x10f8da79 in libcef (+0xf8da79) (0x0022f944)
  63 0x004bd2f7 in blackdesertpatcher32.pae (+0xbd2f7) (0x0022f960)
  64 0x00442649 in blackdesertpatcher32.pae (+0x42649) (0x0022fed4)
  65 0x00442ded in blackdesertpatcher32.pae (+0x42ded) (0x0022fee4)
  66 0x005175be in blackdesertpatcher32.pae (+0x1175be) (0x0022ff30)
  67 0x7b629530 in kernel32 (+0x29530) (0x0022ff48)
  68 0x7bc5cd17 in ntdll (+0x5cd17) (0x0022ff5c)
  69 0x7bc5d538 in ntdll (+0x5d538) (0x0022ffec)
0x10644ca0 libcef+0x644ca0: movb        %al,0x00000000
Modules:
Module  Address                 Debug info      Name (124 modules)
PE      00120000-00122000       Deferred        usp10
PE      00390000-003a5000       Deferred        vcruntime140
PE      003b0000-003f5000       Deferred        dxgi
PE      00400000-0079d000       Export          blackdesertpatcher32.pae
PE      00a60000-00ae2000       Deferred        gdiplus
PE      00af0000-00b87000       Deferred        expapply
PE      10000000-12e2d000       Export          libcef
PE      3b400000-3b439000       Deferred        steam_api
PE      3dfd0000-3e1bd000       Deferred        iertutil
PE      61c40000-61c4c000       Deferred        userenv
PE      62500000-6261c000       Deferred        oleaut32
PE      62c40000-62c66000       Deferred        concrt140
PE      63580000-635b0000       Deferred        oleacc
PE      63900000-63909000       Deferred        psapi
PE      63c00000-63c4c000       Deferred        winhttp
PE      64180000-641a9000       Deferred        winspool
PE      643c0000-643e7000       Deferred        ws2_32
PE      646c0000-646f3000       Deferred        iphlpapi
PE      64a80000-64ab9000       Deferred        win32u
PE      65480000-6550a000       Deferred        rpcrt4
PE      65680000-6571e000       Deferred        msvcrt
PE      65e80000-65ef6000       Deferred        dwrite
PE      66080000-6609a000       Deferred        msacm32
PE      66380000-664a2000       Deferred        ole32
PE      66640000-6664c000       Deferred        version
PE      667c0000-667d9000       Deferred        shcore
PE      66fc0000-66fd3000       Deferred        compstui
PE      67500000-67519000       Deferred        imm32
PE      67bc0000-67d05000       Deferred        comctl32
PE      68280000-68289000       Deferred        jsproxy
PE      684c0000-6851b000       Deferred        combase
PE      68880000-68a20000       Deferred        user32
PE      68cc0000-68d4a000       Deferred        crypt32
PE      69040000-690ae000       Deferred        comdlg32
PE      69840000-6987f000       Deferred        advapi32
PE      6a600000-6a60c000       Deferred        kerberos
PE      6a680000-6a68c000       Deferred        wtsapi32
PE      6aac0000-6ab86000       Deferred        ucrtbase
PE      6bb40000-6bb6e000       Deferred        winex11
PE      6bbc0000-6bbe9000       Deferred        sechost
PE      6c980000-6c9ed000       Deferred        msvcp140
PE      6cc80000-6cee3000       Deferred        wined3d
PE      6d480000-6d491000       Deferred        secur32
PE      6d9c0000-6da2e000       Deferred        d3d11
PE      6da80000-6dafb000       Deferred        gdi32
PE      6e200000-6e215000       Deferred        bcrypt
PE      6ecc0000-6ecd5000       Deferred        dnsapi
PE      6f1c0000-6f1f3000       Deferred        d3d9
PE      6f240000-6f290000       Deferred        winmm
PE      6f6c0000-6f6ca000       Deferred        nsi
PE      70000000-70072000       Deferred        dbghelp
PE      700c0000-700cb000       Deferred        dhcpcsvc
PE      70d80000-70db5000       Deferred        uxtheme
PE      712c0000-712d7000       Deferred        mpr
PE      71400000-71cb9000       Deferred        shell32
PE      77f60000-77fd6000       Deferred        shlwapi
PE      78130000-78265000       Deferred        urlmon
PE      7a800000-7a91f000       Deferred        opengl32
PE      7b000000-7b12c000       Deferred        kernelbase
PE      7b600000-7b653000       Export          kernel32
PE      7bc00000-7bc9d000       Export          ntdll
ELF     7d000000-7d006000       Deferred        
ELF     7d2c5000-7d321000       Deferred        libgssapi_krb5.so.2
ELF     7d321000-7d400000       Deferred        libkrb5.so.3
ELF     7d415000-7d41c000       Deferred        crypt32.so
ELF     7d41c000-7d428000       Deferred        bcrypt.so
ELF     7d428000-7d43a000       Deferred        libresolv.so.2
ELF     7d43a000-7d4dd000       Deferred        opengl32.so
ELF     7d4dd000-7d602000       Deferred        libsystemd.so.0
ELF     7d602000-7d691000       Deferred        libgmp.so.10
ELF     7d691000-7d849000       Deferred        libunistring.so.5
ELF     7d849000-7da00000       Deferred        libp11-kit.so.0
ELF     7da00000-7dc44000       Deferred        libgnutls.so.30
ELF     7dc45000-7dc4b000       Deferred        dnsapi.so
ELF     7dc4b000-7dc52000       Deferred        libkeyutils.so.1
ELF     7dc52000-7dc62000       Deferred        libkrb5support.so.0
ELF     7dc62000-7dc68000       Deferred        libcom_err.so.3
ELF     7dc68000-7dc98000       Deferred        libk5crypto.so.3
ELF     7dc98000-7dca1000       Deferred        kerberos.so
ELF     7dca1000-7dcac000       Deferred        secur32.so
ELF     7dcac000-7dcb3000       Deferred        ws2_32.so
ELF     7dcb3000-7dcc0000       Deferred        libcap.so.2
ELF     7dcc0000-7dcd0000       Deferred        libffi.so.8
ELF     7dcd0000-7dd1b000       Deferred        libhogweed.so.6
ELF     7dd1b000-7dd70000       Deferred        libnettle.so.8
ELF     7dd70000-7dd86000       Deferred        libtasn1.so.6
ELF     7dd86000-7ddb7000       Deferred        libidn2.so.0
ELF     7ddb7000-7ddbc000       Deferred        libdl.so.2
ELF     7ddbc000-7de1e000       Deferred        libdbus-1.so.3
ELF     7de1e000-7de23000       Deferred        libssp.so.0
ELF     7de23000-7de39000       Deferred        libavahi-client.so.3
ELF     7de39000-7de49000       Deferred        libavahi-common.so.3
ELF     7de49000-7dec8000       Deferred        libcups.so.2
ELF     7dec8000-7decf000       Deferred        winspool.so
ELF     7e015000-7e01e000       Deferred        libxfixes.so.3
ELF     7e01e000-7e02b000       Deferred        libxcursor.so.1
ELF     7e079000-7e1cf000       Deferred        libx11.so.6
ELF     7e2f7000-7e30c000       Deferred        libxi.so.6
ELF     7e30c000-7e311000       Deferred        libxcomposite.so.1
ELF     7e311000-7e320000       Deferred        libxrandr.so.2
ELF     7e320000-7e32e000       Deferred        libxrender.so.1
ELF     7e32e000-7e336000       Deferred        libxxf86vm.so.1
ELF     7e336000-7e33b000       Deferred        libxinerama.so.1
ELF     7e33b000-7e342000       Deferred        libxdmcp.so.6
ELF     7e342000-7e371000       Deferred        libxcb.so.1
ELF     7e371000-7e387000       Deferred        libxext.so.6
ELF     7e387000-7e411000       Deferred        winex11.so
ELF     7e585000-7e5b1000       Deferred        libexpat.so.1
ELF     7e5b1000-7e605000       Deferred        libfontconfig.so.1
ELF     7e605000-7e628000       Deferred        libbrotlicommon.so.1
ELF     7e628000-7e637000       Deferred        libbrotlidec.so.1
ELF     7e637000-7e70a000       Deferred        libfreetype.so.6
ELF     7e70a000-7e810000       Deferred        libm.so.6
ELF     7e810000-7e987000       Deferred        win32u.so
ELF     7ee00000-7ee05000       Deferred        libxau.so.6
ELF     7ee09000-7ee49000       Deferred        libpng16.so.16
ELF     7ee49000-7ee5b000       Deferred        libbz2.so.1
ELF     7ee5b000-7ee77000       Deferred        libz.so.1
ELF     7ee77000-7f000000       Dwarf           libwine.so.1
ELF     f7c00000-f7e32000       Deferred        libc.so.6
ELF     f7e69000-f7e70000       Deferred        dwrite.so
ELF     f7e72000-f7e77000       Deferred        libpthread.so.0
ELF     f7e79000-f7f2b000       Deferred        ntdll.so
ELF     f7f31000-f7f66000       Deferred        ld-linux.so.2

Still trying to understand how proton manages to start the launcher but full black.

Some kind of embedded CEF (Chromium Embedded Framework is being used to load the launcher) and it should load this URL : https://launcher.naeu.playblackdesert.com/en-us

Replying to https://github.com/ValveSoftware/Proton/issues/3620#issuecomment-1902630883

Sorry, but I already fixed it. Will start looking at marketplace

Replying to https://github.com/ValveSoftware/Proton/issues/3620#issuecomment-1902683369

Native wininet doesn't work with wine

Sorry, but I already fixed it. Will start looking at marketplace

Please explain further than just "I already fixed it", to prevent users in this thread from re-doing the same work. And if you can provide how you fixed it, so that they may move on to helping with the marketplace.

Replying to https://github.com/ValveSoftware/Proton/issues/3620#issuecomment-1902686806

sorry I was on mobile, providing links: https://gitlab.winehq.org/etaash.mathamsetty/wine/-/commit/08d8187c2acb0e43b5ca505a95a819cc3fdb55d7
screenshot:

Replying to https://github.com/ValveSoftware/Proton/issues/3620#issuecomment-1902688329

wdym blank window
better screenshot after it loaded:

Please edit your comments rather than commenting several times. It spams emails to those watching the issue.

Based on the code he changed, it seems as if the rendering code was being passed a bad drawing surface handler, and not properly erroring out. Thus, black screen (as all of the draw calls failed).

Please edit your comments rather than commenting several times. It spams emails to those watching the issue.

Based on the code he changed, it seems as if the rendering code was being passed a bad drawing surface handler, and not properly erroring out. Thus, black screen (as all of the draw calls failed).

my github is bugging out, blame github

When will your fix @Etaash-mathamsetty, be available in Wine 9.0.0 ? We should probably compile wine from git in order to have it on our side. But it's not available in Proton Experimental.

Somebody should submit the patch to Proton-GE and Proton specifically, as well as wine. If you just submit it to wine, it'll take ages to work it's way into Proton Experimental.

When will your fix @Etaash-mathamsetty, be available in Wine 9.0.0 ? We should probably compile wine from git in order to have it on our side. But it's not available in Proton Experimental.

it's more of a hack right now, i need to test the behavior on windows and see if it does the same thing.

@Daktyl198 @Etaash-mathamsetty already tried to submit one patch (not the whole fix) but it was refused and he was told to put it upstream : https://github.com/ValveSoftware/wine/pull/217

@Daktyl198 @Etaash-mathamsetty already tried to submit it as a patch but it was refused and he was told to put it upstream : ValveSoftware/wine#217

that's not the same patch

As mentioned, not the correct patch. Valve might not take it the correct patch even, but the Proton-GE dev might. He includes much more "hacky" fixes for specific games, which might help us run it while a proper fix is worked out.

Yes you are both correct, but the fix is 2 commits (only the last one is necessary I believe) :

• one that checks for the null ctx : https://gitlab.winehq.org/etaash.mathamsetty/wine/-/commit/3ce1ff2ceb8a3b1b454700327b2803e90b619a46
• one that handles an error : https://gitlab.winehq.org/etaash.mathamsetty/wine/-/commit/08d8187c2acb0e43b5ca505a95a819cc3fdb55d7

I'd prefer to have both even if they're hacky, it's better to have something that works "hacky" than something broken, I'd say.

Finally, I reproduced the crash:

wine: Call from 00000002C73AC5E5 to unimplemented function win32u.dll.NtGdiDdDDINetDispQueryMiracastDisplayDeviceStatus, aborting

GLib-GObject-CRITICAL **: 16:22:55.779: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

It appears that the game behaves differently based on the screen setup. When playing on the Steam Deck's screen, everything seems to work fine. However, upon connecting an external screen using a dock, issues arise. It's an interesting observation that might point to a specific compatibility or configuration challenge. If anyone has insights or suggestions on optimizing Black Desert for an external screen setup, I'd love to hear them!

anyone reached to ge yet? i don't wanna ping him again for the same thing

anyone reached to ge yet? i don't wanna ping him again for the same thing

Me and GE are in touch, he knows

I see this here https://github.com/GloriousEggroll/proton-ge-custom/commit/7d7e959a416ede062d29038930871633aa1bade8

anyone reached to ge yet? i don't wanna ping him again for the same thing

Me and GE are in touch, he knows

Thanks for the quick fix. I wanted to add that the launcher can still crash under certain circumstances. If you login and then click the gear icon at the top right, then apply or close that window, it freezes the launcher.

anyone reached to ge yet? i don't wanna ping him again for the same thing

Me and GE are in touch, he knows

Thanks for the quick fix. I wanted to add that the launcher can still crash under certain circumstances. If you login and then click the gear icon at the top right, then apply or close that window, it freezes the launcher.

I have a fix for that as well, but my laptop is really slow at compiling code. I finally got my pc up and running and I'll test on it once my school is done. Poor thing's CPU failed, and I'll have to return the tester CPU that's in it right now :(

proper fix is here: https://gitlab.winehq.org/wine/wine/-/merge_requests/4912 (made by valve/codeweavers, not me) and it fixes the issues with my patch, such as crashing settings :)

The launcher should hopefully work in just updated Proton Experimental ([bleeding-edge] Beta branch).

The launcher should hopefully work in just updated Proton Experimental ([bleeding-edge] Beta branch).

it updates that quick? damn

Has anyone made any progress on the market? I'm not sure where to look next, outside of the winhttp data. If anyone has any other clues on where to look(other dlls to trace etc), please share.

Has anyone made any progress on the market? I'm not sure where to look next, outside of the winhttp data. If anyone has any other clues on where to look(other dlls to trace etc), please share.

I'm not sure if this is useless info or not, but BDO uses coherent_ui.exe or at least used it for all kind of interface/web functions, not sure if this can be helpful to some people here who knows more. Not sure if this can be relevant?

• The game will make a POST request to /Trademarket/GetMyWalletList. It's POST data is something like: {"userNo":"12345","certifiedKey":"","type":"0"}
  The response is not ascii, it seems like possibly it's encrypted. Interestingly the retrieved bytes is the same size as the log complains about:
  winhttp:read_data retrieved 486 bytes (1012/1012)
log: WorldMarket processJSON Fail size(1012) != originalsize(0), type(8)"

Maybe a dumb question: Could it also be that the response is compressed? (gzip?)

The reason why I had this idea:
I checked with my browser's devtools (F12) what the web central market does (usually you would use the same REST endpoints...).

It calls a /Home/GetMyWalletList endpoint (and a few others).
All JSON responses are gzip compressed.

If the decompression fails for some reason with wine, it may explain the "encryption".
But just a idea.

Replying to https://github.com/ValveSoftware/Proton/issues/3620#issuecomment-1906822779

Yea, it's binary. The return header is: winhttp:process_header L"Content-Type": L"application/octet-stream" 0x20000000

I am looking into this and it is basically clear what issue is about (unrelated to http conversation per se). I hope to fix it rather soon in Proton.

Market should work with the just updated Experimental ([bleeding-edge] branch) now, or at least I can open the market and it shows some stuff in it.

Market should work with the just updated Experimental ([bleeding-edge] branch) now, or at least I can open the market and it shows some stuff in it.

Confirming this is now functioning properly on Proton Experimental. Marketplace and Warehouse both fully functional on Steam Deck SteamOS with Proton Experimental. Thank you so very much!

Black Spirit's Adventure appears to still not work but this is substantially less impactful and less urgent. Thought it was worth noting, however, that the BSA window is blank.

Thanks again gofman, returning to BDO because of you. Much appreciated.

Black Spirit's Adventure appears to still not work but this is substantially less impactful and less urgent. Thought it was worth noting, however, that the BSA window is blank.

If you can describe what is Black Spirit's Adventure and BSA window, and how exactly to get there in a quickest possible way, for people who don't know how to play the game and know nothing / don't have a character, that will probably be helpful.

Black Spirit's Adventure appears to still not work but this is substantially less impactful and less urgent. Thought it was worth noting, however, that the BSA window is blank.

If you can describe what is Black Spirit's Adventure and BSA window, and how exactly to get there in a quickest possible way, for people who don't play the game and know nothing / don't have a character, that will probably be helpful.

Happy to. It's a daily roulette sort of mechanic, very typical of BDO. It's a sort of daily login reward. Certainly not game breaking.

I am not sure if you can access this without at least having a character. However, once in-game, there are a couple of ways to access it. I will try to attach some screenshots showing exactly how. I had to xfer these from Steam Deck to PC so let me know if the resolution is bad and I can try again:

edit to include: image of blank BSA window:

Thanks for your work on the launcher and market.

Another window that doesn't work is the "Setting Archive" window in settings.

You're able to upload your settings and custom ui to the cloud, and download them. It shows a blank screen when you click it.

What it usually looks like

Oddly enough the black spirit adventure and other web based windows were working for me previously. Now they are all blank as above. You can however still click on the buttons, similar to the issues the launcher had. Also, the market seems to be working now, thanks for the quick fix!

Have you tried popping the black spirit adventure window out into its own floating system window using the paper-looking icon on its title bar? I know that used to fix rendering issues for me on Windows.

Floating the window didn't help. I did however recompile wine-ge-custom 8-25 with the two patches for launcher/market and black spirit adventure works fine. So this must be something specific to proton experimental. There also seems to be some other differences with experimental(not surprising I guess), but loading into the game is noticeably slower.

@aveenhof @vevota Thanks for the info. Those windows should hopefully work in the just updated Proton Experimental ([bleeding-edge] branch).

@aveenhof @vevota Thanks for the info. Those windows should hopefully work in the just updated Proton Experimental ([bleeding-edge] branch).

Confirming the window is now rendering as expected on Proton Experimental through Steam Deck (SteamOS, Steam version of BDO).

Once again, thank you very much @gofman for the quick fix. I'll let others pop in if they are experiencing any further issues. I can't believe this was resolved so quickly after BDO becoming workable with Linux. You have my sincere gratitude.

edit to add: any Steam Deck users experiencing crashes, enter "settings" on the game start screen before server selection and disable "low power mode". This automatically re-enables on every launch, but disabling it has prevented me from crashing. Seems like something Proton cannot address but has fixed the crashing issue for me.

Can you tell me how to fix the game self-closing 1-2 minutes after startup? Tried proton experimental and GE-8.25 - does not help. Version of the game is not steam, for ru region.

Can you tell me how to fix the game self-closing 1-2 minutes after startup? Tried proton experimental and GE-8.25 - does not help. Version of the game is not steam, for ru region.

Steam version and Standalone NA version are working fine here. My guess is RU region maybe has some other kind of anticheat that's not supported. Only the steam version is within scope of support here.

Can you tell me how to fix the game self-closing 1-2 minutes after startup? Tried proton experimental and GE-8.25 - does not help. Version of the game is not steam, for ru region.

Is this a home PC or a Steam Deck? If a PC, what Distro are you running, and If not via Steam, how was it installed? Does running with a Steam-based installation work?

The more info you can provide, the more can be done to efficiently identify a problem, or otherwise point you to a place thay can. As stated above, this thread is focused on running the game via Steam install.

Can you tell me how to fix the game self-closing 1-2 minutes after startup? Tried proton experimental and GE-8.25 - does not help. Version of the game is not steam, for ru region.

Is this a home PC or a Steam Deck? If a PC, what Distro are you running, and If not via Steam, how was it installed? Does running with a Steam-based installation work?

The more info you can provide, the more can be done to efficiently identify a problem, or otherwise point you to a place thay can. As stated above, this thread is focused on running the game via Steam install.

I rolled back from the beta version to a stable steam os, also disabled tearing, dynamic shading and scaling mode (all parameters are selected through the three-dot button) - the problem seems to have gone, just so out of the game does not throw out.

The game was installed on pc, then transferred to steam deck via file zilla.
I'm not really interested in the steam version because I need a different account for the game (not the one in steam).

Can you tell me how to fix the game self-closing 1-2 minutes after startup? Tried proton experimental and GE-8.25 - does not help. Version of the game is not steam, for ru region.

Steam version and Standalone NA version are working fine here. My guess is RU region maybe has some other kind of anticheat that's not supported. Only the steam version is within scope of support here.

I saw the issue as well previously, NA Steam Deck Steam install. I believe I was able to get it fixed by lowering all graphics settings, disabling all tearing / shading settings, turning off lower power option and fps limiting. In the few seconds before it crashed it ran beautifully so I am not sure why what I did fixed the issue, but it seems to have solved it for me.

Granted I have yet to spend an extended period in-game so I may have gotten lucky. Just calling out that myself and others did see it on NA as well so it is not Russian anti cheat related.

Happy to assist if there's anything I can do to help.

Replying to https://github.com/ValveSoftware/Proton/issues/3620#issuecomment-1908869068

The game threw out again, but after 5-10 minutes of being in the game, now I will try to lower all the graphics settings to the lowest. thanks for the advice.

Replying to https://github.com/ValveSoftware/Proton/issues/3620#issuecomment-1908871491

Of course. I also noticed settings are reverted / not saved on relaunch. So for now you will need to adjust these settings on the start screen every time you enter the game.

Also running into this issue. Game crashes after 3-5 minutes. Setting all graphics to low and turning off the lower power option. I'm currently going through the tutorial, so I'm not sure if this is relevant to regular gameplay, or if it's caused by any scripts that run during the tutorial.

Trying out standalone NA client on Arch with nvidia proprietary drivers and bleeding edge proton..marketplace works, black spirits adventure and setting archive are blank screens. Not turning off low power mode in settings before character select it's a guaranteed crash after choosing character. No issue with launcher.

Trying out standalone NA client on Arch with nvidia proprietary drivers and bleeding edge proton..marketplace works, black spirits adventure and setting archive are blank screens. Not turning off low power mode in settings before character select it's a guaranteed crash after choosing character. No issue with launcher.

For the standalone NA/EU client, force proton to use the specific patch for the game with the launch command SteamGameId=582660 %command%

Thanks, works now

On January 25, 2024 12:11:42 p.m. EST, Loanne LUCOTTE @.***> wrote:

Trying out standalone NA client on Arch with nvidia proprietary drivers and bleeding edge proton..marketplace works, black spirits adventure and setting archive are blank screens. Not turning off low power mode in settings before character select it's a guaranteed crash after choosing character. No issue with launcher.

For the standalone NA/EU client, force proton to use the specific patch for the game with the launch command SteamGameId=582660 %command%

--
Reply to this email directly or view it on GitHub:
https://github.com/ValveSoftware/Proton/issues/3620#issuecomment-1910638560
You are receiving this because you commented.

Message ID: @.***>

I was mistaken before -- was just getting lucky. Game is crashing constantly on Steam Deck and cannot seem to find any workaround in settings.

Sometimes I can play for a few minutes, sometimes it crashes instantly. Never in-game more than 10-20 minutes or so before a crash.

Not sure what could be causing but happy to provide any additional info that might be helpful. TIA for anyone who is aware of a workaround/resolution!

I can confirm constant crashes on steam deck, sometimes it happens just when ideling ingame, often times it triggers on ingame settings changed

I can confirm constant crashes on steam deck, sometimes it happens just when ideling ingame, often times it triggers on ingame settings changed

I had to install another linux distro in order to play, with another distro works perfect

I can confirm constant crashes on steam deck, sometimes it happens just when ideling ingame, often times it triggers on ingame settings changed

I had to install another linux distro in order to play, with another distro works perfect

Is that on the deck or PC? can you list the steps you took?

Are you all compiling Proton Experimental manually? I tried hopping into my Arch partition for a bit to mess around and I still had the black launcher issue. I removed and re-downloaded Experimental and still no luck. I feel like I'm missing something.

Are you all compiling Proton Experimental manually? I tried hopping into my Arch partition for a bit to mess around and I still had the black launcher issue. I removed and re-downloaded Experimental and still no luck. I feel like I'm missing something.

In your library, rightclick proton experimental and in betas tab change to bleeding edge

In your library, rightclick proton experimental and in betas tab change to bleeding edge

That's what I assumed, but right-clicking proton experimental and clicking "properties" doesn't do anything. It doesn't bring up a properties window. The window shows up for normal games just fine. I'll figure it out now that I know though. It's unrelated to this bug.

Sorry for the beginner question, first time for me swapping to linux. If i install BDO using lutris, how would i apply this patch? Would I need to manually compile proton/wine first?

Probably should mention I am on Ubuntu

Sorry for the beginner question, first time for me swapping to linux. If i install BDO using lutris, how would i apply this patch? Would I need to manually compile proton/wine first?

Probably should mention I am on Ubuntu

Hi, i supposed you’re playing bdo on the launcher and not on steam if you’re asking this. I’ve found an easy way to play bdo on the launcher without having to compile wine but you’ll need steam and lutris. Here’s how i did.

1 - Launch Lutris and click on the little + at the top left, search for black desert launcher and install it ( i reccommand using wine-ge-8-25 for the installation process )
2 - Once the game is installed you should see that if you try to launch it with lutris it will launch a black launcher just close it and close lutris
3 - Now you want to go to steam and select add a non steam game you then click on browse and you search for you blackdesertlauncher.exe
4 - once this is done you right click on you jewly added game select properties and in compatibility you select proton experimental
5 - you should see that now steam is downloading proton experimental once it’s done search for it on your steam librairie and right click on it then go on the beta tab and search for bleeding edge …
6 - proton expérimental should be updating by now and once it’s done you can freely play black desert online

I hope it works for you and i hope you’ll be able to enjoy black desert with all of us
By the way since i’m commenting i would like to thank everyone here who helped in any way making bdo compatible in Linux

I can confirm that the game runs great (now that I figured out the Experimental thing). Probably better than on Windows, tbh. However there is still an issue, which is that minimizing the game to system tray works, but bringing it back does not. Clicking on the systray icon does nothing.

This may be a Gnome + extension specific issue. I normally run KDE or Sway but am trying out Gnome currently. Can anybody else confirm?

I can confirm that the game runs great (now that I figured out the Experimental thing). Probably better than on Windows, tbh. However there is still an issue, which is that minimizing the game to system tray works, but bringing it back does not. Clicking on the systray icon does nothing.

This may be a Gnome + extension specific issue. I normally run KDE or Sway but am trying out Gnome currently. Can anybody else confirm?

In your settings for the tray extension disable legacy icons. This will minimize the game to the wine tray.

My experiences so far (playing like an hour today):
It works fine, FPS is similar to Windows, but less "micro stuttering" (when I open a menu for example).

I experienced the following issues so far (which I could resolve, so it might help others):

• when you don't have a vulkan 1.3 capable driver, the launcher starts, but the game crashes right after the "Wellbia" splash screen (you can see the problem in proton log if you turn it on). Reason for me was that I was still on Debian buster, an upgrade to bookworm resolved this.
• I had to disable "low power mode", too. Low power mode also led to random crashes on Windows for me, so it probably is not purely a wine issue.
• even without low power mode, the first start crashed. Afterwards it worked fine, however.
• when the game is set to "full screen window", I have a black bar on top of the screen (probably for the title bar) and blurry fonts. Setting the game to "full screen" resolved both issues, fonts now look the same as on Windows.

After all: A big thanks to everyone who made this possible that quickly!

Replying to https://github.com/ValveSoftware/Proton/issues/3620#issuecomment-1913082784

Thank you very much for this. It worked great. Also thank you to everyone who worked on this. You guys are amazing wizards with how fast you got this fixed/supported.

My installation steps:

• downloaded .deb from https://store.steampowered.com/about/ and installed it (with dpkg -i)
• switched to steam beta client (not sure if needed, was hoping that a working proton version comes with it)
• installed latest proton GE with instructions from https://github.com/GloriousEggroll/proton-ge-custom?tab=readme-ov-file#native
• added the black desert installer as a non-steam game in steam
  -- set the downloaded proton version for the bdo installer (GE Proton 8-28), then went through the installation
• added the black desert launcher from the install location as a non-steam game in steam
  -- set the downloaded proton version for the bdo launcher (GE Proton 8-28)

Where I noticed problems:

• Small performance issues (expected). Slightly lower average fps than on windows, larger but rare frame drops when casting specific skills
• Logging in through the launcher with a Google account throws an error to install the .net framework. Anyone knows how to do that?
• The black desert adventure game does not open, market works normally
• Game does not open from tray after being minimized. Using the Ubuntu Unity Desktop in my case.
• Resizing the game window is not possible. Once I managed to pull the game during startup to an edge of the screen and the window did resize on accident. Had to restart to correct that. No biggy.

I can confirm constant crashes on steam deck, sometimes it happens just when ideling ingame, often times it triggers on ingame settings changed

I had to install another linux distro in order to play, with another distro works perfect

Can you advise on how you did this? This workaround requires removing SteamOS, correct?

Somehow I played for hours with no crashes yesterday. Now back to crashing every 2 minutes. Cannot figure out a workaround.

Replying to https://github.com/ValveSoftware/Proton/issues/3620#issuecomment-1916028059

When I had SteamOS happens the same, sometimes I could play for hours and sometimes it crashes every few minutes idk what it can be... I installed EndeavourOS removing SteamOS idk if you can do a dual boot, the steam deck is like a normal computer

@dschoerk You're missing the launch parameter Ezyrath(sp?) said needed for non-steam version, your issues should go away after that.

On January 29, 2024 1:23:58 p.m. EST, "Dominik Schörkhuber" @.***> wrote:

My installation steps:

• downloaded .deb from https://store.steampowered.com/about/ and installed it (with dpkg -i)
• switched to steam beta client (not sure if needed, was hoping that a working proton version comes with it)
• installed latest proton GE with instructions from https://github.com/GloriousEggroll/proton-ge-custom?tab=readme-ov-file#native
• added the black desert installer as a non-steam game in steam and went through the installation
• added the black desert launcher from the install location as a non-steam game in steam
• set the downloaded proton version for the bdo launcher (GE Proton 8-28)

Where I noticed problems:

• Small performance issues (expected). Slightly lower average fps than on windows, larger but rare frame drops when casting specific skills
• Logging in through the launcher with a Google account throws an error to install the .net framework. Anyone knows how to do that?
• The black desert adventure game does not open, market works normally
• Game does not open from tray after being minimized. Using the Ubuntu Unity Desktop in my case.
• Resizing the game window is not possible. Once I managed to pull the game during startup to an edge of the screen and the window did resize on accident. Had to restart to correct that. No biggy.

--
Reply to this email directly or view it on GitHub:
https://github.com/ValveSoftware/Proton/issues/3620#issuecomment-1915315313
You are receiving this because you commented.

Message ID: @.***>

Replying to https://github.com/ValveSoftware/Proton/issues/3620#issuecomment-1915315313

I don't know if GE Proton 8-28 have build with the latest patch for the game.
Test with the launch command SteamGameId=582660 %command%.
If not work use Proton Experimental [bleeding-edge] with the same command

The crashes on Deck / SteamOS during loading into game or soon after should hopefully be fixed in the just updated Proton Experimental ([bleeding-edge] branch). A bit better fix to SteamOS is to follow.

The crashes on Deck / SteamOS during loading into game or soon after should hopefully be fixed in the just updated Proton Experimental ([bleeding-edge] branch). A bit better fix to SteamOS is to follow.

Bit early to tell, as I was somehow able to play for an hour or two the other day without crashing and have no idea why, but after a full day of crashing on attempts to be in game, this now appears to be working properly for me (Steam Deck, SteamOS, Steam version of game). Thank you VERY much for the work you've done here.

What do you mean by a better fix?

What do you mean by a better fix?

Just the correct and universal one, you won't notice a difference in BDO between the current vs better fix.

Is anyone else experiencing very large frame spikes on PC? They seem to occur every 60 seconds or so. This isn't something I've noticed while playing on windows. I've tried all kinds of things, setting frame limits, vsync on/off, I've checked my system to see if anything else is occurring during the spikes etc. These spikes can occur when sitting completely idle as well.

CPU: 5800x3d
GPU: 7900xt Mesa 23.3.4
OS: Fedora 39 kernel 6.7.3
RAM: 32GB
DE: Gnome 45.3 on Wayland

Have you checked RAM/Swap usage?
I have noticed BDO needs much more RAM on Linux (like double the amount), which causes some swapping for me as my PC has "only" 16GB RAM.
On Windows I did not notice much swap usage.

• Issue: In Fullscreen mode fps is cap to the refresh rate of the monitor on Linux.

For those that don't know, BDO on windows is uncap in full screen mode, assuming that vsync has been turn off. windowed mode and full screen window mode, (aka borderless) are cap to the refresh rate of the monitor unless you use windows 11 and a gsync/freesync monitor is used, optimizations for windows games should be on in windows 11 settings. Most laptops by default however cannot uncap fps pass refresh rate unless using external display, due to game design and how laptops are typically made. (laptops with gsync, dgpu only, advance optimus or mux switch can uncap fps).

• FIX: dxvk.conf???
  making dxvk.conf file with dxgi.syncInterval = 0 in the file allows you to uncap fps in Linux even on LAPTOPS. Make sure the dxvk.conf file has been put into the folder where bdo.exe is located.
  example on Steam deck. Gaming mode.
  
  in desktop mode.
  
  Tested in the battle arena. using 7 threads instead of 8 with power tools. Disable Frame Limit must be off in steam deck performance tab. If there is a better way to uncap fps let me know. XD

- Laptops

using dxvk 2.3 on windows allows for uncap fps even without the dxvk.conf file on windows 11. Linux users still need to use dxvk.conf file. CAUTION using this could technically be a ban though I think it's unlikely it's not impossible.

- Hardware Tested on

- Desktop
Cpu: 5800x3d
Gpu: 3070
Ram: 16gb
os: windows 11, Popos(proton experimental bleeding edge)

- Laptop
Cpu: i7-8750H
Gpu: 1070maxq
Ram: 32gb
os:windows 11, Popos(proton experimental bleeding edge)

and Steam deck. XD
experimental bleeding edge was use.

Replying to https://github.com/ValveSoftware/Proton/issues/3620#issuecomment-1924750700

You can also disable vsync if you use mangohud. In your config ~/.config/MangoHud/MangoHud.conf add: vsync=1

I can confirm that the game runs great (now that I figured out the Experimental thing). Probably better than on Windows, tbh. However there is still an issue, which is that minimizing the game to system tray works, but bringing it back does not. Clicking on the systray icon does nothing.
This may be a Gnome + extension specific issue. I normally run KDE or Sway but am trying out Gnome currently. Can anybody else confirm?

In your settings for the tray extension disable legacy icons. This will minimize the game to the wine tray.

could you tell me how to do that on ubuntu/unity?

edit: found it! configuration gui can be started with gnome-extensions prefs [email protected], then unselect "Enable Legacy Tray Icons support". As suggested by @wescode, this allows me to bring back the game from tray in Ubuntu/Unity. This works, but isn't very pretty :D

Is anyone else experiencing very large frame spikes on PC? They seem to occur every 60 seconds or so. This isn't something I've noticed while playing on windows. I've tried all kinds of things, setting frame limits, vsync on/off, I've checked my system to see if anything else is occurring during the spikes etc. These spikes can occur when sitting completely idle as well.

CPU: 5800x3d GPU: 7900xt OS: Fedora 39 kernel 6.7.3, Mesa 23.3.4 RAM: 32GB

I think I've found the source of the stutters, and it seems to be how the BDO client manages memory. If you monitor the memory usage of the client, once you see the stutter the mem usage drops ~.13GB every time. I'm not sure if there is much that can be done on the wine/proton side, but this stutter is definitely more prominent on linux.

EDIT: Another interesting observation is that on windows the game will use upwards of 9-10GB of ram, where with wine it rarely will use over 5GB.

Replying to https://github.com/ValveSoftware/Proton/issues/3620#issuecomment-1925237376

the other option is to use a different desktop enviornment

Replying to https://github.com/ValveSoftware/Proton/issues/3620#issuecomment-1924750700

Can you tell me where is located the dxvk.conf, I did'nt really get it.

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

Can you tell me where is located the dxvk.conf, I did'nt really get it.

Sorry i edited my comment. You have to make the dxvk.conf file, add in dxgi.syncInterval = 0 make sure put the file in where bdo .exe is located

DXVK_CONFIG="dxgi.syncInterval=0" works as well

• when the game is set to "full screen window", I have a black bar on top of the screen (probably for the title bar) and blurry fonts. Setting the game to "full screen" resolved both issues, fonts now look the same as on Windows.

A small update on this:
If you switch to fullscreen or windowed, and then back to fullscreen window, the latter works fine.
You will have to do this after every start of the game, however (so it seems to be some initialization issue...).

Thanks to both of you, I'm going to try the prompt and the conf file.

It's so cool that BDO has finally arrived on proton, I was so fade up to change OS never endlessly, I finally threw in the sponge.

There are still the Nvidia API options to ask. If you have any ideas, I'd love to hear from you.

Hello all. I'm having an issue with the game where certain windows just don't load, such as the Black Spirit Dice or Guild Information window. I'm not sure what's causing this. Otherwise the game runs fine.

Hello all. I'm having an issue with the game where certain windows just don't load, such as the Black Spirit Dice or Guild Information window. I'm not sure what's causing this. Otherwise the game runs fine.

Are you running bleeding edge?
Also, are you using launch option SteamGameId=582660 %command% ?

Are you running bleeding edge?
Also, are you using launch option SteamGameId=582660 %command% ?

I decided to try adding adding SteamGameId=582660 to the front of the game's launch options to see if it would help, and it did! Thank you. :)

For anyone else wondering, I am using the bleeding-edge version of Proton Experimental and was previously launching the game with the following options:

NOSTEAM=1 %command%

I did have an update to Proton Experimental before launching the game, so I checked to see if that was the only reason my issue was resolved - and.. nope. I do in fact need to have the SteamGameId part added to the options in order for certain windows to load. This makes my launch options look like this now:

SteamGameId=582660 NOSTEAM=1 %command%

Reply to : https://github.com/ValveSoftware/Proton/issues/3620#issuecomment-1925505675

I did some other tests with proton GE updated.
Proton : GE-Proton-8.30
the steam command line :
DXVK_CONFIG="dxgi.syncInterval=0" PROTON_ENABLE_NGX_UPDATER=1 PROTON_ENABLE_NVAPI=1 MANGOHUD=1 %command%
I don't really notice a big difference with the dxgi option, but it may be because I'm not running the game on laptop but PC and with remaster and high texture definition (which by the way give a better final render on linux than windows).

I did also a game profile in nvidia-settings, not sure it is the best possible because I didn't know all the hidden env options.
I can post it here, if needed.

Oh, I did test on both standalone and steam version of the game.

Edit : note that real good game render is from nvidia 535.145.05 driver, 550 beta give tearing.

Does anyone have a fix for abysmally slow loading times? It feels worse than it did back when I was playing the game on hdd.

I have to ask here as I just logged into my Account Security Center and went to manage login. I now see a very unknown IP address located in the US of A. Which is tagged as San Jose, United States. Does anyone else here see the same? is this some sort of "IP security" function from the launcher?

Reply to psychomantium https://github.com/ValveSoftware/Proton/issues/3620#issuecomment-1932503529

What is the dns resolve system are you using ?
If you do like I do with unbound, this could happen. My IP is never report on the internet because I use unbound and in plus, through Tor which resolve the domains names and never send my IP in metadata. That Why I never use IP security system.
Solution could be to use the same DNS as you have in Windows. But personnaly, I will never do that. :)

Replying to https://github.com/ValveSoftware/Proton/issues/3620#issuecomment-1930922215

It helped me too (Steam Deck platform). I played for 2 hours - no crashes. But the game starts only from desktop mode, from game mode there is an endless "steam" loading icon.
All windows work - guild, black spirit game, etc.
Is there any way to make the launch and from the game mode?

Back to black launcher on Proton 9.0

Launch options used: SteamGameId=582660 NOSTEAM=1 %command%

Proton GE and Bleeding no issues

Back to black launcher on Proton 9.0

Launch options used: SteamGameId=582660 NOSTEAM=1 %command%

Proton GE and Bleeding no issues

Proton 9 is behind proton 8 exp right now

Anyone know how to make the tray icon work on Polybar + i3? its very random, sometimes it works after me clicking 500 times, usually it does not.

I had an issue when using Wayland and Sway to run this game. The launcher was blank and sometimes froze while showing partial content.

The issue was in the display configuration (the use of position is not allowed; well I was using it), e.g. the correct way to configure display is output DP-1 scale 1 adaptive_sync on mode 2560x1440@144Hz.

More about the problem: https://github.com/swaywm/sway/issues/4857

I'm having an issue where my settings are no saved between sessions. Pretty annoying as i'm playing on a french keyboard
Same bug as above, launcher is black and everything

Étrange @Ciflire. C'est un problème connu par le passé, mais ça n'est plus sensé arriver.
Je suis gaucher et j'utilise un mini clavier paramétré à ma façon et je n'ai pas de problème de sauvegarde.
Est-ce un ancien compte ou un nouveau ?
selon la progression dans le jeu, il peut y avoir des soucis, surtout au tout début à cause des tutos.

Tu peux aussi utiliser input-remapper si vraiment ça persiste. le logiciel mettra les touche que tu veux où tu veux. c'est ce que je fais pour rediriger la touche / vers le ; qui n'est pas reconnue par BDO.

Étrange @Ciflire. C'est un problème connu par le passé, mais ça n'est plus sensé arriver. Je suis gaucher et j'utilise un mini clavier paramétré à ma façon et je n'ai pas de problème de sauvegarde. Est-ce un ancien compte ou un nouveau ? selon la progression dans le jeu, il peut y avoir des soucis, surtout au tout début à cause des tutos.

Tu peux aussi utiliser input-remapper si vraiment ça persiste. le logiciel mettra les touche que tu veux où tu veux. c'est ce que je fais pour rediriger la touche / vers le ; qui n'est pas reconnue par BDO.

Je dois avouer que le statut de mon compte est un peu particulier. Je n'ai pas rempli l'autorisation en 2021 pour la migration, donc j'ai encore un accès au jeu mais j'y ai perdu toutes mes données.
Je recommence donc à 0, sans réellement pouvoir dire si c'est un nouveau ou un ancien compte.
Je préfère par ailleurs ne pas utiliser de remapper, et attendre que le problème soit fix d'une manière ou d'une autre. Je ne suis pas particulièrement préssé, le fonctionnement de BDO sur linux est extrêmement récent et cela fait déjà (ou seulement) 1an que je patiente.

tu peux toujours faire un réinstallation au propre, mais pas sûr que ça aide vraiment. On peut reprendre cette conversation sur ce thread de BDO que je viens de créer, ce n'est pas vraiment ici que ça se passe pour ça.

Hey Sorry to bother, but has anyone else been having this issue lately where if you change channels or characters the game just freezes and locks up your computer? Im on Ubuntu 23.10 and its been happening so frequently lately that im missing out on boss trains.

Im using proton experimental too.

I have experienced some game crash resetting the W Manager by the way, but crashes are already know with BDO.

We need more info for a better idea.

If you like, I create a thread in BDO's EN forum with a form to trying help players with their issues. Maybe a better place to talk about this.

Dont know if Im doing something wrong, but whenever I tried Pearl Abyss Launcher with Proton, it just straight up doesnt work. For GE-Proton 9-32, it just hang around there forever, and for older version a popup say rerun the installation with normal user appear. This is on Steam Deck btw, and the launcher is download from SEA BDO Website. Does anyone know how to solve this?

Hard to say.
Did you try with proton-experimental ? (I personnlay tried experimental first and 8-32 after)
Did you have an other BDO installation on PC ? (sometimes windows /user/document/black desert data are useful to start)

Well I tried downloading on PC and then moving to SD, it's working now, thank you. One stupid question tho, how do I use controller with it? Which setting do I have to set?

@NogardDrago Settings -> Interface Settings -> Gamepad -> Use Gamepad + Use Gamepaid UI

Ok so now Im experiencing constant crash, after about 1 or 2 minutes in the game. What should I do in this case? I tried proton bleeding edge, 8-32.

Are you using the launch options?

Which launch option again?

Which launch option again?

SteamGameId=582660 %command%

Oh thank you, I will try it. Work on non-steam version of the game also right?

Ouch, still crashing

After 2 afternoons of troubleshooting I come to you with a comprehensive list of what doesn't affect BSA esque windows not loading in.
Tried both normal and bleeding edge versions of experimental, as well as GE 9.1. Also tried some launch settings as per protondb:

SteamGameId=582660 NOSTEAM=1 %command%

however to no avail. BSA just randomly decided to die, don't recall anything changing, maybe some arch kernel update scadoodle. Windows such as the settings archive also don't ever load.

Update 1: now every version of GE boots me to the login screen on the launcher, making the game unplayable, proton experimental and 9.0+ load the launcher properly but not the windows. Older proton versions have black screens for launchers but you can still start the game normally. No luck with BSA and such though. At this point the only variable I haven't inspected is my kernel. It may have something to do with arch 6.8

Update 2: downgrading to 6.7.8, which I for a fact knew was fine doesn't fix the issue, along with not doing anything to GE problems. I hereby conclude that PA just broke something in the latest patch.

Update 3: clearing all the cache files as per GM instructions doesn't affect BSA either. Though now I can run the game through GE again. Weirdly enough I noticed another bug, I seem to not be able to click on certain UI elements (regardless of proton version):

@mirai-ux , maybe I miss something, but .. what do you mean by BSA ?

@wildtruc
Black Spirit Adventure, the board minigame thingy. Along with that window also the Settings Archive and The Beauty Page do not load

Ahhh.
I notice that the window is curiously link to the SteamGameId=582660, but I had from my side issue with the NOSTEAM=1 option.
Try to remove the NOSTEAM=1 to see what's happening.
Note I'm running the native game too, not the Steam one.
for the record, here is my full and working commande line (nvidia card).
SteamGameId=582660 MANGOHUD=1 PROTON_ENABLE_NGX_UPDATER=1 PROTON_ENABLE_NVAPI=1 ENABLE_VKBASALT=1 %command%

Sadly I tried it both ways but to no avail. Didn't mention it during my previous comment, probably should have. I am running the steam version and am on an amd gpu. Here are my launch options:
SteamGameId=582660 %command%

From reading this issue, it seems as if I'm experiencing very similar issues to what was described in the early days of xigncode. However none of the fixes mentioned do anything. At this point I'm starting to consider whether a proton is just screwed up on my system, or is it really PA. It worked flawlessly earlier. Now I'm just noticing more and more windows that are blank. So far its up to: BSA, SA, Beauty Page, Guild Sayings.

Anyone know how to make the tray icon work on Polybar + i3? its very random, sometimes it works after me clicking 500 times, usually it does not.

For what it's worth, I'm running a very similiar setup, however I've never tested spam clicking the tray to see what happens. From what I managed to read up on, it's probably an xorg issue, that isn't very easily solvable. Wayland may be the easiest way out

It’s not an xorg issue. It’s an issue with his system tray not properly supporting legacy tray applications. Some system trays allow you to disable support entirely, which makes the BDO tray icon float in its own window and it works perfectly.

As an aside, I understand the urge but this GitHub issue is not meant for general tech support getting the game working on your system, but for reporting bugs in the game caused by incompatibilities with Proton. If you can trace your issues getting the game working back to Proton itself, then feel free to post here. Otherwise, please post on another platform. As it stands, those of us watching the issue for important updates are being flooded with emails irrelevant to the issue itself. Sorry, and thank you.

I probably should have clarified my intentions more clearly. At this point, I realize that the issue may be more complex than a simple version swap. My primary goal was to document the troubleshooting steps I've taken and their effects, in case others encounter a similar problem. I initially assumed the issue on Proton's repository might be broader, but I now understand it's more specifically related to Proton itself. Sorry for any inconveniences this may have caused. If I do manage to identify a solution or encounter any further anomalies related to Proton versions, I'll be sure to report back though.

Ok, so because i have also a Steam version, I tried.
Here is the Steam commande line options recommand by the BDOLauncher dev, Proton is GE-Proton8-32 :
SteamGameId=582660 DRI_PRIME=1 MESA_VK_DEVICE_SELECT=1 DXVK_CONFIG="dxgi.syncInterval=0" PROTON_ENABLE_NGX_UPDATER=1 PROTON_ENABLE_NVAPI=1 MANGOHUD=1 %command%
BSA, ok
Settings window, ok.
CShop, ok.

By the way, because @Daktyl198 mention it. I created a thread for Linux Help in BDO EN forum Feedback, there : thread in BDO's EN forum.

Anyone with issue when minimized the game, can't find a way to open it back?
Can I open it back using bash command?
So far I using wmctrl but still it couldn't work:
wmctrl -ia $(wmctrl -lp | awk -v pid=7371 '$3==pid {print $1; exit}')
ArchLinux-wayland

@Ozyohz

It’s not an xorg issue. It’s an issue with his system tray not properly supporting legacy tray applications. Some system trays allow you to disable support entirely, which makes the BDO tray icon float in its own window and it works perfectly.

https://github.com/ValveSoftware/Proton/issues/3620#issuecomment-2041511688

find a bar with a system tray that supports legacy tray apps, or don’t minimize to tray. AFAIK it’s an upstream wine issue where they don’t support modern systray apis.

Ok, so because i have also a Steam version, I tried. Here is the Steam commande line options recommand by the BDOLauncher dev, Proton is GE-Proton8-32 : SteamGameId=582660 DRI_PRIME=1 MESA_VK_DEVICE_SELECT=1 DXVK_CONFIG="dxgi.syncInterval=0" PROTON_ENABLE_NGX_UPDATER=1 PROTON_ENABLE_NVAPI=1 MANGOHUD=1 %command% BSA, ok Settings window, ok. CShop, ok.

I found, that BSA doesn't work without SteamGameId variable set. It's rather strange, I launch non-Steam version of the game and should to set Steam related variable. I also didn't find, what this variable do with the game to make it work properly.

I found, that BSA doesn't work without SteamGameId variable set. It's rather strange, I launch non-Steam version of the game and should to set Steam related variable. I also didn't find, what this variable do with the game to make it work properly.

Part of the way Proton works is by including game-specific workarounds. They are changes to Wine or related code that fixed a bug in one game, but is considered hacky or would break other games so it’s not applied globally. Proton knows to apply these fixes by reading the SteamGameId variable.

Anyone dealing with random closing after 5-10mins on bleeding or ge 9-5 or hotfix lately? Like last 1-2 weeks. Game would be running fine and dandy then randomly close, got a feeling it's Xigncode (Anticheat) complaining about something but the log for it is encrypted.

No closing on Proton 9.0-1 but lost access to the marketplace again.

Args used SteamGameId=582660 %command%

Edit: Trying ge 9-6
Edit edit: ge 9-6 seemed to solve issue

For me I installed BDO with the Lutris script and I keep getting random crashes/closing every 20~ or so minutes. The launcher window is also black. I tried Proton Experimental, GE 9-6 and 9-7. I tried variations of all the launch options above. Running on Arch with latest everything.

Right now I'm using DXVK_CONFIG="dxgi.syncInterval=0" PROTON_ENABLE_NGX_UPDATER=1 PROTON_ENABLE_NVAPI=1 SteamGameId=582660 NOSTEAM=1 %command%

Though, none of those flags (or subsets of them) fix the black launcher or the crashes.

I compiled Proton 9-7 GE with a wine patch and that fixed the black launcher issue, but not the crashes. Is anyone else here crashing every 20~ minutes? Any idea what the fix is?

For me, the launcher opens fine while running BDO through Steam on Proton Experimental and on the latest version of Proton-GE. However, when presented with the 2FA screen where I must type in a code, the launcher doesn't receive any input from my keyboard. I can still click on things, such as links, and it will open those links.

I run the latest version of Hyprland on NixOS.

Does anyone know what might cause this?

Hi every one.
I try those option recently and they really really useful for rendering quality even for 1080 screens :
WINE_FULLSCREEN_FSR=1 WINE_FULLSCREEN_FSR_STRENGHT=2
I replace DLSS and replace FSR BDO options that don't work in classic graphic mode (not remastered)

It doesn't look to a proton bug. I don't thing you need to compil
proton for this (at least it is really required).

You probably may ask Arch community, they will have probably better
answers around the distro specificity.
Note that I experienced Black spirit adventure troubles with NOSTEAM=1.

Le lundi 17 juin 2024 à 08:53 -0700, lambdadelt4 a écrit :

For me I installed BDO with the Lutris script and I keep getting
random crashes/closing every 20~ or so minutes. The launcher window
is also black. I tried Proton Experimental, GE 9-6 and 9-7. I tried
variations of all the launch options above. Running on Arch with
latest everything.
Right now I'm using DXVK_CONFIG="dxgi.syncInterval=0"
PROTON_ENABLE_NGX_UPDATER=1 PROTON_ENABLE_NVAPI=1 SteamGameId=582660
NOSTEAM=1 %command%
Though, none of those flags (or subsets of them) fix the black
launcher or the crashes.
I compiled Proton 9-7 GE with a wine patch and that fixed the black
launcher issue, but not the crashes. Is anyone else here crashing
every 20~ minutes? Any idea what the fix is?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID:
@.***>

@lambdadelt4 Have you tried running the game on Steam (as a 3rd party application) instead of through Lutris? I'm not sure if Proton needs some Steam special sauce.

@vickydotbat did you try using another WM? I've not had this issue on Plasma, but it could be a recent breakage.

@vickydotbat did you try using another WM? I've not had this issue on Plasma, but it could be a recent breakage.

Actually I did not, I will give that a try. Having some issues with Hyprland mouse input anyway.

@vickydotbat did you try using another WM? I've not had this issue on Plasma, but it could be a recent breakage.

Yup. Plasma works fine. Thank you!

idk how you guys can pass the launcher.
I'm using steam version and didn't even get to the launcher. After i click play, it just show the black spirit popup and instantly closed.
I'm using arch + hyprland on nvidia card.

For me, the launcher opens fine while running BDO through Steam on Proton Experimental and on the latest version of Proton-GE. However, when presented with the 2FA screen where I must type in a code, the launcher doesn't receive any input from my keyboard. I can still click on things, such as links, and it will open those links.

I run the latest version of Hyprland on NixOS.

Does anyone know what might cause this?

Have the same issue on Hyprland after the xwayland rewrite, opened an issue https://github.com/hyprwm/Hyprland/issues/7507

Updating to Proton Ge 9.18 and the latest bleeding:
(1730763984 experimental-bleeding-edge-9.0-132433-20241104-pb8e55a-w8e7762-dc466de-v7f9c01)

shows the following error on client launch:

Proton Ge 9.15 has no issues.

Replying to https://github.com/ValveSoftware/Proton/issues/3620#issuecomment-2456690220

I did a little bit of experimentation yesterday and determined that it was caused by dxvk, could you make an issue there

@TheWyn thank you for the report. This should be working again on Bleeding Edge

@Blisto91 Confirmed fixed here on bleeding.

( 1731010930 experimental-bleeding-edge-9.0-133239-20241107-pe13d9e-w680d20-d62970d-v96ab0a )

A bit baffled as to how im seeing all these "works just fine" reports yet on my system after clicking play in the launcher it gets to the ESRB logos with a black screen, sits for a bit and then just closes. Could it be that it doesn't work through a steam account? Since i don't have a standalone account. Could not see anything meaningful in the logs

There are no more problems with this game on my computer except that it doesn't really have fullscreen. However, I also have other games that others report to run well, but I only crash when I run them.

A bit baffled as to how im seeing all these "works just fine" reports yet on my system after clicking play in the launcher it gets to the ESRB logos with a black screen, sits for a bit and then just closes. Could it be that it doesn't work through a steam account? Since i don't have a standalone account. Could not see anything meaningful in the logs

It doesn't even get that far for me. I click play Steam tries says it's launching, nothing happens, and it goes back to play.

A bit baffled as to how im seeing all these "works just fine" reports yet on my system after clicking play in the launcher it gets to the ESRB logos with a black screen, sits for a bit and then just closes. Could it be that it doesn't work through a steam account? Since i don't have a standalone account. Could not see anything meaningful in the logs

a bit of testing later, turns out the game works just fine as a standalone game through the pearl abyss launcher, but through steam it doesn't work. Looking at the logs it seems to get as far as opening the UI host and then crashes. more than that I don't know how to check.

Turns out, all i had to do was verify game files through official launcher.... Kicking myself rn

New issue rose up, tested on ge 9-25, ge 9-21 and experimental. The game sometimes freezes without any real reason, and from then until reboot cannot be started again. The launcher works fine, but when the game tries to load it just goes to a black screen. Launch options: SteamGameId=582660 %command%

The problem with loading and displaying in-game web service content like "Black Spirit's Adventure", "Crafting guide" "Adventurer's guide" etc came back again last month after updating the launcher and game.
The workaround for me is to launch the game using Gamescope .
I wonder why the game needs to be launch in isolated Xwayland container like Gamescope in order for the in-game web service content to be loaded and display correctly. Anyone has similar issue like me?

2nd part is about performance. I found that overall the game has 30 to 40 less FPS when compare to Win10 on the same system at the same test area, using the same variables/settings. I notice the game % GPU Usage is much better on Win10 than on Linux Proton. I am using Nvidia rtx 2080 ti with linux 6.12 Nvidia proprietary driver 570.133.07. Is it nvidia driver issue on linux?

UPDATE (16 MAY 2025) : I found the fix to my issue regarding ingame web service like "Black Spirit's Adventure" dice game content not loading correctly. It has to do with composite extension on nvidia xorg config. I went to /etc/X11/xorg.conf.d/20-nvidia.conf and delete "Composite" "Disable" under "Extensions" section, reboot and black desert now show BSA, beauty page , crafting guide and all the web service content. So the game needs xcomposite extension to display them. Probably I disabled it when doing some tinkering months ago and forgot to revert back. If you disable it, OBS will not have screen capture option, gpu-screen-recorder can't record window etc.

I know it's a beta, but reporting in that bleeding and 10.0-1 lead to a black launcher.

Replying to https://github.com/ValveSoftware/Proton/issues/3620#issuecomment-2883247999

Send log with +opengl

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

Send log with +opengl

steam-582660.log

> glxinfo | grep "OpenGL version"
OpenGL version string: 4.6.0 NVIDIA 575.51.02

This should work like on 9 with the updated Experimental bleeding-edge branch.

This should work like on 9 with the updated Experimental bleeding-edge branch.

Launcher now works with 1747360650 experimental-bleeding-edge-10.0-198101-20250516-pba2272-we9ddca5-de9eff9-vb57878

Also got a black-screen with 1751927214 experimental-bleeding-edge-10.0-217297-20250707-p34d1cd-w1b3059-ddaed0c-vf992d4.

Using Proton 9 (1749140930 proton-9.0-4f) shows the Launcher normally.

Got the problem, that the launcher opens perfectly but right after i click on "launch" i get a flashing Blackscreen and the game crashed immediately. I tried multiple launch options (mostly the ones listet at ProtonDB) and multiple Proton Versions like GE10-4

Steam Runetime Diagnostics and the log

Replying to https://github.com/ValveSoftware/Proton/issues/3620#issuecomment-2523315869

Fixed in Wine 10.15.
Additionally, the launcher black screen issue was also fixed in Wine 10.15.

Not fixed, Wine 10.17, arch, launcher still show black screen, seems to download the game though?

Not fixed, Wine 10.17, arch, launcher still show black screen, seems to download the game though?

Yes, I noticed the issue had returned as early as 10.16.

@TheWyn Do you know if any special settings are required to trigger this issue? I have not been able to reproduce it on Bleeding Edge.
RTX 4080 and same driver version.

@Blisto91 Found the cause, turns out my router based adblocker has picked up whatever url the game is going too. Disregard my bug report.

Replying to https://github.com/ValveSoftware/Proton/issues/3620#issuecomment-3506706075

Game related issue. Fixed in newest patch

There is a new issue with the experimental Proton version. Here is my report:

System Information

• GPU: AMD Radeon RX 7900 XTX
• Video driver version: Mesa 26.1.5 (RADV)
• Kernel version: 7.1.4 (ArchLinux)
• Proton version: Proton Experimental, also reproduced with GE-Proton11-3 and other Wine 11 based builds

Symptoms

The game process aborts during the loading screen right at the end and before entering the game world with the following error:

wine client error:720: wine: Call from 00006FFFFFBBD947 to unimplemented function setupapi.dll.SetupDiGetDeviceInterfaceAlias, aborting

This is a regression against Wine 10 based Proton builds.
It only happens when a USB audio device is connected (in my case a Focusrite Scarlett, VID_1235&PID_8210).

Root cause analysis from debugging the crash minidump:

1. Wine 11 based Proton builds register KSCATEGORY_AUDIO device interfaces for USB audio hardware in the prefix registry, e.g.
   System\CurrentControlSet\Control\DeviceClasses\{6994AD04-93EF-11D0-A3CC-00A0C9223196}\##?#USB#VID_1235&PID_8210#...
   Wine 10 based builds do not create these keys.
2. The game bundles portaudio_x64.dll.
   PortAudio's "Windows WDM-KS" host API enumerates exactly this interface class and calls SetupDiGetDeviceInterfaceAlias for each interface found (pa_win_wdmks.c).
3. SetupDiGetDeviceInterfaceAlias is @ stub in setupapi, so the first call terminates the process.
   The minidump shows the crashing thread inside cfgmgr32/setupapi device interface enumeration called from the game's audio init.

On Wine 10 the registry contained no KSCATEGORY_AUDIO interfaces, PortAudio found zero devices, and the fatal call was never reached.

Additional gotcha for anyone bisecting: the interface keys persist in system.reg.
After one launch with a Wine 11 based build, the game crashes on older Proton versions too, until the {6994AD04-...} DeviceClasses keys are deleted from system.reg.

This will affect any game bundling PortAudio with the WDM-KS backend when a USB audio device is present, not just Black Desert.
A functional implementation of SetupDiGetDeviceInterfaceAlias, or even a semi-stub failing gracefully with SetLastError, would fix the whole class (PortAudio treats per-device failures as "skip device").

Reproduction

1. Have any USB audio interface connected.
2. Launch Black Desert with Proton Experimental (fresh prefix is fine).
3. Immediate abort with the unimplemented function setupapi.dll.SetupDiGetDeviceInterfaceAlias error before entering the game world.

Workaround: remove the {6994AD04-...} DeviceClasses keys from the prefix's system.reg and use a Wine 10 based Proton (e.g. UMU-Proton 10.0-4), or unplug all USB audio devices.

@kisak-valve

https://gist.github.com/WhitePeace36/1bf8f9edeaa25546fa31f94ad60e7e40

and this are the PROTON_LOG logs:

https://drive.google.com/file/d/1zlUevafWSyUYhQKm-uEGr-nXIkJ78FRb/view?usp=sharing

i dont know if my issue is the same but it worked fine a few days ago and now it crashes directly after selecting a character and joining into the game. After the loading is done it crashes. I tried different Proton versions. Experimental, Ge Proton 11-1, Ge Proton 11-3 and Ge Proton 10-34 but nothing worked. I also downgraded my mesa version but also didn't help.

@kisak-valve
i dont know if my issue is the same but it worked fine a few days ago and now it crashes directly after selecting a character and joining into the game. After the loading is done it crashes. I tried different Proton versions. Experimental, Ge Proton 11-1, Ge Proton 11-3 and Ge Proton 10-34 but nothing worked. I also downgraded my mesa version but also didn't help.

Yeah, you have the same issue. You need to switch to any 10.x Proton version and also remove the registry entries that Wine 11 created to get it into a working state again.

@kisak-valve, do you need my logs still? Given that you have their logs already which show the identical problem? Those logs contain an awful lot of information that I would rather not post publicly. I already did the entire debugging for you. The fix is ultimately providing an implementation for SetupDiGetDeviceInterfaceAlias that does nothing instead of just aborting the process.

@fwosar it really worked. Thx :)

@fwosar I tried to look at what is going on there and I cannot reproduce the issue (with USB audio device plugged of course). More so, I don't immediately see any code in Proton which would add KSCATEGORY_AUDIO to DeviceClasses. Can it be that some downstream Proton with custom patches added that to the prefix? Or any other custom things you can think of?

@gofman I tried to replicate it again now, and it no longer seems to happen with Proton Experimental. However, it still happens with GE Proton and various others. I must have had a stale prefix in Steam then, which is odd though, as I never ran the BDO Steam version before, but maybe I forgot to switch Proton versions during my first run. Thanks for looking into it, and sorry for sending you off onto a wild goose chase.

I did locate the exact patch that is responsible for this, just for reference:

https://github.com/xzn/proton-ds5-haptic/blob/master/0003-mmdevapi-setupapi-HACK-additionally-set-usb-audio-en.patch