https://bugs.winehq.org/show_bug.cgi?id=40846
Bug ID: 40846
Summary: Dead by Daylight: Crash on starting the game
Product: Wine
Version: 1.9.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sworddragon2(a)aol.com
Distribution: ---
Created attachment 54829
--> https://bugs.winehq.org/attachment.cgi?id=54829
Terminal output
On starting the game the launcher is visible for some seconds but then the game
crashes. In the attachments is the terminal output.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=40710
Bug ID: 40710
Summary: Splinter Cell: Blacklist crashes with unimplemented
function d3dx11_43.dll.D3DX11CreateTextureFromMemory
Product: Wine
Version: 1.9.11
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3dx11
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
wine: Call from 0x7b43b24c to unimplemented function
d3dx11_43.dll.D3DX11CreateTextureFromMemory, aborting
wine: Unimplemented function d3dx11_43.dll.D3DX11CreateTextureFromMemory called
at address 0x7b43b24c (thread 0009), starting debugger...
Unhandled exception: unimplemented function
d3dx11_43.dll.D3DX11CreateTextureFromMemory called in 32-bit code (0x7b43b24c).
wine-1.9.11-27-gc89dc58
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46720
Bug ID: 46720
Summary: Assassins Creed III / IV startup with builtin
d3dcompiler_43 only show up a black window
Product: Wine
Version: 4.0
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: gamiljydcome(a)gmail.com
Distribution: ---
wine4.0 + dxvk + native d3dcompiler_43 works very well, just a little
renderring problem in a few scenes. with builtin d3dcompiler_43 only starup a
black window, i cut some output info as below:
0009:fixme:d3d:state_linepattern_w Setting line patterns is not supported in
OpenGL core contexts.
0009:fixme:d3d11:d3d11_device_CheckFeatureSupport Returning fake threading
support data.
0009:fixme:d3d11:d3d11_device_CreateDeferredContext iface 0x72e57bc, flags 0,
context 0xa7bef48 stub!
002e:fixme:d3dcompiler:make_assignment Check for casts in the lhs.
002e:fixme:hlsl_parser:hlsl_parse Check for valued return on void function.
002e:fixme:hlsl_parser:hlsl_parse Implicit conversion to the return type if
needed, error out if conversion not possible.
002e:err:d3dcompiler:compile_shader HLSL shader parsing failed.
002e:fixme:d3dcompiler:make_assignment Check for casts in the lhs.
002e:fixme:hlsl_parser:hlsl_parse Check for valued return on void function.
002e:fixme:hlsl_parser:hlsl_parse Implicit conversion to the return type if
needed, error out if conversion not possible.
002e:fixme:d3d11:d3d_blend_state_create Color mask 0x7 not supported for render
target 4.
002e:fixme:d3d11:d3d_blend_state_create Color mask 0x7 not supported for render
target 5.
002e:fixme:d3d11:d3d_blend_state_create Color mask 0x7 not supported for render
target 6.
002e:fixme:d3d11:d3d_blend_state_create Color mask 0x7 not supported for render
target 7.
002e:fixme:d3d11:d3d_blend_state_create Color mask 0x7 not supported for render
target 4.
002e:fixme:d3d11:d3d_blend_state_create Color mask 0x7 not supported for render
target 5.
002e:fixme:d3d11:d3d_blend_state_create Color mask 0x7 not supported for render
target 6.
002e:fixme:d3d11:d3d_blend_state_create Color mask 0x7 not supported for render
target 7.
002e:fixme:d3d_shader:shader_sm4_read_instruction_modifier Unhandled modifier
0x80000202.
002e:fixme:d3d_shader:shader_glsl_sprintf_cast Unhandled cast from 0x1 to 0x5.
0009:fixme:dxgi:wined3d_bind_flags_from_dxgi_usage Unhandled DXGI usage 0x40.
0009:fixme:dxgi:dxgi_output_GetDisplayModeList iface 0xd9d5970, format
DXGI_FORMAT_R8G8B8A8_UNORM, flags 0, mode_count 0x32faac, desc (nil) partial
stub!
0009:fixme:d3dcompiler:make_assignment Check for casts in the lhs.
0009:fixme:hlsl_parser:hlsl_parse Check for valued return on void function.
0009:fixme:hlsl_parser:hlsl_parse Implicit conversion to the return type if
needed, error out if conversion not possible.
002e:fixme:hlsl_parser:hlsl_parse Check for valued return on void function.
002e:fixme:hlsl_parser:hlsl_parse Implicit conversion to the return type if
needed, error out if conversion not possible.
002e:err:d3dcompiler:compile_shader HLSL shader parsing failed.
002e:fixme:d3d11:d3d_blend_state_create Per-rendertarget blend not implemented.
003d:fixme:dxgi:dxgi_output_GetDisplayModeList iface 0xdc8d360, format
DXGI_FORMAT_R8G8B8A8_UNORM, flags 0x1, mode_count 0x134afc04, desc (nil)
partial stub!
003d:fixme:dxgi:dxgi_output_GetDisplayModeList iface 0xdc8d360, format
DXGI_FORMAT_R8G8B8A8_UNORM, flags 0x1, mode_count 0x134afc04, desc 0xf287d60
partial stub!
it seems d3dcompiler hlsl error is common for some dx11/dx9 games from wine
bugzilla, for Assassins Creed III / IV must switch to native d3dcompiler_43 to
avoid startup black window and must work with dxvk to avoid startup crash.
dxvk work almost perfect for most games i tested, with buildin dx11
implementation i always meet crashing or very low fps.
so if wined3d implementation port to vulkan driver including dx9~12 will
natural avoid many crashing, unimplementation, is it?
regards.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=37769
Bug ID: 37769
Summary: Alien Isolation Unhandled exception: unimplemented
function d3d11.dll.D3D11CreateDeviceAndSwapChain
called in 32-bit code (0x7b83a9fc)
Product: Wine
Version: 1.7.33
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3dx10
Assignee: wine-bugs(a)winehq.org
Reporter: winedb(a)bazzawill.info
Distribution: ---
Created attachment 50305
--> https://bugs.winehq.org/attachment.cgi?id=50305
Alien isolation backtrace
Error launching Alien: Isolation
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=32901
Bug #: 32901
Summary: Civilizations V crash while starting in Directx 10 &
11 Mode
Product: Wine
Version: 1.5.23
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3dx10
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jaimerave(a)gmail.com
Classification: Unclassified
Created attachment 43452
--> http://bugs.winehq.org/attachment.cgi?id=43452
Backtrace
I have setup my Wineprefix to Windows 7 and while starting Civilizations V in
directx 10 & 11 mode I get this crash. I'm attaching the backtrace. This is
under Ubuntu 13.04.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47897
Bug ID: 47897
Summary: AMD Mecha Demo is miss-rendered (and extremely slow)
Product: Wine
Version: 4.12.1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3dx11
Assignee: wine-bugs(a)winehq.org
Reporter: witold.baryluk+winehq(a)gmail.com
Distribution: ---
Created attachment 65396
--> https://bugs.winehq.org/attachment.cgi?id=65396
Demo run under Wine
AMD Mecha Demo, uses DX11 and demonstrates use of OIT (order indepdenent
transparency), using per-pixel linked list. To implement it, demo uses atomic
counter in shaders.
Reproduced with Wine Staging 1.12.1, with Mesa 19.2.0-rc2, and Mesa
19.3.0-devel.
Demo works correctly when run using DXVK 1.4.1.
Before starting the demo, I suggest editing a Sushi.ini file to reduce
resolution and make it windowed. Even then you might need to kill it if it
becomes extremely slow.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48222
Bug ID: 48222
Summary: Aria Player 1.959 giving a 122 error on Nvidia RTX
2060
Product: Wine
Version: 4.21
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3dx10
Assignee: wine-bugs(a)winehq.org
Reporter: linuxguy93(a)gmail.com
Distribution: ---
Created attachment 65859
--> https://bugs.winehq.org/attachment.cgi?id=65859
error dialog when importing a sfz library via xml
I've noticed slow GUI updating performance on ARIA Player on Linux using
version 1.959. Also a bigger issue is whenever I import a sfz library via xml I
get an error dialog stating "Starting external process did not succeed 122". I
am using the Nvidia proprietary driver. I do not receive this error when using
wine 4.0.3 only wine 4.21. This also effects people who use sforzando player as
well.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44940
Bug ID: 44940
Summary: Bioshock Remastered doesn't start in windowed mode
Product: Wine
Version: 3.5
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3dx11
Assignee: wine-bugs(a)winehq.org
Reporter: devangm(a)gmail.com
Distribution: ---
Created attachment 61045
--> https://bugs.winehq.org/attachment.cgi?id=61045
log for bioshock remastered opening in steam (with -windowed option)
Bioshock Remastered with the -windowed flag (set as a steam launch option)
should start in windowed mode, but doesn't. Changing to windowed mode from
within the game works fine. Doesn't work on 3.5-devel (ubuntu) and 3.5 staging
(gentoo). The flag works on Windows 8.1.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47898
Bug ID: 47898
Summary: AMD Leo demo doesn't render some shadows properly
Product: Wine
Version: 4.12.1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3dx11
Assignee: wine-bugs(a)winehq.org
Reporter: witold.baryluk+winehq(a)gmail.com
Distribution: ---
Multiple shadows are not rendered correctly in this demo.
Demo works and renders correctly when using DXVK 1.4.1.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44683
Bug ID: 44683
Summary: Kingdom Come: Deliverance: Torch doesn't work properly
(no illumination)
Product: Wine
Version: 3.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3dx11
Assignee: wine-bugs(a)winehq.org
Reporter: ben(a)tokidev.fr
Distribution: ---
Created attachment 60692
--> https://bugs.winehq.org/attachment.cgi?id=60692
+d3d_shader log of the suspected cause
This is on nvidia proprietary driver (although it seems to be replicated by
other users based on
[this](https://forum.kingdomcomerpg.com/t/linux-running-kc-d-with-wine/41173)
topic in the official games forum and is likely not hardware-dependent).
The bug occurs on 3.3, 3.3-staging (the new 3.x rebased fork), and
2.21-staging.
Basically, when the main character (and only him - NPCs with torches do not
seem to be affected) pulls out his torch from the inventory, no illumination is
produced. To be more precise, the illumination effect appears to be there but
blocked by something in front of the character; moving the point of view from
left to right very quickly shows the effect I'm talking about - the
illumination will briefly appear on the left/right but disappears as soon as
the movement stops.
I - perhaps mistakenly - assumed it may be a shader issue because the only
relevant log output when it occurs is a series of shader fixmes; the lines in
question only appear when the torch is enabled. I've attached a log of the
relevant section of the output with +d3d_shader to this bug report.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.