March 2017 - Wine-Bugs - list.winehq.org

[Bug 40669] New: proteus 8 Unhandled exception: page fault on read access to 0x40000372 in 32-bit code
by wine-bugs＠winehq.org March 4, 2017

March 4, 2017

https://bugs.winehq.org/show_bug.cgi?id=40669 Bug ID: 40669 Summary: proteus 8 Unhandled exception: page fault on read access to 0x40000372 in 32-bit code Product: Wine-staging Version: 1.9.10 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: yonatan.el.amigo(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 54541 --> https://bugs.winehq.org/attachment.cgi?id=54541 Backtrace wine: Unhandled page fault on read access to 0x40000372 at address 0x531b2f (thread 01e0), starting debugger... Unhandled exception: page fault on read access to 0x40000372 in 32-bit code (0x00531b2f). -- 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.

1 5

[Bug 42587] New: MandelDx11Double doesn' t work Needs support for D3D11 double prec. floats in shaders..
by wine-bugs＠winehq.org March 4, 2017

March 4, 2017

https://bugs.winehq.org/show_bug.cgi?id=42587 Bug ID: 42587 Summary: MandelDx11Double doesn't work Needs support for D3D11 double prec. floats in shaders.. Product: Wine Version: 2.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: rtfss1(a)gmail.com Distribution: --- Created attachment 57512 --> https://bugs.winehq.org/attachment.cgi?id=57512 Mandelbrot D3D11 demo with double precision support Hi don't know if interested on implementing D3D11 double precision support as it's optional feature and not many (any?) apps/games use it.. Any way long time ago I patched shaders of one of firsts D3D11 compute shader Mandelbrot demos( see Mandel http://users.skynet.be/fquake/) to use double precision floats for calculations.. demo uses high enough zoom by default to show difference if double works or not if using single prec you will see large blocks of same color due to reduced precision.. I attach my patched demo (see MandelDX11double).. If run: Mandel.exe 1 will run using double precision calculations instead Mandel.exe 0 will force to use single prec and will see big blocks of colors due to reduced precision Also note initial SM5 double precision supporti don't know if interested on implementing D3D11 double precision support as it's optional feature and not many (any?) apps/games use it.. Any way long time ago I patched shaders of one of firsts D3D11 compute shader Mandelbrot demos( see Mandel http://users.skynet.be/fquake/) to use double precision floats for calculations.. demo uses high enough zoom by default to show difference if double works or not if using single prec you will see large blocks of same color due to reduced precision.. I attach my patched demo (see MandelDX11double).. If run: Mandel.exe 1 will run using double precision calculations instead Mandel.exe 0 will force to use single prec and will see big blocks of colors due to reduced precision Also note initial SM5 double precision support includes ops: dadd :https://msdn.microsoft.com/en-us/library/windows/desktop/hh446894(v=vs.85).aspx dmax dtof etc.. but complete support came with DX11.1 adding: drcp dfma ddiv (double precision divide): https://msdn.microsoft.com/en-us/library/windows/desktop/hh920925(v=vs.85).… at least you can exercise ddiv opcode if change in mandel.hlsl file: b = b*0.5; with: b= b/2.0; Note code (mandel.cpp) checks doubles supports: g_pd3dDevice->CheckFeatureSupport( D3D11_FEATURE_DOUBLES, &fdDoubleSupport, sizeof(fdDoubleSupport) ); GPUcanDoDoubles = fdDoubleSupport.DoublePrecisionFloatShaderOps; and Wine currently returns 0; So I modified my local Wine sources to return D3D11_FEATURE_DOUBLES as true and verified running dxcapsviewer I made the changes correctly.. Even so program crashes.. Also note with Wine 2.3 demo crashes due to using native d3dx11_43 instead of incorporated d3dx11_42 and D3DCompiler_42 DLL's so I delete this files in (usr/local/lib/wine) so using included DLLs.. at least this way float demo works. has: dadd :https://msdn.microsoft.com/en-us/library/windows/desktop/hh446894(v=vs.85).aspx Note code (mandel.cpp) checks doubles supports: g_pd3dDevice->CheckFeatureSupport( D3D11_FEATURE_DOUBLES, &fdDoubleSupport, sizeof(fdDoubleSupport) ); GPUcanDoDoubles = fdDoubleSupport.DoublePrecisionFloatShaderOps; and Wine currently returns 0; So I modified my local Wine sources to return D3D11_FEATURE_DOUBLES as true and verified running dxcapsviewer I made the changes correctly.. Even so program crashes.. Also note with Wine 2.3 demo crashes due to using native d3dx11_43 instead of incorporated d3dx11_42 and D3DCompiler_42 DLL's so I delete this files in (usr/local/lib/wine) so using included DLLs.. at least this way float demo works.. -- 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.

