troop

I have an question related to those waypoint map-icons for teammates. In OFP, you had some nice, crosshair like icon to pinpoint the location to go to *exactly* (i.e. one bush of an bunch of) - In ArmA, there is this FAT, imho ugly and *annoying* black square, which makes precise placement of troops impossible. Whats more, if you create, say an ambush (bushes..house corner locations?) you got those multiple FAT, ugly squares overlapping each other. (Is this really ingame, or could it be gfx-driver related? Well, 3 different drivers now since release, so I guess, its not that) I really thinks, its a mess. Why was this perfectly suited crosshair icon from OFP changed to the worse? I'm astonished to not have read something yet, to point this out. Of course, I could have missed it. If there is an existing thread, please guide me, thanks. Whats more;..*please* change it back to the fine crosshair! -- If this is not wanted for;..please give me some instructions to do it myself. I cant stand those, really.

This happens, if you are the commander of an group and have the highest rank ...in addition(! ) with an Teamleader present in your group, which has an lower (but not *the* lowest! ), rank after you *and* even lower rank (than Teamleader rank) group members present. Missiondesigners (should) allocate ranks. Read carefully, its somewhat difficult, what makes it happen. - The situation, when it happens goes like this: 1. You, The groups commander, enter an vehicle and *dont* give any commands to your remaining group before you enter. (Example: All; Stop) 2. The function underlying, then *assumes*, you are no longer an member of this group and thus, the next *lower* rank, your Teamleader, assumes command of the remaining group. 3. What you *dont* see in any way is, that he even gives an command to *you*, the 'former' commander! (bug?) Same in OFP. 4. Now, if you exit the vehicle (I would guess, as long as you are in the vehicle, you are considered an own 'group' to your 'real' group...yes, its difficult to explain) you *resume* command of your 'real' group! BUT: 5. The last command, your Teamleader has given the entire group, including invisibly(! ) for you, is still in effect! That means, if now YOU give an command to the group, (return to formation from stop, i.e.) it is really given to your Teamleader, instead of ALL. The result from that is: 'ALL, follow ALL' (or: follow 2; that happens as well, if the Team Leader is the *same* rank as you in the mission! ) 6. To avoid/resolve 'ALL follow ALL' (or follow 2) all you have to do (after existing vehicle) is *acknowledge* the 'invisible' command: Just use '0' and then '1' or '2' for either *Done* or *Fail* In the same moment, *true* command is given back to you, the 'real' Commander. - Yeah, I know, this is damn hard to describe;..but its exactly as that. Next time, you get frustrated about loss of command, just do step 6; thats all. - Edit: Sorry, got it wrong first time. Of course, the command is '0' and then 1 or 2...not '5' like I wrote first. Edit2: Thanks to plaintiff1 for pointing out my error with 'invisible'

You can disable the ingame AA/AF functions and then use nhancer 2.2.2 to create an profile for ArmA with (truly) maxed AA/AF levels. You can even use CSAA and transparency AA then within ArmA. (checkmark; 'enhance ingame AA settings' ) (8800s) And yes, you can forcefully prevent any (ingame; custom) optimizations from happening. --- Though, keep in mind, Suma[Dev] mentioned elsewhere, that this 'forceful' approach can trigger any kind of problems with ArmA, including BSOD or other image anomalies. Be warned. Try it;..but if there are said anomalies, do not report them as bugs;.. *always* only report bugs which happen, while using purely the *ingame* settings...NOT forced external ones! --- As I already mentioned here elsewhere, the AA/AF functions of ArmA seem to be *custom* made and not standard. You can directly compare image quality/filtering/performance with *ingame* Very high AA/AF levels vs nhancer (driver level forced) AA/AFx16 image quality/filtering/performance settings and you will discover, that ArmAs image quality (and thus overall performance) vastly differs. - 1. Using ArmAs ingame settings, you will get nice image quality and 'good' performance. (Think about heavily optimized modes even if 'Very high' settings are used;..very similar to the optimization level options, the *driver* itself is providing, i.e. Trilinear optimization) 2. Using nhancer driver level forced settings for AA/AF, you will get superior image quality ingame, but this comes at the prize of *heavy* performance loss! Try it yourself, make screenshots and compare against each other (+Fraps for FPS) Heres hope that one day, once ArmA and drivers, specifically for the 8800s, have fully matured/optimized, you will (hopefully) be able to truly experience ArmA performant and in addition get the very best possible image quality with the 8800s. I do not know, if its the exactly same story with the ATi cards. Someone would have to test this out fully to confirm/deny.

