y_t

I love my G15. I use Everest to display all my critical hardware monitoring info (lost the second screen when going SLi). I currently only use one macro key for the FLUSH command =/ -YT

That info was posted in Feb. Suma's comment was posted in August and this part seems to give hope that there is in fact something that can be done: "The game can be adjusted to detect this and adjust fogging accordingly" -Suma

Fog issue on Single 8800 GTX, dual 8800 GTX, single HD 2900XT but not on single X800XT. Extremely playable but fog issue is there. It seems that when transitioning between scenes (say when clicking on Multiplayer from the main menu) there is a brief second where the background looping scene "clears up". Related??

I'm going to check later tonight myself but is there a difference between using fear.exe and using the built in arma.exe SLi profile that exists in the XP v162.18 drivers? I only see about 20-40% bar usage while playing. C2D 6600 @ 3.3 2x 8800 GTX KO 1920x1200 (normal AA in game and very high AF) I finally got around to comparing the built in arma.exe vs fear.exe SLi profiles (driver 162.18) and found, quite to my surprise, a huge improvement in SLi using fear.exe. Non scientific testing but ArmA Mark went from ~3000 to ~4000. I tried forcing AFR 1,2 and SFR on the arma.exe profile and found that AFR1 is the only one that actually works at all. Not being an SLi profile guru I am assuming that there are special timings/settings on the fear.exe profile that optimize it. Is that right? Anyway, just wanted to share this with other SLi users and maybe get any feedback about others experiences. YT

I'm laughing constantly while reading this thread. I'm not sure if I'm laughing at him or with him however =D Either way it's funny as hell. ROFL.

I'm going to check later tonight myself but is there a difference between using fear.exe and using the built in arma.exe SLi profile that exists in the XP v162.18 drivers? I only see about 20-40% bar usage while playing. C2D 6600 @ 3.3 2x 8800 GTX KO 1920x1200 (normal AA in game and very high AF)

LOL. Why are you posting on the board?

.... They always release official drivers after weeks of testing.... Â or you would want them to write a new driver and release it directly without testing? (Driver date+Release Date on the same day??). But I agree though, im also thinking about going for ATI next time Would it be any different than it is now? They regularly break things in NEWER drivers while fixing other things.

LOD = level or details, its about the quaility of textures map on 3D models, the higher the LOD is the better GFX on model can be seen, to find out what problem is you better first dumb down to XP first(feel lame? i can tell you vista is still not for gaming, sometime very unstable, for now) next using the latest driver to test as much version of the game as possible, i guess you using EU DVD version 1.04 so try reinstall the hold game with a clean windows to see if the problem still there, make sure you tested most latest nV drivers and see if all version of the drivers have the same problems if all the above shows the same result, then ArmA is surely not running happy on your system, its better to report on BTS, make sure that you give enought info like your spec, OS version, driver versions, game versions, add pictures or even error logs created by the program itself(forgot where they put it through) would be even better to help sort out the problem in next patch Sorta what 4 in 1 said... Level of Detail Here's the Wiki: LOD Basically its a procedure to reduce/increase the complexity of objects in the game based on their orientation to the players (cameras) eye. The nice increase in FPS some people are seeing is no doubt realted to adjustments in LOD calculations implemented by BIS in 1.05+ (amongst other things). For some people (I guess with certain H/W + S/W configs like me) the LOD is all buggered up. Here is an example. I took these shots last night. It's a repeatable issue and this is what I do to make it happen every time: 1. Start game (1.05) and run mission ArmA Mark 2.0 2. After Mark (2880) is finished goto my campagin save (Counterattack) 3. Take screen shot. 1. Start game (1.05+) and run mission ArmA Mark 2.0 2. After Mark (3050) is finished goto my campagin save (Counterattack) 3. Take screen shot. Sweet  XP SP2 C2D 6600 @ 3300 8800GTX @ 625/1000 (101.02) X-Fi Dell 2407FPW

I am seeing this with the beta patch and a 8800GTX (101.02 driver).

What driver versions are the 8800 users running? I am currently using 101.02's. Maybe that is contributing to my woes?? I'll try some other ones after I get home. Stupid nVidia

http://lee.plankton.ch/ArmA_105b_GF66_88.jpg ? You beat me to it

I guess I'm one of the "100" people that still have technical issues. Unlucky me huh? With the beta patch my LOD is all fkered up. The LOD never switches for many/most objects in the world from the super low poly models with out textures, even when 2m away. I wish people would stop claiming that the 8800 fog issue was fixed by BIS. They admitted over two weeks ago that they had a code bug that prevented anyone from seeing over 5K. The fog bug is still there (scroll down to the post from Lee H Oswald here). Yes it's way better now but it's not magically fixed. Nvidia is still on the hook here (see: Source engine fog bug)Â As a funny side note, running ArmAMark with the patch makes the UAZ in the first scene immediately swerve left and miss the bridge. To it's credit, the AI stops, backs up (sometimes over compensating) and eventually rights himself to drive off. Too funny. When running the same test without the patch he just drives straight on to and off the other side of the bridge everytime.

I've been running mine with that setting. It dosent limit my framerates tho. Does it keep yours from goin up? they go over, i think the nvidia driver handle that but seems to make Mp smoother, Â it may have an effect on the way data in out works. Â I feel i get smoother gameplay in Mp with it set to 30, Â if you change any visual setting it will go back to 60 immediatly. I would think the purpose of that setting is not to LIMIT the framerate but to attemp to dynamicaly change the display settings (to a certain extent) in order to maintain that as a minimum frame rate. That's how it works in Vanguard and a few other games I know of. I actually set mine lower (~20) so that I could keep the highest quality while maintaining playability in single player anyway. If I'm totally off base then I appologize.

Patch is very nice for the draw distance. I have major LOD problems with it however. LOD seems to not even switch on objects only 2m away!? Nasty blocky terrain and objects. Seems to have started after playing for about 30 minutes. C2D E6600 8800GTX 101.02 UK patched to 5137 and then beta 5143

To those this may help, Running 1.05 UK (in Seattle, just couldn't friggin wait) on my ATI rig and was hard crashing within 15 minutes. I started walking through the hints and tips sticky thread and managed to get the game running *very well and stable*. Quick summary: 1. Installed the MS dual core hotfix (confirmed registry set to 1) 2. Installed AMD Dual Core Optimizer 3. I am running Cat 7.2's! 4. Game settings: Visibility = 1200 (sounds low but I played it for a long time before I even noticed the setting) Resolution = 1680x1050x32 Aspect = 16x10 Terrain = Normal Objects = Normal Texture = Normal Shading = Normal Postprocess = Low (big frame rate hit if high) AF = Normal Shadow = Normal AA = Normal (big frame rate hit but it's totally worth it to remove the jaggies) Blood = High (need more blood)! ArmA Mark ~1650 Started a new campaign and played through 5 missions and all the cutscenes continous (~1 hour) and then it's been looping the menu scene for another hour. Absolutley beautiful and not a hickup. System specs: DFI LP CFX3200 X2 4600 X1900XT CF ed. (single card) 2 GB ok RAM 250GB WD Caviar (16 MB) On board Audio XP SP2 Hope this helps someone out there!