Known Bugs

From MCM Combat Operations
Revision as of 18:55, 6 November 2012 by Bellimora Resident (development | contribs) (Created page with "Here is a list for known bugs for MCM. If you are aware of a bug please add it to the page with as concise information as possible on how it appears and what's precisely wron...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Here is a list for known bugs for MCM. If you are aware of a bug please add it to the page with as concise information as possible on how it appears and what's precisely wrong.

Weapon Bugs

Any bugs with any particular weapon system go here. Section title should be the weapon's name, if it's a version packaged with the mech, put the mech name prior to the weapon.

Baal: HellFire Napalm Cannon

Issue: Flamer does not shut down and operates even when mech is disabled. Reproduction: Equip and activate flamer, fire it while being destroyed. Workarounds: Removing the weapon will prevent it from attacking. Other Notes: It is possible to attack mechs without your meter activated in this fashion. However, doing so is considered cheating and will result in stiff penalties.

LRM2

Issue: LRM2 missiles have difficulty tracking a target Reproduction: Get a missile lock with a LRM2 fire them, particularly from long range Workarounds: Firing the missiles within 64 meters of the target seems to produce far more reliable performance. Other Notes: I am personally guessing it's due to the max range limitation of llMoveToTarget which a lot of missiles in MCM use. If that is the case, a quick fix would involve having the missiles move to the nearest valid target repeatedly until the intended target is in range, or even easier, shortening the lock range.