I wonder if any of you remember this happening to anyone else
when the game was /current/ and ye all raiders played the game?
This happens on more current hardware.
(CPU: Multicore)
GPU: GeForce 9600GT (Nvidia)
Driver: GeForce 178.24(2008-10-15) Driver-bundle under WinXP
The Game crashed immediately when level 5 (Kazakhstan) loads.
Since i had no problem up to this level it took me a while to
think to try turning off 'Next generation content'. The game then
plays just fine, and i did the whole level with it off. I later
replayed the end-fight against the Unknown Entity with 'Next
generation content' turned on without problem (and what a
difference having it turned on does!) so i know it only affects
an unknown part at the beginning of that level.
Later in Nepal when landing on the ground after sliding/jumping
the multi-slopes after the plane-wreck the game also crashes. Now
i immediately knew to switched off NextGenContent and could turn
it on again after having killed the 5-6 Mercenaries that are
waiting a little ways further ahead.
I wonder what kind of graphics are used at these two places in
the game that causes it to crash. I have not tried other versions
of the GPU drivers, but have not not had problems with these in
other games that i know of.
--
Nah-ah. I'm staying out of this. ... Now, here's my opinion.
Please followup in the newsgroup.
E-mail address is invalid due to spam-control.
The only issue I recall wer some graphic issues such as a dark ledge
in Bolivia just after the tunnel and jumping to that higher ledge,
where Lara faces the crevice she uses to shimmy over the tunnel.
This was fixed with patch 1.2
I laughed out loud a little later in the Bolivia level when i
came to the entrance of the first archaeological site when ..
"Isn't she beautiful. I'm falling in love all over again."
"You say that to all the ruins."
(Wondering how fun the Crystal Dynamic crew must have had
when they thought up this, and wondering how the Core-people felt
about it.)
But before i found the solution for my problem, among the
things i tried was to reinstall, to a different partition
(default location), and play with ver. 1.0 and i didn't see the
problem there in the beginning of Bolivia. But i found out that
my problem occurs in both 1.0 and 1.2 versions.
But just know, using a search-engine i quickly find that i'm
not the only one with this particular problem i am having. The
following link is to an inquiry about it and the answers links to
many previous ones as well.
<http://forums.eidosgames.com/showthread.php?t=76457>
And they even spell "crash" correctly in the header. ;-)
Great game all the same, just like the quote above allude to.
Note that most of these issues occur with Nvidia video cards.
ATI cards also have issues, but their list of issues seems to be
smaller than the list for Nvidia cards.
The other issues might be running with XP X64 or Vista. I
have ATI card and XP SP3, and just redid Kaz level without any
problems.
Well, I remember that I got no problem with my older Nvidia Driver... so it
is a new problem with the driver... I have to take a look maybe I find the
older driver, so I can test it.
I also got with the new Driver also some problems in other games, where I
had before no problems.
Bye, DUDI.
--
http://www.gamestar.de/community/userpages/j/josches/ (Profil by Gamestar)
http://www.xfire.com/profile/dudi1969/ (Profil by Xfire)
http://www.sysprofile.de/id82547 (MY PC)
I find it... It is the Driver: 178.13
you can find it here:
http://www.nvidia.com/Download/Find.aspx?lang=en-us
search for all drivers, also older an beta.
Than you find an link for an download.
bye, DUDI
Sorry... but it did not help...
I don't know why...
I know that it did work well in the past...
That's strange...
I did send the problem to the Eidos support... since this I wait for an
answer...
Reading some of the problem-reports i find on the net, i can't
find a common thing; different OS's, different cards with
different drivers that were current at the time of the reports.
Maybe Nvidia GPUs are over-represented like but out of the 13
GPUs i counted people reporting 3 were ATI/Radeons. I also think
AMD CPU's were overrepresented, and if X2 means multicore with
Athlons, that multi-core were, but there was one claiming this
crash using an Intel PIV @ 3 GHz (that is a singlecore CPU i
think). I replayed the Ghana/Africa level using the
'/onecpu'-switch in my Boot.ini file but the game crashed again
when the Kazakhstan-level loaded, so multi-core is not the issue
for me.
>>>
>>> Well, I remember that I got no problem with my older Nvidia Driver...
>>> so it is a new problem with the driver... I have to take a look maybe
>>> I find the older driver, so I can test it.
>>> I also got with the new Driver also some problems in other games,
>>> where I had before no problems.
>>> Bye, DUDI.
>>>
>>
>> I find it... It is the Driver: 178.13
>>
>
> Sorry... but it did not help...
> I don't know why...
> I know that it did work well in the past...
>
> That's strange...
> I did send the problem to the Eidos support... since this I wait for an
> answer...
>
> bye, DUDI
If i understand you, you say that you play TR VII now and are
having this crash-problem in Kazakhstan, but that you've played
it earlier without it. Also that going back to earlier drivers
that you think you used earlier didn't help. Sounds like some of
the forum-postings i found, but elsewhere sometimes the reverse
were happening.
We can all hope that Eidos takes a look and creates a proper fix,
but the problem have persisted through the two updates even if
the error was reported in their forum within a month of the games
release (t-59068) so i'm not too optimistic.
Oh well, even if no solution exist or will exist, everyone seems
to agree that the workaround to turn off 'Next generation
content' for the troubling sections will let you play on.