Jump to content

HHawk

Member
  • Content Count

    45
  • Joined

  • Last visited

  • Medals

Posts posted by HHawk


  1. Well I am not going to download a new OS for just one single game.

    It means a lot of work; download the OS, create a new partition, install the OS, download the latest drivers for everything, update Directx and install the game.

    Returning the game and getting a full refund works a lot faster and less of a hassle.

    This is the first game which crashes continuesly on my new PC; games like Crysis Warhead, Far Cry 2, Fifa '09, Football Manager 2009, etc. etc. etc. All work without problems, except for this game. So...

    And apparently it crashes also for people with Windows XP (look above). So I have drawn my conclusions and returning this game, now! Maybe I will pick it up from the bargain bin later when the problems / bugs are solved.

    Cheerios


  2. Ok then, keep crashing. At least your e-p33n will still be at full mast :)

    Good luck.

    Eth

    PS : Why do you have -cpucount=8, that's a given if you have HT on and useless if HT is off.

    Revert to the 182.50 drivers as your video memory is being detected as 256MB (this is a known problem with Win 7/Vista 64). This causes performance problems.

    I loaded the configuration in my bios without the overclock, but the result was the same. I have HT on and I tried 4 and 8, but both crash eventually.

    I am using 182.50 drivers at the moment, already reverted back to them, but still same result.


  3. Game crashes. Sometimes after 30 mins, sometimes after 5. In short; game is unplayable.

    I already submitted a support ticket as well including all the files.

    But I think this should get solved, pronto.

    Was Armed Assault 1 also badly coded like 2?

    My ArmA2.cfg:

    language="English";
    adapter=-1;
    3D_Performance=100000;
    Resolution_Bpp=32;
    Resolution_W=1920;
    Resolution_H=1440;
    refresh=85;
    winDefW=1920;
    winDefH=1440;
    Render_W=1920;
    Render_H=1440;
    FSAA=0;
    postFX=0;
    HDRPrecision=32;
    lastDeviceId="";
    localVRAM=2146435072;
    nonlocalVRAM=2146435072;

    And using this in my shortcut:

    "E:\Armed Assault 2\arma2.exe" -mod=@English -nosplash -maxmem=2047 -cpuCount=8 -winxp

    Maybe I overlooked something...

    Systems specs are in my signature. TY.

    ---------- Post added at 08:27 PM ---------- Previous post was at 08:16 PM ----------

    And I just crashed again.


  4. AHHHH!!!! It will only get worse from here on in....

    Was it a clean CTD or did you get the "cannot commit" message?

    ---------- Post added at 06:11 PM ---------- Previous post was at 06:04 PM ----------

    Just spotted this on the BIS "Arma 2 expectaions page" -

    Note the last line... missed on both accounts then BIS eh? Now thats good development eh? Not really a good excuse either as multi processor tech (2 CPU's on the mobo not multicore) have been arround for at least 5-6 years and multicore has been around since before Arma 1 was out.

    BIS, GET A GRIP!!

    On a serious note, if bulldogs quoted post is correct and this turns out to be bad multicore utilisation it just shows how bad development was. Can BIS seriously say this never came up in testing??? Were the test rigs single core even though min specs say (and I quote from the UK retail case here) "CPU: Dual Core Intel Pentium 4 3.0 GHz, Intel Core 2.0 GHz, AMD Athlon 3200+ or faster". I really dont get whats going on at BIS.

    Maruk, Im sorry for being so hard on BIS but I am just so damned annoyed about this. I have been a faithful defender of the BIS wargames since OFP ver1. I just want you guys to really pull something special out of the bag instead of a constant stream of near misses.

    Excellent reply. I agree 100%!


  5. Same issue. Demo ran fine on high/highest settings. Arma2 itself ran fine on day one on near-max settings (I think I turned shadows down slightly just to be safe).

    Then, last night (day 2 of play) even ratcheting down the settings to minimum, every 3-5 seconds the game would hang, making it impossible to move or even type messages to my co-op buddy.

    Stats:

    Vista 64

    4GB RAM

    nVIDIA GeForce 9800M GTS with 1GB video memory

    Intel Core Duo 2.26GhZ

    Not only it crashes / hangs / freezes, but the game also:

    - has problems with textures flashing

    - poor AI; even with the latest patch 1.02.5xxx-something the AI (your teammates) still stay back. Sigh...

    - did I mention the game crashes often?

    Man, I am starting to wish I never had bought this game.


  6. I finally got rid of it!

    I first ruled out overheating as I monitor my system and nothing passed any historic overheating thresholds for my system. Every other game (even CrysisW) runs flawless with the temperature I was getting on Northbridge, CPU, GPU and Harddrive. But still it

    sure looked like overheating in Arma 2. Weird.

    So I opened up the case and pointed a big fan at "everything" (even memory) and what do you know, no stuttering or fps spikes at all.

    But this didn't satisfy me, as I still suspected Arma 2 to be the culprit. So I monitored my CPU's two cores separately and found out that Arma 2 is very poor at distributing the load between them. Instead it taxes one core and overheats it, making it slow down, and suddenly finds itself in need of CPU cycles so it starts grabbing from the other core making the first cool down some. Then it starts taxing the still very warm first core again making it overheat in notime and so on in an endless loop.

    No other game does this so poorly so that is why I can run other games without overheating with the same temperatures.

    So the temporary cure is to REALLY cool down your CPU like you never needed before. Still, that wouldn't be needed if the game distributed the load more effectively so to not let one core run 100% and overheat.

    Yup... The game has been poorly developed. I wonder why we put up with these unfinished and badly developed games. Sigh.

×