Jump to content

Lrm Ct Targeting Code - What Might Be Happening


No replies to this topic

#1 Deathlike

    Member

  • PipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • Littlest Helper
  • Littlest Helper
  • 29,240 posts
  • Location#NOToTaterBalance #BadBalanceOverlordIsBad

Posted 30 March 2013 - 09:05 AM

I'm starting to think the LRM CT homing code is somewhat related to the Streak code (or missile code in general). It has been noted before that LRMs and Streaks seem to use the same locking code, despite obvious differences in behavior to the missiles themselves.

There was a bug that allowed Streaks to lock faster to when adding Artemis... considering the fact that Artemis is not supposed to do anything for streaks.

When the missile damage code was explained to use for the purposes of the hotfix, it started to become evident to me that they shared the same damage code to begin with... this includes how splash operated.

So, if you put two and two together... I believe the entire missile code, while having similarities and some shared behavior, was coded together in one big messy state (a cluster****). If proper design and coding principles were applied, this would not have happened as it were in the first place.

My guess is that LRMs is using the "Streak" code to target the CT... which is what Streaks tend to do in the first place. Since LRMs are slow, you wouldn't really notice it (Streaks are fast, so it's pretty easy to see what has happened).

If I understand what they are trying to do, they have to rewrite the entire missile code to properly separate the behaviors of each missile type, and then properly "merge" the damage math together. Otherwise it would become far more difficult to add future missile types...

This most likely won't be accomplished by 4/2. There is no quick fix for this behavior.





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users