Dels

View File Boeing F-32A/B/C Warhawk II Pack This is my F-32A/B/C Warhawk II pack. It includes all the files for all three versions of the F-32. Please read the readme file (included) for installation instructions and credits. Additionally, please read the readme file for STOVL handling tips for the F-32B. Dels Submitter Dels Submitted 06/08/2026 Category What If Hangar  

G'Day all, It's finally released! Head over here to download it. Regards Dels

Yes it is. I agree, it is a shame that the canopy bow cannot be hidden. Maybe I might feel energised to build a cockpit in the future, but not now. But yes, I fully intend to give credit where it is due. Dels

...also, using the F-35 cockpit but with some modified textures and a new HUD. Dels

G'Day everyone, I decided to do a destroyed model too. Dels

...and the first in game shots of the F-32B. Dels

G'Day all, First in game shots of the F-32C. Dels

G'Day all, Just a quick update. The F-32 will come with a new weapon, the AGM-187A JAGM-F. It can be loaded on the BRU-61 and is drop launched. Dels

Just to close this one out, I can confirm that multiple launch rails for an internal pylon does not work like external pylons and is unfortunately not possible as part of the aircraft model. The only options are: 1. Separate internal pylons - but you will run out of animation slots very quickly. 2. Launch rails/racks (TER/MER/TLR/WGR/2BR/2AR/2IR) - but you will not be able to specify which one gets loaded from the loadout screen, you can only specify it preloaded from the _loadout.ini. You can use the 'SpecificStationCode=' entry but then all the weapons you want to load will need that SpecificStationCode= as well. Dels

Thanks for the reply. Yes, I've tried using the same entries as external pylons but it doesn't seem to work. I suspect that launch rails may not be supported for internal pylons, so I think I'll have to build separate internal pylons. Dels

G'Day all, I'm tying to have separate weapon rails for the F-32 weapon bay and have found that the usual _DATA.ini entries (below) don't seem to work. ModelNodeName=XXX (This is the main moving pylon in the bay) ... LaunchRailNodeName=XXX (This is the launch rail attached to the moving pylon) Does anyone know if there's a way to make this work? So far, the only option I can think of is to have separate main pylons for each rail that I want. Thanks Dels

G'Day all, some more game shots. This week I've been working on the bump and spec maps, plus the decals (4FS USAF and 77SQN RAAF) pictured below. Dels

First in-game pics of the A model. Dels