Hype The Time Quest Regression

SpawnHappyJake · Post by **SpawnHappyJake** » Tue Jan 31, 2012 12:24 am

There's an old Ubisoft game called "Hype the Time Quest".

For many Wine versions, Wine could not get past the Hype installer. It would go up to 117% and fail. Then a version came where if you unchecked the DirectX check, the install would work (or maybe that's all you had to do to begin with). But the game would fail to start with an error about MaiD3Dvr_bleu.exe. Then a Wine version came where the game actually worked, but needed a dinput override. And eventually a Wine version came where you didn't need to uncheck the the software test or do the override, and the game worked. Ok the exact chronological ordering might have been off a little, but that's more or less it.

Now we're back at square one with Wine 1.4 rc1. The installer fails without unchecking the software test. If you do uncheck it, I get the same old MaiDvr_bleu.exe error when I try to start the game.

To be more specific, Wine 1.3.29 was one of the first versions that could run Hype, but it needed the dinput override. Back in 1.3.29 you did have to uncheck that DirectX software test to keep the installer from failing.

It'd be sad to see functionality that's been so hard for Wine to obtain be lost and frozen that way in the next stable. So I hope you guys put it back before 1.4 is released.

Note: Wine has never been able to show the pre-game videos in Hype. But it did get the actual game running quite well. When I showed a friend the game working in Wine he said that Wine was running Hype more stably than one of the Windows versions did. Casting a fire spell crashed that Windows version he was talking about (95?), but Wine handled it.

And I did have the 1.4 Gecko installed when I was doing this.

So...helpful details....

I'm running Linux Mint 11 64-bit (yeah, haven't taken the time to upgrade, isn't that sad?), obviously I'm taking about Wine version 1.4 rc1, I'm running Hype in a completely clean prefix with the exception of Gecko being installed (that implies no Zeckensack's Glide wrapper), I'm running Hype in D3D mode rather than 3DFX mode (which becomes an option in the presence of Zeckensack's), Wine output in terminal says there was an unhandled fault on read access to memory and later gives a list of deferred stuff (those two things are a resurrection of how Wine used to not be able to run Hype - seems to be the same bug resurrected), and it's really the same old bug.

For example, I used to get this error back when Wine couldn't run Hype but could get past the installer the first time: https://lh5.googleusercontent.com/-CeRQ ... 0Error.png

Same error nowadays, except the bottom paragraph saying to report the bug isn't in the message any more and now there's a cool "Details" button in the error message. Who put that in; it's pretty cool? So I used the details button and got the backtrace and put it here: http://pastebin.com/7srywFKG.

Because people usually ask, here's my hardware info:

Dell XPS 8300
Intel i7-2600 processor 64-bit @3.4 GHz
Winbond Motherboard
8 gigs of SODIMM DDR3 RAM @ 1333 MHz, 4 two-gig sticks, only 4 slots
Winbond A03 BIOS
[SB X-Fi Xtreme Audio] CA0110-IBG (sound card)
ATI Redwood [Radeon HD 5670] (graphics card)

