Far Cry 1.1 freezes graphics on level after Carrier

  • Thread starter Thread starter Arild Bjørk
  • Start date Start date
A

Arild Bjørk

We've tested Far Cry on a newly, aquired system with these specs:

AMD Athlon64 3000+
MSI MS-7010 VIA-K8T800 based
512mb PC3200 DDR SDRAM
200 GB Seagate Barracuda 7200.7
8x DVD+/-RW brenner
Ati Radon 9800XXL (Pro/XT)
TV-card
3 FireWire ports
6 USB 2.0 ports
Integrated 5.1 surroundl with S/PDIF in and out
56K Fax/modem
100 Mbit integrated network controller
54 Mbit wireless network card

Far Cry is patched to 1.1. We've tried with the driver that came with the
system. I think it was 4.7 or 4.6 and the newly launched 4.8 from ATI, but
the same problem happens.

We finished the Carrier level and the next level loaded. The loading screen
didn't disappear, but we heard that the audio was back to the game play
where you are placed in a boat soon to arrive at an island. No matter what
we tried, we were not able to get into the game or quit to the desktop. The
system didn't hang, because the sound worked. We could hear the boat rev
when pressing the right key. At the time of the hang visuals were at very
high at 1024x768.

We reset the machine, started Far Cry again, and loaded the quicksave that
was done by the system before we reset it. We moved the mouse around to have
our character look around and in a few seconds the graphics froze and Radeon
cut the signal to the screen. Tried several times, but the same happened
every time. We tried to lower visuals to high, but the same thing happened.
Previously we had played through the previous level with all settings to
Very high except textures which were set at medium at 1024x768. Through
these level there was one similar incident. We thought it was the Radeon
that had overheated, but was not convinced as we have an impression that Far
Cry is buggy.

We then fired up Doom III and played it for an hour on high settings at
1024x768. No problems at all. No freezing of graphics. If I'm not wrong Doom
III is OpenGL-based and Far Cry is Direct3D. There must be a/several bugs in
the Far Cry code since Doom III works fine and after our opinion stresses
the system way more than Far Cry.

Do anyone here have an opinion on what we should do to be able to play Far
Cry? I've searced the net and found one that said we should use the Catalyst
4.4-driver.
 
Arild Bjørk said:
We've tested Far Cry on a newly, aquired system with these specs:

AMD Athlon64 3000+
MSI MS-7010 VIA-K8T800 based
512mb PC3200 DDR SDRAM
200 GB Seagate Barracuda 7200.7
8x DVD+/-RW brenner
Ati Radon 9800XXL (Pro/XT)
TV-card
3 FireWire ports
6 USB 2.0 ports
Integrated 5.1 surroundl with S/PDIF in and out
56K Fax/modem
100 Mbit integrated network controller
54 Mbit wireless network card

Far Cry is patched to 1.1. We've tried with the driver that came with the
system. I think it was 4.7 or 4.6 and the newly launched 4.8 from ATI, but
the same problem happens.

We finished the Carrier level and the next level loaded. The loading
screen
didn't disappear, but we heard that the audio was back to the game play
where you are placed in a boat soon to arrive at an island. No matter what
we tried, we were not able to get into the game or quit to the desktop.
The
system didn't hang, because the sound worked. We could hear the boat rev
when pressing the right key. At the time of the hang visuals were at very
high at 1024x768.

We reset the machine, started Far Cry again, and loaded the quicksave that
was done by the system before we reset it. We moved the mouse around to
have
our character look around and in a few seconds the graphics froze and
Radeon
cut the signal to the screen. Tried several times, but the same happened
every time. We tried to lower visuals to high, but the same thing
happened.
Previously we had played through the previous level with all settings to
Very high except textures which were set at medium at 1024x768. Through
these level there was one similar incident. We thought it was the Radeon
that had overheated, but was not convinced as we have an impression that
Far
Cry is buggy.

We then fired up Doom III and played it for an hour on high settings at
1024x768. No problems at all. No freezing of graphics. If I'm not wrong
Doom
III is OpenGL-based and Far Cry is Direct3D. There must be a/several bugs
in
the Far Cry code since Doom III works fine and after our opinion stresses
the system way more than Far Cry.

