I've just got a brand new Matrox Mystique. GP2 framerates improve
considerably, but I have found a huge problem. Sometimes, when you press
ESC, the game just crashes and you have to reboot. It does that when you
want to skip the introduction, or when you go from a driving session to the
menus. A friend of mine has the same problem.
Has anybody else found out the same thing?
Any solutions?
>I've just got a brand new Matrox Mystique. GP2 framerates improve
>considerably, but I have found a huge problem. Sometimes, when you press
>ESC, the game just crashes and you have to reboot. It does that when you
>want to skip the introduction, or when you go from a driving session to the
>menus. A friend of mine has the same problem.
>Has anybody else found out the same thing?
yes.
None, except for the "skip the introduction" thing...use the "gp2 -nointro"
command, and that gets beyond the intro-to-game hang.
I wish Matrox would step up and address this problem, as it seems to be a
common complaint...at first I thought it was just me (and spent considerable
amount of time troubleshooting), but from the various posts over the past two
months, it's apparent that Matrox is the culprit. Too bad, 'cause otherwise
it's a great card.
John Wehman
Quoted text (16 lines)
>>I've just got a brand new Matrox Mystique. GP2 framerates improve >>considerably, but I have found a huge problem. Sometimes, when you press >>ESC, the game just crashes and you have to reboot. It does that when you >>want to skip the introduction, or when you go from a driving session to the >>menus. A friend of mine has the same problem. >>Has anybody else found out the same thing? >yes. >>Any solutions? >None, except for the "skip the introduction" thing...use the "gp2 -nointro" >command, and that gets beyond the intro-to-game hang. >I wish Matrox would step up and address this problem, as it seems to be a >common complaint...at first I thought it was just me (and spent considerable >amount of time troubleshooting), but from the various posts over the past two >months, it's apparent that Matrox is the culprit. Too bad, 'cause otherwise >it's a great card. >John WehmanOk hi everyone. I'm new here but i have the solution :-)))
1. I send e-mail to Matrox and they told me that it should be a new bios
update coming soon which fixes the problem!
2. But they didn't read themselves the manuals of the board. Anyway do
this:
There are in the CD-ROM with the drivers the programs vbetsr.exe and
vbesetup.exe
run them before you run the game (or put them into the autoexec.bat) and
the problems are gone!! :-)


































