@Dee-Jay -
Excellent feedback and good points all. Your explanation of the “-208” makes perfect sense to me now because I also used such “tricks” to help me associate items during my programming days (I’ve been retired for over 20 years, which is why I do silly projects like this for fun now). Your efforts and results are amazing. I just didn’t know it was you who was doing it.
I’m glad that you compromise to a degree regarding IRL vs. strong user expectations. I might not be able to hear/feel the landing gear lock IRL, but it’s an important confirmation for me that the landing gear is working, because I’m too focused on lining up with the runway to look away from the HUD.
The speedbrake might not have a faint “beep” when extended IRL, but it’s a far more convenient confirmation than trying to gyrate my TrackIR to see the hidden physical cockpit indicator (I use the modifed “airbrake” ogg file).
I might not be able to faintly hear my ground munitions release from my wings, but it helps me to confirm the all-to-briefly blinking FPM.
Really, Dee-Jay, my primary purpose was to highlight obvious typos, inadvertent data swaps, and other obvious anomalies, which I did.
But if you could explain to me the way the BMS code interprets and implements the inside_cone_angle_deg and outside_cone_angle_deg values, I would love to spend some time & testing to try to improve the transitional attenuation effects. I just couldn’t glean enough insight from the explanation given at the top of the F4SndTbl.textproto file to understand.
Thanks for your insight, and your dedication.