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@winehq.org Reporter: luisalvaradox@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
https://bugs.winehq.org/show_bug.cgi?id=44368
Józef Kucia joseph.kucia@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |joseph.kucia@gmail.com
--- Comment #1 from Józef Kucia joseph.kucia@gmail.com --- FIXME messages are not bugs. What problem do you experience?
https://bugs.winehq.org/show_bug.cgi?id=44368
--- Comment #2 from Luis Alvarado luisalvaradox@gmail.com --- The game as seen here https://imgur.com/a/5GenE basically has a lot of graphical issues. It also freezes if I set the value any higher than LOW. My hardware is an Nvidia GTX 1080, 64 GB DDR3, an SSD Samsung 950 Pro and an Intel 6700k. Does this help?
https://bugs.winehq.org/show_bug.cgi?id=44368
--- Comment #3 from Józef Kucia joseph.kucia@gmail.com --- (In reply to Luis Alvarado from comment #2)
The game as seen here https://imgur.com/a/5GenE basically has a lot of graphical issues.
Does it work better if you enable CSMT?
https://bugs.winehq.org/show_bug.cgi?id=44368
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|d3d_shader:print_glsl_info_ |Fallout 4 has graphical |log and multiple shader |issues |errors |
https://bugs.winehq.org/show_bug.cgi?id=44368
tokktokk fdsfgs@krutt.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |fdsfgs@krutt.org
https://bugs.winehq.org/show_bug.cgi?id=44368
Józef Kucia joseph.kucia@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Fixed by SHA1| |dd0ea0a61463db83c647a9367ca | |61e2b69a98eb3 Status|UNCONFIRMED |RESOLVED
--- Comment #4 from Józef Kucia joseph.kucia@gmail.com --- The issue shouldn't occur when CSMT is enabled. CSMT is enabled by default since Wine 3.2.
https://bugs.winehq.org/show_bug.cgi?id=44368
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #5 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 3.7.
-
wine-bugs＠winehq.org