malichek

I actually hope it stays as a small single-purpose tool. Not every useful sim utility needs to become a whole product with accounts, installers and a support burden. The browser/local-storage approach is part of the appeal for me: open it, get a sensible short flight, send it to SimBrief, then close it again. That fits the way a lot of us use the sim on weeknights.

I run it the second way: AIG Traffic Controller is running with the FSHud integration enabled, then FSHud traffic is set to External. I don't normally enable the internal AIG option at the same time, because it feels redundant and can just add load. For coverage, the basepack is only a starting point. I still add the airlines for the areas I fly most, otherwise some airports can look quiet even when the setup itself is working.

Nice idea, and I like that it is browser based. For short evening sessions I often spend too much of the available time choosing a route instead of flying it, so a 40-60 minute selector around decent airports is useful. The no-install part matters too, because small tools like this are much easier to actually use when they don't become another thing to maintain.

That is a good example of why the game/simulator argument never made much sense to me. The same box can be a training tool one minute and a toy the next, depending on what the person is doing with it. At home I obviously don't have the motion or consequences, but I still use MSFS that way sometimes: a quick look at a route, airport layout, or cockpit workflow before a planned sim flight. Then another evening it is just for fun. Both can be true.

Yes, the base model package is still useful without the live injector/Navigraph. Install the FSLTL base models through the FBW installer and leave the sim's own AI or real-time traffic enabled; the sim can use the installed models and liveries for matching. The Navigraph part is for the new FSLTL live traffic feed, not just for having the model library present. I wouldn't expect exactly the same behaviour as the injector though. Default traffic is still default traffic, so matching and airport behaviour can be hit and miss. For a no-subscription setup it's worth trying, just keep expectations modest.

I've had similar mixed results with live traffic lately. The nice part is the schedules and models are there when it works, but I still don't trust it for a flight where I want the airport to behave predictably. For IFR I usually prefer the more controlled setup with AIG and FSHud, even if it's less 'live'. At least the traffic flow and sequencing are more repeatable. FSLTL coming back is good news, but I think it still needs a bit of settling down before I would call it reliable again.

For me the Black Square sweet spot is the mix of systems depth and variety. A2A probably still has a slight edge in that last bit of hand-flying character, but BS keeps me coming back because I can jump from the Bonanza to the Duke or Starship and each one still feels worth learning on its own. I don't really see it as a winner-loser thing, more like different strengths.

I’d strip it right back to vanilla first and test in steps. The fact that it got a bit better with real-time traffic off makes me think it may be traffic or another add-on spiking the sim rather than just raw FPS. If it were mine, I’d try one short flight with an empty Community folder, all traffic off, and no ChasePlane. If that settles it, add things back one at a time, first ChasePlane, then traffic, then anything else you normally load. That usually finds the culprit a lot faster than changing random graphics settings.

For me the hardest ones are the visual arrivals where the runway shows up late and the terrain tempts you into chasing it. Madeira is the classic example, but even shorter coastal approaches can get messy fast if I let the approach become reactive instead of stabilized. What the video really shows well is that a go-around is not the failure. Trying to salvage a poor setup usually is. In the sim I’ve had much better results since I started treating an early go-around as the smart option instead of the embarrassing one.

I'd look at it as two separate questions: is it usable in 2024 today, and is there a bigger native refresh coming later. From the posts above it sounds like the first answer is yes, but the second one is still speculation. If it were me, I'd buy it for what it does now, not for an unannounced future update. If Black Square does more with it later, that's a bonus, but I would not count on a timeline until they say so on the Just Flight forum.

I have, but only with the default real-time option. In my setup it has been the least predictable of the traffic modes, and the stutters were the part that pushed me away from it. For normal IFR flights I usually get a more stable result by turning default real-time off and using either AIG traffic controller or BATC, depending on what I want from the session. So I do not think it is just you.

Yes, that’s the one I meant. In my setup AI Manager is mainly for installing and updating packages. For the actual flight, the important bit is that the sound pack is installed and OCI sees it properly. Otherwise you can have traffic moving around and the airport still feels strangely quiet.

For normal use I only open AI Manager when I want to install or update packages. Once the library is in place, the injector is the runtime part. On the sound side, check whether the separate AIG sound pack is installed and verify OCI again, because you can have traffic showing up but still end up with a pretty quiet airport if that piece is missing.

