FritzDaKat

And another reason why Rivatuner is just so useful as some versions of the forceware driver have certain adjustments disabled. On my box, theres nowhere in the control panel to adjust pre-render settings whereas inivatuner gives me the ability to. And best of all, in many cases Rivatuner will roll itself back a step if a setting you've changed is incompatible with the Application. It's also got a nice Hardware monitoring feature which will let you keep an eye on your FPS, GPU core temp's, and all sorts of other hardware info while ingame without the same performance hit some people get from running Fraps. Rivatuner also has a handy users forum over at guru3d.com for those that would otherwise be totaly lost with it. Downside? It still wont uinlock my fanspeed, s'ok thou I've got the Iceberq

Would be nice to get input from others, make it sticky, change [FIX] to {Workaround] perhaps, really did help a fair amount. Of course there is the risk of ppl causing serious damage to their hardware if not careful Still, used properly, it's a handy tool

Yep, but I was by 50% on gpu & ram. Dunno why. Seems best in my case to cut Ram by about 14% and leave Gpu alone. Cleared up all the funny artifacts I was getting since the SP1 update. Thanks for reminding me of Rivatuner, I missed it

Eeeek. Try the Map_Misc addon. lol Has refuel, rearm and repair objects with a user defined placable radius. I just missed the way the Ofp "Maintenance buildings" required UI to activate them. I suppose I could figure out a way to script a user input to (de)activate it somehow.

It does seem to reduce the video "lag spikes" a bit, but the overall performance drops a hair while underclocked. Very strange to note the fact that when underclocked and locked in like that, my card actually runs hotter than normal, still quite safe (According to manufacturer anyway) at around 60c. (+/- 7c) (Vantec Iceberq 6 cooler )

Sounds like a plan but just curious, have you enabled the temperature monitor to see what effect having it locked in "performance mode" is?

It could also be related to the fact that a good number of mice have a low polling rate and mediocre resolution. Drove me crazy in many games, trying to snipe, "Noooope, a lil' to the left,,, Noooo, back right,,," etc. So I ran out and got a Logitec G5 gaming mouse, lets me control the sensitivity as well as the polling rate. Not to mention it gives you 3 presets for sensitivity to configure sooo I've got mine set at fast (1600 / Very nice for flying choppers, driving cars), Medium (800 / Good for on foot and general aiming), Low (400 / Veeeery nice for sniping ) Also has a 4-way scroll wheel which lets you set L-R scroll as numpad - or + as well as 2 thumb buttons (Which are actually somewhat annoying as I use it Left-handed ) The Mouse has a nice feel to it in general and also has a cartridge that lets you add small weights (included) to better balance it to your prefrence. The only real drawback is that it costs about $60 USD, but in light of what some are dropping on RAM and Video cards for their gaming boxes, it's tiny taters.

Well, delaying or turning off TDR in either case isn't really "fixing" anything, it's simply changing the way windows responds when conditions meet the requirements to trigger a TDR event, i.e. anytime your framerates dip below 6.25 fps, even if only for a fraction of a second. By disabling it altogether I ended up with more CTD's as I think it disables the recovery process, so when the driver hangs, Windows just says "So you really dont want TDR? Ok then, back to the desktop you go." Whereas extending the delay not only increases the TDR response time but actually allows a larger window of opportunity for the drivers to recover. At least this is how it appears to be behaving. P.S. I've also added that -zprime command switch recently and the game appears more fluid while using the 169.44 drivers (More stable than later betas for me), much like the "fluidity increase" btwn 169.44 and the 174.74 / 85 drivers.

Agreed, I'd take it further and say its my favorite environmental ambience enhancing addon. I play the Quarantine mission mostly and the flies on corpses effect is just awesome with the "Zombies" (I may have to extend the effects to some of the RH_pistols for personal use )