1 0

[Bug 42539] New: Exact Audio Copy seems to detect drive but claims ' no audio CD in drive'
by wine-bugs＠winehq.org March 4, 2017

March 4, 2017

https://bugs.winehq.org/show_bug.cgi?id=42539 Bug ID: 42539 Summary: Exact Audio Copy seems to detect drive but claims 'no audio CD in drive' Product: Wine Version: 2.2 Hardware: x86-64 URL: http://www.exactaudiocopy.de/ OS: Mac OS X Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: scott(a)doemail.org Created attachment 57439 --> https://bugs.winehq.org/attachment.cgi?id=57439 CLI output EAC's seems to know about my disc drive in some fashion because it shows it shows an item in a checkmark list in the configuration wizard, but its name is empty. On top of that, EAC thinks there is no audio CD in the drive when there is. winecfg correctly detects and shows the drive + the audio CD however. The drive I am using: https://www.amazon.com/gp/product/B00AO1XFM0 Repro steps: 1) Install EAC 2) Launch EAC and start the configuration wizard a. If this not your first time launching EAC, launch the wizard through EAC->Configuration Wizard... 3) Press Next 4) Note the checkmarked item with a blank name 5) Press Next 6) Press Next 7) Press Next Expected: 8) EAC auto detects the drive features Actual: 8) EAC displays a dialog saying "EAC couldn't find a CD in the drive to be tested." CLI output attached + screenshots -- 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.

1 8

[Bug 42511] New: winnt.h: invalid conversion from 'void*' to ' volatile char*'
by wine-bugs＠winehq.org March 3, 2017

March 3, 2017

https://bugs.winehq.org/show_bug.cgi?id=42511 Bug ID: 42511 Summary: winnt.h: invalid conversion from 'void*' to 'volatile char*' Product: Wine Version: 2.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jonathon(a)manjaro.org Distribution: --- Created attachment 57399 --> https://bugs.winehq.org/attachment.cgi?id=57399 Build log to failure GCC throws an error when building 'airwave', a WINE-based bridge for Windows VST instruments (https://github.com/phantom-code/airwave) This attempts to include /usr/include/wine/windows/winnt.h, and fails with 'invalid conversion' error (winnt.h:5441:26). Building on Arch (Manjaro) with GCC 6.3.1 and WINE 2.2 using this PKGBUILD: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=airwave-git -- 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.

1 5

[Bug 41341] New: Box Sync Setup ended prematurely
by wine-bugs＠winehq.org March 3, 2017

March 3, 2017

https://bugs.winehq.org/show_bug.cgi?id=41341 Bug ID: 41341 Summary: Box Sync Setup ended prematurely Product: Wine Version: 1.9.19 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: audiger(a)live.fr Distribution: --- Created attachment 55688 --> https://bugs.winehq.org/attachment.cgi?id=55688 Console output Hello, When I tried to install Box Sync with the latest wine version (currently 1.9.19), the installation ended prematurely. I put the output of the console in attachment. You can find the program here if you want to test it: https://e3.boxcdn.net/box-installers/sync/Sync+4+External/BoxSyncSetup.exe -- 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.

1 4

[Bug 42509] New: The Witcher 3 hangs the system on startup
by wine-bugs＠winehq.org March 3, 2017

March 3, 2017

