Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Cloud Surfing

Members
  • Joined

  • Last visited

  1. You're probably not doing anything wrong. From your screenshots it looks like the basic SimBrief route is just KJQF DCT PEGTE DCT KHKY, but FSHud is auto-building extra procedure legs around KER4, JOTTA, ALDOH and ZOMAR, then failing on the JOTTA segment. I'd try it in this order: 1. Import the route without SID, STAR or approach if possible. 2. If FSHud already added them, clear those procedure legs first and keep it as the simple direct route. 3. Check that your SimBrief navdata cycle and FSHud navdata match, because this kind of error often comes from procedure mismatches. 4. As a quick test, try rebuilding the same short hop directly inside FSHud and see if it still invents the extra legs. For a route that short, I'd personally keep it very simple and let ATC assign the departure or arrival later if needed. The main clue is that JOTTA isn't in your original route, so the problem looks more like procedure interpretation than a bad SimBrief import on your side.
  2. If you're mainly an IFR/payware user, I'd just get Standard. That's the route I'd take now because most of my time ends up in PMDG/Fenix-type aircraft anyway, so the higher-tier bundles don't really change much for me. If one specific included aircraft really matters to you, then it can be worth it, but otherwise I'd keep the extra money for add-ons you'll actually use.
  3. I still keep 2020 installed, but I haven’t gone back full time. For me 2024 became usable once I stopped trying to throw everything at it at once and kept the setup a bit simpler. Most of my flying is IFR in the PMDG 737, and lately some Fenix too, and in that use case it’s been solid enough that I’d rather keep moving forward with it than rebuild my whole routine around 2020 again. Not saying the frustrations aren’t real, just that for me the balance has shifted over the last couple of months.
  4. For me it's AIG. FSLTL was convenient, but in 2024 I've had better luck with AIG for airline coverage and schedules, then I just let the sim's real-time traffic do the rest. If your main focus is airline traffic around bigger airports, that's probably where I'd start. If you care more about GA variety, then I can see why people end up looking at GAmod or PSXT instead.
  5. I haven't tried the new push-in towing yet, but GSX is still one of the few add-ons I keep installed all the time. For me it just makes airliner and bizjet turnarounds feel less bare. I'm curious how reliable the new push-in feature is at add-on airports though, because that's the part I'd most want to use in practice.
  6. If your main goal is keeping airline traffic around the airports after the FR24 feed change, I’d probably look at AIG first. It takes more setup than FSLTL, but for me the model coverage and schedules are still the main reason I keep it installed. If you want the simpler route, keeping the FSLTL models and pairing them with another injector is easier, but if the question is which setup feels most convincing overall, I still end up back on AIG more often than not.
  7. What’s worked better for me is treating model matching and ATC as two separate problems. If I just want believable airport traffic in 2024, default real-time traffic with better models can be good enough. If I want proper IFR flow, spacing and vectors, I still end up using a dedicated ATC layer because that part still isn’t really solved by the traffic feed itself. So to me the FSLTL injector disappearing is more about losing a workflow people were used to than losing the only workable setup.
  8. I’m using FSHud together with AIG for traffic and schedules, and for me it covers pretty much every airport I normally fly to.
  9. I went through that phase too, especially with default ATC in terrain-heavy areas. For me the biggest change was stopping trying to make the built-in ATC behave like something reliable for IFR and instead either flying the procedure myself or using a third-party tool when I actually wanted the ATC side to be part of the flight.\n\nIf you enjoy IFR itself, I wouldn’t give up on it because of the stock ATC. The procedure part can still be really satisfying once you separate it from the weak link. In my case I do a lot of offline IFR and FSHud has been the one that felt the most usable for that, mainly because the vectoring and airport configuration side give me more predictable arrivals than the default sim does.\n\nIf you fly a lot in Alaska specifically, I’d also simplify the environment while you’re getting comfortable again: shorter routes, one aircraft you know well, and published procedures you can cross-check yourself instead of trusting every descent blindly. That made IFR a lot less frustrating for me.
  10. I'm using FSHud - Air Traffic Control, it's completely "other world"! It's not related to the MSFS "code" limitation as you mentioned! I'm using it exactly because I can setup which 3rd Ai traffic sources I can use, or even all together (FSLTL, FS Traffic, AIG...) FSHud will take off all traffic, you will hear all conversation, beside of that it's have 2 COM radio as in real life and you can hear it both at the same time! On top of this Airport Manager - where you can config any airport according real life operation. I'm using it and very happy to see 70 active aircraft, vectors, speed restrictions and etc...
  11. Third party ATC I'm using outside of the career mode only! But for IFR even in career mode sometimes, but the problem is that default ATC program for different levels...And I try FSHud - Air Traffic Control build in route manager instead of Simbrief, there you can set at each point altitude you want, so it can work!
  12. Same here. I just start requesting lower altitude a bit before TOD and keep doing it in steps until ATC finally clears the descent. It’s dumb, but it avoids the penalties.
  13. As I understood right, fshud is injecting traffic where you heading and where you was flown. With AIG TC it will injector all traffic that AIG TC give, that's why you see more. Plus FSLTL current. So you will get scheduled & kind of live from FSLTL. That's how I get 90 live traffic! I turn off everything when flying with 3rd party ATC. I mean aircraft L, but airport vehicles I leave....
  14. I'm using the following settings: Simulator traffic: Enable (It will intercept all the traffic from the sim - FSLTL in my case) External: Enable (I'm using AIG Traffic Controller) https://www.alpha-india.net/software/ Or you can enable AIG if you don't want to use AIG Traffic Controller. FSLTL: Running AIG Traffic Controller: Running And that's all!
  15. For me, FSHud + AIG + FSLTL all running together at the same time! Two sectors flown, zero issues, and it was handling 70–96 traffic in the sim. Insane.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.