From: De Eye-lands, Mon
Ahhh, found the code part that does loads. Woof ! Almost don’t want to comment, because I can imagine the howls of outrage and demands that something different be done (probably 20 different somethings) directed at poor Michael. But … I’ll get with Michael on this and try to keep it under control, because it’s pretty complex and a change will be incredibly involved because there’s loads of unintended consequences. Anyway … here’s the deal.
Ordnance and DTs are subject to a matrix of potential loads and Ord/DT locations (conditions): They are not strictly independent, because some Ext Range load conditions depend on Norm Range load conditions. The matrix is very large. It’s so big, it would be easier for me to dump 8 sqdns into my test box and start regressing. Since anybody could do that, publishing the results won’t give anything away, so it makes sense to do that.
Publishing the matrix may well help modders come to a better understanding of both the stock load conditions as well as the multiple alternative Filter and Alt fields. What you are seeing is WAD. I’ve reproduced it and altered it many times. The rationale for it might be this, or might be that, but it is what it is. Once the matrix is published, you will be able to more intelligently adapt (modify) your planes.
For your example, the Nom Range DT replaced the Nom Range Ordnance (as it should), but because there are specific and well understood adaptations, the Ext Range DTs do not replace the Ext Range Ord (as they should not, under the circumstances). Your nom range DT config is for sweeps and GA and bears, oh my! Guns, not torps. Your ext range DT config allows for a couple bombs in addition to guns for sweeps and GA and bears, oh my! Not perfect, but adequate. No way to do an either/or, torps/bombs config for nom range DT missions, so something must get lost in the porridge.
Once you see the matrix, you will understand.
Nous n'avons pas peur! Vive la liberté! Moi aussi je suis Charlie!
Yippy Ki Yay.