https://bugs.winehq.org/show_bug.cgi?id=42509 Bug ID: 42509 Summary: The Witcher 3 hangs the system on startup Product: Wine-staging Version: 2.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: shtetldik(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 57398 --> https://bugs.winehq.org/attachment.cgi?id=57398 Wine log (The Witcher 3 hangs system) Since update of wine-staging to 2.2, Witcher 3 started hanging hard on startup. The screen goes black, and keyboard becomes completely unresponsive. The system can still be rebooted if accessed for example from another machine over ssh. OS: Debian testing, x86-64, KDE Plasma 5.8.4. Graphics: AMD RX480, Mesa / Gallium 0.4 on AMD POLARIS10 (DRM 3.8.0/4.9.0-1-amd64, LLVM 3.9.1) See attached Wine log. -- 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.

1 8

[Bug 41394] New: 3DMark2001se 'Car chase' speed regression on mesa/nouveau
by wine-bugs＠winehq.org March 3, 2017

March 3, 2017

https://bugs.winehq.org/show_bug.cgi?id=41394 Bug ID: 41394 Summary: 3DMark2001se 'Car chase' speed regression on mesa/nouveau Product: Wine Version: 1.9.16 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: randrik(a)mail.ru Distribution: --- After upgrading wine to ver. 1.9.18 I noticed strange speed regression. After bisecting wine I found this commit was source of it: first bad commit: [b62f4139eda58e8e25cbc58864fcea2599a20e97] wined3d: Swizzle D3DCOLOR attributes in the GLSL FFP replacement when necessary I'm using nv92 (GeForce 8800 GS) video card with relatively new kernel (4.8.0-rc7-x64+) and 32-bit Slackware OS with many manual updates, including git Mesa drivers. Initially I blamed mesa for speed regression, or my specific build of it, but after testing Mesa 12.0.3 and seeing same very low speed there I tried wine bisect first. May be there is interplay between some bugs, or nouveau simply can't handle slightly different kind of load. But most other tests in this benchmark works fine, and older 3DMark2000 also speedy. I tried to make apitrace of this issue but under apitrace both good and bad commits played 'car chase' scene (low/high detail) smoothly. Without apitrace running bad commit mostly slows down to 0-1 fps even on low detail scene. Compressed traces are at https://cloud.mail.ru/public/75Mf/fFuSprBh9 Bug still present in current git head (post 1.9.19). -- 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.

1 4

[Bug 41907] New: Necropolis: Unimplemented copy from WINED3D_LOCATION_TEXTURE_RGB to WINED3D_LOCATION_TEXTURE_RGB for depth /stencil buffers
by wine-bugs＠winehq.org March 3, 2017

March 3, 2017

https://bugs.winehq.org/show_bug.cgi?id=41907 Bug ID: 41907 Summary: Necropolis: Unimplemented copy from WINED3D_LOCATION_TEXTURE_RGB to WINED3D_LOCATION_TEXTURE_RGB for depth/stencil buffers Product: Wine Version: 1.9.24 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fjfrackiewicz(a)gmail.com Distribution: --- Whenever I run Necropolis I always get the following lines in my terminal output: fixme:d3d:surface_load_location Unimplemented copy from WINED3D_LOCATION_TEXTURE_RGB to WINED3D_LOCATION_TEXTURE_RGB for depth/stencil buffers. err:d3d:wined3d_texture_load Failed to load location (srgb 0). Clean 32-bit prefix in Windows 7 mode with the game running in DX11 mode. Wine-1.9.24-71-g2390219 -- 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.

1 5

[Bug 42506] New: STALKER Shadow of Chernobyl crashes on startup
by wine-bugs＠winehq.org March 3, 2017

March 3, 2017

https://bugs.winehq.org/show_bug.cgi?id=42506 Bug ID: 42506 Summary: STALKER Shadow of Chernobyl crashes on startup Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: leslie_alistair(a)hotmail.com Distribution: --- Created attachment 57384 --> https://bugs.winehq.org/attachment.cgi?id=57384 Log of +tid,dpnet,dplay,loaddll,d3d_shader STALKER Shadow of Chernobyl crashes on startup, just have the nvidia logo screen. 12f5887a2358b4f91a882eeac57c9f1dd28c50ba is the first bad commit commit 12f5887a2358b4f91a882eeac57c9f1dd28c50ba Author: Henri Verbeet <hverbeet(a)codeweavers.com> Date: Tue Feb 21 00:40:03 2017 +0100 wined3d: Parse the shader version in shader_sm4_init(). Signed-off-by: Henri Verbeet <hverbeet(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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.

