[Bug 40291] New: Borderlands crashes when forced DirectX 9 using -DX9
https://bugs.winehq.org/show_bug.cgi?id=40291 Bug ID: 40291 Summary: Borderlands crashes when forced DirectX 9 using -DX9 Product: Wine Version: 1.9.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3dx9 Assignee: wine-bugs(a)winehq.org Reporter: vblanton(a)gmail.com Distribution: --- Created attachment 53931 --> https://bugs.winehq.org/attachment.cgi?id=53931 backtrace from commandline, lsusb, lspci Borderlands runs decent on my Fedora/MacBook Pro/Intel 3000 without any arguments (~20fps). However, I read online that one could achieve significantly faster frame-rates by forcing Borderlands to only use DirectX 9 with "-DX9" "wine Borderlands.exe -DX9" This, however causes the game to crash I thought this might be interesting, valuable information, or perhaps even fixable. -- 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=40291 super_man(a)post.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |super_man(a)post.com --- Comment #1 from super_man(a)post.com --- I think your log shows bug 39570 also bug 23807. But I don't know the reason for the crash. -- 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=40291 --- Comment #2 from Vlad Blanton <vblanton(a)gmail.com> --- thanks super_man I don't know about the first bug (39570), but the second one (23807) shows up running the game normally, so I don't think that is it. I commented on that bug. it seems that it isn't an acute issue anywhere so not going to be fixed 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=40291 tokktokk <fdsfgs(a)krutt.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fdsfgs(a)krutt.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.
https://bugs.winehq.org/show_bug.cgi?id=40291 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WORKSFORME CC| |focht(a)gmx.net Status|UNCONFIRMED |RESOLVED --- Comment #3 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, I can't reproduce this with Wine 1.9.4 the bug was reported with. I've tested with Nvidia gpu / driver and Intel gpu (via Mesa). It's likely that OP had a broken hw/sw setup. Resolving 'WORKSFORME' here. --- snip --- $ pwd /home/focht/.wine/drive_c/Games/Borderlands/Game/Binaries $ wine ./Borderlands.exe -DX9 ... --- snip --- Tidbit #1: There is a crash on startup if 'PhysX' is missing. Some scene installers/repacked "game of the year" editions I've tested with don't bundle it. Before you ask ... same "test environment" as OP: backtrace shows "Borderlands.GOTY.Edition-KaOs". Go figure. --- snip --- ... 0024:Call msvcr90._wcsicmp(08d99b40 L"..\\WillowGame\\Config\\WillowEngine.ini",09313b50 L"..\\WillowGame\\Config\\WillowEngine.ini") ret=0042f8ac 0024:Ret msvcr90._wcsicmp() retval=00000000 ret=0042f8ac ... 0024:Call msvcr90._wcsicmp(05f44c00 L"bDisablePhysXHardwareSupport",08e97dc0 L"bDisablePhysXHardwareSupport") ret=0042f8ac 0024:Ret msvcr90._wcsicmp() retval=00000000 ret=0042f8ac ... 0024:Call KERNEL32.LoadLibraryW(01b521f8 L"PhysXLocal/PhysXLoader.dll") ret=00aae416 ... 0024:Ret PE DLL (proc=0x9a21400,module=0x9a20000 L"PhysXLoader.dll",reason=PROCESS_ATTACH,res=(nil)) retval=1 ... 0024:Ret KERNEL32.LoadLibraryW() retval=09a20000 ret=00aae416 ... 0024:Call KERNEL32.LoadLibraryA(01db5710 "PhysXLoader.dll") ret=018b3fe4 ... 0024:Ret KERNEL32.LoadLibraryA() retval=09a20000 ret=018b3fe4 ... 0024:Call KERNEL32.GetProcAddress(09a20000,01ebc5c6 "NxGetCookingLib") ret=018b40bb 0024:Ret KERNEL32.GetProcAddress() retval=09a2a540 ret=018b40bb ... 0024:Call advapi32.RegOpenKeyExA(80000002,09a2c3fc "Software\\NVIDIA Corporation\\PhysX\\Runtimes",00000000,00020219,0287f344) ret=09a2a2e8 ... 0024:Ret advapi32.RegOpenKeyExA() retval=00000002 ret=09a2a2e8 ... 0024:Call advapi32.RegOpenKeyExA(80000002,09a2c428 "Software\\Ageia Technologies",00000000,00020219,0287f344) ret=09a2a2e8 ... 0024:Ret advapi32.RegOpenKeyExA() retval=00000002 ret=09a2a2e8 0024:trace:seh:raise_exception code=c0000005 flags=0 addr=0xaae5fa ip=00aae5fa tid=0024 0024:trace:seh:raise_exception info[0]=00000000 0024:trace:seh:raise_exception info[1]=00000000 0024:trace:seh:raise_exception eax=00000000 ebx=00000000 ecx=0287fbec edx=08e088f0 esi=08da75c0 edi=08e088f0 0024:trace:seh:raise_exception ebp=00110cf4 esp=0287fba8 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00010216 0024:trace:seh:call_stack_handlers calling handler at 0x19956b8 code=c0000005 flags=0 0024:trace:seh:call_stack_handlers handler at 0x19956b8 returned 1 0024:trace:seh:call_stack_handlers calling handler at 0x198dd94 code=c0000005 flags=0 0024:trace:seh:call_stack_handlers handler at 0x198dd94 returned 1 0024:trace:seh:call_stack_handlers calling handler at 0x198dde6 code=c0000005 flags=0 0024:trace:seh:call_stack_handlers handler at 0x198dde6 returned 1 0024:trace:seh:call_stack_handlers calling handler at 0x17db95f code=c0000005 flags=0 0024:Call msvcr90._except_handler4_common(01f131c0,017db538,0287fb50,0287fe90,0287f884,0287f83c) ret=017db97f 0024:trace:seh:_except_handler4_common exception c0000005 flags=0 at 0xaae5fa handler=0x17db95f 0x287f884 0x287f83c cookie=32eac016 scope table=0x1e95840 cookies=-2/0,-44/0 0024:trace:seh:_except_handler4_common level 0 prev -2 filter 0x13922d7 0024:Call KERNEL32.CreateFileW(01fe6638 L"C:\\users\\focht\\My Documents\\My Games\\Borderlands\\Binaries\\..\\WillowGame\\Logs\\unreal-v4875-2020.04.28-23.34.52.dmp",40000000,00000000,00000000,00000002,00000080,00000000) ret=0138cd29 0024:Call ntdll._wcsicmp(01fe6638 L"C:\\users\\focht\\My Documents\\My Games\\Borderlands\\Binaries\\..\\WillowGame\\Logs\\unreal-v4875-2020.04.28-23.34.52.dmp",7b05508a L"CONIN$") ret=7b00f05e 0024:Ret ntdll._wcsicmp() retval=ffffffcb ret=7b00f05e ... --- snip --- -> 'winetricks -q physx' fixes this. Tidbit #2: Comment #1 referenced bug #23807 due to: --- snip --- fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24) WINED3DFORMAT! fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the format lookup table --- snip --- These messages are harmless and indicate no problem. $ wine --version wine-1.9.4 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=40291 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #4 from Austin English <austinenglish(a)gmail.com> --- Closing. -- 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