http://bugs.winehq.org/show_bug.cgi?id=21310
Summary: motocross madness crashing since 1.1.35 Product: Wine Version: 1.1.35 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: Brunoooh@laposte.net
Hi,
sorry for reporting something "out of the ordinary" and I'm waisting some of your time
my personnal aim is to run Microsoft's Motocross Madness (the 1st one) within a virtual computer (sorry... I'm a great fan of this game and as years passes more and more GPUs and OSs are uncompatible)
because it has a check for a 3D card before launching it's impossible to use in a windows virtual machine... but thanks to you Wine devs I'm able to use it within an Ubuntu VM
actually I was able :(
emulation as never been perfect : perfct menus but ingame textures are completely wrong (a mix of very flashy colors for the area and only black for the player) but the game was launching and somebody knowing the game could play it
but since the last Wine upgrade the game can't launch (black screen then a windows like text box telling me to report the crash if it doesn't crash the same in a real windows OS
I'm sorry if this is irrelevent and if my explanations are quite confused
Any help or tip is welcomed and if I can give you more details just tell me what to look for and I'll send it to you
PS : I had to roll back Wine version, synaptics only offered me 1.0.6 version : I did and the game went back to buggy but working emulation ;)
http://bugs.winehq.org/show_bug.cgi?id=21310
Nikolay Sivov bunglehead@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|motocross madness crashing |motocross madness crashing |since 1.1.35 | Severity|blocker |normal
--- Comment #1 from Nikolay Sivov bunglehead@gmail.com 2010-01-10 10:47:23 --- Attach a crash log as a plain text file. Are you able to build Wine from sources?
PS : I had to roll back Wine version, synaptics only offered me 1.0.6 version :
Never used Ubuntu actually, interesting what this 1.0.6 is supposed to mean. Officially vanilla Wine from 1.0 stable branch has only 1.0.0 and 1.0.1 releases. Please specify output of 'wine --version' for this 1.0.6 package.
http://bugs.winehq.org/show_bug.cgi?id=21310
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression
--- Comment #2 from Jeff Zaroyko jeffz@jeffz.name 2010-01-10 13:15:26 --- Does the demo have the same problem?
http://download.microsoft.com/download/motorcross/Trial/1.0/WIN98/EN-US/Msmc...
http://bugs.winehq.org/show_bug.cgi?id=21310
Wylda wylda@volny.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |wylda@volny.cz
--- Comment #3 from Wylda wylda@volny.cz 2010-01-11 16:46:23 --- (In reply to comment #2)
Does the demo have the same problem?
Well, full game have an into movie and game crashes just before the playing of this movie.
Demo doesn't have intro movie, so you have to be really careful if you want to repeat this problem with _demo_. It's better to switch to windowed mode. Good case would be window with picture "Motocross maddness"+crash message and bad case would be black window+crash message.
1. Confirming, please consider UNCONFIRMED->NEW and KEYWORDS: +DOWNLOAD
2. I did a regression test between 1.1.34 and 1.1.35:
0e270bbd226c34bd2831673c1c546f8db76b0487 is first bad commit commit 0e270bbd226c34bd2831673c1c546f8db76b0487 Author: Henri Verbeet hverbeet@codeweavers.com Date: Mon Dec 14 20:49:52 2009 +0100
wined3d: Send window messages through the swapchain before sending them to the application.
:040000 040000 82a4d1078cd0ab3156aba80508dbd3d830b37dee 4cd0938c1bf4a1e0f3bb09ba258447f0fe5a98ed M dlls
3. If i remember correctly this commit should already be fixed for other reported games (right Henri?), but it looks like, it still fails for this older game. This game still fails under 1.1.35 and 1.1.36.
4. Revert of this patch after git checkout makes that problem go away.
5. Adding author of this patch to CC.
--private keyword: bisected
Correct download link: http://www.filefront.com/listing/pub2/Motocross-Madness/Official-Files/Demos
http://bugs.winehq.org/show_bug.cgi?id=21310
Wylda wylda@volny.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |hverbeet@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=21310
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download Status|UNCONFIRMED |NEW Ever Confirmed|0 |1
--- Comment #4 from Austin English austinenglish@gmail.com 2010-01-11 18:12:30 --- Confirming.
http://bugs.winehq.org/show_bug.cgi?id=21310
--- Comment #5 from Brunoooh@laposte.net 2010-01-13 14:33:02 --- sorry, the roll back version was 1.0.1, my mystake (for some reason synaptics tells me 1.0.1 ubuntu6, I got confused while reporting the bug)
I've also tried why the demo : it gets the same problems as the full game + the text is misplaced making it harder to tweak the game
as it seems I'm reporting two different things : - the game no longer launching since 1.1.35 - the game working but with wrong textures with previous versions
would you like me to post a screenshot of the texture problem ?
http://bugs.winehq.org/show_bug.cgi?id=21310
--- Comment #6 from Wylda wylda@volny.cz 2010-01-14 02:29:31 --- (In reply to comment #5)
as it seems I'm reporting two different things :
This is generaly bad, to put two things in one bug report.
would you like me to post a screenshot of the texture problem ?
As above - this one is about crashing (that's what is bisected) and not texture problem, so let's wait for Henri's free time.
http://bugs.winehq.org/show_bug.cgi?id=21310
--- Comment #7 from Henri Verbeet hverbeet@gmail.com 2010-01-16 09:19:40 --- If this uses ddraw, it's likely a duplicate of bug 21025. (Which was marked as FIXED, but isn't. Seiklus working is mostly a matter of getting lucky.) What does the backtrace look like?
http://bugs.winehq.org/show_bug.cgi?id=21310
--- Comment #8 from Brunoooh@laposte.net 2010-02-18 04:28:54 --- sorry for being so noob, but what is a backtrace ?
http://bugs.winehq.org/show_bug.cgi?id=21310
--- Comment #9 from Jeff Zaroyko jeffz@jeffz.name 2010-02-18 05:30:21 --- There is an example here, http://wiki.winehq.org/Backtraces They are usually printed to the terminal when your program crashes.
http://bugs.winehq.org/show_bug.cgi?id=21310
--- Comment #10 from Brunoooh@laposte.net 2010-02-19 12:27:07 --- Created an attachment (id=26309) --> (http://bugs.winehq.org/attachment.cgi?id=26309) halted
http://bugs.winehq.org/show_bug.cgi?id=21310
--- Comment #11 from Brunoooh@laposte.net 2010-02-19 12:28:59 --- here's everything I got :
Backtracing for thread 0014 in process 000e (C:\windows\system32\services.exe): Backtrace: =>0 0xb7fe242e (0x0064e8c8) 1 0x7b83b40e ReadFile+0x1fe() in kernel32 (0x0064e928) 2 0x7ee27735 in rpcrt4 (+0x47735) (0x0064e968) 3 0x7ee1ceba in rpcrt4 (+0x3ceba) (0x0064e9b8) 4 0x7ee1d3c1 RPCRT4_ReceiveWithAuth+0x81() in rpcrt4 (0x0064ea38) 5 0x7ee21cef in rpcrt4 (+0x41cef) (0x0064ea98) 6 0x7bc6f964 call_thread_func+0xc() in ntdll (0x0064eaa8) 7 0x7bc6fb40 call_thread_entry_point+0x70() in ntdll (0x0064eb78) 8 0x7bc781fb in ntdll (+0x681fb) (0x0064f3b8) 9 0xb7e664ff start_thread+0xbf() in libpthread.so.0 (0x0064f4b8) 10 0xb7de049e __clone+0x5e() in libc.so.6 (0x00000000)
Backtracing for thread 0010 in process 000e (C:\windows\system32\services.exe): Backtrace: =>0 0xb7fe242e (0x0054e688) 1 0x7bc765d5 NTDLL_wait_for_multiple_objects+0x275() in ntdll (0x0054e8a8) 2 0x7bc768d2 NtWaitForMultipleObjects+0x62() in ntdll (0x0054e8d8) 3 0x7b869f92 WaitForMultipleObjectsEx+0x102() in kernel32 (0x0054ea18) 4 0x7ee28c54 in rpcrt4 (+0x48c54) (0x0054ea58) 5 0x7ee1fac1 in rpcrt4 (+0x3fac1) (0x0054ea98) 6 0x7bc6f964 call_thread_func+0xc() in ntdll (0x0054eaa8) 7 0x7bc6fb40 call_thread_entry_point+0x70() in ntdll (0x0054eb78) 8 0x7bc781fb in ntdll (+0x681fb) (0x0054f3b8) 9 0xb7e664ff start_thread+0xbf() in libpthread.so.0 (0x0054f4b8) 10 0xb7de049e __clone+0x5e() in libc.so.6 (0x00000000)
Backtracing for thread 000f in process 000e (C:\windows\system32\services.exe): Backtrace: =>0 0xb7fe242e (0x0033fa28) 1 0x7bc765d5 NTDLL_wait_for_multiple_objects+0x275() in ntdll (0x0033fc48) 2 0x7bc768d2 NtWaitForMultipleObjects+0x62() in ntdll (0x0033fc78) 3 0x7b869f92 WaitForMultipleObjectsEx+0x102() in kernel32 (0x0033fdb8) 4 0x7b86a05b WaitForSingleObjectEx+0x3b() in kernel32 (0x0033fdd8) 5 0x7ee58e44 RPC_MainLoop+0x74() in services (0x0033fe18) 6 0x7ee5cf5a main+0x31a() in services (0x0033fe88) 7 0x7ee64364 in services (+0x14364) (0x0033feb8) 8 0x7b858415 in kernel32 (+0x48415) (0x0033fee8) 9 0x7bc6f964 call_thread_func+0xc() in ntdll (0x0033fef8) 10 0x7bc6fb40 call_thread_entry_point+0x70() in ntdll (0x0033ffc8) 11 0x7bc4c7fa in ntdll (+0x3c7fa) (0x0033ffe8) 12 0xb7e8e05d wine_call_on_stack+0x1d() in libwine.so.1 (0x00000000) 0xb80cf42e: jmp 0xb80cf423
Backtracing for thread 0017 in process 0011 (C:\windows\system32\winedevice.exe): Backtrace: =>0 0xb80cf430 (0x0074e8b8) 1 0x7ec4ebeb in libdbus-1.so.3 (+0x2cbeb) (0x0074e8d8) 2 0x7ec46cd7 in libdbus-1.so.3 (+0x24cd7) (0x0074e918) 3 0x7ec44ebf in libdbus-1.so.3 (+0x22ebf) (0x0074e938) 4 0x7ec2f92e in libdbus-1.so.3 (+0xd92e) (0x0074e968) 5 0x7ec30617 in libdbus-1.so.3 (+0xe617) (0x0074e998) 6 0x7ec80fd0 in mountmgr.sys (+0x10fd0) (0x0074ea98) 7 0x7bc6f964 call_thread_func+0xc() in ntdll (0x0074eaa8) 8 0x7bc6fb40 call_thread_entry_point+0x70() in ntdll (0x0074eb78) 9 0x7bc781fb in ntdll (+0x681fb) (0x0074f3b8) 10 0xb7f534ff start_thread+0xbf() in libpthread.so.0 (0x0074f4b8) 11 0xb7ecd49e __clone+0x5e() in libc.so.6 (0x00000000)
Backtracing for thread 0016 in process 0011 (C:\windows\system32\winedevice.exe): Backtrace: =>0 0xb80cf42e (0x0064e4a8) 1 0x7bc765d5 NTDLL_wait_for_multiple_objects+0x275() in ntdll (0x0064e6c8) 2 0x7bc768d2 NtWaitForMultipleObjects+0x62() in ntdll (0x0064e6f8) 3 0x7b869f92 WaitForMultipleObjectsEx+0x102() in kernel32 (0x0064e838) 4 0x7b86a00a WaitForMultipleObjects+0x3a() in kernel32 (0x0064e858) 5 0x7ed6fbde wine_ntoskrnl_main_loop+0x38e() in ntoskrnl (0x0064e9f8) 6 0x7ee65441 in winedevice (+0x5441) (0x0064ea48) 7 0x7ee39d8c in advapi32 (+0x29d8c) (0x0064ea98) 8 0x7bc6f964 call_thread_func+0xc() in ntdll (0x0064eaa8) 9 0x7bc6fb40 call_thread_entry_point+0x70() in ntdll (0x0064eb78) 10 0x7bc781fb in ntdll (+0x681fb) (0x0064f3b8) 11 0xb7f534ff start_thread+0xbf() in libpthread.so.0 (0x0064f4b8) 12 0xb7ecd49e __clone+0x5e() in libc.so.6 (0x00000000)
Backtracing for thread 0013 in process 0011 (C:\windows\system32\winedevice.exe): Backtrace: =>0 0xb80cf42e (0x0054e9a8) 1 0x7b83b40e ReadFile+0x1fe() in kernel32 (0x0054ea08) 2 0x7ee3bef9 in advapi32 (+0x2bef9) (0x0054ea98) 3 0x7bc6f964 call_thread_func+0xc() in ntdll (0x0054eaa8) 4 0x7bc6fb40 call_thread_entry_point+0x70() in ntdll (0x0054eb78) 5 0x7bc781fb in ntdll (+0x681fb) (0x0054f3b8) 6 0xb7f534ff start_thread+0xbf() in libpthread.so.0 (0x0054f4b8) 7 0xb7ecd49e __clone+0x5e() in libc.so.6 (0x00000000)
Backtracing for thread 0012 in process 0011 (C:\windows\system32\winedevice.exe): Backtrace: =>0 0xb80cf42e (0x0033f848) 1 0x7bc765d5 NTDLL_wait_for_multiple_objects+0x275() in ntdll (0x0033fa68) 2 0x7bc768d2 NtWaitForMultipleObjects+0x62() in ntdll (0x0033fa98) 3 0x7b869f92 WaitForMultipleObjectsEx+0x102() in kernel32 (0x0033fbd8) 4 0x7b86a00a WaitForMultipleObjects+0x3a() in kernel32 (0x0033fbf8) 5 0x7ee3b899 in advapi32 (+0x2b899) (0x0033fe38) 6 0x7ee3bb41 StartServiceCtrlDispatcherW+0x121() in advapi32 (0x0033fe68) 7 0x7ee64787 wmain+0x47() in winedevice (0x0033fe98) 8 0x7ee656a2 in winedevice (+0x56a2) (0x0033feb8) 9 0x7b858415 in kernel32 (+0x48415) (0x0033fee8) 10 0x7bc6f964 call_thread_func+0xc() in ntdll (0x0033fef8) 11 0x7bc6fb40 call_thread_entry_point+0x70() in ntdll (0x0033ffc8) 12 0x7bc4c7fa in ntdll (+0x3c7fa) (0x0033ffe8) 13 0xb7f7b05d wine_call_on_stack+0x1d() in libwine.so.1 (0x00000000) 0xb7f3342e: jmp 0xb7f33423
Backtracing for thread 0019 in process 0018 (C:\windows\system32\explorer.exe): Backtrace: =>0 0xb7f3342e (0x0033f0c8) 1 0x7bc765d5 NTDLL_wait_for_multiple_objects+0x275() in ntdll (0x0033f2e8) 2 0x7bc768d2 NtWaitForMultipleObjects+0x62() in ntdll (0x0033f318) 3 0x7b869f92 WaitForMultipleObjectsEx+0x102() in kernel32 (0x0033f458) 4 0x7e8c918e X11DRV_MsgWaitForMultipleObjectsEx+0xee() in winex11 (0x0033f488) 5 0x7ed24d68 in user32 (+0x94d68) (0x0033f4b8) 6 0x7e9aaeb9 in user.exe16 (+0xaeb9) (0x0033f4f8) 7 0x7ecef538 GetMessageW+0x128() in user32 (0x0033f538) 8 0x7ee620eb manage_desktop+0x48b() in explorer (0x0033f748) 9 0x7ee62f5a wWinMain+0x5ea() in explorer (0x0033fe18) 10 0x7ee64d25 wmain+0xa5() in explorer (0x0033fe98) 11 0x7ee64c72 in explorer (+0x14c72) (0x0033feb8) 12 0x7b858415 in kernel32 (+0x48415) (0x0033fee8) 13 0x7bc6f964 call_thread_func+0xc() in ntdll (0x0033fef8) 14 0x7bc6fb40 call_thread_entry_point+0x70() in ntdll (0x0033ffc8) 15 0x7bc4c7fa in ntdll (+0x3c7fa) (0x0033ffe8) 16 0xb7ddf05d wine_call_on_stack+0x1d() in libwine.so.1 (0x00000000) 0xb80a442e: jmp 0xb80a4423
Backtracing for thread 001d in process 001c (C:\windows\system32\winedbg.exe): Backtrace: =>0 0xb80a442e (0x0033f6a8) 1 0x7bc765d5 NTDLL_wait_for_multiple_objects+0x275() in ntdll (0x0033f8c8) 2 0x7bc768d2 NtWaitForMultipleObjects+0x62() in ntdll (0x0033f8f8) 3 0x7b869f92 WaitForMultipleObjectsEx+0x102() in kernel32 (0x0033fa38) 4 0x7e82318e X11DRV_MsgWaitForMultipleObjectsEx+0xee() in winex11 (0x0033fa68) 5 0x7ebb6d68 in user32 (+0x96d68) (0x0033fa98) 6 0x7e904eb9 in user.exe16 (+0x14eb9) (0x0033fad8) 7 0x7eb81538 GetMessageW+0x128() in user32 (0x0033fb18) 8 0x7eb4f0e1 in user32 (+0x2f0e1) (0x0033fb68) 9 0x7eb4f38f DialogBoxParamW+0x8f() in user32 (0x0033fb88) 10 0x7ee2d021 display_crash_dialog+0x101() in winedbg (0x0033fbb8) 11 0x7ee43507 dbg_active_auto+0x77() in winedbg (0x0033fe18) 12 0x7ee4883e main+0x54e() in winedbg (0x0033fe88) 13 0x7ee4d824 in winedbg (+0x2d824) (0x0033feb8) 14 0x7b858415 in kernel32 (+0x48415) (0x0033fee8) 15 0x7bc6f964 call_thread_func+0xc() in ntdll (0x0033fef8) 16 0x7bc6fb40 call_thread_entry_point+0x70() in ntdll (0x0033ffc8) 17 0x7bc4c7fa in ntdll (+0x3c7fa) (0x0033ffe8) 18 0xb7f5005d wine_call_on_stack+0x1d() in libwine.so.1 (0x00000000)
I've also posted a screenshot of halted MCM.exe
http://bugs.winehq.org/show_bug.cgi?id=21310
--- Comment #12 from Jeff Zaroyko jeffz@jeffz.name 2010-02-19 16:27:18 --- next time attach output as a file if it's more than 10 lines or so.
What you've pasted shows the wine crash dialog plus everything else which is uninteresting. All you should need to do is click ok to the dialog and then the backtrace should be printed. Otherwise run the program with winedbg which is the first set of instructions on the linked page.
http://bugs.winehq.org/show_bug.cgi?id=21310
--- Comment #13 from Wylda wylda@volny.cz 2010-02-28 04:31:34 --- Created an attachment (id=26536) --> (http://bugs.winehq.org/attachment.cgi?id=26536) console log from wine-1.1.39-163-g583f0f0
(In reply to comment #7)
If this uses ddraw, it's likely a duplicate of bug 21025. (Which was marked as FIXED, but isn't. Seiklus working is mostly a matter of getting lucky.) What does the backtrace look like?
Hi Henri, here you are. (taken from full version)
http://bugs.winehq.org/show_bug.cgi?id=21310
--- Comment #14 from Luke gaming4jc2@yahoo.com 2010-03-13 15:23:40 --- Created an attachment (id=26789) --> (http://bugs.winehq.org/attachment.cgi?id=26789) Launch + Backtrace on wine 1.1.40...
Decided to get my old CD out and give it a shot. It's actually hard to get a good backtrace from this program because it cannot attach to the process. Also, the program closes itself and opens a new instance in memory causing a quick change of PIDs. Attached is my launch attempt + bt all log.
http://bugs.winehq.org/show_bug.cgi?id=21310
--- Comment #15 from Jeff Zaroyko jeffz@jeffz.name 2010-03-13 15:31:40 --- (In reply to comment #14)
Created an attachment (id=26789)
--> (http://bugs.winehq.org/attachment.cgi?id=26789) [details]
Launch + Backtrace on wine 1.1.40...
9 0x7ee1f02a display_crash_dialog+0x10a() in winedbg (0x0033fb68)
Is the crash dialog still on the screen at this point? iirc, you need to acknowledge the dialog and a backtrace should be forthcoming from winedbg.
http://bugs.winehq.org/show_bug.cgi?id=21310
--- Comment #16 from Wylda wylda@volny.cz 2010-03-15 04:55:47 --- (In reply to comment #15)
Is the crash dialog still on the screen at this point? iirc, you need to acknowledge the dialog and a backtrace should be forthcoming from winedbg.
Hi Jeff, and is it really necessary to use debuger, when the game can be simply run and provides clean backtrace like in comment #13? Thanks for answer (will be useful for my next bugreports).
Anyway, the problem is bisected, so it is just waiting for Henri's free time ;)
http://bugs.winehq.org/show_bug.cgi?id=21310
Dan Kegel dank@kegel.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dank@kegel.com
--- Comment #17 from Dan Kegel dank@kegel.com 2010-03-15 22:29:54 --- (wine itself runs winedbg to generate those backtraces...)
http://bugs.winehq.org/show_bug.cgi?id=21310
--- Comment #18 from Henri Verbeet hverbeet@gmail.com 2010-03-16 13:26:26 --- Does http://bugs.winehq.org/attachment.cgi?id=26843 (attached to bug 21426) make any difference?
http://bugs.winehq.org/show_bug.cgi?id=21310
--- Comment #19 from Wylda wylda@volny.cz 2010-03-17 19:37:35 --- (In reply to comment #18)
Does http://bugs.winehq.org/attachment.cgi?id=26843 (attached to bug 21426) make any difference?
Hi Henri, yes this patch makes the game to run again. It works for full version and even for demo. Thank you Henri!
BTW: This patch is applicable only to wine-1.1.40-191-g4b5f6ad, there was a reject when trying to apply to wine-1.1.40-224-g0498534.
So when this get applied to git, this bug can be closed. When this happen, i will fill a new bug for weird in-game texture colors (mentioned in AppDB even for version 1.1.17). If you have a time ;) you can check demo for this issue. Console log says:
err:d3d7:IDirect3DDeviceImpl_3_GetRenderState Unexpected texture stage state setup, returning D3DTBLEND_MODULATE - likely erroneous
http://bugs.winehq.org/show_bug.cgi?id=21310
--- Comment #20 from Henri Verbeet hverbeet@gmail.com 2010-03-18 12:01:53 --- Should be fixed by 0838d0ab6491bdc0fb32d0b8715fbb57088b926a.
http://bugs.winehq.org/show_bug.cgi?id=21310
--- Comment #21 from Wylda wylda@volny.cz 2010-03-18 17:12:44 --- (In reply to comment #20)
Should be fixed by 0838d0ab6491bdc0fb32d0b8715fbb57088b926a.
FIXED under wine-1.1.40-263-g93b3ba7. Thank you Henri!
http://bugs.winehq.org/show_bug.cgi?id=21310
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED
--- Comment #22 from Austin English austinenglish@gmail.com 2010-03-18 18:14:04 --- Fixed.
http://bugs.winehq.org/show_bug.cgi?id=21310
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #23 from Alexandre Julliard julliard@winehq.org 2010-03-19 14:10:47 --- Closing bugs fixed in 1.1.41.
http://bugs.winehq.org/show_bug.cgi?id=21310
--- Comment #24 from Brunoooh@laposte.net 2010-03-21 12:05:08 --- Thank you very much for fixing this !
Now back to the other bug concerning that game (Texture bug reported as bug 21748)
http://bugs.winehq.org/show_bug.cgi?id=21310
--- Comment #25 from Brunoooh@laposte.net 2010-04-17 05:56:02 --- Created an attachment (id=27398) --> (http://bugs.winehq.org/attachment.cgi?id=27398) regressing again in 1.1.43 ?
Maybe I did something wrong, but since 1.1.43 (fixing motocross madness texture bug) I get the error message back again (see attachment)
Yet I am surprised as bug 22070 as been closed after successful testing with the latest wine : they couldn't have checked for corrected textures if the game couldn't launch...
So either I did something wrong (any tips ?) than please forgive this comment and close the matter or something has been added later, preventing (again) the game from launching
http://bugs.winehq.org/show_bug.cgi?id=21310
Brunoooh@laposte.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |REOPENED Resolution|FIXED |
--- Comment #26 from Brunoooh@laposte.net 2010-04-17 05:58:02 --- please correct me if it's working elsewhere
http://bugs.winehq.org/show_bug.cgi?id=21310
--- Comment #27 from Brunoooh@laposte.net 2010-04-17 06:09:41 --- Created an attachment (id=27399) --> (http://bugs.winehq.org/attachment.cgi?id=27399) I hope I got the backtrace right this time
http://bugs.winehq.org/show_bug.cgi?id=21310
Brunoooh@laposte.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|1.1.35 |1.1.43
http://bugs.winehq.org/show_bug.cgi?id=21310
--- Comment #28 from Wylda wylda@volny.cz 2010-04-17 09:35:09 --- (In reply to comment #26)
please correct me if it's working elsewhere
Hi, yes wine-1.1.43 is working with mcm1 for me. I usualy do the retest for bug reports where i am involved. So when i write FIXED, than i did the testing and it's working for me, not like yeee i think this should work somehow ;)
The backtrace looks good, but i can't interpreted ;) Are you sure, that's wine-1.1.43? Check:
1. wine --version 2. Video card and drivers? (nvidia v195.36.15 here) 3. gcc --version (as i noticed some reports about failures with recent gcc)
http://bugs.winehq.org/show_bug.cgi?id=21310
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Version|1.1.43 |1.1.35 Resolution| |FIXED
--- Comment #29 from Jeff Zaroyko jeffz@jeffz.name 2010-04-17 09:50:45 --- This bug was fixed. Do not reopen, file a new bug.
http://bugs.winehq.org/show_bug.cgi?id=21310
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #30 from Jeff Zaroyko jeffz@jeffz.name 2010-04-17 09:51:02 --- Closing fixed.
http://bugs.winehq.org/show_bug.cgi?id=21310
Wylda wylda@volny.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |0838d0ab6491bdc0fb32d0b8715 | |fbb57088b926a Regression SHA1| |0e270bbd226c34bd2831673c1c5 | |46f8db76b0487
https://bugs.winehq.org/show_bug.cgi?id=21310
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net Component|-unknown |directx-d3d