HUD: per-weapon pip data dump + the real authored ranges recorded
[hud] pip diagnostic logs each registered pip's classID/PipPosition/ WeaponRange/PipExtendedRange/PipColor. The live dump corrects the "everything is 500m" assumption: BLH lasers red @500 (x3, ext=1), missiles amber @800 (x2), PPCs blue @900 (x2) -- the pips sit at their weapons' max-range marks on the range ladder (caret below a pip = that weapon reaches), so 7 weapons read as 3 weapon-system groups. KB + comments corrected. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Fable 5
parent
5038d64382
commit
4e7561714e
@@ -1545,6 +1545,11 @@ BTReticleRenderable *BTBuildReticle(Entity *mech)
|
||||
RGBColor pc = wp->PipColor();
|
||||
float r = (float)pc.Red, g = (float)pc.Green, b = (float)pc.Blue;
|
||||
if (r < 0.0f || g < 0.0f || b < 0.0f) { r = 0.78f; g = 0.08f; b = 0.02f; }
|
||||
DEBUG_STREAM << "[hud] pip: classID=" << (int)ws->GetClassID()
|
||||
<< " pos=" << wp->PipPosition()
|
||||
<< " range=" << wp->WeaponRange()
|
||||
<< " ext=" << wp->PipExtendedRange()
|
||||
<< " rgb=(" << r << "," << g << "," << b << ")\n" << std::flush;
|
||||
gBTReticle->AddWeapon(
|
||||
wp->WeaponRange(),
|
||||
wp->PipPosition(),
|
||||
|
||||
Reference in New Issue
Block a user