patham
Member-
Content Count
13 -
Joined
-
Last visited
-
Medals
Community Reputation
0 NeutralAbout patham
-
Rank
Private First Class
-
Maxter, Try resetting your HDRPrecision to 8, this should allow you to enable AA again. PH
-
Some tips that have worked for me: 1/After a graphics driver update check the Display Properties/Settings/Advanced/Troubleshoot window   that "Enable write combining" is checked and Full Hardware acceleration is selected. 2/For WinXP get 3 Gb of physical memory (it's cheap) and turn off your swap file, initially I had  my doubts about this, but it sorted my crashes to desktop from 1.08 onwards 3/If you have an AGP chipset increase the AGP memory aperture size to as high as it will go. Some  motherboards do not have this option, unfortunately. Contrary to popular notions this does not  use up memory. Point number 2 had the biggest effect on my ArmA experience.
-
UNN, I had trouble finding it too, if you've got XP Pro and your account is at "Administrator" or "Power user" level, it will be in "C:\Documents and Settings\'your profile name'\Local Settings\Application Data\ArmA". If you have XP Home you will have to change your account type to "Administrator" to access that folder.
-
UNN, I had trouble finding it too, if you've got XP Pro and your account is at "Administrator" or "Power user" level, it will be in "C:\Documents and Settings\'your profile name'\Local Settings\Application Data\ArmA". If you have XP Home you will have to change your account type to "Administrator" to access that folder.
-
Jack I've checked Gigabytes web site and yours is not the only M/board type that does have an AGP aperture size selection in the BIOS. For some reason Gigabyte have not implemented this item. I thought initially that it may have to do with the VIA chipset but least one Intel 865PE chipset board (ga-8i865pe) is similar. More explanations below of AGP aperture http://www.techpowerup.com/articles/overclocking/vidcard/43 http://en.wikipedia.org/wiki/Agp There also seems to be a problem with driver handle leaks on certain ATI drivers see this     PH
-
@Jack-UK What's the make/model of your motherboard?
-
Jack I've got an Award BIOS as well, hit the Delete key during startup. When the menu appears select "Advanced Chipset Features". About ten items down you should see "AGP Aperture Size", immediately above the "Init Display First" entry. I'm not sure changing this setting in your case will help, as you have probably the fastest AGP card around with 1/2 a Gig of VRAM, but you could try it. This setting does not "ring-fence" that portion of system RAM for GFX so it shouldn't make your PC run badly. See URLs below for explanation. http://www.adriansrojakpot.com/Speed_D....02c.htm http://arstechnica.com/guides/tweaks/bios.ars/3 http://www.lostcircuits.com/advice/bios2/12.shtml
-
@blackt12 See this for possible fix                PH
-
@Jack-UK I'd just like to share my tuppence-worth, the demo ran reasonably at 1024X768 most settings normal except AA, shaders low, blood off, shadow detail low. I didn't have the foliage slowdown, I think because of the shaders. But the full game ran much worse than that. In missions, huge blocks that should have been textures, trees without detail, only base textures on vehicles. The campaign cutscenes were either 2D cartoons or white text on black screen. I tried all of your hints, no change. Write combining had a small effect, but the tweak that cracked it was changing the AGP Aperture in the BIOS from 65 to 256. Now up until this the conventional wisdom was this setting should be as low as possible because VRAM was big enough to handle anything thrown at it. This game is different, probably bad LOD drop down handling. Run in windowed mode it became evident that my CPU was not stressed (60%) and there was plenty of system RAM unused (300Mb). This fix probably is only useful if a user has 128Mb of VRAM and >1000Mb system RAM. Apart from gameplay, the change increased my Armamark score from 1309 to 1722. Hope this helps some of the community play a long-awaited game properly.
-
@Andyx I've had the same trouble with the cutscenes at the start of the campaign and I've got the same GPU (6600gt 128?). Every tweak I tried didn't make any difference until I changed the "AGP aperture" in the BIOS from 64 to 256Mb. Started the campaign again and this time when the news reporter showed up on screen textures were now visible, up to this she was like a 2D cartoon character. When the Corazol convoy text appears the screen goes black but after ~ 10 secs. we are ingame on the mission. Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Prescott 3.2G OC 3.5G 1024Mb 6600GT 128
-
I had the same error when running the program after the update from demo version 5114 to 5116. I don't know if this is your problem, but the reason for the error was that I neglected to copy the new .EXE from the zip file to the Armademo folder. Hope it helps. Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â PH
-
@ Comes That was my error, I was dumb enough to forget to copy the new .exe build into the Armademo folder. PH
-
Just downloaded demo 5116 and got an error dialogue "Error compiling pixel shader PSSpecularAlpha", previous releases have worked fine. P4 3.2 1024 Mb 6600GT PH