thr0tt

Hi, how did you do that in msconfig ? Did you get the graphical artifacts like in this this thread or other issues ? Edit: Found it, its under Boot.ini and Advanced Options. I wonder if this worked for anyone else although seems a bit harsh to reduce the amount of RAM you have just to play one game.

As Ginger says thread title misses off the remaining ATI card estate :) . Shame folk who post things like Krony1664 has appear to only read the 1 page in the 38 page thread and all the things we (the community) have tried on several different cards, different setups etc. all we need now is the magical fix from Krony1664 to state that it must be an overheating issue. Still, as the insight here that my AMD x4 955 BE CPU and HD3850 are too old to run the game it seems that there may be little hope for others too. Lastly - The issue for me doesn't really exist as I have a work around which is increasing the AGP Aperture so the game works fine but I don't like using the work around, thank you for telling me 'it won't work though' but maybe some time invested in reading before you post comments would give you a better stance ? I am posting to help and get to the bottom of the issue with the other ATI users to stop 'must be a hardware issue' posters to stop posting such rediculous standard answers. Cheers.

I don't. The title of the thread is : graphics bugs with ATI 4800 series (4850/4870/4890) not 'My ATI card works ok ?' If you want to discuss your working card then please don't hijack this thread and create your own please. Thanks.

Indeed, you can read whatever you wish in any post and make speculative threads therefore stating official news on nothing that has been said. This is just another 'Where is the 1.03 patch' thread.

If you look around you will see that there are some 'signs' that a patch is coming Soonâ„¢. There is no weight in drip feeding fixes that may actually depend on other fixes. Let us all be patient and watch this space...

You may have issues running the game still when it does the CD check on startup which is another reason to somehow get your game returned to the shop as faulty and get them to give you a new one. Good luck though.

How about the option to create groups in the field, you know, you are part of a group and only half are team players so the other half including some other stragglers can join a group, similar to that you could in a vehicle.

Did it work ?

Return the disk to the shop and tell them it won't load and it looks like the disk is scratched. They will be able to return it and you will get a new copy rather than this problem everytime you install the game.

When playing for long period periodically do Shift - then type flush to clear out your textures, this will enable it to keep running ok. Note that Shift - will not display anything on screen but after you type flush it will say 'activating flush' and sort your issue out. Rgds.

Two camps, those who feel the game is working as it should and the FPS are what you should expect for such a complex game with some graphical improvements over ArmA 1, the other camp do not... :) Hardware aside, the game is not running as it should (i'm on that camp).

Yup looks like mine, just seeing if the ram in the cfg was different. I run 1680x1050 now with pp off which appears to help a little. Will try changing the ingame memory option to see if that really has an effect (for me). One thing I can't live with is no shadows though and that can be a killer. Ok, had a go and no difference. I did notice your terraingrid set to 25 which is 'low' Terrain Detail in settings but I have never had an issue with terrain its really just buildings and their textures that kills the game (for me), how can a game with such lush folliage and terrain detail run so well but as soon as you introduce a building and then town it cripples the game...

What does your ArmA2.CFG show under Local and NonLocal ram ? Can you post the contents please.

Remember to make sure you have one in your inventory too otherwise ctrl-m will only show the map, mistake I have made on Vet mode and only finding out when I am 'somewhere' on the map :/

There are other posts here with system exhitibing the same issues. If it was solid 29fps then most gamers would be ok with that but as it dips and rises in random areas but more likely dips in and near towns then it doesn't help gameplay. Do a search as another user also posted the same (may be similar system) and tested lots of different resolutions. For me, I have now turned Post Processing off which helped although the PP should have been masking the low FPS. But like many here, the magic 1.03 patch of all patches that is being secretly worked on is going to be the one that makes everyone forget all the issues they had, and we will look back in 6 months time and laugh at these posts... all mine included.

There is a fault with the engine that is in every other thread posted in the troubleshooting forums, if you check the stick ATI problem thread then you will probably see the same issue but it is more evident on ATI hardware. Unfortanetly BI have not admited this is a game problem but has pointed the finger of blame at your hardware having a fault which is pretty shocking really.

Mist17, load up your BIOS, when in there press CTRL-F1, that should bring up a 'hidden' advanced options and in there you should be able to increase the Aperture. Give that a go and let me know how you get on. Make sure it is set to 512MB and that you haven't made your ArmA2.cfg readonly as it needs to change that when you start the game again. Thr0tt. Edit: Just a small note: On doing this change your windows will startup slower and when exiting some games it will appear to hang, this is normal behavious while it flushes the ram or something so be patient, this is why I want this problem fixed as it is rather annoying but at least it should remedy you not being able to play the game.

AARRGGGGHHHH !!!!!! Please check the Sticky: graphics bugs with ATI 4800 series (4850/4870/4890) - This is exactly this issue and ARMA problem, I can understand the initial immediate response of overheating but please 26 pages of folk who all have the same issue are all overheating and I can stop it happenning by increasing my Aperture to 512MB and it doesn't come back, hmmm how CAN that be overheating ? Mist17, find that Aperture setting in your bios don't go stripping your machine down, buying speical fans, new PSU's etc, it will NOT solve your problem.

Would either defuse the situation or increase it ten fold, hmmm, a sticky with weekly updates would work for me with some answers to some questions posted on the forums which seem to be void of BI devs now.

I get that too, almost like speckles on shadows or dark areas only. Nothing major and bearable but not desirable. As you can see our systems are pretty different... could be an engine undocumented feature like the rest of the non-issues here. ;)

There must be a setting to change AGP aperture in your BIOS, very suprised if it isn't there. Post your mobo make and model and I will see if I can find it for u.

Runs on my system 20-60FPS in places but very random. Your CPU will let you down, saying that its all lucky dip with ArmA 2. If you are able, increase the AGP aperture in your BIOS to 512MB and that should sort he artifacts. If not then you are stuffed like the rest of the ATI users here (not all but some).

Agreed, make this a priority, the game isn't a real game without sharks with lasers on their heads.

Depends on what server you play on and if you are able to get like minded folk to join in with you. Most of the time I manage to get a squad together or at least have 2 or 3 of us working together ignoring the remaining cannon fodder that blindly runs at objectives. Only guaranteed way to get some sort of tactics together however is to join a private server with like minded folk.

I had a crackling issue and popping on previous driver sets, currently I use 6.0.1.1368 which work for me and I no longer get the crackling sound during or starting the game. May be worth a go. For info. the latest drivers on Creatives site didn't work well for me and many other due to some odd behaviour when closing down windows (long delay trying to shut down).