Tomb Raider 2 problem with ATI Rage Pro (XPert@Play)
David Putnam
No matter what settings I use in the setup dialog
I still get stray polygons that flash on the screen
I also get weird color flashes.
The red lifebar and blue breathbar at the top of the screen
have visible lines drawn back to the top left corner from each of the
vertices of the rectangle.
It looks similar to problem I got when I tried to
run GLHexen II with that OpenGL->Direct3D wrapper.
It's just not quite as bad.
TombRaider 2 is still playble but it gets anoying after a while.
Is anyone else using an Xpert@ card to play this game.
It looks great running it triple buffered at 1024x768x32 apart from the
glitches.
I tried setting it to lower resolutions and the problem was the same.
On the box for this game it states specifically that it suports Direct 3D
on ATI cards. I wonder if anyone at CORE/EIDOS ever tested it with a Rage
Pro ATI board?
Is there a possiblity this is a driver problem that ATI needs to fix?
I've run other D3D games and haven't seen any problems(Jedi Knight,
Mageslayer, Terracide)
Martin Pazderka
>No matter what settings I use in the setup dialog
>I still get stray polygons that flash on the screen
>I also get weird color flashes.
>The red lifebar and blue breathbar at the top of the screen
>have visible lines drawn back to the top left corner from each of the
>vertices of the rectangle.
Hi David, this is Martin from Austria.
I bought TR2 a few days ago and have got exactly the same problem when
I run it on my XPert@Work (PCI, 4Megs).
After trying all the settings in the setup dialog box - without
success - I have contacted both the UK and US Eidos support via mail,
but got no response yet.
As you wrote, other D3D games are OK.
I hope Core/Eidos will release a patch for this bug as it is very
annoying.
CU, Martin
--
Martin Pazderka
http://www.pazi.home.pages.de/
Wayne
In article <MPG.ee60e72a...@news.inconnect.com>,
dputnamN...@allencomm.com says...
> No matter what settings I use in the setup dialog
> I still get stray polygons that flash on the screen
> I also get weird color flashes.
> The red lifebar and blue breathbar at the top of the screen
> have visible lines drawn back to the top left corner from each of the
> vertices of the rectangle.
>
I had exactly the same porblem with the game on our Compaq 4840 (which
has the Rage Pro chipset). I ended up taking the game back. Sugsequently,
I found updated rage pro drivers (on the Psgnosis site, not ATI!), which
were required to play G-Police. The updated drivers fixed G-Police, maybe
they'll fix TR II. Try www.psygnosis.com
--
Wayne Hixson
whi...@jetcity.com
Techtite
Aside from the age-old "download latest drivers from ATI's web site"
tip, there is always the eventual specific ATI Rage patch promised by
the box. Actually, the box should say (if it doesn't) that specific
patches will be made for the cards specified, though until now there is
only Direct3D "universal" support of 3D acceleration. Also, sometimes
your card has features that the default setup does not activate;
re-check the TR2 setup screen and fiddle with the check boxes and see if
that helps at all. I have a new Xpert@Play as my latest 2D/3D card
though it's connected to my year-old Monster 3D and I think that's what
Direct3D is using, so I doubt I can be of much help. However, last year
when Eidos/Core said that 3Dfx and Rendition patches would be out soon
after the game, it took them less than a month to release it, so it
shouldn't be too long this time.
David Putnam
I thought I should post the answer I found to my question.
> No matter what settings I use in the setup dialog
> I still get stray polygons that flash on the screen
> I also get weird color flashes.
> The red lifebar and blue breathbar at the top of the screen
> have visible lines drawn back to the top left corner from each of the
> vertices of the rectangle.
>
> It looks similar to problem I got when I tried to
> run GLHexen II with that OpenGL->Direct3D wrapper.
> It's just not quite as bad.
>
> TombRaider 2 is still playble but it gets anoying after a while.
>
> Is anyone else using an Xpert@ card to play this game.
> It looks great running it triple buffered at 1024x768x32 apart from the
> glitches.
I take it back it won't run triple buffered at 1024x768x32
It runs great at double buffered 1024x768x16
but I almost like it better at 800x600x32 triple buffered.
> I tried setting it to lower resolutions and the problem was the same.
>
> On the box for this game it states specifically that it suports Direct 3D
> on ATI cards. I wonder if anyone at CORE/EIDOS ever tested it with a Rage
> Pro ATI board?
>
> Is there a possiblity this is a driver problem that ATI needs to fix?
>
It is most definitly a driver problem.
I found a set of divers in a self extracting executable that someone
over in comp.sys.ibm.hardware.video pointed to at
http://sl5.atitech.ca/hidden/
get the file w95-2237.exe
This is a newer set of drivers for Xpert@Play
These drivers work great with Tomb Raider 2
The Rookie
On Wed, 26 Nov 1997 23:39:58 -0800, whi...@nospam.jetcity.com (Wayne)
wrote:
>In article <MPG.ee60e72a...@news.inconnect.com>,
>dputnamN...@allencomm.com says...
>> No matter what settings I use in the setup dialog
>> I still get stray polygons that flash on the screen
>> I also get weird color flashes.
>> The red lifebar and blue breathbar at the top of the screen
>> have visible lines drawn back to the top left corner from each of the
>> vertices of the rectangle.
>>
>[Clip]
>
>I had exactly the same porblem with the game on our Compaq 4840 (which
>has the Rage Pro chipset). I ended up taking the game back. Sugsequently,
>I found updated rage pro drivers (on the Psgnosis site, not ATI!), which
>were required to play G-Police. The updated drivers fixed G-Police, maybe
>they'll fix TR II. Try www.psygnosis.com
>
>--
>Wayne Hixson
>whi...@jetcity.com
I also noticed this fenomena on my Viper V330 which uses the Riva 128
chip. Maybe it's not a card problem but a direct 3d problem????
Steve Roberts
On Thu, 27 Nov 1997 02:13:40 -0700, dpu...@SPAMNOTinconnect.com
(David Putnam) wrote:
>It is most definitly a driver problem.
>I found a set of divers in a self extracting executable that someone
>over in comp.sys.ibm.hardware.video pointed to at
>http://sl5.atitech.ca/hidden/
>get the file w95-2237.exe
>
>This is a newer set of drivers for Xpert@Play
>These drivers work great with Tomb Raider 2
Not on my system they don't! I get all the symptoms described at the
top of this thread - big blocks of white appearing, incorrect
shadowing, transparent foreground rocks etc.
However, I have heard that a new set of DirectX drivers were sent to
Microsoft for certification last week, so hopefully it will only be a
matter of time before they are released.
Steve
*** Views expressed are my own and should not be taken to represent BBC policy.
*** Visit the Doctor Who Restoration Team Homepage for info on BBC restorations.
*** http://ourworld.compuserve.com/homepages/steveroberts/restorat.htm
Bill
I have the exact problem with my Xpert@play, 8 mg card. I bought
blade runner and myth at the same time as tombraider2. Both of those
games run flawlessly. A shame.
bill
On Wed, 26 Nov 1997 10:46:49 -0700, dputnamN...@allencomm.com
(David Putnam) wrote:
>No matter what settings I use in the setup dialog
>I still get stray polygons that flash on the screen
>I also get weird color flashes.
>The red lifebar and blue breathbar at the top of the screen
>have visible lines drawn back to the top left corner from each of the
>vertices of the rectangle.
>
>It looks similar to problem I got when I tried to
>run GLHexen II with that OpenGL->Direct3D wrapper.
>It's just not quite as bad.
>
>TombRaider 2 is still playble but it gets anoying after a while.
>
>Is anyone else using an Xpert@ card to play this game.
>It looks great running it triple buffered at 1024x768x32 apart from the
>glitches.
>I tried setting it to lower resolutions and the problem was the same.
>
>On the box for this game it states specifically that it suports Direct 3D
>on ATI cards. I wonder if anyone at CORE/EIDOS ever tested it with a Rage
>Pro ATI board?
>
>Is there a possiblity this is a driver problem that ATI needs to fix?
>