troop

You can do that. (2 items A, then 1 item B and then 1 item A again. Even produce 3 items C inbetween. :) ) See: http://forums.bistudio.com/showthread.php?135771-Production-Queue-gt-Drag-items-up-and-down

The manual only mentioned to LMB to remove items from the queue - but did anybody know, you can also drag your items up and down for priority production of an item while retaining(!) production status of an already say half manufactured item (blue bar) ? Very happy to discover this, because remove only was not fun, if you needed something more urgently and had to later add it again in lowest spot. Using drag items, you can also (somewhat, to an extend) control material expense rate. You may have noticed that with more expensive items, material expense rate rises. Now if you don't need that item next, but rather want to keep up production time with material income or even boost material income for an amount of time, just drag some low value item to the top spot in the queue, thus lowering material expense.

At around (after) savegame size has reached ~84-85 MB, trying to save the game in either new slot or overwriting an existing one, will result in lockup of the game. Looking for the saved file in profiles folder, shows filesize 0kb. There also should be an option implemented to delete old saves within the game.

Does this addon help a little? Great Addition. VFTCAS - Terrain Collision Avoidance System http://forums.bistudio.com/showthread.php?t=89392

174.74b;..very good driver that! Using since release; better than any one before. Recommendation: Do not install/use the even newer 174.82 Beta too many problems.

Do you need this specific version or the latest avaiable? OpenAL 2.0.3 http://www.techpowerup.com/downloads/637/OpenAL_2.0.3.html

Setting '0' is unsupported from driver level (exactly because of the instability) and even if Rivatuner is capable of 'forcing' the value, it is *not* recommended to do so. Standard setting on every fresh driver install (keep that in mind) is '3' ..depending on your setup, use 1 or 2. (using 2 here myself) - Also observe, that not every game engine benefits from the lowest possible (= stable/fastest) setting;..there are as well some engines, which perform best with values even above '3' However, I think '6' is the highest setting you should ever use, because beyond that, everything exhibits bad mouse lag and other problems (like sound skipping etc.) So, for always peak performance (per different engine), its favorable to set up an profile for each and every game you play using nHancer, for example. One setting is just not optimal for everything.

SPOILERS! . . . . . . . The sneaky approach. 1. Change weapon to silent one and order squad to stealth/stop. Take along 3 charges. 2. Move N along western shore past the first 2 guards. 3. Sneak NE low 'n slow until ridge. 4. Crawl E until E bushline. Observe patrol of 3. 5. Kill patrol of 3 fast @ ~30-35m distance from behind. 6. Crawl NE, then N towards Shilka; place charge. 7. Crawl back all the way to the western shore. 8. Sneak N for bush cover, then crawl NE past several guards(! ) 9. Crawl NNE, then turn SE towards bushline with second, hidden Shilka; place charge. 10. Crawl back NNW and in safe distance, sneak NE, then E to northern bushline. 11. Crawl SSE towards southern bushline. - 12. Call in the attack via Radio and wait for the alarm to go off. Once the hectic is on... - 13. Run- stop/shoot -Run- stop/shoot -Run towards last Shilka, killing 3-4 enemies around; place charge. 14. Make to safe distance, blow Shilka;..mission complete. - Safe frequently. Once you hear an enemy voice; curious, its time to reload(up to point 11). It can be done 90% solo/silent. Try this way: http://img156.imageshack.us/my.php?....kc4.jpg

@Mod: Please merge with this one; answer partially given. Thanks. http://www.flashpoint1985.com/cgi-bin....t=69094

This is because you lost some of your initial mercenaries members in an fight and they got replaced by rebel soldiers (rookies) to fill the ranks. Just like in OFR: Resistance; your initial buddies are unique characters. Dont let them get killed, if you want to keep them throughout the campaign. Not an error.

This is because you lost some of your initial mercenaries members in an fight and they got replaced by rebel soldiers (rookies) to fill the ranks. Just like in OFR: Resistance; your initial buddies are unique characters. Dont let them get killed, if you want to keep them throughout the campaign. Not an error.

Personally, I just could not imagine (in an positive sense! ) what BIS would be able to come up with;..apart from ArmA 2. But if any 'new' franchise, I would expect nothing less than 'at least' the same scope and depth of engine/gameplay options from some such new, because BIS made themselves known of this. To this day, there still is nothing similar out there...if you plan to top yourself..cant wait! Its been soo many years (7) now (thank you very much! ) and frankly, I (we? ) became so used to the OFP/ArmA 'world' that anything even remotely more 'mainstream' by BIS ...would 'feel' very, very odd. No? As it may, times goes by, interests and needs change;..maybe an split-up is possible? Until then, playing ArmA + great addons and missions, waiting patiently for 1.09 and ArmA 2 to arrive..

SPOILERS! . . . . . . . Same here. The guy with the prince though, does tell you, 'she is heading to the Airport' According to other reports, there should appear an dynamic marker on the map, showing her position. There *is* an red marker on the map (all the time; check out) which marks the position of an fuel-station NW of Corazol and E of the Airport[Fi51]. This marker does not move. There are 2 cars and 2 civilians. - How I did it (with some objectives not checked in the end): 1. Route first reinforcements 2. Race South; there is an faint dirt strip leading east towards 'the' farm(Really bad to see;..not on the map! ). Kill attackers there. (One might miss them, if they are already deep enough into the strip) 3. Turn around, race further south towards the crossing, turn left via Modesta to Gaula. Turn left towards Bajo Valor;.. and here, you will encounter an moving dynamic marker, which is an larger force, about to attack 'the' farm from the *South* (check briefing) 4. If you managed all this in time, you will only have some few strugglers at the farm;..if you do *not* manage it, there will be an pretty hefty firefight...or else. 5. Once you kill the last attacker near the farm(objective *not* checked), an cutscene pops in, which seals the fate of the queen. 6. Ok;.. but there was no dynamic marker (played mission three times already) showing her position and checking the airport turns up nothing. - Either it is *not* really 'the' airport meant, or the scripting fails somehow. I'm pretty sure, I did everything in order;..except Point 3;..once I learned, what to expect. But all three times, I have played slightly different (with big firefight, or completely avoiding it) with the same (non-ending mission) result.