If this pauses are indeed network access attempts, you can try to block those off with an personal firewall and see, if it helps the cause. Just to try if its the reason, download and install Freeware Tiny Personal firewall 2.0 (3.0 = money) http://www.devhood.com/tools/tool_details.aspx?tool_id=785 Install Tiny and startup ArmA; the Firewall should react upon it and ask you to allow access for ArmA.exe to connect to the Internet. Just deny that (an denial rule is created). Then, shutdown ArmA and try it again, this time with the editor. Still pauses? Sidenote: If this firewall (out of date) causes problems on your PC, uninstall it after the test and get an proper, up-to-date one. (Tiny, Kerio;..just NOT Zonealarm! If it does *not* cause problems, you should create 2 rules One for access granted, if you want to play MP and one denial rule (which you got already) . - Just activate the rule depending on your needs and deactivate the other. If, however, you do not need anything net related, just deactivate your network card in device manager.

Hi, Check this please. http://www.flashpoint1985.com/cgi-bin....t=59291 - http://www.flashpoint1985.com/cgi-bin....t=59373

Hi White935 Check this entry and afterwards your settings. Its an overload of textures (in too high detail setting) - http://www.flashpoint1985.com/cgi-bin....t=59373 You should be able to tune it in a way, where this problem either ceases to exist, or creeps up at least in an reduced manner. Yes, its not pretty, when it happens, but can be avoided. Not sure, if BIS will be able to fix this completely..for every GFX-card/setting/amount of VRAM there is. We'll see. Also, memory allocation has been changed completely going from 1.04 to 1.05 so dont be surprised too much, if you did not have this with 1.04. (Instant map load with 1.05, for example..instead of everytime new loading it from HDD) ohh;..and please let us know, if you can successfully tune it to an point, its bearable, thank you!

Did you buy the 505 games (v1.04) version and patch it to 1.05 already? If that does not turn out good, maybe patch 1.06 will fix all the various startup problems. Sorry, cant be of more help right now.

You are correct. I've removed some negative Vista bits from my former post. Thanks for pointing out.

Aint that the truth. If there had been an -5 rating, I'd given it. Particulary for the insults. Also, it felt all the time like he was totally trying;..but failed miserably. Is it just made up?

The choppers follow some route all around the island. You must try to be in their route and be quick about shooting them down. Do not read the 'mission solution' (inside briefing) if you want more tension. Do not lose your truck. Put at least one more stinger on your nr.2 (I mean the missile only, not launcher) I dont wanna spoil too much. Good chances to get an chooper, would be in the general vincinity of Cayo and three opportunities would arise around Corazol. Thats where the turbine sound came from anyways..

Rough Guideline ArmA on different Videocards-avaiable VRAM-suggested(! ) settings. Ok, derived from Windows XP SP2 tests on 6800GT GLH 256MB (res:800x600 - 1152x864max) (nforce2 AGP) 93.81b driver 7800GS+ 512MB (res:1152x864 - 1600x1200max) (nforce3 AGP) 93.81b driver 8800GTS 640MB (res:1280x1024 - 1920x1440max) (nforce4 PCIe) 97.92NGO driver (could not test 128MB VRAM settings; lack of gfx card) disabled* stands for: If 'disabled' at your current reasonable resolution provides OK framerates and *no* errors; try option one notch higher OR one notch higher resolution with same settings. Of course, there are the 2 main other factors; your CPU und avaiable RAM size. But in general, approach low with the graphical settings and if satisfactory results, try either (1) higher res OR more eye candy, not both at the same time. Texture Detail is *critical* for so many errors reported, so at every res, I suggest you keep it at 'normal' at all times. (Until an future patch/driver further tweaks this component) And yes, I specifically mean the 8800s Shading Detail is similar critical, but to an lesser extend. (depends very much on GFX card specific architecture, see below) LOD errors, missing textures and the like are caused by too high settings for the capability of the gfxcard/internal design (pipelines/bus bandwidth/AGP aperture and PCIe system bus) plus driver issues. All tests/settings aimed for 19-35FPS, no LOD errors/flickering Higher FPS are possible, of course. Viewrange has the most effect on FPS with suggested settings. For faster, aim lower. 128MB VRAM (no tests; lack of card; speculation) Viewrange: 500-800 Terrain Detail: very low Object Detail: very low/low Texture Detail: normal Shading Detail: disabled/very low Post Process: low Anisotrophic: disabled* Shadow Detail: disabled* Antialiasing: disabled* Blood: High --- 256MB VRAM (1024x768) Viewrange: 800-1200 Terrain Detail: very low/low Object Detail: low Texture Detail: normal Shading Detail: low Post Process: low Anisotrophic: low/normal Shadow Detail: disabled/low Antialiasing: disabled Blood: High --- 512MB VRAM (1280x1024) Viewrange: 1000-1500 Terrain Detail: low Object Detail: normal Texture Detail: normal Shading Detail: normal Post Process: low Anisotrophic: normal/high Shadow Detail: normal Antialiasing: disabled/low/normal Blood: High --- 640MB VRAM (1600x1200; 1920x1440 with *lowered* settings fine) Viewrange: 1200-2000 Terrain Detail: low/normal Object Detail: normal Texture Detail: normal Shading Detail: normal/high Post Process: low/high Anisotrophic: high/very high Shadow Detail: normal/high Antialiasing: disabled/low/normal Blood: High --- 768MB VRAM (1600x1200, 1920x1440 no tests; lack of card; speculation) Viewrange: 1200-2500 Terrain Detail: low/normal/high Object Detail: normal/high Texture Detail: normal(! ) Shading Detail: normal/high Post Process: low/high Anisotrophic: high/very high Shadow Detail: normal/high Antialiasing: disabled/low/normal Blood: High ----- Try, suggest, discuss, I guess. Edit: 8800GTS has 640MB; I had 768MB written. corrected.

