Bug List – ArmA: Armed Assault Talk

Subsonic (Silenced) Ammunition

Currently, silenced ammo, that is presumed to be subsonic, generates supersonic cracks. Maybe it's a bug, maybe it's a engine limitation. I suggest adding a wish list entry for config boolean isSupersonic, or something like that. Opinions? --Sniperwolf572 22:43, 15 December 2006 (CET)

Add it to the audio bugs list, and possibly your wish to the wishlist. then clean this up. :) hoz

Supersonic crack is generated only when ammo is moving at supersonic speed. There is no need for any flag. Some silenced weapons really do fire supersonic rounds. Which weapon / ammo do you think the behaviour is currently wrong? --Suma 13:05, 18 December 2006 (CET)

I've looked trough the config, and noticed that you can assign different sounds to cracks too, so my wish is already there. Since we have two types of ammo for the M4, and weapon sounds are assigned to weapons now instead of ROF and magazines, SD ammo would be a logical choice to have subsonic ammo for M4. SD ammo for M4 currently generates cracks. I also believe that MP5SD6 uses subsonic ammo (currently generates supersonic crack), and there are also two magazine types for it (MP5 mags are not "named", small bug which I will submit), so I'm assuming one is SD, and could be made subsonic. I'm not sure about other weapons, but, since weapons now determine sounds and not magazines, I would suggest making all magazines that have their SD variant subsonic. And we can still use the non SD variants as non-subsonic ammo. --Sniperwolf572 14:54, 18 December 2006 (CET)

To make clear my point - if a config-side fix it is much cleaner to really make the ammo speed subsonic than to disable supersonic crack for ammo to pretend it is subsonic. --Suma 14:59, 18 December 2006 (CET)

Yes, I understand what you were saying, I was just another making a counter-point to my wish. ;) Ammo speed is indeed a cleaner fix. Hence, I suggest making all ammo that has SD counterpart subsonic. For example, 30Rnd_556x45_StanagSD (B_556x45_SD) to be subsonic, but 30Rnd_556x45_Stanag (B_556x45_Ball) supersonic. --Sniperwolf572 15:14, 18 December 2006 (CET)

Questionable Bugs

Are they really bugs or should they be removed?

Removed Items

Ok, I moved these here because there's already a 50 page thread on the forum about this and the flight model has already been brought to BI's attention. If they're cleaned up and perhaps merged, and can qualify as a bug, then they can be resubmitted. --Big Dawg KS 22:23, 21 December 2006 (CET)

• Rudder controls for AV-8B lose noticeable effect in too slow speeds. Consider this: stall speed for the plane seems to be around 200 (you can barely keep it's nose up). At this speed you should be able to use rudder to adjust the plane heading (for example aligning for runway when landing). Also rudder is used for aiming (to some extent) when firing the minigun. At the moment you can't turn the heading enough with pedals to aid landing or attacking with minigun. Another point; when you bank hard (close to 90deg left or right) you should be able to keep the nose of aircraft from falling with rudder. This issue will probably apply to other fast moving winged aircraft as well. (tested with joystick with rudder axis). 21 Dec 2006. [v 1.00 - 1.02] -Tuusita

Can we call this a bug? I'm not sure if it's actually a bug or your opinion (wish). --Big Dawg KS

I would call it a physics problem. Rudder physics on all aircraft, fixed and rotary wing, are wrong.

--ColonelSandersLite

Still, if it's a non-feature and not technically a bug, it doesn't belong here. We all know there is serious debate about the current flight model in ArmA, I don't think we need to continue it here. --Big Dawg KS 22:23, 21 December 2006 (CET)

• Controlling AV-8B throttle with joystick throttle axis is difficult. When you set throttle axis to near center it seems there is "an autothrottle" that increases throttle when nose is pointing up (above horizon) and decreases throttle when nose is pointing down (below horizon). This "autothrottle" is not able to hold speed when you are banking and your nose points slightly down; it will decrease throttle even if your speed is slowing down since your nose points below horizon. Suggested fix: 1)(preferred)control aircraft throttle directly (when throttle axis is designated in Controls) OR 2)make "autothrottle" try to hold the speed (the speed when throttle axis was centered). 21 Dec 2006. -Tuusita

Again, I think this is more of a wish than a bug, unless it is a serious issue that makes it unplayable. There's been a lot of dispute about the flight model and there are many conflicting opinions as to how serious a problem it is, if one at all. --Big Dawg KS

Multiple reports about same bug

• Rudedog's and Pennywise's bug reports about MP shooting bug are one and same, they should just be combined into single bug report. It affects all weapon in multiplayer, with unpatched German client and whether you Join-In-Progress or not. This bug is in 1.03 demo dedicated server as well. --Feersum

I wasn't able to find the dupe. Someone else must of removed it. hoz

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, 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)
• 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 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

Talk about the Priorities

So, what have we decided on other users changing bug priorities? I've just noticed some more subjective bug rating. --Sniperwolf572 18:12, 23 December 2006 (CET)

They should leave them at 0 so the proper people can see them easier and make sure they're properly prioritized, IMO at least. --Big Dawg KS 19:16, 23 December 2006 (CET)

I agree, not that it matters or that I change priorities but I think this would be the best way to see what is happening. Also for users. But I think the bug list should have a content list as well to the sections like the talk page. It makes locating sections much faster --SniperAndy

Someone will always try to increase the priority, I think thats a given. Best we can do is just keep an eye on it. Lets try to keep as much chit chat out of the bug reports as possible. If the chat helps with the problem then so be it, if it takes away from the report then copy it to here with a link. Good job so far in maintaining the list. What about a separate section for the demo bugs, I noticed one or two and these bugs should be minimal(hopefully) to warrant lots of sections? hoz