[Bug 58327] New: Crash from d3d11 (assertion failed) in S.T.A.L.K.E.R. Anomaly when using a scope

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=58327

Bug ID: 58327
           Summary: Crash from d3d11 (assertion failed) in S.T.A.L.K.E.R.
                    Anomaly when using a scope
           Product: Wine
           Version: 10.9
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: d3d
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

Created attachment 78695
  --> http://bugs.winehq.org/attachment.cgi?id=78695
Savegame to easily trigger the crash

East of the Yanov station in Jupiter, looking down the scope of your weapon
will crash d3d11 if you look East while you are at a specific location:

---snip---
Assertion failed!

Program:
Z:\home\tactica\Downloads\Anomaly\Anomaly-1.5.3-Full.2\bin\AnomalyDX11.exe
File:dlls/d3d11/inputlayout.c
Line: 416

Expression: "iface->lpVtbl == &d3d11_input_layout_vtbl"
---snip---

(note: the quoted text above was typed manually)

How to reproduce:

1. Download and unpack STALKER Anomaly. It doesn't require any installation.
2. Unpack the attached savegame files into /appdata/savedgames/ in the game
directory.
3. Use winecfg to install d3d11 as override for Wine.
3. Start the game running /bin/AnomalyDX11.exe
4. After the main menu opens, load the provided savegame.
5. Once in the game proper, simply click RMB to use the scope of your weapon
while looking at those ruined vehicles

The crash does not happen if:

a) You run AnomalyDX9.exe instead
b) You move the camera to point elsewhere before using the scope, say 90
degrees to your right or left
c) You use the shotgun instead (press 2), which doesn't have a long range scope
attached
c) You load the same savegame on 64-bit Windows 7 and play there, using exactly
the same visual settings (I double checked that)

This using 64-bit (only) Wine 10.9 on Void Linux (x86-64) with the stock AMDGPU
driver.

[Bug 58327] Crash from d3d11 (assertion failed) in S.T.A.L.K.E.R. Anomaly when using a scope

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=58327

tactica  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #1 from tactica  ---
Created attachment 78696
  --> http://bugs.winehq.org/attachment.cgi?id=78696
Backtrace

This is the backtrace from the debugger.

[Bug 58327] Crash from d3d11 (assertion failed) in S.T.A.L.K.E.R. Anomaly when using a scope

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=58327

--- Comment #2 from Rafał Mużyło  ---
Does this also fail in wine 10.8 ?

If not, it might be a regression tied to 5f014fb0.

Also, attach whole console output, not just the backtrace, though given that
the failure is an explicit assertion, it will likely not matter.

[Bug 58327] Crash from d3d11 (assertion failed) in S.T.A.L.K.E.R. Anomaly when using a scope

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=58327

--- Comment #3 from tactica  ---
10.8. 10.7 and 10.1 all fail the same way I'm afraid. These are the only cached
binaries I have. I didn't bother removing and re-applying d3d11 with winecfg
between each downgrade, hopefully that's OK.

The console output doesn't seem to show anything relevant but I'll attach what
I get from 10.1 just in case.

In the meantime I also tried maximizing the visual settings for the game, which
eventually resulted in the same crash being triggered out of nowhere while
moving around at a very high location, with plenty of distant places to look
at.

[Bug 58327] Crash from d3d11 (assertion failed) in S.T.A.L.K.E.R. Anomaly when using a scope

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=58327

--- Comment #4 from tactica  ---
Created attachment 78704
  --> http://bugs.winehq.org/attachment.cgi?id=78704
Console output from Wine 10.1