https://bugs.winehq.org/show_bug.cgi?id=40328
Bug ID: 40328 Summary: Rayman 3 Crashes loading 2nd level. Product: Wine Version: 1.8.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: SolisX007@yahoo.com Distribution: ---
Rayman 3 Crashes loading 2nd level with wine-1.8.1.
BTW: Rayman 3 works fine with wine-1.2.1.
https://bugs.winehq.org/show_bug.cgi?id=40328
--- Comment #1 from Lunknown SolisX007@yahoo.com --- Created attachment 53989 --> https://bugs.winehq.org/attachment.cgi?id=53989 Rayman 3 Backtrace
https://bugs.winehq.org/show_bug.cgi?id=40328
--- Comment #2 from Lunknown SolisX007@yahoo.com --- Also Rayman 3 also crashes on wine-1.9.5.
https://bugs.winehq.org/show_bug.cgi?id=40328
super_man@post.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |super_man@post.com
--- Comment #3 from super_man@post.com --- The crash points to this function
http://source.winehq.org/git/wine.git/blob/6bc0ce26a853b51f11958545bfa5570bd...
https://bugs.winehq.org/show_bug.cgi?id=40328
--- Comment #4 from Lunknown SolisX007@yahoo.com --- Is that the fix? So should i replace that file with the one your link?
https://bugs.winehq.org/show_bug.cgi?id=40328
--- Comment #5 from super_man@post.com --- (In reply to Lunknown from comment #4)
Is that the fix? So should i replace that file with the one your link?
That points to a location something is broken. It needs some correction which isn't done yet.
https://bugs.winehq.org/show_bug.cgi?id=40328
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression
--- Comment #6 from Austin English austinenglish@gmail.com ---
0000002d (D) Z:\mnt\sda3\Games\PC\R3\program files\Ubi Soft\Rayman3\Rayman3.exe
Are you running this from windows?
Can you please run a regression test: http://wiki.winehq.org/RegressionTesting
Also, please retest in 1.9.6.
https://bugs.winehq.org/show_bug.cgi?id=40328
--- Comment #7 from Lunknown SolisX007@yahoo.com --- Hello Austin English,
No i'm not running it from windows. It's just my storage drive.
I'll try wine-1.9.6 the report back.
https://bugs.winehq.org/show_bug.cgi?id=40328
--- Comment #8 from Nikolay Sivov bunglehead@gmail.com --- If it was installed using Windows and then you run it with Wine, reusing existing installation, that's not supported in general. First try to install this game with Wine.
https://bugs.winehq.org/show_bug.cgi?id=40328
--- Comment #9 from Henri Verbeet hverbeet@gmail.com --- This sounds fairly similar to 29663 and 29878.
https://bugs.winehq.org/show_bug.cgi?id=40328
--- Comment #12 from Nikolay Sivov bunglehead@gmail.com --- (In reply to Lunknown from comment #10)
Hello Nikolay Sivov,
I installed Rayman 3 using wine not windows. The Rayman 3 CD-Rom has the directory program files in the first disc.
I see, ignore my comment 8 then.
https://bugs.winehq.org/show_bug.cgi?id=40328
--- Comment #10 from Lunknown SolisX007@yahoo.com --- Hello Nikolay Sivov,
I installed Rayman 3 using wine not windows. The Rayman 3 CD-Rom has the directory program files in the first disc.
https://bugs.winehq.org/show_bug.cgi?id=40328
--- Comment #11 from Lunknown SolisX007@yahoo.com --- Hello Everyone,
Ok i tested Rayman 3 on wine-1.9.6 and it still crashes at the same spot. I will try and do a regression test hopefully today.
https://bugs.winehq.org/show_bug.cgi?id=40328
--- Comment #13 from Lunknown SolisX007@yahoo.com --- Hello Everyone,
Okay i tried to do a regression test on Rayman 3 but i ran into a problem.
wine-1.3.37 has the crash
wine-1.3.22 does not have the crash.
However all wine-versions from 1.3.23 - 1.3.36 have a crash either in the middle or near the end of the stage. I will attached a backtrace of the crash for version 1.3.30. Any ideas how i can continue?
https://bugs.winehq.org/show_bug.cgi?id=40328
--- Comment #14 from Lunknown SolisX007@yahoo.com --- Created attachment 54035 --> https://bugs.winehq.org/attachment.cgi?id=54035 1.3.30 Rayman 3 backtrace
https://bugs.winehq.org/show_bug.cgi?id=40328
--- Comment #15 from Austin English austinenglish@gmail.com --- (In reply to Lunknown from comment #13)
Hello Everyone,
Okay i tried to do a regression test on Rayman 3 but i ran into a problem.
wine-1.3.37 has the crash
wine-1.3.22 does not have the crash.
However all wine-versions from 1.3.23 - 1.3.36 have a crash either in the middle or near the end of the stage. I will attached a backtrace of the crash for version 1.3.30. Any ideas how i can continue?
Bisect 1.3.36 and 1.3.37 and find the commit that fixes the crash in the first level. Cherry pick that commit before building (and revert before running git bisect good/bad or git will complain) to find the other regression.
https://bugs.winehq.org/show_bug.cgi?id=40328
--- Comment #16 from Lunknown SolisX007@yahoo.com --- Hello Austin English,
Do you have intructions on doing this?
Cherry pick that commit before building (and revert before running git bisect good/bad or git will complain) to find the other regression.
https://bugs.winehq.org/show_bug.cgi?id=40328
--- Comment #17 from Austin English austinenglish@gmail.com --- (In reply to Lunknown from comment #16)
Hello Austin English,
Do you have intructions on doing this?
Cherry pick that commit before building (and revert before running git bisect good/bad or git will complain) to find the other regression.
https://wiki.winehq.org/Reverse_Regression_Testing
has some more info. What you'll want to do is a second bisect, between 1.3.36 and 1.3.37. Your goal is to find the commit that fixes the crash mid/end of level (but before the second crash). So, do:
git bisect start git bisect good wine-1.3.36 # crashes earlier git bisect bad wine-1.3.37 # crashes later ./configure --disable-tests make -j5
then test Rayman. If it crashes loading the second level, consider it bad, if it crashes in first level, it's good.
That will eventually give you some commit, let's call it fixed_sha1.
To then find the original regression, do: git bisect reset git bisect start git bisect good 1.3.22 git bisect bad 1.3.37
as normal. Now, it gets a bit different. For each build, you'll want to do: git show $fixed_sha1 | patch -p1 ./configure --disable tests make -j5 git checkout -f # resets your tree to normal # test rayman here git bisect good/bad # as normal
hope that helps. Ping me on IRC (austin987) if you need more help, or ask on the forums.
https://bugs.winehq.org/show_bug.cgi?id=40328
Wylda wylda@volny.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |wylda@volny.cz
--- Comment #18 from Wylda wylda@volny.cz --- Created attachment 54438 --> https://bugs.winehq.org/attachment.cgi?id=54438 rever of wine-1.3.22-193-g68b15bc on top of wine-1.9.9
If i revert wine-1.3.22-193-g68b15bc, Rayman 3 runs fine. I got into 3rd level.
Without this revert Rayman 3 always crashes for me in first level, when flying rabbit pickup first red "ball". So without rever i could not even reach level 2.
Thus this bug could be fixed in wine-1.9.9 and we are back at bug 29878, or better bug 29663, as i don't have problem with sound, but crash on first level.
https://bugs.winehq.org/show_bug.cgi?id=40328
--- Comment #19 from Lunknown SolisX007@yahoo.com --- Hello Everyone,
Yeah there is a new bug in wine-.1.9.9. For the old bug i had done a regression test and in had gotton this
b00e7039c5fcaa613b9776a38fe60bb697146b42 dc1aeeb2f843e9a09c77f3433267c0e46cb1134e 9c112996d01dd5af735d8a16710aac3fbd52023b
https://bugs.winehq.org/show_bug.cgi?id=40328
--- Comment #20 from Wylda wylda@volny.cz ---
Yeah there is a new bug in wine-.1.9.9.
Which bug? You need to describe it and if that's truly new, than you need a new bug report (one bug per bug report).
The regression test is not useful in this state. You need to say, before this commit game behave like this... and with this commit there is this problem.
Putting 3 commits here, when no-one knows how to replicate the issue for each of these commit isn't helpful. And notice, that each bug report has only _one_ field for "Regression SHA1:"
https://bugs.winehq.org/show_bug.cgi?id=40328
--- Comment #21 from Lunknown SolisX007@yahoo.com --- Hello Wilda,
The new regression i was talking about in wine-1.9.9 is the one you mentioned the crash in the first level.
I guess i will have to do a little work on the regression test.
https://bugs.winehq.org/show_bug.cgi?id=40328
--- Comment #22 from Wylda wylda@volny.cz ---
I guess i will have to do a little work on the regression test.
Best thing would be, if you could take clean wine-1.9.9 and apply patch from comment 18. Please report back, what works and what does not work for you in Rayman 3.
https://bugs.winehq.org/show_bug.cgi?id=40328
--- Comment #23 from Lunknown SolisX007@yahoo.com --- Hello Wylda,
Ok i tried the patch on wine-1.9.9. I see that ubisoft logo does not show up but i can hear the sound. And the screen freezes up at the Rayman 3 menu also the sound can be heard in the background.
This was tested with the nouveau driver 1.0.12.
https://bugs.winehq.org/show_bug.cgi?id=40328
--- Comment #24 from Wylda wylda@volny.cz --- Created attachment 54448 --> https://bugs.winehq.org/attachment.cgi?id=54448 crash log from vanilla wine-1.9.9 & nouveau
This was tested with the nouveau driver 1.0.12.
OK, you forced me to boot into nouveau ;) I always used nvidia's proprietary, i.e. v352.79.
So here is my recipe, which makes Rayman 3 working even with nouveau: * 32bit wine-1.9.9 + patch from comment 18 * nvidia GTX970, nouveau v1.0.12 * current Debian Stretch 64bit + multiarch 32bit * GOG version of Rayman 3 * R3_Setup_DX8.exe: 1280x960x16, textures quality 16bit * KDE: resolution changed from 1920x1200 to 1280x960 * winecfg -> Libraries: no existing overrides
With above, i can finish very first level with picking up the "red balls". Second level loads correctly and i can play the second level.
If i do _not_ use patch from comment 18, i get the crash with nvidia proprietary and even with nouveau on the Rayman's first level. Nvidia proprietary crashes reliably on first red ball, nouveau usually allows to pickup 3 or 4 red balls.
Console log from vanilla wine-1.9.9 & nouveau.
https://bugs.winehq.org/show_bug.cgi?id=40328
--- Comment #25 from Lunknown SolisX007@yahoo.com --- Hello Wylda,
I would have to assume there is something wrong with the wine-1.9.9 i compiled. I tried the wine-1.9.9 from the downloads section on both 32bit and 64bit systems on both rayman 3 plays until you get a few red orb then crashes.
https://bugs.winehq.org/show_bug.cgi?id=40328
--- Comment #26 from Lunknown SolisX007@yahoo.com --- Hello Wylda,
Tried to using the wine-1.9.9 patch on wine-git. I got the same results as earlier. When i reverted your patch the game loaded up fine.
Tested on
Slackware Current 32bit 03-26-2016. Resolution Tested 800x600 windowed. Nvidia GeForce 430 GT using nouveau driver 1.0.12. AMD X255 3.1gz CPU. 2 gig Cosair memory.
https://bugs.winehq.org/show_bug.cgi?id=40328
--- Comment #27 from Lunknown SolisX007@yahoo.com --- Hello Everyone,
I want to try to revert the last 3 patches. When i try to do
bash-4.3$ git show b00e7039c5fcaa613b9776a38fe60bb697146b42 | patch -p1 -R patching file dlls/msi/action.c Hunk #1 succeeded at 501 (offset -23 lines). Hunk #2 succeeded at 1581 (offset 1 line). Hunk #3 succeeded at 5248 (offset 332 lines). Hunk #4 succeeded at 5357 (offset 329 lines). Hunk #5 succeeded at 7744 (offset 451 lines). Hunk #6 succeeded at 7852 (offset 452 lines). Hunk #7 succeeded at 7989 with fuzz 1 (offset 461 lines). patching file dlls/msi/custom.c Hunk #2 FAILED at 1164. Hunk #3 succeeded at 1218 with fuzz 1 (offset -28 lines). Hunk #4 FAILED at 1262. 2 out of 4 hunks FAILED -- saving rejects to file dlls/msi/custom.c.rej can't find file to patch at input line 205 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |diff --git a/dlls/msi/events.c b/dlls/msi/events.c |index 785d98a..d42ac5b 100644 |--- a/dlls/msi/events.c |+++ b/dlls/msi/events.c -------------------------- File to patch:
What is going wrong?
https://bugs.winehq.org/show_bug.cgi?id=40328
mrdeathjr28@yahoo.es changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mrdeathjr28@yahoo.es
https://bugs.winehq.org/show_bug.cgi?id=40328
winetest@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest@luukku.com
--- Comment #28 from winetest@luukku.com --- To me it looks like that only a small patch is needed to get this game working. The bugs that are mentioned earlier are marked fixed.
This bug could be somehow related to bug 22303. It has a commit id. And the commit touches same area of code.
https://bugs.winehq.org/show_bug.cgi?id=40328
--- Comment #29 from Lunknown SolisX007@yahoo.com --- This issue seems to fixed in wine-2.4.
https://bugs.winehq.org/show_bug.cgi?id=40328
Lunknown SolisX007@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED
--- Comment #30 from Lunknown SolisX007@yahoo.com --- Fixed.
https://bugs.winehq.org/show_bug.cgi?id=40328
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #31 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 2.5.
-
wine-bugs＠winehq.org