So I loaded a debugger and stepped though some of it.
The difference appears to be simply due to the way the internal db viewer operates, it sort of creates a fake instance of the aircraft to operate on while doing all it's queries and html generation for display. A by-product of doing that is it uses certain defaults\settings for the unit type. In the case of all the other F-22's, the last loudout in it's available loadouts are INTERNAL only loadouts, so no drop tanks. But in the case of #2201 the last is the long range SDB loudout. From what I can tell it always chooses the last one to assign to the unit for the purposes of the db viewer.
Now the DB viewer is smarter than I thought, and maybe smarter than it should be without more refinement, because using that loadout data it will then calculate off the baseline database numbers what the signature values should be based on the loadout's weapon profile similar to how the game would see it while it was actually in use. Different things effect different stuff in different ways. For example aircraft #2201 last loadout has drop tanks so it's running though the weapons loadout sees the drop tanks in the weapon record entries, and does some fancy calcs to add a penalty. #4858's last loadout for example is internal only sdb's, so it doesn't penalize because there are no drop tanks for example.
Also I noticed at the same time, things like throttle matter -sometimes. Default throttle used during my tests inside the db viewer seemed to be fullstop for an f-22 during the IR detection (but not during the others)...why idk, but fullstop in that case gets you 1.5x IR detection range increase in the db viewer for side and rear (but not front), if it defaulted to cruise or default it would use the actual number in the database 1x, if loitering it uses 85% of the value and at full\military 1.2x and flank\afterburner 1.5x. Just examples. Sensor pods in a loadout from what I can tell will also hit you.
IDK what exactly the right solution is in terms of what we want the DB viewer to show, I mean it would be freaking sweet if we could actually select a loadout and speed profile and see the values change but that's definitely an involved feature request even though the scaffolding appears to be in place vs just bug or tweak. Maybe for now the best approach is just not have the db viewer try to calculate beyond the baseline values? Basically just show what's in the database. It's just my opinion but I'd put more value in knowing the baseline at a glance vs some calculation based on what ever happens to be the last loadout and\or a fullstopped speed. Why fullstop speed incurs a IR detection penalty in the first place idk, but that's a separate ball of wax assuming it's not just something specific to the db viewer calcs.
< Message edited by KnightHawk75 -- 5/8/2020 11:09:53 PM >