January 2018 - Wine-Bugs - list.winehq.org

[Bug 41209] The Magic School Bus Explores the Solar System: Error message asking for the game to be reinstalled

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=41209 Michael Stefaniuc <mstefani(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |2.0.x -- 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.

Jan. 17, 2018

[Bug 44365] armel build fails: selected processor does not support `strd r4,[sp]' in ARM mode

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44365 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1| |5e3534ee411a8c5baea5022705e | |ac0e3c7f3cc70 CC| |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.

Jan. 17, 2018

[Bug 44365] armel build fails: selected processor does not support `strd r4,[sp]' in ARM mode

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44365 Jens Reyer <jre.winesim(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jre.winesim(a)gmail.com Keywords| |regression -- 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.

Jan. 17, 2018

[Bug 44368] d3d_shader:print_glsl_info_log and multiple shader errors

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44368 Józef Kucia <joseph.kucia(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |joseph.kucia(a)gmail.com --- Comment #1 from Józef Kucia <joseph.kucia(a)gmail.com> --- FIXME messages are not bugs. What problem do you experience? -- 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.

Jan. 17, 2018

[Bug 44368] New: d3d_shader:print_glsl_info_log and multiple shader errors

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44368 Bug ID: 44368 Summary: d3d_shader:print_glsl_info_log and multiple shader errors Product: Wine Version: 3.0-rc6 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: luisalvaradox(a)gmail.com Distribution: --- When starting Fallout 4 with Wine 3.0 RC6 I found out that the game LITERALLY started. I am able to use it. I was actually expecting it to fail with an error without showing anything, but it just worked, out of the box. I have only tested 2 minutes of it, but here is the output am getting in the terminal just to help along. For lines that repeated themselves many times, I put an approximate amount of lines that showed at the end of the actual line (eg: Showing 100x more lines): 002c:fixme:d3d11:d3d11_device_CreateTexture1D iface 0x8c4f0, desc 0x23cd60, data (nil), texture 0x23ef60 stub! (1000x More Lines) 002c:fixme:d3d11:d3d11_immediate_context_IAGetVertexBuffers Failed to get vertex buffer 16. (500 More Lines) 002c:fixme:d3d11:d3d11_immediate_context_IAGetVertexBuffers Failed to get vertex buffer 17. (500 More Lines) 002c:fixme:d3d11:d3d11_immediate_context_IAGetVertexBuffers Failed to get vertex buffer 18. (500 More Lines) 002c:fixme:d3d11:d3d11_immediate_context_IAGetVertexBuffers Failed to get vertex buffer 19. (500 More Lines) 002c:fixme:d3d11:d3d11_immediate_context_IAGetVertexBuffers Failed to get vertex buffer 20. (500 More Lines) 002c:fixme:d3d11:d3d11_immediate_context_IAGetVertexBuffers Failed to get vertex buffer 21. (500 More Lines) 002c:fixme:d3d11:d3d11_immediate_context_IAGetVertexBuffers Failed to get vertex buffer 22. (500 More Lines) 002c:fixme:d3d11:d3d11_immediate_context_IAGetVertexBuffers Failed to get vertex buffer 23. (500 More Lines) 002c:fixme:d3d11:d3d11_immediate_context_IAGetVertexBuffers Failed to get vertex buffer 24. (500 More Lines) 002c:fixme:d3d11:d3d11_immediate_context_IAGetVertexBuffers Failed to get vertex buffer 25. (500 More Lines) 002c:fixme:d3d11:d3d11_immediate_context_IAGetVertexBuffers Failed to get vertex buffer 26. (500 More Lines) 002c:fixme:d3d11:d3d11_immediate_context_IAGetVertexBuffers Failed to get vertex buffer 27. (500 More Lines) 002c:fixme:d3d11:d3d11_immediate_context_IAGetVertexBuffers Failed to get vertex buffer 28. (500 More Lines) 002c:fixme:d3d11:d3d11_immediate_context_IAGetVertexBuffers Failed to get vertex buffer 29. (500 More Lines) 002c:fixme:d3d11:d3d11_immediate_context_IAGetVertexBuffers Failed to get vertex buffer 30. (500 More Lines) 002c:fixme:d3d11:d3d11_immediate_context_IAGetVertexBuffers Failed to get vertex buffer 31. (500 More Lines) 002c:fixme:d3d11:d3d11_immediate_context_RSSetState Ignoring DepthClipEnable 0. (500 More Lines) 002c:fixme:d3d11:d3d11_immediate_context_RSSetViewports Multiple viewports not implemented. (500 More Lines) 002c:fixme:d3d_shader:print_glsl_info_log 002c:fixme:d3d_shader:print_glsl_info_log ----------- 002c:fixme:d3d_shader:print_glsl_info_log ------------- 002c:fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: "vs_out[10]" might be used before being initialized 002c:fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: "vs_out[11]" might be used before being initialized 002c:fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: "vs_out[12]" might be used before being initialized 002c:fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: "vs_out[13]" might be used before being initialized 002c:fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: "vs_out[14]" might be used before being initialized 002c:fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: "vs_out[15]" might be used before being initialized 002c:fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: "vs_out[16]" might be used before being initialized 002c:fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: "vs_out[17]" might be used before being initialized 002c:fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: "vs_out[18]" might be used before being initialized 002c:fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: "vs_out[19]" might be used before being initialized 002c:fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: "vs_out[1].zw" might be used before being initialized 002c:fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: "vs_out[20]" might be used before being initialized 002c:fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: "vs_out[21]" might be used before being initialized 002c:fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: "vs_out[22]" might be used before being initialized 002c:fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: "vs_out[23]" might be used before being initialized 002c:fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: "vs_out[24]" might be used before being initialized 002c:fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: "vs_out[25]" might be used before being initialized 002c:fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: "vs_out[26]" might be used before being initialized 002c:fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: "vs_out[27]" might be used before being initialized 002c:fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: "vs_out[28]" might be used before being initialized 002c:fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: "vs_out[29]" might be used before being initialized 002c:fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: "vs_out[2]" might be used before being initialized 002c:fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: "vs_out[30]" might be used before being initialized 002c:fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: "vs_out[31]" might be used before being initialized 002c:fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: "vs_out[3]" might be used before being initialized 002c:fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: "vs_out[4]" might be used before being initialized 002c:fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: "vs_out[5]" might be used before being initialized 002c:fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: "vs_out[6]" might be used before being initialized 002c:fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: "vs_out[7]" might be used before being initialized 002c:fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: "vs_out[8]" might be used before being initialized 002c:fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: "vs_out[9]" might be used before being initialized 002c:fixme:d3d_shader:print_glsl_info_log 0(37) : warning C7050: "R3.zw" might be used before being initialized 002c:fixme:d3d_shader:print_glsl_info_log 0(40) : warning C7050: "R6.yzw" might be used before being initialized 002c:fixme:d3d_shader:print_glsl_info_log Fragment info 002c:fixme:d3d_shader:print_glsl_info_log Info log received from GLSL shader #552: 002c:fixme:d3d_shader:print_glsl_info_log Vertex info 002c:fixme:d3d_shader:shader_sm4_read_instruction_modifier Unhandled modifier 0x00155543. (50 More Lines) 002c:fixme:dxgi:dxgi_swapchain_Present Unimplemented sync interval 1 (200 More Lines) 002c:fixme:xinput:XInputSetState (index 0, vibration 0x23e7a0) Stub! 0046:fixme:thread:SetThreadIdealProcessor (0x4408): stub -- 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.

Jan. 17, 2018

[Bug 44367] d2d: FillEllipse/DrawEllipse are not implemented

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44367 --- Comment #4 from Stan <markau0(a)lycos.com> --- Yes, at the bottom of this page https://www.xferrecords.com/products/serum -- 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.

Jan. 17, 2018

[Bug 43995] Uplay - Assassin's Creed 4 Black Flag won't start

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=43995 --- Comment #31 from mi.bar.2001(a)gmail.com --- I've tried to record the stuttering, but the video was laggy and the sound disruption was just inaudible -- 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.

Jan. 17, 2018

[Bug 44367] d2d: FillEllipse/DrawEllipse are not implemented

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44367 Nikolay Sivov <bunglehead(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|d2d1 FillEllipse |d2d: | |FillEllipse/DrawEllipse are | |not implemented -- 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.

Jan. 17, 2018

[Bug 44367] d2d1 FillEllipse

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44367 Nikolay Sivov <bunglehead(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Version|unspecified |3.0-rc6 Ever confirmed|0 |1 --- Comment #3 from Nikolay Sivov <bunglehead(a)gmail.com> --- Alright, thanks. It's definitely not implemented yet. Is this VST plugin available as a free trial version, to test things? -- 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.

Jan. 17, 2018

[Bug 44367] d2d1 FillEllipse

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44367 --- Comment #2 from Stan <markau0(a)lycos.com> --- It happens with Wine 2 and Wine staging 2.21, it's been around for a while. Yes, it doesn't draw some parts of the vst display that I assume depend on FillEllipse and DrawEllipse. -- 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.

Jan. 17, 2018