Talk:ArmA: Armed Assault: Bug List

Introduction

This talk page has multiple purposes, please respect that information from time to time will be purged from this page. You can view the history at any time by clicking the above tab.

Defining Priority

⚠

Bug priorities To make it easier for BI people to see important bugs, we introduced bug priority templates. Add new bugs with priority 0. Only BigDawgKS, Sniperwolf572, Plaintiff1, the BI staff, and the wiki sysops are allowed to set priorities to values higher than 0.

How does one define a priority?

Priority 1

• Any issue that causes a CTD (crash to desktop) during a normal gameplay. CTD using mission or content creation are not considered priority 1, esp. when caused by scripting and it is possible to avoid the CTD by not using the construct triggering it.
• Any issue that prevents the game from loading.
• Any issue that prevents installation of a patch
• Any issue that decreases performance significantly, up to the point of making the game unplayable. (especially if this was working better in previous ver)

Priority 2

• Issues that prevent MP game play
• Any other issue that causes a CTD, including mission scripting.
• Any issue that prohibits game play as per design
• Issue that prevent the operation of a vehicle/unit/object as designed. (can't get in vehicle, helicopter moves incorrectly)
• Issues that allow cheating. (example: sniper sites allows a person to see through walls)
• Significant performance issues (low fps in situation where decent fps would be expected)

Priority 3

• Annoying behavior, such as Repeated voice command.
• Sounds that aren't working as they were designed.
• Collisions in models which affect game play. (such as doors which prevent entry, invisible wall)
• AI not doing as they should/designed. (stuck, not running for cover, etc)
• Mission issues that prevent the completion or playability.
• Scripting commands that do not work as intended and/or at all

Priority 4

• Any issue that causes an in game error (missing paa, missing name)
• Graphical Nuisances (missing textures)
• Annoying collision issues.

Priority 5

• Missing sounds which maybe were never intended.
• Spelling errors
• Minor mission issues that don't affect the game play

Buglist Preamble

I think it would be a good idea to add something about keeping your ArmA up to date when submitting bugs to the introduction section. Something for the demo users could look something like:

It would be a great help to us if you would keep your arma builds up to date when submitting bugs using the demo! This way, if you are reporting bugs, we are sure that the bugs you are reporting haven't already been fixed in the newest build. The newest build is available here: [1]. Thanks in advance. --Plaintiff1 00:17, 14 January 2007 (CET)

Questionable Bugs

I've noticed that some users are reporting bugs using old builds. There are a lot of obsolete bugs on the bugs list in terms of the latest demo builds. I've flagged them. Do you think we should whipe them out now or wait for an official patch? --Plaintiff1 00:17, 14 January 2007 (CET)

Newer Entries

• No way to control parachute. It seems randon. This is a feature that's been available in BF for years ! :--Major Latency

Then make a wish in the wishlist. hoz

Night vision is apparently unusable on certain system settings. The HDR effect gets overbright and all you see is green light. My graphics card is GF6600GT with the newest drivers. Here is a picture [v1.02] --Celery

Does it stay like this? It takes some time to accomodate to the bright image Scruffy 22:37, 5 January 2007 (CET)

Removed, I think this is by design, it takes time for the NV to adjust. hoz

• AI can enter bases which are surrounded with walls/fences through walls/fences. They don't look for an entrance or a hole.

No location given not signed, useless. hoz

When you crouch with a riffle and apply turbo forward you remain crouched and unable to sprint forwards. However when you use a pistol you are able to use turbo forwards from a crouched postion and return to crouch at the end of your run. From a crouched position and riffle in hand you should be able to Turbo forward then crouch again at the end of your run -TheOne

Not a bug as per design, as mentioned by marek in the Demo TS thread. hoz

• Mission will start automatically after certain time when all players are in briefing screen. This should be changed to all players greened up or admin mission kick off. The current auto start does not allow for a proper weapons selection or mission planing. Sometimes people just end up without any weapons in the scenario. --SniperAndy

More of a wish then a bug. I think this is by design to keep the games moving, annoying as it is.hoz

• Should there be a different explosion effect when tanks fire into the ocean/water -NipWup

Wish/request hoz

• Wood stacks looking strange if destroyed pic [1.02] burns 02:07, 16 December 2006 (CET)

This might also be a design decision, as if wood stacks get unbalanced and collapse. --Sniperwolf572 17:27, 18 December 2006 (CET)

I think it's because tehy fall like trees if damaged. Seems to be dependent on angle as one fell to the right side. Scruffy 22:40, 5 January 2007 (CET)

As per design, not really a bug, make a wish for a better damaged model.hoz

• eg: on island Suthern Sahrani get AI to drive tank from grid reference Gd,56 to Ff49 (on the road) at around Grid Ga,53 and Gb,54 AI has trouble keeping to the road, or try's to find away around by going up the hill. I found that AI has problems navagating near steep land formations. Sometimes AI will plot a corse strait up the hill from grid Gd,56. [Demo 1.03] -NipWup

I beleive if the combat mode is set to careless you might see this behavoir. Try a very basic mission and change the combat modes. hoz

Some sounds are overriden by others eg: when gunner in humve and you can year a distant vehicle driving, the driving vehicle's sound is muted for the piriod of time you openfire*, this might be associated to the hardware acceleration issue where eg: you can hear a chopper starting up from the otherside of the island, *firing the gun might just be muting the bug. (ver 1.3.0.5110) on a X-fi elite pro (driver ver 1.01.14) -NipWup

I believe this is a feature of the HDR sound engine. --Plaintiff1

I respect your input, but i really dont think so. Most games with high sound quality settings enabled allow for the most possible number of sounds to be played at one time, this adds to sound detail which makes games sound good.

When a loud sound plays you can't hear the quiet ones. There's not many sounds louder than a gun going off in your face. This is a feature that acts exactly as BIS described it. Whether or not you like it is your issue. --Plaintiff1

does BIS describe that sounds are muted when louder sounds are played as a feature ? im sorry that ive missed this, can you provide me with a link where they list the sound features. and where did you get the impression that i dislike this ? ive said in my original report that this might be muting a different bug. im reporting somthing that I think might be a possible bug or fix other bugs, im not here to debate with you about a game feature. let the bis crew decide whether this is a bug or feature. -NipWup

I found Maruk's original post as well as several other mentions in other forums through the simple magic known as google. I have also been able to find mentions of it on the simhq reviews and forums, but their site is down for maintenance at the time of this writing. Moreover, this technology was already implimented in OFP:Elite. So yes, you did miss it; and no, it's not a bug. BIS has already explicitly stated its nature as a feature. Consider removing it? Thanks. --Plaintiff1 05:10, 11 January 2007 (CET)

http://www.flashpoint1985.com/cgi-bin/ikonboard311/ikonboard.cgi?act=ST;f=63;t=49299

Hi Tech

• HDR (High Definition Range) rendering is implemented to allow good dynamic range of the image in various daytime conditions.

• Similar system to HDR is also implemented for sound so you can hear well low volume sounds in quite areas and also large explosions during combat.

• AI can do everything that you can do. AI can also be mixed in with humans when playing multiplayer (as bots and opponents).

http://redorchestragame.com/forum/showthread.php?t=10160&page=22

I found out that the sounds work quite well when you deactivate "hardware acceleration" in the game options, but enable "EAX"...

while the weapons don't have echoes, these things are eceptionally well done:

• Helicopters and tanks roar at a frightening level and realistically can be heard from kilometers away.
• Gunshots sound different dipending on whether they shoot at your direction or away from you.
• There is a clearly audible snap (allthough not as pronounced as dslyecxi would want them, I suppose ^^) when bullets pass you.
• The High Dynamic Range Audio works even more impressive than in OFP: loud sound make less loud sounds even more silent for a short period of time.
• Sound shadows: when an object/building/tree is between you and the source of the sound, the sound is muffled.

--Plaintiff1 05:10, 11 January 2007 (CET)

• When player is driver he cannot reveal and mark targets for the gunner.

Driver cannot switch vehicles lights on and off without (needs a permission from gunner) [Ger v1.02] -- Miki

Driver is not commander, in M113 gunner is commander and therefore gunner issues lights on/off, targets. hoz

• After picking some grenades, I have to push "F" twice to go through "HandGrenade" weapon - Lou Montana ArmA Demo 5116

Picking up 2 different kinds of grenades is likely whats happening here. hoz

• Switching view from inside to outside of a jeep will autocenter when leaving view (by the way, the center view of HMMWV is too high :) - Lou Montana ArmA Demo 5116

By design. hoz

• Wrecks of Trucks and Cars (for instance "UralWreck") doesnt fall down if you place them in the air. Do they have a physics at all ? Screenshot [1.02] - Snowball

As per design, the wreck is in Class strategic like a house, physic's don't apply. hoz

• Binoculars are always put away (changing to weapon) when player changes stance from standing to crouch... very annoying! I suggest that binoculars should work in the same way like scoped weapons do; choose binoculars with "b" or through action menu and watch through them with the right mouse button. they should stay in hands while moving unzoomed [1.02 german] --TheVoodoo

Bug or strange design decision? It was like this in ofp, for what it's worth. --Plaintiff1 23:25, 18 January 2007 (CET)

anyway, its time to improve the useability of it! --TheVoodoo

Then make a wish, not a bug. hoz

• Hello, I have a X1400 Mobility Radeon graphic card 128 Mo and sound and screen freezes after 30min of game.

Unfortunately, we need much more information than this if we are going to keep this bug, so please consider revisiting it. --Plaintiff1 20:58, 19 January 2007 (CET)

Hit the BIforums for help, or submit more useful details. BI Forums are the best bet though.hoz

Realism Bugs

I would like to call into question the validity of the realism bug category. I simply do not see how this category can exist without turning into a wishlist. Observations such as vehicles burning underwater are valid imersion concerns- however, this is not a gameplay or stability issue: It is a lack of feature which belongs on the wishlist. Asking for a rethinking of the armour values algorythmns or assignments are also wishlist material. Things that BIS *INTENDED* to happen are not bugs, and those that were left out due to engine constraints are also not bugs- they are things BIS intended not to happen due to performance or other considerations. To be honest, we need a copy of the design document in order to ascertain what a bug is. In absence of that, I think we can safely knock off the reaslism bug category, as there are more much more pressing matters.

I should probably say that it's not that realism problems aren't bugs, however, ALL bugs that aren't stability related could be said to be realism bugs, and realism may or may not have been the ultimate goal in most areas of the gameplay scope. Furthermore, game balancing issues which may fly directly in the fact of realism are *features*, the direct opposite of bugs.

This list will not be completely controllable, as anyone can write on it, but I think that with careful structuring of form, users can be coaxed in the right direction. If this is a desirable state of being for this wiki, that category completely flies in the face of it. --Plaintiff1

Well, as we don't have access to any design documents we have to guess what a bug really is. I think we all can agree on using simple common sense. If it is implemented in OFP, it certainly should be in ArmA. -Xpz

I partially agree. Common sense would dictate that if there is a glaring stability or gameplay issue, that it is probably a bug, so common sense is one tool we can use to judge bugs. However, there are a lot of ways in which ArmA and OFP are different, so I don't think that they should be compared for this purpose. This doesn't, however, address the validity of the 'realism bug' category. --Plaintiff1

It would be nice to have more information on what BIS intended (and did not) and what they consider bugs. --Big Dawg KS 00:57, 6 January 2007 (CET)

We can ask them for it but most likely we'll just have to put a system in place that makes the bug list make more sense. For instance 'You can't go prone on hills'. Is that a really a realism issue or is it a control issue? And what does 'can't go prone on hills mean? I don't think it's an issue where BIS neglected to put in that feature, throwing realism to the wind. None of those bugs in the realism issue bug section make any sense as realism bugs. I don't think that realism can ever be the best possible category to put a bug in. I think that broken physics (if they are truly broken as opposed to lacking in detail) can go in the physics category, control problems (like not being able to do something in some situations- like go prone- but you can in others can go in a control bugs category, and bugs that are not bugs can go in a feature request wiki page. Further weapon issues like excessive/ not enough recoil in a game breaking way can go under weapon issues, while weapon tuning can go on the wishlist. --Plaintiff1

• 1: can't move while reloading or fireing full automatic omg !! i can understand it while lieing down, 2: unarmed characters cant neel, 3: same explosion effect heat and sabart ?, 4: chopper feul runs down too fast when dammaged a little bit + engine stops arfter too litle damage, implement control dificulties when damaged ?, no engine smoke when damaged, being able to crash land a plane or chopper and survive, 5: being able to controll a parachute, 6: no recoil or vibration or any fireing effect from vehicle mounted guns (and no muzzle flash from Humve), and some dont have the belt fed effect, reload actions would be nice too, 7: Rifle shells eject from pistols, 8: cant pivot while reloading at or aa weapons 9: bullet proof windows on some buildings, 10: no M24 bolt action ?, 11: smoke from smoke grenade usless on steep slopes, smoke disapears into side of mountain, 12: UH60 miniguns. *cough*, firing vibration effects, and can you make it spin any faster (wind up to speed), 13: need light emmiting glowing tracers from weapons not green and red lines, and faint intermitant tracers from small arms fire, 14: detachable and retachable mods to weapons on the field, 15: at night, burning vehicles abruptly stop emmiting full light when burning stops, 16: shell ejection from weapons should fly much further, 17: first person view proper reload actions and weapon movement, 18: characters have to compleat action before dieing, 19: it wouldve been nice to have ragdoll effect, grenades,tanks or any explosive cant sent a person flying, + vehicle breakup when expload, sending deblies averywhere, 19: dismemberment option (character decapatation) nothing much happends when you hit a soldier square on with a tank shell ?, 20:is it possible to add heat haze effect on the deasert plains during the day and exaust from choppers, jets and tanks -NipWup

• 1: vehicles can burn on fire underwater, 2: handguns fire accuratly over 600m, 3: no internal tank instraments and can't veiw inside tank body, 4: it would look more real if the sun glare/beam effect showed and continue through the gaps of tree leaves -NipWup

These were removed because they are mostly non-features/wishes. You could be right about the realism section. Maybe we should put an important notice there explaining what is actually a realism bug, or maybe even removed altogether. --Big Dawg KS 01:15, 6 January 2007 (CET)

Just to chime in here. I would be ok with removing the Realism section. Just be sure to move the decent reports to the appropriate section. hoz

• AI walking through walls reported by bt_1900 and Lujon

And isn't this sort of an engine limitation? AI can walk through everything since OFP, the LODs just tell them not to do it most of the time. Scruffy 22:30, 5 January 2007 (CET)

• Wouldn't it be more logical to keep all bugs listed and put a status flag next each reported bug so that everyone can see that it has either been fixed in a new build or

its being worked on. Otherwise we will just keep on adding the same or slightly different variations of the same bugs which will create a huge amount of extra work.

Anyway just a suggestion - use it don't use it. Major Latency - removed from realism issues since not related to a actual bug --SniperAndy

Demo bugs

• ARMA demo [1.3.0.5109] performance issues where menus and functions lag performance, dropping frame rates to 0 or producing connection lag. I’m not sure which. Switching between Map and 1st person takes a few seconds, makes it very hard to navigate without getting killed.

Getting in and out of vehicles or switching positions sometimes takes a few seconds.

Overall performance setting: very low

My stats:

Amd Athlon 64 x2 4800 (I know its not optimized for dule core)

NVidia Quadro FX 3450/4000 x1 [no sli]

Mem 2 gig

Sb Audigy X-fi

Connnection : Cable

• Starting the game with Crossfire enabled causes the game not to start. The ArmA mouse cursor loads to a black screen. Esc allows you to exit the program. Windows claims that 'memory could not be written'. The RPT file alludes to a driver problem. RPT excerpt available on the talk page. [Demo v1.03] --Plaintiff1 10:43, Dec. 27th

• Server crashes every time when CTI (Capture The Island) mode is started. [Demo 1.03 build 5110] - Osmo