[Bug 46553] New: The Witcher: Enhanced Edition Director' s Cut has texture issue with builtin d3dx9_35
https://bugs.winehq.org/show_bug.cgi?id=46553 Bug ID: 46553 Summary: The Witcher: Enhanced Edition Director's Cut has texture issue with builtin d3dx9_35 Product: Wine Version: 4.0 Hardware: x86-64 OS: Linux Status: NEW Severity: minor Priority: P2 Component: directx-d3dx9 Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- Created attachment 63424 --> https://bugs.winehq.org/attachment.cgi?id=63424 screenshot Some objects have bright textures when player isn't near to them and look normal when near. Native library helps with this. wine-4.0-230-g78a8445a2a -- 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=46553 --- Comment #1 from Andrey Gusev <andrey.goosev(a)gmail.com> --- Created attachment 63425 --> https://bugs.winehq.org/attachment.cgi?id=63425 +d3dx -- 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=46553 Shmerl <shtetldik(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |shtetldik(a)gmail.com --- Comment #2 from Shmerl <shtetldik(a)gmail.com> --- This also manifest in various flickering and black textures mostly indoors. When using native d3dx9_35 override, the problem goes away. -- 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=46553 --- Comment #3 from Shmerl <shtetldik(a)gmail.com> --- Created attachment 63448 --> https://bugs.winehq.org/attachment.cgi?id=63448 The Witcher save near a fireplace with black flickering textures Move forward and backward while facing the fireplace, and you can see black texture flickering. -- 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=46553 --- Comment #4 from Shmerl <shtetldik(a)gmail.com> --- I also see various errors like this: 0009:fixme:d3dx:d3dx_set_shader_const_state Unexpected param size 4, rows 1, cols 1. ... 0009:fixme:d3dx:ID3DXEffectImpl_ValidateTechnique iface 0x257e1920, technique 0x257aa1a8 semi-stub. ... 0009:fixme:d3dx:d3dx9_base_effect_get_desc partial stub! ... 0009:fixme:d3dx:ID3DXEffectImpl_ValidateTechnique iface 0x25a31990, technique 0x2593dd00 semi-stub. ... 0009:fixme:d3dx:D3DXCreateTextureFromFileInMemoryEx Generation of mipmaps for compressed pixel formats is not implemented yet. ... -- 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=46553 Paul Gofman <gofmanp(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gofmanp(a)gmail.com --- Comment #5 from Paul Gofman <gofmanp(a)gmail.com> --- Created attachment 63478 --> https://bugs.winehq.org/attachment.cgi?id=63478 Handle short parameter length in d3dx_set_shader_const_state(). Does this patch change anything? It is supposed to fix 'Unexpected parameter size' which can potentially affect things, but does not concern texture mipmap generation. -- 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=46553 --- Comment #6 from Andrey Gusev <andrey.goosev(a)gmail.com> --- (In reply to Paul Gofman from comment #5) Still the same just with 'fixme:d3d:state_fillmode Unrecognized fill mode 0.' -- 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=46553 --- Comment #7 from Paul Gofman <gofmanp(a)gmail.com> --- (In reply to Andrey Gusev from comment #6)
(In reply to Paul Gofman from comment #5)
Still the same just with 'fixme:d3d:state_fillmode Unrecognized fill mode 0.'
I think d3d FIXMEs are unlikely related if it works with native d3dx. So the FIXME's for d3dx 'Unexpected parameter size' went away but nothing changed in the picture? -- 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=46553 --- Comment #8 from Andrey Gusev <andrey.goosev(a)gmail.com> --- (In reply to Paul Gofman from comment #7) It looks so. -- 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=46553 --- Comment #9 from Paul Gofman <gofmanp(a)gmail.com> --- Looks like a duplicate of multiple metabugs like Bug #34342, Bug #34658. The game runs out of virtual memory. I could reproduce the crashes. Most of the time out of memory messages precede it, like: --- 0009:err:d3d:wined3d_resource_allocate_sysmem Failed to allocate system memory. --- Game crashes right on loading with native d3dx. It goes further with bultin d3dx, loads level, but only to crash inside the hole as reported earlier. I've tested the game with Wine from Proton which has IMAGE_FILE_LARGE_ADDRESS_AWARE override hack. With the hack turned on the problem goes away. At least I was able to load level and drive the hound around the two areas next to the save without issues (both native and builtin d3dx). -- 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=46553 --- Comment #10 from Paul Gofman <gofmanp(a)gmail.com> --- (In reply to Paul Gofman from comment #9) Please ignore my previous comment (or if someone can delete these 2 then even better). It was meant for a different bug, sorry for the noise. -- 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=46553 Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |patch -- 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=46553 Neko-san <nekoNexus(a)protonmail.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nekoNexus(a)protonmail.ch -- 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=46553 --- Comment #11 from Gijs Vermeulen <gijsvrm(a)gmail.com> --- Still present with wine-10.8-247-ge0bb1dba3d6, reproduced with the save from Comment 3. Native d3dx9 still works around. -- 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.
participants (2)
-
wine-bugs＠winehq.org -
WineHQ Bugzilla