But mind you, last time we had this bug, it did not work on my laptop either (haven't tried laptop + Hype + Wine 1.4 rc 1 yet). So I really don't think it's a hardware issue. Especially given the bugs that Wine fixed to make it work. It has worked on my hardware in the past with earlier Wine versions, and now it isn't working on that same hardware with 1.4 rc1.

I'm also using the same installation and version of Linux now as when it was working.

If you want more details, see my entries in the AppDB: http://appdb.winehq.org/objectManager.p ... ngId=66769
http://appdb.winehq.org/objectManager.p ... ngId=66907

I give lots of detail there and shortcuts to lots of screenshots.

Hope this gets working again. You've done it once. You can do it again.

Jake

Andrew Fenn · Post by **Andrew Fenn** » Tue Jan 31, 2012 12:46 am

Hi Jake,

I'd link you to wiki but it seems to be down at the moment. Basically the
best thing you can do for an issue where something stopped working is to
use "git bisect" to help you figure out exactly which commit the regression
was introduced in. This will make it much much quicker for your problem to
be fixed.

Here is a tutorial on how to use git bisect http://webchick.net/node/99 and
I am assuming you already know how to use git, wine and compile it etc. If
not then perhaps it's best to wait for the wine wiki to come back up and
figure out how to do that first.

Regards,
Andrew

On Tue, Jan 31, 2012 at 12:24 PM, SpawnHappyJake
<[email protected]>wrote:

There's an old Ubisoft game called "Hype the Time Quest".

For many Wine versions, Wine could not get past the Hype installer. It
would go up to 117% and fail. Then a version came where if you unchecked
the DirectX check, the install would work (or maybe that's all you had to
do to begin with). But the game would fail to start with an error about
MaiD3Dvr_bleu.exe. Then a Wine version came where the game actually worked,
but needed a dinput override. And eventually a Wine version came where you
didn't need to uncheck the the software test or do the override, and the
game worked. Ok the exact chronological ordering might have been off a
little, but that's more or less it.

Now we're back at square one with Wine 1.4 rc1. The installer fails
without unchecking the software test. If you do uncheck it, I get the same
old MaiDvr_bleu.exe error when I try to start the game.

To be more specific, Wine 1.3.29 was one of the first versions that could
run Hype, but it needed the dinput override. Back in 1.3.29 you did have to
uncheck that DirectX software test to keep the installer from failing.

It'd be sad to see functionality that's been so hard for Wine to obtain be
lost and frozen that way in the next stable. So I hope you guys put it back
before 1.4 is released.

Note: Wine has never been able to show the pre-game videos in Hype. But it
did get the actual game running quite well. When I showed a friend the game
working in Wine he said that Wine was running Hype more stably than one of
the Windows versions did. Casting a fire spell crashed that Windows version
he was talking about (95?), but Wine handled it.

And I did have the 1.4 Gecko installed when I was doing this.

So...helpful details....

I'm running Linux Mint 11 64-bit (yeah, haven't taken the time to upgrade,
isn't that sad?), obviously I'm taking about Wine version 1.4 rc1, I'm
running Hype in a completely clean prefix with the exception of Gecko being
installed (that implies no Zeckensack's Glide wrapper), I'm running Hype in
D3D mode rather than 3DFX mode (which becomes an option in the presence of
Zeckensack's), Wine output in terminal says there was an unhandled fault on
read access to memory and later gives a list of deferred stuff (those two
things are a resurrection of how Wine used to not be able to run Hype -
seems to be the same bug resurrected), and it's really the same old bug.

For example, I used to get this error back when Wine couldn't run Hype but
could get past the installer the first time:
https://lh5.googleusercontent.com/-CeRQ ... 0Error.png

Same error nowadays, except the bottom paragraph saying to report the bug
isn't in the message any more and now there's a cool "Details" button in
the error message. Who put that in; it's pretty cool? So I used the details
button and got the backtrace and put it here: http://pastebin.com/7srywFKG
.

Because people usually ask, here's my hardware info:

Dell XPS 8300
Intel i7-2600 processor 64-bit @3.4 GHz
Winbond Motherboard
8 gigs of SODIMM DDR3 RAM @ 1333 MHz, 4 two-gig sticks, only 4 slots
Winbond A03 BIOS
[SB X-Fi Xtreme Audio] CA0110-IBG (sound card)
ATI Redwood [Radeon HD 5670] (graphics card)

But mind you, last time we had this bug, it did not work on my laptop
either (haven't tried laptop + Hype + Wine 1.4 rc 1 yet). So I really don't
think it's a hardware issue. Especially given the bugs that Wine fixed to
make it work. It has worked on my hardware in the past with earlier Wine
versions, and now it isn't working on that same hardware with 1.4 rc1.

I'm also using the same installation and version of Linux now as when it
was working.

If you want more details, see my entries in the AppDB:
http://appdb.winehq.org/objectManager.p ... ngId=66769

http://appdb.winehq.org/objectManager.p ... ngId=66907

I give lots of detail there and shortcuts to lots of screenshots.

Hope this gets working again. You've done it once. You can do it again.

Jake

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-us ... hment.html>

SpawnHappyJake · Post by **SpawnHappyJake** » Tue Jan 31, 2012 12:57 am

My bad. Forgot to set Windows version to NT 4.0.

However, I still need to use the native dinput, whereas at one point the Wine dinput was sufficient, if I'm remembering right.

And furthermore, Wine isn't consistently running Hype. Sometimes it crashes when it tries to start the game. (After you click "Play"). When it crashes I get that bleu error again.

And still no intro videos.

When I nicely exit Hype (hit the exit button in Hype), I come back to a properly-resolutioned desktop. But if I rudely kill Hype by using a keybinding to bring up gnome-system-monitor, which then makes the panel accessable, and then right-click and close Hype from the panel, my resolution does not correct itself. I'm guessing it's supposed to be that way, but just wanted to make sure.

Thanks for the reply, Andrew.

Jake

Post by **dimesio** » Tue Jan 31, 2012 8:54 am

SpawnHappyJake wrote: However, I still need to use the native dinput, whereas at one point the Wine dinput was sufficient, if I'm remembering right.

Run a regression test and file a bug. http://wiki.winehq.org/RegressionTesting

File bugs for the other problems, too, if none are already filed.

You've been around here long enough to know that bugs are filed on bugzilla, not the forum.

jjmckenzie · Post by **jjmckenzie** » Tue Jan 31, 2012 11:06 am

On Tue, Jan 31, 2012 at 6:54 AM, dimesio <[email protected]> wrote:

SpawnHappyJake wrote:
However, I still need to use the native dinput, whereas at one point the Wine dinput was sufficient, if I'm remembering right.

Run a regression test and file a bug. http://wiki.winehq.org/RegressionTesting

When you file the regression bug please add in the version of Wine
that did work (last known version...)

And the regression test may take a little while.

I'm going to start to beat on Wine 1.4-rc1 with the programs that I
use for testing.

James