Scribblenauts Unlimited (218680)

[pprotonrep]

I tested Scribblenauts Unlimited and it works like a charm.

• Ubuntu 18.04.1 LTS (64 bit 4.15.0-33-generic)
• GeForce GTX 1070/PCIe/SSE2 (396.54)
• Proton 3.7 (default configuration)

System information from steam

[Zero86Sk]

I conform it works wonderfully.

My Steam info: https://gist.github.com/Zero86Sk/d629f657c1ae861c36657cdf238a7765

[Utopanic]

It still works perfectly on proton version 3.16-4beta My steam info: https://gist.github.com/Utopanic/106a4807d0c0079057a9b85c06634e06#file-utopanic-s-system

[polymachine]

Hi I'm having issues with starting the game, as in it doesn't.

Steam shows the game as running for a second and then it's gone again.

Launching via the console gives no output, as if i hadn't attempted to start a game at all.

Here's the Proton log, which a google search showed as similar to Issue #1402, with the divergence that both my home and root disks run on ext4, no windows mounted.

I've also tried using older proton versions, but those throw up dozens of "File not found" error windows (in the rendering style of wine) and nothing else changes.

I've also tried redefining the wine prefixes and starting outside of steam, whereupon i get an error complaining about some openvr config folder not being found.

[kisak-valve]

Hello @polymachine, 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.

[polymachine]

Thank you, here's the info.

[kisak-valve]

Can you try a newer nvidia driver series?

[polymachine]

Tried nvidia-430.26 as the newest available, same behaviour though.

[tariqk]

So I'm having similar problems as @polymachine for one my kids' user accounts (but strangely, not for the other user account on this computer). This is the system information for the affected account, and here's the crash log I obtained after running Scribblenauts once.

[zorbathut]

Some reports and a fix:

This worked fine on my desktop, which is an AMD box running an NVidia card. This did not work fine on my daughter's computer, which is an AMD box running an AMD card. Is that related? I do not know.

I tried Proton 7.0, 8.0, and Experimental, crashes on all of them. Crashlogs attached:

steam-218680-7.0.log steam-218680-8.0.log steam-218680-experimental.log

8.0 and Experimental have the same errors, which I will reproduce part of here:

527.206:0188:018c:fixme:d3dcompiler:D3DCompile2 Ignoring flags 0x101.
527.206:0188:018c:err:d3dcompiler:D3DCompile2 Failed to compile shader, vkd3d result -4.
527.206:0188:018c:err:d3dcompiler:D3DCompile2 Shader log:
527.206:0188:018c:err:d3dcompiler:D3DCompile2     <anonymous>:22:34: E5000: syntax error, unexpected KW_SAMPLER_STATE
527.206:0188:018c:err:d3dcompiler:D3DCompile2 
527.206:0188:018c:fixme:d3dcompiler:D3DCompile2 Ignoring flags 0x101.
527.206:0188:018c:err:d3dcompiler:D3DCompile2 Failed to compile shader, vkd3d result -4.
527.206:0188:018c:err:d3dcompiler:D3DCompile2 Shader log:
527.206:0188:018c:err:d3dcompiler:D3DCompile2     <anonymous>:81:1: E5000: syntax error, unexpected KW_TECHNIQUE
527.206:0188:018c:err:d3dcompiler:D3DCompile2 
527.206:0188:018c:fixme:d3dcompiler:D3DCompile2 Ignoring flags 0x101.
527.206:0188:018c:err:d3dcompiler:D3DCompile2 Failed to compile shader, vkd3d result -4.
527.206:0188:018c:err:d3dcompiler:D3DCompile2 Shader log:
527.206:0188:018c:err:d3dcompiler:D3DCompile2     <anonymous>:46:8: E5005: Function "tex2Dlod" is not defined.
527.206:0188:018c:err:d3dcompiler:D3DCompile2 

7.0 has different errors, but mostly in that it doesn't have the detailed information. I think it's actually the same bug.

The good news is that (thanks to the people at vkd3d-proton!) I also have a fix. Install d3dcompiler_47 into that Wine prefix and it's all better! You can do this with winetricks, or use protontricks as a convenient wrapper; I used protontricks.

I'm not sure whose fault this bug is - should Scribblenauts be installing it? Should Proton be installing it? Is it actually a bug in the underlying shader compiler? But hopefully this helps someone out who's hunting for info.

[mbriar]

I'm not sure whose fault this bug is - should Scribblenauts be installing it? Should Proton be installing it? Is it actually a bug in the underlying shader compiler?

Although some games do ship the native d3dcompiler dll, i don't think you can consider it a game bug to rely on it already being present on a windows system. The bug is in wine's implementation of d3dcompiler, which nowadays is actually handled mostly by upstream vkd3d (not vkd3d-proton) in both wine and proton.

[zorbathut]

Sigh.

I don't suppose you've got a URL to the place to report bugs in vkd3d? That's actually how I found vkd3d-proton originally, but I'm not having any luck finding just bare vkd3d.

[kisak-valve]

https://bugs.winehq.org/describecomponents.cgi?product=vkd3d