4.34 ATC : IMPORTANT INFORMATION
-
It’s on the list indeed.
By the way, she says “winds” as in “the road winds through the hills” [waind] instead of as in “the wind blows” [wind]. -
I already did but just wasn’t sure after reading that cutting and pasting was the way sings were done.
EDIT:
There’s one thing to mention about the ATIS. If you change freq. during the TTS-lady reads her text then she doesn’t care about it. ATIS will complete the whole message even if I’m already out of the channel. Maybe that’s already on your listread “know issues” in the release post
-
It’s on the list indeed.
By the way, she says “winds” as in “the road winds through the hills” [waind] instead of as in “the wind blows” [wind].Precisely what we’ve explained about editing frags sound samples to create a new word. … not always easy … not always a perfect result.
-
Precisely what we’ve explained about editing frags sound samples to create a new word. … not always easy … not always a perfect result.
Time to sleep DJ
We are talking TTS here
-
Time to sleep DJ
Crap … :neutral:
So TTS.
It is tied to local windows Speech Engine voice that you have chosen in window Synthetic Voice & Language setting. They doesn’t all works the same (including how the “space” and “coma” are played by TTS). Nothing we can do about it. This is local.
-
Crap … :neutral:
So TTS.
It is tied to local windows Speech Engine voice that you have chosen in window Synthetic Voice & Language setting. They doesn’t all works the same (including how the “space” and “coma” are played by TTS). Nothing we can do about it. This is local.
That means the user has to set the language to English for the Windows Speech Engine? That could be a tricky one, as you pointed out.
-
That means the user has to set the language to English for the Windows Speech Engine? That could be a tricky one, as you pointed out.
I do not remember if “it has to be” English, but yeah probably.
-
This post is deleted! -
guys
do you think i could remove the UHF frequencies from the switch To “tower” / “ground” calls ? this was initial implementation long time ago,
If that was just me i would remove them
opinions ?
If you mean “Contact Tower on 2 9 3 4 5 0” then I would say, please leave them - they definitely have their uses, especially in emergency situations.
-
guys
do you think i could remove the UHF frequencies from the switch To “tower” / “ground” calls ? this was initial implementation long time ago,
If that was just me i would remove them
opinions ?
Vote for leaving the frequencies
-
Another vote for leaving the freqs. I really enjoy the immersion they add and they have valid uses as others have stated.
-
If you mean “Contact Tower on 2 9 3 4 5 0” then I would say, please leave them - they definitely have their uses, especially in emergency situations.
Agree.
-
I would leave in the frequencies, but put them in another place. Every flight receives a departure clearance of some sort, and from what I’ve been told, during that clearance, Ground would inform you about the upcoming frequencies.
E.g. (real-life phraseo may differ slightly)
Kunsan Ground, Falcon 11, fourship F-16, [tail numbers and positions], request clearance.
Falcon 11, cleared as fragged, initial climb 8000, squawk 1421 in sequence, expect departure frequency 292.650, Eyeball 1 frequency 250.6. -
To me what you are describing is rather a civilian or GAT IFR clearance. On jet (tied to SOPs) what I am used to know is closer to what we have in game.
Keep it simple guys. I see no reason to change that.
-
I tried a 4-ship overhead recovery (me leading 3 AI). It was so close to working. Only #4 had a height keeping failure and hit the ground. Everyone had good timing and path as seen from above.
-
-
Manual says that overhead is “limited to flights of 2” but for fun I tried with 4. I don’t think it was fuel but a decision by the AI to fly lower and lower. He left pattern height after the break turn and then skimmed the ground throughout the rest. Finally near roll out on final he hit the ground after skimming the dirt at ~100’ for the latter half. I did have an ACMI but deleted it.
I did a simple training TE and they recovered all four fine. Maybe it was Pohang (successful) vs. wherever the 14th FS is in Tiger Spirit. I’ll keep an eye out for it to happen again.
Oddly when I did 4-ship lineup (slot 4), second element refused to takeoff until I called airborne to departure control and then did so in formation. Maybe that’s because I was earlier than fragged T/O. I had tower clearance but I’m pretty sure it was before fragged. When I did it again with a taxi commit and I think at or near fragged with slot4 line up (and a better line up in terms of how close some A/C were) then it did auto at normal interval without waiting on me saying airborne. I’m still learning how far to go down the runway to allow room to lineup. I’m much more confident about picking a downwind side though, the radio call and windsock are valuable.
The transition from wedge to the automatic (nice, btw) echelon for overhead isn’t super smooth. #4 always overshot by a lot despite lots of power margin. I’ll probably manually get them into echelon before I call overhead approach.
I’m still trying to conform my overhead to match the AI. They do 300/2.0g break into a slightly high ~1700’ circuit. Speed drops off to 250 at 90deg of break but they don’t let it get less than 250 until perch and they wait until perch for landing gear. Their perch is also much later than I’m used to. I have yet to turn at or later than their base. They are 200 knots at 90deg of base turn rolling out ~155 on a high 500’ but they are 300’ by 1nm. I think theirs is better than mine and I’d adapt anyway.
Curious how AI does it so I flew the same as #4. First love the lead calls to push approach or tower. He calls go echelon and close it up (once). He did the same thing as me, coming tangent to the airfield at 5nm aside in a steady descent 350kt. Then at 10nm/4kft there is a big nasty slowing turn (2G 300kt) to line up but otherwise good. Initial height was 1702’ MSL for a 36’ MSL airbase. Lead breaks even before the numbers but nicely everyone calls their break. I do too even though no AI follows me. Interval are 5s as expected giving ~5000’ sep. on downwind. I do it too early but I’ll practice.
Lead calls final midpoint base turn which seems just right. I’m curious just how early you can though. Maybe we can call at perch. I could see why programmer would like that point since it’s when closure to field goes from - to + and heading is within ±90 of runway. I land at 1,500’ separation from Three unlike everyone else’s 3,000’ mostly due to the early break turn.
As for the comms, it’s pretty good. It would be nice to shave fractions of time off if possible. E.g. skip “on” for “Contact tower on” and if frequency is “292.300” say “two niner two three” instead of “two niner two three zero zero zero”. It takes a smart script to recognize when it can abbreviate to significant digits.
-
I don’t understand where did you read that overheads were limited to 2 ac ???
-
Good idea for the frequency that we can easily shorten
-
I think I got confused with formation landing paragraph. I’m still practicing how to do with overhead compatible with AI, you really have to get slow to 250 then back on the power strongly to stay 250 on break turn. Yardstick really helps monitor distance. If they want 5000’ that’s what? 0.8nm? Then 0.5 on final for 3000’ spacing. I think I was 0.4 and 0.2 last time, don’t know how I did 5,000/6076 and got 0.4.