Do anyone here have an opinion on what we should do to be able to play Far
Cry? I've searced the net and found one that said we should use the
Catalyst
4.4-driver.
Click to expand...

try testing ur directx in directX diag start >run >dxdiag see if you get any
errors in there,

Ive played farcry through three times, and have also formatted system
inbetween and carried over the profile and never had any problems with
farcry 1.1, i also run mine on everything very high and ultra high,
everything set to maximum on 1024x768, except for anti-aliasing on low, and
runs smooth, maybe try another 512mb Ram, though i used to run it on 512mb
PC2700 and yet had no problems.
--
Almeyda

AMD2500XP @3200XP-11X200-2.21Ghz
A7N8X-E Deluxe > Corsair TWINX1024 XMS3200LL DualChannel
HIS Excalibur 9800XT 256mb @463/399 (Omegas 2.5.51 & ATI tool 0.20 No
Artifacts)
1x80GB SATA Seagate 8mg cache > 2x40GB ATA Seagate
SB AudigyES > ANTEC SuperLanboy 350 Case (350W SmartBlue PS)
 
you could try farcry 1.2 even though its a bugged patch, it actually works
for me no problems

smithy
 
I was playing splinter cell 2 a couple nights ago and it kept freezing like
that at one certain area of the game, I tried playing a different level then
and it worked fine but then go back to this one spot and it would freeze the
computer again. I opened the side of the case and setup a big room fan to
blow inside...then I was able to pass that area. go figure! So today I
bought a slot fan to help cool it down that extra bit so I don't need to
have this huge room fan lol.
 
Arild Bjørk said:
We've tested Far Cry on a newly, aquired system with these specs:

AMD Athlon64 3000+
MSI MS-7010 VIA-K8T800 based
512mb PC3200 DDR SDRAM
200 GB Seagate Barracuda 7200.7
8x DVD+/-RW brenner
Ati Radon 9800XXL (Pro/XT)
TV-card
3 FireWire ports
6 USB 2.0 ports
Integrated 5.1 surroundl with S/PDIF in and out
56K Fax/modem
100 Mbit integrated network controller
54 Mbit wireless network card

Far Cry is patched to 1.1. We've tried with the driver that came with the
system. I think it was 4.7 or 4.6 and the newly launched 4.8 from ATI, but
the same problem happens.

We finished the Carrier level and the next level loaded. The loading screen
didn't disappear, but we heard that the audio was back to the game play
where you are placed in a boat soon to arrive at an island. No matter what
we tried, we were not able to get into the game or quit to the desktop. The
system didn't hang, because the sound worked. We could hear the boat rev
when pressing the right key. At the time of the hang visuals were at very
high at 1024x768.

We reset the machine, started Far Cry again, and loaded the quicksave that
was done by the system before we reset it. We moved the mouse around to have
our character look around and in a few seconds the graphics froze and Radeon
cut the signal to the screen. Tried several times, but the same happened
every time. We tried to lower visuals to high, but the same thing happened.
Previously we had played through the previous level with all settings to
Very high except textures which were set at medium at 1024x768. Through
these level there was one similar incident. We thought it was the Radeon
that had overheated, but was not convinced as we have an impression that Far
Cry is buggy.

We then fired up Doom III and played it for an hour on high settings at
1024x768. No problems at all. No freezing of graphics. If I'm not wrong Doom
III is OpenGL-based and Far Cry is Direct3D. There must be a/several bugs in
the Far Cry code since Doom III works fine and after our opinion stresses
the system way more than Far Cry.

Do anyone here have an opinion on what we should do to be able to play Far
Cry? I've searced the net and found one that said we should use the Catalyst
4.4-driver.
Click to expand...
If you're running the Radeon at 8x AGP try 4x - maybe
your mobo isnt stable at 8x. Try the latest VIA drivers for
your mobo. If you're trying to use EAX - don't - it only works with Audigys
on that game. The 4.4s are advisable because the 4.5-4.7 drivers introduced
a glitch in how lighting/shadows are done and not because they were
unstable. Ive used the 4.8s on Far Cry and it was glitch free and stable.
Hope this helps.
 
Back
Top