Far Cry 2 specs released


Recommended Posts

Why? The requirements are almost identical to Crysis:

http://en.wikipedia.org/wiki/Crysis#Development

Funny how they kept claiming it wasn't going to be demanding like Crysis, yet the requirements are virtually the same.

...also, why can developers never list the minimum OLD gen card (as they did here) AND the minimum current gen card? EG: 6800/9500 or whatever it would be.

@ sanctified: That'll play it.

why ? it might the 6800 is on par with X1650

68xx is high end older gen

X16xx newer gen mid range so .....

I think the specs look pretty low to be honest. I have a 6800 which just meets the minimum requirements and its quite an old card now. To meet the requirements of a game that hasn't even been released yet is pretty impressive.

yea , but that mean it will run on low on 6800

being made in '04 almost four year old

Why? The requirements are almost identical to Crysis:

http://en.wikipedia.org/wiki/Crysis#Development

Funny how they kept claiming it wasn't going to be demanding like Crysis, yet the requirements are virtually the same.

...also, why can developers never list the minimum OLD gen card (as they did here) AND the minimum current gen card? EG: 6800/9500 or whatever it would be.

@ sanctified: That'll play it.

The recommended video card is actually a lot lower, Far Cry 2 is an 8600GTS and Crysis is an 8800GTS. Far Cry does have slightly higher cpu requirement though.

The beauty of Crysis is that the game scales up beautifully even at low-medium settings. That maybe because of CryEngine 2. Let us see if the much vaunted Dunia Engine can do the same.

lol , are you serious , crysis scaling plain sucks

lol , are you serious , crysis scaling plain sucks

Why would you think that? Moreover what I meant was the game even at low/medium graphical detail looks much better and realistic than other games at high details.

The beauty of Crysis is that the game scales up beautifully even at low-medium settings. That maybe because of CryEngine 2. Let us see if the much vaunted Dunia Engine can do the same.

I half agree. I think the engine ran fine but it was very much map dependant. I don't subscribe to the belief that everyone needs a game to run at 50fps on max settings to be considered optimised. Indeed, for what was on the screen at any one time I think it ran well for mid range hardware at the time. I mean other games on other engines such as Unreal and Dooms engine weren't doing anywhere near what Crysis was in terms of the size of maps and the ability to destroy basically everything.

On the other hand Crytek really did a number on themselves in terms of map design. As I mentioned above, when it ran well on certain maps it was fine. Thats until you hit later levels and for whatever act of stupidity the games requirements get ramped right up for the later levels which ended up playing far worse than earlier ones based on pretty much everything I've read as well as my own experience.

So I don't think it's unfair to call the CryEngine 2 optimised, however their map designs were the real unoptimised part IMHO and the guys leading the level design teams should be ashamed IMHO to have such wild variations in performance between levels.

I also think Far Cry 2's specs to be honest seem pretty modest. Both games are playable on 8800GT's (well FarCrys is on paper having not tried it) which sell for less than $200 and were that price at Crysis release too so you certainly didn't need a monster rig. Besides the obvious map design issues which caused in consistent performance at later stages, I think the other big issue is too many people are conditioned to the train of thought that they must run a game at closed to maxed out otherwise it's not worth bothering with.

As long as Far Cry 2 doesn't have an ice level I'm sure I'll be just fine.

sorry if the above reads poorly...it's a bit past my bed time :p

I agree Smigit, Strange thing is though the beginning island levels are the best looking in the game and are massive, it seems crytek did some poor optimization near the end where the levels were even smaller and didn't look any better which is kind of ridiculous.

I agree Smigit, Strange thing is though the beginning island levels are the best looking in the game and are massive, it seems crytek did some poor optimization near the end where the levels were even smaller and didn't look any better which is kind of ridiculous.

it look like it was fine till you get to the stage were you board the alien mothership where all hell break lose performance hit big times

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • No news articles about the Arch Linux repo being majorly infected with malware?!?
    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
  • Recent Achievements

    • One Month Later
      Sharbel earned a badge
      One Month Later
    • First Post
      BizSAR earned a badge
      First Post
    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      598
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      79
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      70
  • Tell a friend

    Love Neowin? Tell a friend!