winsaudi

Over the many years (25 I think?) that I have been a member of this forum, that is the best post I have ever read! (And some have been close to priceless, but this one wins the cigar/goldfish/biscuit *delete as applicable) Moral of this tale? Do not ever try to bullsh!t an expert. Not ever! Never. I said "Never!" Got it? I'm now going to have a beer and will raise a toast to @WildCard& @MJKERR Cheers fellas! You've made my day! One of you in one way and the other one in another! All the best, Wayne

Oh look! Yet another installation problem. Perhaps it really is time for FT to finally take action?

Is it not about time you had a better installation package? This forum continues to be littered with people having installation issues yet nothing is done about it. What is it now? More than 4 years of continuous problems and nothing gets better. Very disappointing.

The BMT Micro servers in Fremont, Atlanta, and Newark all give me v27.

I did the same and it gave me v27. Weird.

Did you download from BMT Micro or elsewhere?

I disagree, RT does not seem to be updated. The BMT Micro webpages still download v27 which was released in December and does not include ZBAD.

STRING LINE ERROR: 8 - JFK,LHR,764,DL, 001,07:29:12:00,1,DL Have a look at this line in your schedule and replace the colon between the 2 times with a comma.

@smirabal Shawn, Just looking at your screenshot above shows that your microphone is not set up. “Set up your mic for speech recognition. Get started” suggests how you might fix your issue. I recommend selecting “Get started” and follow the prompts. Wayne

Yes, thanks Craig. For some reason my iPad would not let me quote the incorrect statement by MJKERR.

Not true. London Heathrow switches runways at 1500 each day.

But in the meantime you are going to perpetuate the confusion by continuing to produce add-on airports (one per month according to a recent boast) that have default installation paths to an incorrect folder? As a previously loyal customer, I find that a very disappointing decision given that the problem could be fixed so easily.

@scoobflight @FeelThere @FeelThere Ariel This installation path problem has existed for years. Can you not add a smart installer such as that used by @nyergesdesign for his RC add-ons? Wayne

@WildCard that method would fix the voice callsign but unless @nyergesdesign does something in the manifest files of the RC pack to account for this, then one of those lines will result in white aircraft. Simply copying the .ba entries and also labelling them similar to “dot whatever fake IATA code” is used for the domestic shuttles would work.

Yes. They didn’t do it for Gatwick and I don’t expect they will do it for Heathrow but I would love to be proved wrong. Both SPEEDBIRD & SHUTTLE, after all isn’t it called “Real Traffic”?

So, going back to the original request by @andredragt to have the vast majority of BA traffic at T5 with just a few from T3, as in the real world, is it not easier to allocate just a small number of T3 gates in the airport coding only for BA? Such as: Terminal 3: AAL,ACA........ etc Terminal 3BA: BAW That seems a workable compromise. Now, how do you get the BA domestic flights to use the correct callsign SHUTTLE while still keeping BAW/BA codes and not getting white aircraft?

🤣 brilliant! That post has made my day.

I disagree with your first sentence. Here is a screenshot of FAA JO Order 7110.65W page 2-4-5. This policy document begins "This order prescribes air traffic control procedures and phraseology for use by personnel providing air traffic control services."

An old installer burned to anything is no use whatsoever when the latest version of an add-on needs to be downloaded and installed. What is needed is the hyperlink to be able to download the latest version of Real Traffic, and the product registration key of course. Customer Service <cservice@bmtmicro.com> are extremely helpful.

Phew! Thanks Ben.

Guys, Point number 2 in the lead post is not a bug and it also happens at other airports for good reason. Please look at the hold short points for LEBL 07L which I have circled in red on the screenshot from Google Maps. I have yet to play LEBL but the aircraft stopping on the taxiway reported by @GoalieMedic seems to be a correct simulation. Imagine an aircraft crossing the undershoot of the runway on a taxiway just as another aircraft is on short finals to land, there is a collision risk plus a wake turbulence/jet wash risk; hence the hold shorts to allow clear separation. @hexzed does not specify which other airports or runways he is referring to but I'd stake my house on the fact that the aircraft are obeying hold short lines before crossing an undershoot. I hope this helps and reduces any frustration you may be feeling by watching this happen within T3D. I would be reporting it as a bug if aircraft didn't stop! Wayne

Vic, Exactly! I hope you can see how easy it would be for those of us that edit for reality/correct pronunciation. Thanks for listening. Wayne

Can the 3 of you fix the Falcon won't take-off problem please?

Vic, Thanks for your comments on my observations. For the first point, I see that you agree that a mix of IATA and ICAO is cumbersome and should be streamlined. For the second, sorry but I disagree with you. Surely it would be easier to have a master reference file for airlines and airports rather than the current plethora? The current 16 airlines files within the game do not list just those airlines specific to that airport as there are dozens and dozens of irrelevant listings in each file, same for the 16 airports files. What about changes? I have to edit the RT airline data because it contains errors. Here is a somewhat tongue in cheek example, if American Airlines was taken over by Walmart, (e.g. WMT, WM, WALMART, Walmart Airways, USA) using your system we would have to amend 16 different airlines.txt files whereas using my method would require one line of text amended in a central airlines.txt file. Because the TTS system results in some weird pronunciations I change the airlines.txt files to get the call sign pronounced correctly, but I have to do so up to 16 times when I really only want to do it once. Then every time RT is updated I have to go back and edit/replace 16 files instead of one. When EGKK is released make that 17, etc, etc. Wayne

On this matter, this article is worth reading: https://www.flightradar24.com/blog/clearing-up-call-sign-confusion/#more-5710