Yeah I've never had these issues before with custom loading and the numbering scheme was always the hardpoint # versus the first one you could edit.
I know for sure that the hardpoint line is what's causing a crash.
The kicker is some other missions I made it didn't crash when I did this.
I'm going to test if it's the ACTUAL plane itself that's the issue.
Don't know why it would be but the only thing left to check.
I've done entire campaigns where I custom loadout the planes and never had saving issues before this is a very random crash on me.
The kicker was it did it, erased the file, so I started over again, had it working, changed hardpoints on the PT (from 2 on 6 to splitting it between 6 & 7 1 per pylon because I had the room in the PT) and crashed again, which is what brought me here.
Also the custom loading ignores the settings so you can put an AIM54 on a pylon that doesn't allow Phoenix because those restrictions only apply to custom loadout screen.
I've also done this before where I had like an AIM-54 on an F-15C (random fantasy mission it was stupid but I digress it worked).
--------------------------------------------------------------------------------------------------
EDIT #1
--------------------------------------------------------------------------------------------------
YEP!
Something is wrong with F4C.PT
Code:
obj
type F105.PT
pos 1165427 10000 1790042
angle 90 0 0
nationality3 0
flags $4017
speed 598
alias -1
controller $80
name Player
skill 1
react $0 $ffff $0
searchDist 0
hardpoint 5 1 F450.GAS
hardpoint 6 2 PAVEWAY.JT
hardpoint 7 0
hardpoint 8 0
.
This worked perfectly and to show how the number starts at 0 here is the hardpoints.
Now what is wrong with F4C.PT?
No clue.
What am I going to do?
Figure it out?
Nah!
Just going to redo the PT
--------------------------------------------------------------------------------------------------
EDIT #2
--------------------------------------------------------------------------------------------------
Tested F4.PT and it worked like a charm so I just deleted F4C.PT and made F4.PT (F-4D) into the F-4C (F4C.PT) and tested it and everything works.
So something was clearly wrong
with the PT file god knows what though but it was an easy enough fix.