Can anyone confirm, the fog bug is finally gone? Or at least much, much better..starting with this driver version! Check this out (QG; range): (ViewRange 2500m; more does not further improve) Fog better with 163.71whql_01 Fog better with 163.71whql_02 Fog better with 163.71whql_03 Sooo;..if 163.71 provides reduced fog, will the announced 1.09 patch reduce it even further? All I can say is, if it stays this way, like shown in the pics, I'm already happy. Maybe BIS can say a word or two, if there was any code change that came with QG, or if this is indeed all credits to the driver.

^ You are right and I admit it. Asking an moderator to lock this. Played some other missions now...same as before. Did I mention, I really hate this fog bug THAT much? I want to apologize to everyone, getting his hopes up..another time. I'll shut up now. Go play.

Yes, I do not deny, it is still there;..but playing ArmA on an daily basis;..after installing the driver and then QG, which arrived today, I *immediately* noticed the difference. It is not completely gone, but waaay better. Yes;..sorry for the pics, they do *not* do justice, to what I've said. But if you have been plagued by the fog bug for soo long time, you will notice it yourself from the get go. What can I say, Pics like Picture 3 just not were possible;..you would not have seen the sniper at that distance due to the fog bug. (on my setup) Edit: I'd like to add..for me, the fog bug was in full 'effect' from driver 162.18 to 163.69b. (Tried all of them released) 163.71whql, for the first time, shows an clear improvement.

First impression is positive. Testing right now. Forceware 163.69 Vista 32bit Forceware 163.69 Vista 64bit Forceware 163.69 WinXP 32bit Forceware 163.69 WinXP 64bit 163.69 Release Notes: WinXP Vista

In addition (NVidia card), check for the little app 'NVTray' NVTray_1.0.5.1-B4 which will allow you to doubleclick trayicon to enable coolbits and also enables the classic control panel (if you want it) With an rightclick, you get to setup for example render ahead frames easily. And yes, of course RivaTuner 2.04 for more controls.

Yes, still. (on my setup) I can play for hours and hours with certain, not maximum res/viewdistance/detail settings (sweatspot) but if I change anything to higher/more than these settings, the crash will occure still. (flying much faster than on foot) The memory error (VidMem not released properly) on 8800s is still present with these drivers. NVidia said, it would be fixed with an september driver release;..however, this one is not it. - Apart from that, this driver performs *very* well and has got nice IQ too. Not only with ArmA, but with every other game I tried with it.

@Balschoiw ^ Thats exactly why I asked. Thanks for the excellent explanation of possible problems. - Right now, if you look around in the middle of an town, you already can run into explained problems with texture loading based on scene complexity/detail. And that is with non-enterable buildings. If you now take into consideration, just *how* much more details (windows/lookthrough/interiors! ) would have be to displayed at all times (turning) you would imagine the problems present now already could only become (very much?) worse. - All I could think of to handle/counter this would be *very* dense cities with very limited possible viewing range (so the machine still would be able to (only) render the immediate surroundings of the player;..but how about wider areas (where a much greater deal of details would have be to displayed all time), let alone *flying* over such city? Wouldnt this kill *every* machine? - Nevertheless;..I'd really love to play in an small town with 100-150 buildings..and if they were (also) AI-navigation friendly, all the better. Just beginning to sweat thinking about it.. Edit: Snake Man; thanks! I will definetely try this one.

Question: Is it possible to create an unique (smaller?) island with, say 100-150 enterable buildings? (think desert town) Would ArmA even be able to handle this amount of buildings at all or would it totally crumble? Playable vs non-playable FPS? Not sure, but is this an (power of) CPU thing, (power of) GFX-card + avaiable memory thing, or (ArmA-objects) limitations thing? If not 100-150, what *is* the limit?

Try and see, if lowering the following settings together make it go away: (What is your ingame resolution? Does it also happen one notch down?) Viewdistance: 1200-1600m Terrain detail: low or normal Object detail: low or normal Texture detail: normal Shading detail: normal Shadow detail: normal Postprocessing: low AA: disabled AF: can be kept very high Edit: Oh, an no, this has nothing to do with the 'mouselook-freeaim' slider setting.

^ Phantastic! All over it! Thank you.

^ Also, there needs to be some small 'cosmetical' fix, while you order an AI soldier to drop some ammo (for you on longwinded missions, where you run out) Say, you order to drop an Stanag round; no problem, an little ammopouch is displayed right next to him. But if you order to drop an M136 or an frag, there is no visual resemblance of the ammo dropped; its invincible. Yes, you get the 'take ammo' symbol and can then use the action menue to take the round[if its more than one type of ammo, you get the 'gear' symbol], but its really hard in the heat of the battle sometimes. - In addition, on the map, you get an blue 'ammo[dropped] symbol' [small blue crate thingy]and once you took the round, this symbol will not be deleted from the map. Maybe this small fix makes it into 1.09? Thanks. - http://img338.imageshack.us/my.php?....ht9.jpg -

Installed yesterday; and just like 163.44[major improvement for me] smooth and stable operation on my setup for several hours of play.