I like the idea of it as a cleaner starting point for people who want traffic in the sim without building a big OCI setup first. If someone already spent time tuning a custom library though, I would probably treat this more like a baseline option than a reason to rebuild everything overnight.

I'm waiting for this one too. What I really want to test is seeing real aircraft around me again directly through FSHud. If this works well, it could be a much cleaner solution than the old FSLTL setup, especially now that FSLTL is not really an option for FSHud anymore. For me the interesting part is not only the traffic itself, but how well it all works together with the ATC side once it's out.

I don’t think there’s a single yes or no answer here. For me the bigger issue is consistency. In some higher fidelity GA aircraft, especially the A2A Comanche and the Black Square Bonanza, the left turning tendencies feel believable enough and you work the rudder without really thinking about it. In quite a few default aircraft though, the behavior still feels too muted or just uneven from one model to the next, so the sim ends up giving mixed messages.

Most of the time when a flightsim.to mod does nothing in MSFS, it's because the zip unpacked with one folder level too many. I would check that first. In the Community folder you should end up with the actual mod folder directly, not Community\some-folder\another-folder\the-mod. If you open the final folder you should see the manifest/layout files there straight away. Also make sure the mod matches the aircraft variant it was built for, and restart the sim after copying it in. If you want, post the exact folder path you ended up with and it'll be easier to spot what's off.

I had the same moment with that panel. Once I realized the KDI-572R was sitting right below the HSI, the manual suddenly made a lot more sense. The Black Square Bonanza is one of the few add-ons that really got me to slow down and learn the older radios instead of just falling back to GPS every time. It makes short IFR hops a lot more interesting.

Nice to see this finally packaged. For someone who already has a bigger hand-built OCI setup, is the basepack meant more as a clean-start shortcut, or is there a sensible way to layer it in without replacing a lot of existing packages?

I think ConstVoid is right on that one. For me the whole point of FSHud is that it can sequence and vector traffic around my flight, so I use it with regular AI traffic rather than real-world replay traffic. PSXT/RealTraffic is great if your priority is mirroring the live sky, but once the ATC engine needs to start moving aircraft tactically those two ideas pull in different directions.

If you already know you want to fly real airline routes most of the time, I'd go straight to the 800. That's the variant you see everywhere, and the freighter plus BBJ versions make the package easier to justify. If you mainly want to learn the PMDG 737 and keep the entry cost down, the 600 is still a very good buy because the cockpit flow is basically the same and it's a fun little rocket. Personally I'd pick based on the kind of flying you want to do. For route variety and real-world relevance, the 800 gives you a lot more room.

I just came across this FR24 forum reply and it raises an obvious question for me:\n\nhttps://forum.flightradar24.com/forum/radar-forums/flightradar24-api/232177-question-regarding-of-the-free-fr24-live-data-api-shutting-down-on-30th-of-april\n\nA Team FR24 reply there says they never had an agreement with FSLTL, that they were not shutting down APIs on April 30, and that there has never been any free FR24 API. They also say FSLTL and others were using FR24 data without permission.\n\nSo if that is the case, why was FSHud compatibility blocked in the first place? I thought the explanation was tied to FR24 non-commercial licensing, so now I’m genuinely confused what the real reason was.

Little Navmap would be my first check too, because it usually tells you exactly which model title the sim is using. If the bad Caravan is still showing after removing the AIG C208 folder, I'd start suspecting it isn't coming from AIG at all. It could be a default model or another traffic package still sitting in Community.\n\nIf you want to isolate it quickly, I'd try one short test with only AIG-related traffic packages enabled and everything else traffic-related disabled. If the texture issue is still there after that, then at least you know it's not a leftover package conflict.

On the Bonanza I would separate plug fouling from persistent wear. If I taxi or idle too long full rich, I can definitely foul the plugs in that flight, but I have not seen it behave like some mystery permanent damage state by itself. If the annoyance is mainly the plugs, fine-wire plugs or the tablet clean-plugs option pretty much solves it.

For me it is mostly tricycle. Most of my flying is IFR in the 737, so tailwheel is more of an occasional mood thing than a default choice. I enjoy it when I want a slower VFR session, but if I had to pick only one for regular use, tricycle wins on pure convenience.