PDA

View Full Version : shouldwe view the CoD release like the initial MSflightsim-X release problems ?


zapatista
08-30-2011, 04:10 AM
remembering how fsX was almost unplayable at release time, on all but uber pc's, and that it took people with even high end pc's months to tweak and tune things so it would run right (and you still yrs later need a high end current pc to run it well), are their similarities there or is the current CoD game/gfx engine just seriously flawed ?

for CoD there are indications that people with high-end intel quad cores and 3 gb gfx cards have somewhat fluent gameplay at medium settings, maybe that were the similarity ends

can any high end gaming pc owners provide some comparison what it is like in overall gameplay in the rest of the CoD game ?

Continu0
08-30-2011, 06:05 AM
I never played Flight Simulator X but i think the problem in CoD is different.

I do have a rather strong system and i am getting a nice gameplay(at least over the canal) but CoD has some other problems which don´t have anything to do with the hardware at all.

First, there are some obvious bugs like appearing trees in the air(fixed now), not working AI, not working radio-commands or not working load-out-menu. And so on...

And secondly, the Game as a whole is not tuned to it´s best yet. What I mean by this is for example that on my 6core-System only 1 core is used by the game. So the game is fare away from using the full potential of my system.

For sure you get a better gameplay on a high-end system. watch on youtube, there are some crazy guys:

http://www.youtube.com/watch?v=Zvgy6-FLOT0

The thing that probably makes the community angry is the feeling of having an unfinished product. with all the bugs fixed, tuning made(mentioned above), CoD would be a great game that runs totaly fine on an average PC.

Seeing the full potential of the game but not having it is hard for people:)

Friendly_flyer
08-30-2011, 07:10 AM
One does not exclude the other. We could well have an "fsX-problem", made worse by a lack of tuning and debugging. I guess we'll see (or hope we'll see).

RocketDog
08-30-2011, 09:16 AM
I bought both games on release. FSX ran slowly but, IIRC, everything worked pretty much as you would expect and everything was present and correct. I enjoyed it from the day I installed it. It's a pity MS didn't develop it further, but it was always serviceable.

However, although CLOD runs (at least for me) at reasonable FPS after the first patch, the problem with it is that so much of it was/is missing. The devs clearly recognise this and have an ever-expanding list of things they are going to put into the sim at some unspecified point in the future. To me, the main failings of CLOD are i) unrealistic terrain, ii) poor AI, iii) no FSAA, iv) poor sounds, v) no weather, vi) no historical dimension beyond the useless campaigns, vii) poor QMB, viii) poor FMs, ix) undocumented FMB, x) endless minor yet irritating bugs. Because of this I don't enjoy playing with CLOD and I haven't started it up in weeks.

To me it looks like CLOD could still go one of two ways. It might be that it actually follows the RoF example and builds up over the next year or so to something really worthwhile. I'm not very confident of this because the damage to the brand has been quite severe and the devs seem hell bent on antagonising their customers by refusing to talk to them (compare the way 777's Jason interacts on the forums with his customers to the way Luthier behaves).

Alternatively, it might be that it follows the path of Silent Hunter 5, where the publishers decide that it's beyond salvage and walk away after a couple of basic patches.

To date, I think there is a better parallel with Silent Hunter 5 than with FSX.

Blackdog_kt
08-30-2011, 09:41 AM
I think that a lot of it is is a case of undocumented behavior which doesn't make sense to document properly, because a lot of stuff is placeholders and subject to change and that will render any documentation obsolete pretty fast :-P

Most of the times, problems are either due to directx version used, .net libraries and people not realizing that running at full graphics is impossible if your PC doesn't exceed the recommended specs.

It runs fine on my two year old PC:
i7 920 @2.7 Ghz (stock clock speeds)
Ati 4890 1GB
3GB RAM
Win7 x64

I use mostly medium settings, a couple of low settings and a couple of high ones, running it at 1680x1050. Runs fine and stutter free at 25-60 FPS (capped due to Vsync) depending on the terrain bellow me. The only way to make it start having hiccups is fly very low (like rooftop level) over London, otherwise it's all fine.