No wonder the School of Hard Knocks in this game is so hard to graduate from!
Agree with the need for a code change. At the very least the Beest info screenie should say "Alternate Load" next to the drop tank.
Maybe you can fire-bomb his ships with it?
I posted the above series over Second Coffee, went away to watch "Morning Joe", noted that it's snowing like a sumbiotch, then came back, calmer, to see if my posts had generated any comments, or just yawns. Or, worse, that I was totally mistaken, which is the saddest sort of forum spanking one can get: The Righteous Indignation Cha Cha Followed By Pie In The Face.
Nice to know I wasn't imagining this state of affairs.
I wonder how many attacks I've missed out on over the years because the game let me torp + DT?
I understand that the DB screens aren't set up to say "either/or", and that I suppose we could be expected to know from the screenshot that a Beest only has one 'C' hardpoint, but I really don't know the wing and fuselage configurations of every plane in the game. I expect that when the interface has trained me, in good doggie fashion, that "yellow=good/possible, red=bad/impossible" I don't have to interpolate between the DB and screenshots and what the interface is telling me. The interface is a deal between dev and player. It shouldn't backstab you.
In effect, my Beests this turn went out looking for two BBs with machine guns. Worse, they did it at extreme ranges. I don't know if they would have been in attack range without the DTs, but at least I could have been sure they had fish.
From a code standpoint I doubt the DB has a flag which would allow a universal DT exception check to be done. Probably have to put in a whole stack of aircraft model error traps to resolve DT and weapon interferrence. But without them this is a crappy situation, which even worse can still bite you even if you do the hand-work of going to the DB and checking. Of the three data sources I showed above, only one shows the truth.