F-15E -220/-229 Improvement Project
-
Now, what’s just not getting into my head, probably has more with BMS then F15 alone, …
HOW!? …You can have SAME NAMED hardpoints definition variables with different setup/weapons… AND HELL, IT WORKS !! … there is tiny logic to the case. but it beats illogical BMS logic,
eg. in keyfile you can’t have same device twice to the same callback … eg… For open/close canopy you can’t have CTL + C and SHF + C defined at the same time , … but you can have JOY TG2 and CTL + C , but those are different devicesso… really… no, I mean , I’ve tested it and it works, from the beginning I was very suspicious about it , but , WTH… I’ll try as is… I couldn’t believe with my own eyes…
So, special THANKS for something marvelous in design
Can you please elaborate and explain what you meant? Did you found a way to select specific pylon/pair of pylons instead of using available callbacks like SimCBEOSB_6L or SimCBEOSB_6R or NextAGWeapon?
-
Of course, no prob, but you’ve misunderstood what I probably expressed kinda wrong.
You can see definerack f15e-cft-single-rack-right is defined multiple times with different configurations (there’s 3 or 4, I think, but just 2 for example)
…so the SAME variable is defined more then 2 times with different values … and it’s a GO … (something like a$ in for/next loop, close but not the same, … , for a$=a+1. so a$= can have different values)
So, honestly, when importing in my racks, I’ve never thought it would work, that previous variable would be overwritten by next., or it would have the first value and could not be changed… but I was wrong)
…so it works, so I know there’s more to the case then I’ve imagined.But in keyfile , when you define value for a callback , you can’t have 2 key-combos for a single callback from the same device, only one would work… … like I’ve said you can’t have CTL+c & SHF+c for open/close canopy…
…but you CAN have CTL+c and JOYBUTTON4 for the same callback , because are different devices , DX and keyboard…so that is where I got it wrong , it is NOT the same behavior as for racks variable(s) … so that expands possibilities I wasn’t aware of…
So… COOL
definerack f15e-cft-single-rack-right # Changed 8/21/2019 to define GBU-10 load rackct 2725 rackstations 2 weapjettmodes EMERGENCY,SELECTIVE addwclass gbu addwid 293 292 286 287 227 # GBU-24A/B GBU-24/B # 8/21/2019 added 286, 287 GBU-10C/B GBU-10G/B B61 addloadorder 1 definerack f15e-cft-single-rack-right # 8/21/2019 added GBU-27 AGM-154 rackct 2725 rackstations 6 weapjettmodes EMERGENCY,SELECTIVE addwid 294 140 141 # GBU-27/B AGM-154A AGM-154C addloadorder 1 addloadorder 0 2
AAh, for the pylons , well I’ve programed the stick so on S3+NWS , I have NextAGwpn to change weapon type, and when in air I use NWS to select left/right pylon for the same weapon …
…but for CBOSB_ … it is useful when you program your weapons still on the ground (since I don’t have Cougar MFD’s , or touchscreen) , but since it work’s only once it’s buggy, but that’s because of BMS pure F16 9 hardpoints definiton in the code … maybe that will be implemented for the other types of planes (with 7hps, 11hps) … maybe not … but I’ve already decided I dont suffer much because of that … (but I did)
here’s what I have on stick for the AGweapons
DEF X10 S3 AND X9 AND NOT S1 DEF X11 DELAY(300) S1 AND S3 AND NOT X9 BTN X10 /H {DX3 DX5} BTN X11 SimFuelDoorToggle BTN S1 /I KD(X9) DLY(100) KU(X9) Rem - click DX NextAGwpn , hold - Refueldoor /O /H DX5
keyfile
# MslStep/S1 SimMissileStep 4 -1 -2 0 0X0 115 # MslStep/S1 SimNextAGWeapon 260 -1 -2 0 0X0 115 #foxy click NextAGwpn , hold RefuelDoor
-
(cut!)
Ech…, I thought that you figured out some magic way to select specific pylon/pylons by not explicitly using NextAGWeapon or SIMCBEOSB… Even selecting specific weapon type would be ok.
Neventheless thanks for the explanation
-
-
-
-
-
-
-