1 7

[Bug 42504] New: Computemark 2.1 is almost working now with Wine 2.2..
by wine-bugs＠winehq.org March 3, 2017

March 3, 2017

https://bugs.winehq.org/show_bug.cgi?id=42504 Bug ID: 42504 Summary: Computemark 2.1 is almost working now with Wine 2.2.. Product: Wine Version: 2.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rtfss1(a)gmail.com Distribution: --- Created attachment 57382 --> https://bugs.winehq.org/attachment.cgi?id=57382 fixme output Hi, Computemark 2.1 uses compute shaders and seems Wine 2.2 has gained a lot of compute shader support.. So using either Wine 2.2 or Wine Staging 2.2 program launches and tests seems to run altough we get black screen while the test runs.. seeing wine output we see basically this errors using Nvidia 378.13 on a GTX970: 1)Nvidia GLSL Compiler errors: fixme:d3d_shader:print_glsl_info_log 0(31) : error C1101: ambiguous overloaded function reference "texture3DLod(sampler3D, vec3, float)" fixme:d3d_shader:print_glsl_info_log (0) : fpf gpf vpf tpf hpf gp4 fp50 vp50 cp50 gp50 uvec4 texture3DLod(usampler3D, vec3, float) fixme:d3d_shader:print_glsl_info_log (0) : fpf gpf vpf tpf hpf gp4 fp50 vp50 cp50 gp50 ivec4 texture3DLod(isampler3D, vec3, float) fixme:d3d_shader:print_glsl_info_log (0) : vec4 texture3DLod(sampler3D, vec3, float) 2)lots of repeated fixme like: fixme:d3d11:d3d11_immediate_context_CSSetShaderResources iface 0x15c18c, start_slot 0, view_count 2, views 0x33fd10 stub! fixme:d3d11:d3d11_immediate_context_CSSetUnorderedAccessViews Ignoring initial counts. So seems if texture3DLod is fixed and maybe _CSSetShaderResources stub implemented maybe we will have ComputeMark more or less working.. 3)also when DXBC parser can't parse some DX bytecode: fixme:d3d11:skip_dword_unknown Skipping 4 unknown DWORDs: fixme:d3d11:skip_dword_unknown 0xab2742ec fixme:d3d11:skip_dword_unknown 0x2f3269de fixme:d3d11:skip_dword_unknown 0x610001ec fixme:d3d11:skip_dword_unknown 0xf81b8396 fixme:d3d11:skip_dword_unknown Skipping 1 unknown DWORDs: fixme:d3d11:skip_dword_unknown 0x00000001 fixme:d3d11:shdr_handler Unhandled chunk "RDEF". fixme:d3d11:skip_dword_unknown Skipping 1 unknown DWORDs: fixme:d3d11:skip_dword_unknown 0x00000008 fixme:d3d11:skip_dword_unknown Skipping 1 unknown DWORDs: fixme:d3d11:skip_dword_unknown 0x00000008 fixme:d3d11:shdr_handler Unhandled chunk "STAT". fixme:d3d_shader:shader_sm4_read_instruction_modifier Unhandled modifier 0x80000142. fixme:d3d_shader:shader_sm4_read_instruction_modifier Unhandled modifier 0x00155543. fixme:d3d_shader:shader_sm4_read_instruction_modifier Unhandled modifier 0x80000142. fixme:d3d_shader:shader_sm4_read_instruction_modifier Unhandled modifier 0x00155543. I attach a fixme log but for example a GLSL compute shader thant Nvidia can't compile is: fixme:d3d_shader:shader_glsl_validate_link Program 2 link status invalid. fixme:d3d_shader:shader_glsl_dump_program_source Shader 1: fixme:d3d_shader:shader_glsl_dump_program_source GL_SHADER_TYPE: GL_COMPUTE_SHADER. fixme:d3d_shader:shader_glsl_dump_program_source GL_COMPILE_STATUS: 0. fixme:d3d_shader:shader_glsl_dump_program_source fixme:d3d_shader:shader_glsl_dump_program_source #version 150 fixme:d3d_shader:shader_glsl_dump_program_source #extension GL_ARB_gpu_shader5 : enable fixme:d3d_shader:shader_glsl_dump_program_source #extension GL_ARB_shader_bit_encoding : enable fixme:d3d_shader:shader_glsl_dump_program_source #extension GL_ARB_shader_image_load_store : enable fixme:d3d_shader:shader_glsl_dump_program_source #extension GL_ARB_shader_image_size : enable fixme:d3d_shader:shader_glsl_dump_program_source #extension GL_ARB_shading_language_packing : enable fixme:d3d_shader:shader_glsl_dump_program_source #extension GL_ARB_texture_cube_map_array : enable fixme:d3d_shader:shader_glsl_dump_program_source #extension GL_ARB_texture_query_levels : enable fixme:d3d_shader:shader_glsl_dump_program_source #extension GL_ARB_uniform_buffer_object : enable fixme:d3d_shader:shader_glsl_dump_program_source #extension GL_EXT_gpu_shader4 : enable fixme:d3d_shader:shader_glsl_dump_program_source #extension GL_EXT_texture_array : enable fixme:d3d_shader:shader_glsl_dump_program_source #extension GL_ARB_compute_shader : enable fixme:d3d_shader:shader_glsl_dump_program_source layout(std140) uniform block_cs_cb0 { vec4 cs_cb0[1]; }; fixme:d3d_shader:shader_glsl_dump_program_source uniform sampler3D cs_sampler0; fixme:d3d_shader:shader_glsl_dump_program_source uniform sampler3D cs_sampler1; fixme:d3d_shader:shader_glsl_dump_program_source writeonly uniform image3D cs_image0; fixme:d3d_shader:shader_glsl_dump_program_source vec4 R0; fixme:d3d_shader:shader_glsl_dump_program_source vec4 R1; fixme:d3d_shader:shader_glsl_dump_program_source vec4 tmp0; fixme:d3d_shader:shader_glsl_dump_program_source vec4 tmp1; fixme:d3d_shader:shader_glsl_dump_program_source layout(local_size_x = 8, local_size_y = 4, local_size_z = 4) in; fixme:d3d_shader:shader_glsl_dump_program_source void main() fixme:d3d_shader:shader_glsl_dump_program_source { fixme:d3d_shader:shader_glsl_dump_program_source R0.xyz = (ivec3(gl_GlobalInvocationID).xyz); fixme:d3d_shader:shader_glsl_dump_program_source R0.w = (uintBitsToFloat(0u)); fixme:d3d_shader:shader_glsl_dump_program_source R0.xyz = (texelFetch(cs_sampler0, floatBitsToInt(R0).xyz, floatBitsToInt(R0).w).xyz); fixme:d3d_shader:shader_glsl_dump_program_source R1.xyz = (vec3(ivec3(gl_GlobalInvocationID).xyz)); fixme:d3d_shader:shader_glsl_dump_program_source R0.xyz = (-R0.xyz + R1.xyz); fixme:d3d_shader:shader_glsl_dump_program_source R0.xyz = (R0.xyz + uintBitsToFloat(uvec4(0x3f000000u, 0x3f000000u, 0x3f000000u, 0u)).xyz); fixme:d3d_shader:shader_glsl_dump_program_source R0.xyz = (R0.xyz / cs_cb0[0].xyz); fixme:d3d_shader:shader_glsl_dump_program_source R0.xyzw = (texture3DLod(cs_sampler1, R0.xyz, uintBitsToFloat(0u)).xyzw); fixme:d3d_shader:shader_glsl_dump_program_source imageStore(cs_image0, ivec3(gl_GlobalInvocationID).xyz, R0.xyzw); fixme:d3d_shader:shader_glsl_dump_program_source return; fixme:d3d_shader:shader_glsl_dump_program_source } fixme:d3d_shader:shader_glsl_dump_program_source -- 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.

1 11