Not sure exactly;..but from the looks of it, it is the same with XP, if its behaviour is 'tweaked' to prevent applications from 'stealing focus' TweakUI (Powertoys) can handle (better: force) this for XP (flash minimized icon in taskbar 'n' times; default is 3...instead of immediately switching minimized to activ windows..very useful) Nevertheless, I have seen this with many games, which run Videos (different app; like binkplayer) *before* the game process. Usually, an quick Alt-Tab to Desktop and then Alt-Tab back to the game process (Do not click on the process in the taskbar) gives back focus to it. Vista? No idea, but I assume very similar;..just Alt-Tab one full cycle out to desktop and back into the game. Edit: I'd like to add, if you use the -nosplash parameter, there should be no need for Alt-Tab, because instead of intro, game process is directly started. Works out?

Thanks! THAT one made my day. Oh and sorry (giggle) I do not have an helpful answer for you.. ...mmmmmwahawahawahawahahwahwhawaha....

Kiwi;..isnt that the 101% same situation with Windows XP back then? Did you personally 'Xperience' the pile of shit, called Windows XP 1.0 ? I came aboard long after SP1 and only then was totally convinced..compared to W98SE2 before. Games? Drivers? Apps? The lot? And very unfortunally, ArmA got released (with XP support 'only' ) to almost the exact same time as Vista; 8800; the *other* lot. Everyone is in the same boat and only few managed to get their code 'in shape' for Vista release. Thats my impression anyways. BIS is not an big company and judging from ArmA 1.0 state, they were struggling to get out an working version at all. (Pure assumtion) Give it some time, please. Edit: Removed some negative Vista opinions from my post.

@DPhreeze Sit down, relax and start over. Uninstall ArmA and clean Reg. Install 1.0 and then go via 1.02 first. Attempt 1.05 international. Dont use no-DVD, DT, Y**U, language patch. What gives? Be specific about eventually occuring errors.

Desertfox; this is OT, but... I want to share an special sig line, I found elsewhere especially with you. NO ONE, take this personal in any way, ok? Please. I just thought, its funny...and wised up.

About running ArmA on the new Vista OS, BIS has only acknowleged, that there could be problems. (and temp fixes, like the one you mentioned) Vista OS is not directly supported by ArmA as of yet. That is as far as I know, nothing more. If there are other, newer official statements, I do not know about. If it can be patched, to fully support Vista OS, I also dont know. On the box, only Xp is stated as officially supported. I'm sorry, cant offer more for now..so please consider this answer as one of many. Also, you maybe want to read this: http://www.flashpoint1985.com/cgi-bin....t=60071 and that: http://www.flashpoint1985.com/cgi-bin....t=60235 8800 cards are new technology as well with complete new internal design. However, I for one do not have any problems (honestly) running ArmA on XP SP2 and 8800GTS (97.92 driver) See posts mentioned. I do have the heavy fog as well.

Because many with this kind of setup assume, it *must* be possible to run ArmA with the maximum settings, the program provides? Opteron 165/1800MHz @2.88GHz Coming from DualCore nforce3/2GB RAM/7800GS+ 512MB AGP I'm running it now on DualCore nforce4/2 GB RAM/8800GTS 640MB Guess what happens, if I choose my settings too high? (I dont have, but also with SLi setup?) Arma runs like crap! (Perfectly normal) If however I lower my settings to slightly different tunes on above said setups, ArmA runs like 'it was meant to run' in your words on both machines. (fluid, no hickups, no studder, no texture failure, no 800700e AND good-looking) - I *assume* there is no 'normal user' desktop setup, which is capable of running ArmA with maximum settings..today. Just look back at OFP at the time. Same story almost. So, is anyone forcing to run ArmA with settings, his machine is simply not capable of? ('My setup MUST run ArmA with max settings, because every other game does?' ) Of course, there are an sh**load of other problems currently, aside performance/settings Edit: Hmm..reading again, this could be come across wrong. I do not want to sound aggressiv and its not meant to be. I am sorry. Also, I'm nothing special. ArmA (after a lot of tweaking) just runs really satisfactory on my different machines. Edit 2: Plus, *never* assume the *minimum* requirements printed on the box could run games and at the same time be fun. Everyone sees the fine screenshots 'n all and could be tricked into thinking it would look like that on his machine with min. specs and run stellar at the same time. Reality proves time and time again, that not even recommended specs, and sometimes (OFP/ArmA) even specs *far* beyond that, cant run maximum settings...currently.

