Jump to content

dogz

Member
  • Content Count

    197
  • Joined

  • Last visited

  • Medals

Posts posted by dogz


  1. Rebel... from what you have stated you are now using an LCD when before you were using a CRT?

    If so you should Google: "Frame rate limited by a factor of refresh rate".

    eg Max 60fps will sometimes default to 15 or 20 fps (Vsync can affect this)

    also check your config file, some on here (Alex72) find settings of 0 frames on both to give good results others use upto 8 frames.

    Otherwise it could be as suggested by GURU... something has changed on your system...eg spyware/ backgound processes... always troubleshoot when NOT connected to a network/internet first.

    Run Malwarebytes free version with latest defs... it is one of best freeware scanners

    GL M8


  2. Specs:

    Windows 7 64bit

    Intel Core 2 Duo E6600 2.40Ghz

    4 gigs of DDR2 800 ram

    ATR Radeon 4890

    20fps. No graphic changes except view distance actually improve FPS. No AA, normal to high settings. Horrible texture pop-in, flickering, every bug under the sun.

    It's sad when I want to go back to ArmA just to have decent FPS.

    I find it really amusing that particularly in this type of thread... with all that has been proved about how important storage subsystem is. ie(HD/Ramdisk/Flash)

    People still post "my A2 is slow" etc... but they dont say what HD etc that they have...

    BTW Wasdie your CPU is very weak for A2

    My Q6600 3.0Ghz runs at 70 -90% on all 4 cores most of the time.

    if you can get at least 9 series quad and get it up near 3-3.5Ghz you will see big gains.


  3. Hmm...In forrests performance is ok (20-30 fps) but in towns or villages I have only 10-20 fps. I cant use patch 1.05 becouse I still have poblem witch flashing textures.

    My comp spec.

    Core2duo 1,86GHz

    3GB DDR2 533Mhz

    GeForce GTS 250 512 MB

    and two disks 7200 with 32MB buffers

    Windows 7 32bits.

    Resolution 1680x1050 and everything switch to normal without postprocessing (off).

    I dont think you can expect too much with that cpu...


  4. you dont say in what form of the game you are playing but you must make sure the "Artillery module" is loaded for that mission.

    easiest way to demo is to open the editor and load the module and the "static unit" yourself.

    If you are playing online/user missions it varies, some missions dont allow it.

    there is the chance that you have somehow borked your keybinds as well... so as long as your menu options scroll/work the same for the other stuff it should work.

    ps if you did not know bind a key to "Optics" and it will give you the optical sight for direct fire (mouse button does not always work.)

    I found some info here:http://forums.bistudio.com/showthread.php?t=93120


  5. kklownboy get real and look around how many game publishers and developers arent interested in testing their games before release. What they do are simple tests - I bet that BIS devs didnt play-test through their own missions/campaigns and modules. You may take a look how many issues and bugs have been reported here and at DevHeaven since release. ;)

    Time will tell if your crystal ball skills have stopped BIS devs to fix bugs & issues of Arma2.

    not sure about that.... but one thing that stands out in all the DEV gameplay vids is that they are hires, smooth as silk and no texture popping...


  6. Use the gun sight?

    OP is saying that he cant see forward of the gun for close direct fire and that he must use the map based LR aiming which I have just found to be true in some testing.

    It must depend on scripting and difficulty setting of the mission.

    It requires crosshair enabled in game options/difficulty and must be below expert level.

    Which gunsight are you referring to?


  7. to get the best info for OC you should go to an OC forum there are many... and with specific settings for just about any mainboard/cpu combo out there.

    You will be able to find ppl with your setup that have found the best settings and the "LIMITS"

×