Position and hold / line up and wait
-
Don’t bother contacting tower for anything. Just qnh and active runways. Once you get into multiplayer you just make standard calls to say where you are and what you’re doing. No need to contact atc.
-
Bad idea in campaign….
-
Don’t bother contacting tower for anything. Just qnh and active runways. Once you get into multiplayer you just make standard calls to say where you are and what you’re doing. No need to contact atc.
Bad advice. Very bad advice as it can scrub all the IA traffic by hijacking IA takeoff slots and won’t be “as fragged” at push.
-
Seems like the sounds would need new recordings, new voice actors, to replace any wrong sound or less than realistic ATC lines.
ATIS would be awesome, and it seems like with the new weather in place, useful. Granted it would need new recording for new lines.
-
we still can do ATIS in MP ;). We do it for some of our flight. Pretty easy to do.
-
How do you get up to date weather in 3D?
Also, seems like AI ATIS would be relatively easy - certainly I would have thought it easier than say, improved ATC.
-
I make the weather with zigrib, so I know it. We just prepare the frag with an automatic voice recorder, and we broadcast eveything on a specific frequency with the information letter.
-
Beside, WDP has a metar, or ATIS line as well
-
Mentally replace “position and hold” with “hold position” and that solves that one. I don’t even know why that voice file was in there as I don’t think Falcon ever did that kind of operation.
BMS ATC flow is quite good but idiosyncratic. A good example is to find a busy scenario and join as the wingman monitoring tower and following lead. The AI is very good at departures and being indistinguishable from one in airbase ops is a compliment. I don’t know how precise it’s done in airlines but in BMS a takeoff time of 11:06 before Tornados at 11:07 and after F-15s at 11:05 should be possible. And that’s scheduled times, not “oh well whatever order ends up happening.”
Good flow is to depart the chocks more or less “just in time” and in the launch order for a minute or so wait at the EOR. AI calculates it based on the distance to taxi. Knowing who is taking off before you and when is valuable info. “Hmm, Claw2 just asked. They are scheduled for 09:21 and it’s 09:14:30 now. That’s 5.5 minutes. My T/O is scheduled 09:25 so I’ll plan to taxi 09:19:30.” After the first call it’s all automatic. In recent versions the T/O clearance can be granted up to 2 (or more?) minutes early.
-
Weapons delivery planner has a button that shows take off schedule. It’s in the lower left corner in a he data card page.
-
All good info, thanks….a lot !!
-
Mentally replace “position and hold” with “hold position” and that solves that one.
Or imagine it is before late 2010 which is at least when switched to it here in the States. I believe BMS says for the most part the are going for circa date of the even before then.
Also word is editing the ATC sound files is very time consuming. I I’m curious how long the ITO guys took to add the Hebrew.
@Red:
Beside, WDP has a metar, or ATIS line as well
While I’m glad WDP has the line and it is better than nothing, METAR =/= ATIS or even AWOS/ASOS. There are have been more than a few times listening to the updates they provided over the before takeoff METAR/TAF etc. have made me say something like “that was not what I was expecting, this will be interesting” One slightly easier aspect of actually adding them would be that you wouldn’t have to voice act them, many ATIS and all AWOS/ASOS are computer voices.
-
Biggest challenge is figuring out what your position within the que mixed in with the AI who try to squeeze past you.