Open the Arma\beta folder and see if ifc22.dll is in there or not. If not, copy/paste the one in the main folder into the beta folder. (If it is but it's still not working, copy/paste anyway just to be sure the pre-existing copy isnt corrupt.)

And RE: the error message some get in "#5". Looking closely, I see that you're running version 1.08. Have you tried installing the 1.09 patch prior to the 1.11 / 1.12 beta patches? (I dont think I did either, but got no error, still worth a shot.) Difference being that the beta patches run alot like a mod, whereas the 1.08 & 1.09 patches are normal in the sense that they update pre-existing game files if that makes any sense to ya'. P.S.: Could help to be sure you're logged on as an administrator when installing the game.

What ArmA version?

The boxes are just sort of a splash-screen that runs while ArmA runs a mini benchmark on system hardware to better configure your "ideal system default settings". My row of boxes checks all but the last 2, then the game starts. #1: What drivers are you using for that 8800gt? #2: Have you tried re-downloading the game? Theres always the chance that a small file got corrupted along the way somwhere in the process. #2b: Before reinstalling the game, be sure to delete any previous remnants of your old instalation (Do a full system search, show hidden & system files as well just to be sure) and be sure to run a registry cleaner after having uninstalled ArmA and rebooting your system. Thats all that comes to mind at the moment.

Wow, just read the updates on the 1st post. Some very interesting things in the works  As far as "adding to the atmosphere" goes, I found adding heavy fog not only adds much to the "Creep-out" factor, but actually seems to improve performance as it seems to act like a long distance view blocker, thereby reducing the amount of textures and so-forth needing to be rendered by the GPU. I was toying with fog settings from .5 to .86 and it looks pretty nice in the dusk thru dawn hours, but pretty lame in broad daylight, mabey replace the _overcast = 0 in the environment with some fog? Also the Hi-Fi sound FX update really adds to the immersion level as the sounds are just so much more than Vanilla (but does nothing to the RH_Pistols sounds unfortunatly   ) Has alot of other aural tweaks beyond guns too. One idea I had regarding storyline and possible sub-missions was if say, the cause of the Yomie uprising was related to a meteor shower, or some bio-weapon which would leave an object somwhere in the spawn area which would be the "cause". Then mabey after a number of the Newspapers or other sort of info (Mabey just time passing / CDC finding out why) have been found it will be revealed that by retreiving these meteor rocks or Bio-weapon containing breifcases (Mabey it's the SLA's "Final Solution"?) the related spawn area will be disabled? As always just thinkin "outloud". I needed a break from my nvlddkm has stopped responding issue (But I think I may have fixed my problem.) ***Edit*** Another afterthought after hunting for survivors in Ortego for 20 minutes with no luck (Heard them, but couldnt find any with all the darn walls) Mabey make them call out for help or shout out to see if anyones around when the player is within say 150 meters of them? I'll find some nice lil' soundbites and samples for ya' to mess with & throw the pack on rapidshare or somethin'.

#1: System Spec's please? #2: It is a known issue, but it's not just known to ArmA, not just to Nvidia. It seems to affect people somewhat randomly. This can happen both in game as well as on desktop and sadly there is a looong list of possible causes. I've seen reports of people fixing the issue with a New power supply, by adding additional cooling to their GPU, by making certain changes to their registry, by disabling Aero in Vista systems etc. I'm sure someones "fixed it" by making sacrifices to the Green man somwhere as well. The underlying issue really seems to be related to drivers vs. OS vs. Virtual adressing space required by the application in question in some cases, changes made by SP1 (like my case) may trigger the issue Not that I want to discourage you from finding a workaround, you may get lucky and find it's a simple process for your scenario. But I've been searching various forums for about 11 hours a day over the past few days and theres no single, simple solution to fix everyones problem. #3: (If you run Vista, The next time this happens to you, alt tab out of the game and see if theres an error message saying "nvlddmkm.sys has stopped responding but recovered" in yout taskbar, Google it and hopefully you can find an applicable workaround to your particular scenario. But first, add your system spec's to the first post so we know where to start looking.

With those drivers on my system, it runs very sweet too, however I still eventually receive errors after about 5-10 minutes (pretty random) of gaming or even just sitting on my desktop.  From all I've read re. the SP1 update & Vista in general, the core of the issue seems to be related to a. The way in which the SP1 update handles Vsyc as described in the post above. b. The way in which Vista, "The video memory manager component of WDDM virtualizes the available video memory resources for applications to use,",,, "However, the virtualization of video memory increases the amount of virtual address space that applications use. Consequently, some applications may exhaust virtual address space when running on 32-bit Windows Vista." c. all of the above Why it works differently for you and I, I would have to suppose is the difference in hardware. Some vid cards & / or bios might better enable the usage of these features whereas others do not. Sadly for me, (short of trying to find the appropriate entries and edit the registry to try and disable these "features" as a temporary workaround) this means waiting for Vista and Nvidia to get on the same page. Right now it seems like Vista is working to adapt to hardware vendors while in the same time, hardware vendors are working to update to Vista. This is hard to do when both are "constantly" making revisions and updates... And the word is clusterf$#@...  It all boils down to patience.... Unfortunatly, I start CDL training in a couple weeks meaning A.F.K. for a few weeks, then O.T.R for 3 weeks at a time with only 2 days off inbetween.   Need a laptop without these issues for while on the road.  ***Update*** Eureka! I have finally found my interim solution to the issues I'm having. Regedit, HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers Added 2 new D_WORD values in that key TdrDdiDelay   dword:00000012  (Hex value) TdrDelay     dword:00000012  (hex value) Essentially what this accomplishes is simply to slightly extend the time it takes for the Windows TDR function to kick in. TDR is what causes the game to black out and jump to the "receiving screen", also what triggers the "nvlddmkm.sys has stopped responding" error to appear in the taskbar from time to time. So in ArmA, basicly any time framerates may momentarily drop below 6.25 fps for just a fraction of a second 16ms by default (i.e. large # of textures loading, memory error, overheating GPU, underpowered GPU etc.) and by adding a slight delay to it, some systems will never trigger the TDR function. Again, all very dependant on individual cases, but this fix should work for many playing on mid to lower end gaming systems (Provided the root of their cause isn't an actual hardware fault.) Keep in mind TDR is not a bug, it's a feature!!  The initial report of this fix I saw suggested using a value of 20, but there was alot of studdering and what-not going on so I cut it down a bit, running fairly clean with the 174.74 beta forceware drivers. 30 minutes in game with no error reported (would only take 15min. or so before) *Update* With the 174.93 beta driver and no TDR delay added in registry, I still get the occasional black "Receiving,,," screen. Replacing the TDR delay in the registry, I had an appcrash after about 10 minutes.  In either case however, the game lost much of the fluidity it had gained with the 174.74 ad 174.85 beta drivers.

Well I dont have any direct info for you other than to say I've seen many reports regarding there being a bug with SLI & AA (Suprise!) I can at least direct you HERE. It's an offshoot from the nZone forums (User to User support specificly related to SLI cards.) Unfortunatly they require registration to view threads. But you should be able to find a few interim fixes / workarounds for your issue (I'd hope) Theres also a Forum section which seems to offer Beta Games for SLI users Best of luck.

Just trying to get to the bottom of my nvlddmkm has stopped responding issue here and for a temporary fix it appears as if a regedit will be required, so it occoured to me to share a thought on the subject with regard to Vista and those who will be making the XP-sp2 to sp3 transition. (Or installing new drivers for that matter) Keep in mind as updates are released from hardware vendors and Microsoft, these updates will often expect certain entries and specific values to be present in your registry, and if you've been running thru and changing 0's to 1's or adding new D_Words, Strings & Values, there stands a good chance that future updates to your system may not work as expected.  So just as a "good rule of thumb" to the brave of heart who would like to see if that "new fix" will work for solving their issues, PRIOR to making any changes in a registry entry, right click on the Key folder where you intend to make the change and hit Export. This will create what will essentially be a registry patch that you can later re-install into your registry prior to installing any future updates. (With 98se I used to keep mine in my own windows subfolder called "Mypatches", much easier to find this way  ) Not that changing a 1 to a 0 is so hard to recall, but with D_word additions / deletions, it makes life alot easier.  Some might think this excessive, I just feel it's better safe than sorry (I recall a few instances re: tweaking the connection speed in 98se where later updates and fixes didnt work properly for the reasons I had outlined above.) Also, I'd name the "patch" something relative to what you were making the change for, i.e. nvlddmkmfix1.reg. Hope this helps someone. Â

SP1 seems to be the culprit for some folks because of THIS According to Microsoft, they've supposedly implemented a "Power Saving Feature" which is supposed to disable VSync after a period of about 16ms when theres no refesh info (No mouse movement, no fresh screen render) It's got me a bit puzzled as I've done a few full searches of my registry and have as yet been unable to find the related registry entry.  The problem seems to be that in pre-SP1 drivers (or drivers not written to support this function) when this gets called into play, the Vsync remains disabled  It would certainly sound like probable cause for the "nvlddmkm has stopped responding" error I've been randomly receiving. Happens rarely now, but at any time (In game, on Desktop etc.) with the 169.44 drivers. "So use the 1.74.xx drivers,,," but then the system tends to reboot itself, or the gamma whites or blacks out my screem much more frequently. Yet it does seem to be a good sign in the sense that this is one of those Vista "features" that we have to wait on Nvidia to properly support, meaning it should happen sometime in the next 5 or 6 months... The only related non-MS forum thread I've found on it was on this Flight Sim  fan site P.S. If anyone does find this registry entry, could ya tell me where? I wanna disable it.  ***Edit*** : Couldn't find it because it exists as part of what should be the driver update supporting the feature, meaning I need to find the relative reg. entry, but found some leads on tracking it down.

Such a joy compaired to the vanilla audio. Thanks once again for a nice piece of work. Really adds alot to the immersion level. . Â Â Â Â Â <--- 2 tup. ***Edit*** By the way, I really like how when the guy next to me unloads a PK ammo can next to me, I'm partially deaf for a while. Again big + to the immersion level.

Judging by the picture, best guess would be that althou your cards aren't in SLI mode, something's telling them they're supposed to be. I.E. SLI, 1 card renders upper half, second bottom half. In your shot, it looks like the intro (Minus text and so forth) has been crushed down to the lower half of the screen. Video cards "We're not running in SLI mode" CPU / Mobo Chipset "But theres two of you! so we're spitting your video image Video card 1 " I want no part of this" Video card 2 "Ok, I'll do the rendering" I'd be checking the Asus site as well as Intel or Nvidia (Thats a P35 right? / Intel) for updates to the chipset inf files /drivers, not just video & sound. Chipset inf files controll the handling of I/O from various system resources (sound-video cards to CPU, CPU to PCI slots, ram etc.) And if you do find there is one uninstall your video & soundcard drivers before installing the chipset update as it wil lay out certain guidelines for how the sound - video card drivers should be configured on install. (IIR, the 174.85 beta drivers @ guru3d.com are supposed to have improved SLI handling listed as one of the "fixes")

Well, before you try opening the registry editor and going in manually, try using a registry cleaning utility (Theres quite a few at http://www.webattack.com/. It's a great site to find pre-tested, spyware free shareware & freeware utilities for a great number of purposes, registry cleaning being one of them. (I use the Eusing free registry cleaner, works pretty good) In the event you're running Vista there may be something left from the Italian install in the Windows\System32\DriverStore\FileRepository folder as well, I'd guess the best way to find the folder in question would be to search thru the folder creation dates in there. I'm sure Vista has a few more folders which hang on to residuals from uninstalled app's elswhere (Like documents & settings folder) So I'd say a search for "leftover files after uninstall" in Google might be in order. Also, in cases of the File Repository and the Documents & settings folder, you must alter the access privelages (Need to be logged as administrator to do so) to allow for deleting of unwanted files (I'd personally suggest making a backup of anything you want to be rid of just for saftey's sake, mabey go as far as setting a restore point before fudging with things.) Anyway, once you've run a reg.cleaner and ensured theres nothing left from ArmA / Codemasters / Atari / Cousin Joe, go ahead & try again. Good luck

Anyone working on heavy equipment? Bulldozers, steamrollers, shortbed dump trucks, multi-story cranes etc.? Stuff heavier than a tank and more low end torque. (mabey the fallen trees could be pushed around to form roadblocks? if not, City busses and 5 ton truck wrecks would do) And if someone were to make a workable crane, could they add a remote for operating the crane from the load platform? (Im thinking rooftop access to the buildings without proper internals just for sniping, provided the load platform can be made to lift the character, I'd have to guess handrails are in order.) I Guess the Crane could be based off something like the SCUD launcher. Mabey that lift assembly could be modified to operate on the dump truck or the bulldozer? A pack of Tractor trailers would be cool too with unhookable 5th wheels and all., empty / loaded flatbeds, closed trailers weighed down just for the sake of adding to the forward momentum, "Battle beds" bristling with MG's, launchers, HQ, "Field hospital", surveilance, etc. Mabey a mobile launching station for the UAV addons? Most important of all, MG turrets on them all (depending on size) like the Road Warrior Bulk fuel trailer, all armored with semi-protected "crows nests" along it's back, A flamethrower could be handy for this too. (I can see the framerate dive already, but lord it could look sweet) Just some thoughts running thru my mind before I pass out.

class = unique identifier name = song title sound[] = path to the song and some volume setting (just leave those at 1) - copy and paste up so many of these class sections as you have tunes - make sure each class is unique; feel free to put crazy numbers in addition to a sensible name - the name section isn't integral, but it makes you able to distinguish between songs in the player - make sure the path is 100% correct - doublecheck everything Note that the only "name" which can have spaces is the name= "XXX" line, The class myTrack1 cant be written as my Track 1 ,my_Track_1 would work Same applies for the filename of the .ogg file, no spaces allowed, well, [i]you could use spaces[/i] but you would never get to hear the track ingame. Great Toy Hulk, thanks much. P.S. Any chance of having a repeat, or shuffle feature in the future so I dont have to keep hitting "Play music" in the middle of a firefight?

Yes, I've noticed that even when I have my ArmA folder, subfolders, & / or .exe added to the standard shield/custom level/advanced tab/ scanner exceptions list there is a notable performance hit. Just right click the taskbar icon and pause the standard shield provider, goes away. Thou as I havent played the game online, not sure if the Network or Web shield has much if any impact on game performance. Another possible issue could be fragmentation or bad clusters on the hard drive. I had about a weeks period during the 1.07 patch where my performance gradually declined to the point where my avg. was about 10 fps on all low settings. I ran chkdsk which found a number of bad clusters, after they were fixed the framerates were back up to the low 30's mid 40's. Defragging also improved performance after I went about 6 months without doing so, started noticing alot of studdering and pauses in all my games, COD:UO, MOH:AA/SH, ArmA, etc. untill I defragged, then it was almost like a fresh install. Again thou, with regard to the video drivers, open your windows\system32 & windows\system32\drivers (Or XP equivalent) folders and verify the files last modification date (right click-properties-details tab\date modified) as I've noticed with Nvidia, there are often "left overs" when uninstalling old drivers which dont allow the new drivers to update properly. I'd have to guess that it's possible for the same to be the case with some ATI driver components (as it seems to be the result of Windows XP\Vista's ability to cache old driver files away for use in the event of rollbacks etc.) I'm really thinking it's a matter of getting the game to run "as best as possible" but the real solutions to playability aren't going to come from BIS as the root of the trouble is in the mess of buggy drivers from hardware vendors scrambling to catch up to Microsoft and from MS who seem to insist that all faults seemingly related to their software are in fact due to bad hardware, bad ram, or basicly anything they can think of that doesnt involve them taking any blame... it depresses me to see how many people are getting duped into running out and buying new hardware in hopes that their App. of choice will work, only for a hotfix which addresses their old issue to be released some months down the road. Another topic I've seen very little mention of aside from Video and soundcard drivers are the mainboard chipset drivers which can have an incredible impact on the performance of the hardware you install . I.E. The last system I built, started with an old TnT2 untill I got a Ti4400 (When they were still $500). At first when I installed it, I found I had gotten better performance with the old 64Mb card untill six months later after Intel released an update for the i850 chipset after which, the Ti4400 began to perform how one would hope it would after spending $500 on it (Too bad by that time they were already retailing for $200 and the 5x00's were out. lol) Hmmm.... Mabey I'm gonna go do that myself now come to think of it.