I recently had a brain fart and forgot to pull up my gear before 300 kts. and had hung landing gear. The Left Rear LG indicator light went dark when I first attempted to raise the LG but the Nose and Right Rear lamps stayed on. I cycled the LG handle again and got all three lights to go out. Caught up with my wingman for a visual check and he said I had all my LG stowed and didn’t see any doors open so I went along with the mission as planned with no issues.
On egress, due to my earlier mishap and the fact that I was low on fuel, we decided I would take an alternate airbase so I wouldn’t cause an issue with a closed runway at home plate. When I contacted the alternate and got in the pattern I decided to use the ALTERNATE GEAR EXTENSION due to my error on take off and suspicion that the landing gear might be damaged. I was expecting one of the rear wheels to malfunction due to earlier indications. To my surprise I had both rear wheel indicators illuminated and the nose wheel was dark. I also had no indication on the HUD for approach. After some quick discussion with the flight lead about weather or not to eject somewhere safe or try to land it I decided I would try to land with damaged nose(?) gear.
It is shortly after this point that the unexpected occurred and brings me to my question. When I turned on final and my airspeed dropped below 180 kts, I heard a clunk and noticed I was now getting landing cues on the HUD. I looked at the LG indicator lights and my Nose indicator was now green. I continued in for a successful landing and was able to use braking to clear the EOR since I lost usage of my NWS as a result of using the Alt Gear.
That being said, my question is…Will gravity cause the nose wheel to lock into place after falling below a certain speed when using the Alt. Landing Gear? I have read about this somewhere, but can’t remember exactly where. Tried to find in the docs. and this is the closest thing I could find…
T.O. BMS1F-16CM-1 (Page 235)
“Alternate gear extension provides a pneumatic ‘use only once’ means to lower the landing gear. The alternate gear handle when pulled opens the landing gear doors, release the main legs from stowing and they lower and lock in place thanks to gravity and airflow. The nose wheel lowers against airflow and must be pushed forward thanks to the pneumatic system of the alternate gear extension. For this reason, it should be accomplished at the lowest possible airspeed below 300 knots and preferably below 190 knots to ensure nose wheel gear lock.”
U3 has been great. I really have never had any issues with CTDs or performance issues. I took a break from BMS (no reason) just life, kids and I moved. Came back to find the new forum and the U3 update. I didn’t even read the change log for U3 to be honest, I just know its going to be better and the fact that it’s the hard work of others you will never see me complain. The fact that the sim works so well, there is never any reason to be in the forum wishing for things to be different.
You need to lock a target for CCIP to work? Never heard this before!
Yes - for it to be accurate…at least in RL you do. As I mentioned, the system has to include height above target in order to solve the bombing triangle, so you don’t have to lock the target, you just need to lock something at the same elevation. But after that, you can use the symbology to bomb whatever you can see.
A trick I learned back when I was working on RL Harriers - very handy.
I’ve had trouble with ccip also, and came across this thread. When you say lock, you are talking an actual tms up lock through fcr or tgp, or will a steerpoint provide the information? I’ve watched a number of pop up bombing examples and they’ve all been off of a steerpoint and ccip, no “lock”.
Yes - an actual sensor lock on something near the target height; radar, FLIR/laser, steer point. If you have a steer point at near the same elevation, or set the elevation of a close steer point to the equivalent target elevation, I don’t see any reason why that wouldn’t work…you’d have to designate the steer point. The important thing is matching the elevation of the desired target.
Could it be something changed? I have used the server and app before, but get stuck atm at “Discovering Server…”. Both the server and iOS cliënt have been updated. Not sure where to start my troubleshooting…
I noticed something strange regarding the IA behavior flying sweep missions through several TEs I created…I don’t know why, IA sweep flights have never respected the TOT for each waypoint (10min late) …I could understand if the IA flights met some opposition during the transition but this was not the case. By the way, the ambush cap flights have never been impacted by this “issue”…they arrived on time and where planned
So this consequence makes hard the flights planning…and on the other side, this brings some spice and random events (if it is well random)
Thank you very much for your offer, It’s very kind of you to offer me to join your group.
Nevertheless, I left the team because of some internal disagreements but also because I wanted to be free, without any expectation from anybody.
When I was in the team, several people questioned my unorthodox choices, starting by good friends of mine.
As you saw, I never make classical fighters or models. What I do is rarely expected, and often leads to frustration : « why Radium initiated an FCK-1 while there is still ugly models in the database ? ». This is a rightly asked question, but I don’t work like that. I work with passion only.
So, I want to see remain fully independent, if you have some suggestions you can let me know them, but I don’t want to be a part of a group anymore for BMS development, otherwise, it would be illogical that I left them team.
It kinda is tho (double-tap TMS-down) … I think Mav or someone else on the dev team mentioned implementing that for a future release. In meantime, it could probably be emulated with JG or Autohotkey or similar…
But I agree cursor-enable is probably higher priority for HOTAS, if you like dogfighting with HOB missiles.
Map the same button to both trigger detents.
wait wat … you can map a single button to multiple callbacks? does that only work with trigger, or in general? I had no idea
seems like there are a few potential things, that only have effect in distinct contexts, that could share a button… like Wheelbrakes and the Paddle-switch
or things that you almost always want to do simultaneously, like reset-fov and reset-trackir
will have to play around with this… [edit: I can’t get this to work in the general case. maybe it’s special-case code for the triggers?]
When I was still using the cougar I had to do the “retrieve / apply” dance before it was detected properly (USB version). In CCP, I had to click “retrieve settings from device” and then “apply settings to device” after every reboot.