And make sure, you download the DirectX 9.0c >February 2007< release. There are several older ones, which do not include the file. If you plan on downloading the redistributable, that is.

Alright. First, this will be an hard one to tackle and it will be *very* time consuming, since it can have a number of causes; so be prepared. (stop: 0x0000008e) It is an serious one, and your system in general is not healthy. Hardware and/or software. I know by experience with one such.. The causes could be: OS GDI error (graphical subsystem of XP) Video card driver error RAM faulty (or misconfigured) Rootkit even - Now, you wrote about problems (and resolve by removing Sli setup) with other games as well, so it is not ArmA only, that causes this error for you? Well, take your pick. Either RAM or 7800GTX driver first. Whatever you do; you *should* make an full drive backup, before you proceed with the suggestions about chipset or vidcard drivers. RAM: You got an special mainboard there, which allows for various RAM tweaking, which are beyond the scope of most other mainboards;..did you 'tweak out' your RAM? If yes, then reset it(timings) to automatic detection(by SPD), or choose some general relaxed settings. After this, retry to start ArmA. If this does not help, remove RAM sticks and try with one only. Try *both* separate. This should reveal, if one of your sticks is either faulty, or if your RAM setup is to 'sharp' Yes, ArmA is very sensible to overclocking in general. - 7800GTX driver: So, other games are working correctly, after you removed the second vidcard? But still, you get this error with one 7800GTX and *only* with ArmA? If so, I suggest you completely uninstall (not just reinstall over) your current driver and also kill all remains with >driver cleaner pro< in >safe mode< (Know, how to do it? If not, check Guru3D.com and the Nvidia drivers forum section; DC Pro is explained in detail there or in its readme) Once done, reinstall 7800GTX drivers; I'd suggest 93.81b for your card. btw;..do you know your chipset drivers version for your nforce 4 board? Can you tell, which ones you used? From mainboard support CD or the avaiable remixed ones? - OS GDI error: Not much, you can do now, if this should be the cause. It should have been fixed with SP 2 of XP. If in doubt, reinstall SP2 over. (+ all patches afterwards! ) If you plan to change mainboard soon anyways, I suggest you skip this point for now until the time of newbuild. (OS>chipset drivers>vid-drivers>sound drivers>ArmA) http://support.microsoft.com/kb/315335 http://support.microsoft.com/kb/330187 - Rootkit: Well, you *never* know for certain. Found someone, who had this as potential cause for stop: 0x0000008e, after he tried every suggestion and none of the obvious solutions helped. Check your minidumps! See info below. You've planned on changing your mainboard soon anyways? Then you *definetely* should make an complete wipe of your current system and build up anew from null. (Not just using an image of your current system and adjusting it to your new setup/hardware) http://www.short-media.com/forum/showthread.php?t=50966 -- Yaa, I know, its not pretty. Back then, it was faulty RAM for me. Its an serious error and you should act, because you very well could lose important data, even if its only ArmA, that triggers this one for you now.

Please check, if you have set this checkmark; if yes, then remove it to see, which error is involved. (automatic System restart at error) my computer>RMB>properties>advanced>start and restore >settings>systemerror[actions; 3 tickmarks]>automatic restart I am not certain about the exact wording, but you should find it easily. Remove that last checkmark out of 3. What happens? Bluescreen or an Microsoft error message? Something else?

I do own the same Medusa 5.1 headset talked about here and testify ArmA working very well with it. About soundquality;..its good enough. (booom) And everything better will be more expensive. Of course there are 'better' solutions to be bought.

Hehe;..slightly offtopic, but then again; doesnt this bit fit oh-so-nicely what have been written herein with regards to Vista-gameplay(issues) ? Recommended, funny read(Stalker on an uber-machine) http://www.1up.com/do/blogEntry?bId=7971246&publicUserId=5380845

Thankfully, this has already been fixed in 1.06 http://bugs.armed-assault.net/view.php?id=1625