Runs fine now on proton 3.16-4.
Doesn't work for me, starts then crashes instantly.
Any advice?
Hello @Arefu, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report. Also, please add PROTON_LOG=1 %command% to the game's launch options and drag and drop the generated $HOME/steam-$APPID.log into the comment box.
I have also problems when using proton no matter whether the 3.16-4 or the 3.16-7 beta
to be precise, by default it just crashes saying "Direct3d could not be initialized. This Game requires support for Feature Level 10"
pushing in
PROTON_USE_WINED3D=1 PROTON_LOG=1 %command% or just
PROTON_USE_WINED3D=1 %command%
leads to the game starting, but as soon as I try to do a duel or go deck edit it crashes.
steam-480650.log
here's a log from 3.16.7
System info (I actually use Kubuntu 18.04 instead of Ubuntu, probably doesnt matter but wanted to note):
Computer Information:
Manufacturer: Unknown
Model: Unknown
Form Factor: Laptop
No Touch Input Detected
Processor Information:
CPU Vendor: GenuineIntel
CPU Brand: Intel(R) Core(TM) i3-7020U CPU @ 2.30GHz
CPU Family: 0x6
CPU Model: 0x8e
CPU Stepping: 0xa
CPU Type: 0x0
Speed: 2300 Mhz
4 logical processors
2 physical processors
HyperThreading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Unsupported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported
Operating System Version:
Ubuntu 18.04.2 LTS (64 bit)
Kernel Name: Linux
Kernel Version: 4.15.0-1033-oem
X Server Vendor: The X.Org Foundation
X Server Release: 11906000
X Window Manager: KWin
Steam Runtime Version: steam-runtime-beta-release_2019-01-10
Video Card:
Driver: Intel Open Source Technology Center Mesa DRI Intel(R) HD Graphics 620 (Kaby Lake GT2) x86/MMX/SSE2
Driver Version: 3.0 Mesa 18.2.2
OpenGL Version: 3.0
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 60 Hz
VendorID: 0x8086
DeviceID: 0x5916
Revision Not Detected
Number of Monitors: 1
Number of Logical Video Cards: 1
Primary Display Resolution: 1600 x 900
Desktop Resolution: 1600 x 900
Primary Display Size: 15.04" x 8.46" (17.24" diag)
38.2cm x 21.5cm (43.8cm diag)
Primary VRAM Not Detected
Sound card:
Audio device: Realtek ALC236
Memory:
RAM: 15924 Mb
Miscellaneous:
UI Language: English
LANG: en_DE.UTF-8
Total Hard Disk Space Available: 60347 Mb
Largest Free Hard Disk Block: 31801 Mb
VR Headset: None detected
Recent Failure Reports:
Hello @Arefu, please verify you have vulkan drivers for your video chipset with apt policy mesa-vulkan-drivers mesa-vulkan-drivers:i386.
installed them
Installed: 18.2.2-0ubuntu1~18.04.2
Candidate: 18.2.2-0ubuntu1~18.04.2
Version table:
*** 18.2.2-0ubuntu1~18.04.2 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages
100 /var/lib/dpkg/status
18.0.0~rc5-1ubuntu1 500
500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
mesa-vulkan-drivers:i386:
Installed: 18.2.2-0ubuntu1~18.04.2
Candidate: 18.2.2-0ubuntu1~18.04.2
Version table:
*** 18.2.2-0ubuntu1~18.04.2 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/universe i386 Packages
100 /var/lib/dpkg/status
18.0.0~rc5-1ubuntu1 500
500 http://archive.ubuntu.com/ubuntu bionic/universe i386 Packages
but still crashes nicely.
also @kisak-valve I think that ping went wrong.
483811.663:0023:0038:fixme:d3d11:d3d11_device_CreateDeferredContext iface 0x115070, flags 0, context 0x1410d3a60 stub!
Crash because no deferred context support in wined3d. Wined3d needs staging patchset https://github.com/wine-staging/wine-staging/tree/master/patches/d3d11-Deferred_Context to support it now. However, if you have DXVK working, it should not crash since DXVK implemented deferred context. Please remove PROTON_USE_WINED3D=1 and try with DXVK.
NOW We're talking. Guess I'll update my entry at ProtonDB. just quicktested through.
Might be an awesome idea to have something in proton read those error messages, and for example go straight into recommending vulkan drivers, or flipping on wine3d
@Arefu can you try again? I am able to run it without issue with Proton 5.0-9
I have played the game for the past 2 days for 10+ hours and didn't get a single issue, plus it looks that for the past year there hasn't been any issues (in protondb https://www.protondb.com/app/480650) and working with steamplay for the past 6 months.
If an admin sees this, please close this bug as its no longer valid and open a whitelisting request.
Hello @kaincenteno, there's no need to have a separate whitelist request. You can grab the Whitelist Request template, copy it to this issue report, and fill it out, then we'll have a holding period for others to give feedback before I switch this issue report over to a whitelist request.
Awesome! Thank you @kisak-valve :smile: I am looking to contribute as much as I can.
Play button in the Steam client is sufficient.Hello, is anyone seeing an issue with this game and Proton 5.0 that would block it from being whitelisted?
proton 5.0x1 2020-08proton 5.0-9x1 2020-08proton 3.16-4x1 2019-01PROTON_USE_WINED3D=1`x1 2019-02PROTON_LOG=1x2 2019-02PROTON_USE_WINED3D=1x1 2019-02PROTON_USE_WINED3D=1 %command%x1 2019-02PROTON_USE_WINED3D=1 PROTON_LOG=1 %command%x1 2019-02
I know it's because the game requires Direct X 11, however under normal WINE I got it "launching" at least, I was just wondering if anyone knows where I can find a cheeky config file to change the WINE settings under the hood if they're still there.