STK

I'd start with the default Cabri, then the default Airbus Helicopters H125, and then go from there if you're first learning helos. The Dauphin is indeed quite different but at least getting the foundations down especially in the H125 should lead to a slightly easier pathway into the Dauphin. Same rotor rotation direction, more automation, wheels, and generally less squirrelly than the helicopter literally called Squirrel in French.

Anything by Taog is your best bet, to include their new AS365 Dauphin. There is a learning curve with the Dauphin though in terms of how they've implement the force trim functionality, requiring new mappings and likely a different mindset than what you're used to based on all of the other's implementations. Your list is good otherwise, except I'm not fond of the Scout/Wasp but I last used it in 2020 and should probably try it in 2024 to see if it's more realistic now (maybe they updated it). Also take a look at the default H125 (NOT the 225), and from an addon perspective, the Miltech/Stratoware MBB Bo105.

A few things really matter when flying in the sim: Frame rate. If you are in an area with complex scenery, traffic, and weather and may get frame choppiness, you're not going to be brining in the helicopter for a controlled landing. Trim: learn how to use the rotor trim functions default to msfs2024, and in the case of the Taog Dauphin, learn it's unique and more realistic implementation involving force trim and trim release while maneuvering. Trim matters, and especially in the default helos like the H125 (AS350) is just as much of a dance of constant modifications as control pressures are. Note I said control *pressure*. Your movements on any joystick hardware should generally be measured in millimeters, not centimeters, especially when hovering. Apply slight pressure in the direct you want to go using your palm muscles and fingertips, rather than using your wrist and arms. Focus your view out the window, on the horizon, not on the instruments, and not near the ground in front of you. If you are practicing hovering, pick a building or tree 100-200 meters away and focus on that as your reference point and ensure it doesn't drift around your window, not on what's immediately below and around you. Simulation users are drawn to their instrument panels and what's below them. Look up and out. Start small and work up from there. Use an airfield with a helipad and practice hovering first. Then practice pedal turns / pivoting in one spot over that helipad. Then, practice controlled departure from the helipad (and end the flight). Finally, practice approaches. An approach to a pad shouldn't take 5 minutes as you dawdle closer. Keep it swift, plan ahead, settle into a walking pace ground effect as you are near the edge of the pad, and just smoothly bring it in while arresting the decent. It's a balance between coming in too hot and having to lift the nose excessively vertically, and coming in too slow and spending 5 minutes on the approach. Smooth, steady, constant approach to touch down. Use a quality helicopter addon with realistic flight dynamics. Learn how different power settings require different degrees of anti-torque pedal ("rudder pedal") input and anticipate that input for the power setting you are using. Also know what to expect regarding countering torque if you are using a European or Russian helo vs a US/Canada made aircraft.

@anilcougar - what's the latest update with this effort?

I hope that Anil jumps back in here and further substantiates things (and selfishly for me, answers my additional questions on traffic handling a page or two back), especially with the system moving into beta. Beta to me means that an initial feature set is locked down, of course with future features to come later after an initial release. I suspect, yes speculation, that he's pulled back a bit in order to maybe focus on more careful messaging to the public on what precisely is being offered and how from a technical standpoint, but I am happy with how responsive and patient he's been with the community up to this point. The fact that's he's leaning on AI to generate his communications, and the initial philosophical statements were a put off, but he has been able to elaborate on features when asked. Here's hoping for good things.

A follow-on inquiry despite a couple users feeling like we aren't supposed to ask the developer questions. I'm glad that the dev has been forthcoming with responses. My understanding, admittedly a weak one, is that there are severe limitations in how AI aircraft are/can be controlled by external interfaces in MSFS. I recall other products that can sequence the user through/around traffic, but past efforts at sequencing AI traffic models have been clumsy, in that they have to basically slew AI aircraft around to separate them, slew them around holds, etc, rather than rely on their own coded flight models. For this software's solution could it / will it direct AI traffic into holds, or enforce speed restrictions, or give any sort of other direction and the AI traffic will follow that? You previously said that AI will be managed, but from a technical perspective, HOW will they be managed? Again, I thought there were interface limitations between built-in traffic handling code within MSFS, and those of external interfaces. (AIG at least used to have some issues with the fluidity of aircraft in flight, for example). Asking simply because I don't know how that works, not to challenge statements. Is it slewing them or relying on their own flight dynamics? A few examples: Runway incursions - if ATC tells an AI aircraft to abort take-off, will it? Ground taxi routes - As your real-world ATC advisor can likely attest, at busy complex airports, sometimes traffic is cleared at the last second to a different routing as they are taxiing to the runway (Delta 123 continue straight rather than right on alpha, then follow company - for example). Can that happen here to the user AND to AI? Holds - let's say it's rush hour with poor weather on top of that. Will I be in a stacked hold with AI traffic above and below me (thinking the Heathrow stacks here) prior to being cleared for approach? Will I see AI aircraft models in holding patterns? Re-routings - AI aircraft is scheduled to fly from airport A to B via fixes 1, 2, and 3. Would the ATC amend their routing to fixes 4, 7, and 9, and the AI traffic model follow that new routing? Any technical detail you can share about how your model interacts with how MSFS handles AI traffic would be great to hear! Thank you!

@anilcougar I greatly appreciate the honest responses and details provided rather than marketing speak. The openness has impressed me, and there seems to be no hesitation to provide answers. It seems we have a run of the mill angry avsim user in this thread who already is insulting me, despite the fact that you seem to have no issues responding to my questions. Thanks again for the thorough responses. I’ll watch this development with interest. @cowpatz The initial post was full of philosophical speak and flourish without software engineering detail, but luckily the company responded with real detail on core questions. Also, as indicated they are going into beta, not “hardly in the alpha stage” as you state. You seem to be a very ill tempered and short tempered individual in the face of questions that try to dig past generic marketing statements. It seems like the developer has handled them with patience and grace luckily. It also seems they have implemented more than you know, with answers to integration questions being met with a surprising yes. I hope you have a better day. I learned a lot from the dev responding to my questions.

What AI model are you using to baseline your architecture and how will the use of your selected logic algorithms and backend frameworks impact user pricing? Can we presume that this is a subscription based model? What about text and voice features? Does this require voice recognition and interaction, or can a user select from pre-set responses akin to the default ATC simulation in MSFS today? What voice models are you using for audio feedback? It sounds like you are starting the scope just as all other providers have, with IFR as the baseline, then moving into VFR operations, and I presume also with other scopes such as helicopter flights, VFR corridor support, and special use airspace. Is this an accurate roadmap? Finally, as much as I hate those who immediate do the "this is all AI, that's AI, you're AI" screeching, I must ask, because I'm noticing a particular cadence and sentence structure utilized in your forums posts, are you supplementing any written responses with AI in any way? (It may be due to what I perceive as a marketing cadence, but I'm just curious based on your company's portfolio and topic profile).

We need a lot more operational detail rather than numerous one-liner "soundbites" akin to the "in a world...." movie trailers. IFR, VFR, both, other options (VFR On Top, Special VFR, etc etc?) AI integration: Does this work with packages like FSLTL live traffic, default MSFS live traffic, JustFlight, AIG injected traffic? Do you use your own injector? If so, what's the source? Will I be given traffic alerts (as well as AI pilots)? FAA vs ICAO phraseology differences? JFK is infamous for their controllers not using formalized language (either FAA or ICAO approved) thus leading to a lot of problems with pilots trying to understand casual instructions in their non native language. Aircraft types. Most here use modern jet airliners on scheduled routings. What about our light sport pilots? What about helicopter operations? Do you support proper helo phraseology such as "...at your own risk"? Weather implementation: Is your ATC product aware of weather (live weather and/or user preset weather)? Can a pilot deviate around weather? Will ATC put you in a hold due to storms over an airfield or advise of storm fronts on the route and accommodate a different routing? Non-standard procedures: Can I request a radar assisted approach? Can ATC implement LAHSO (land and hold short operations) at an airport due to traffic? Ground taxiing: Will I be accurately directed to following company traffic to the runway (for example) if I'm operating as the same airline as an AI aircraft ahead of me? Probably more questions but these are the immediate ones come to mind until more info is provided via follow-on responses or edits to the original post. Always interested in new ATC services but this really reads with a lot of superfluous marketing speaks. Give me the facts, not just the philosophy.

There's a thread on this model on the Official Forums which I've contributed to. I've reached out to nemeth deisgns about the flight dynamics and sounds, in which the former is now clarified in the new manuals (prohibition on maximum flaps usage though the aircraft does permit them to be extended that far), as well as extremely poor sounds. Nemeth acknowledged that the sounds are not sufficient (and were outsourced) but not sure how they will address that failing. It's a nice looking model overall and has fairly in-depth systems. Allegedly more updates are coming.

Loving this one and flying it daily. It's faster than most light singles and can at least keep up with the light twins I have for 3/4 of their speed range. (Example: Just as fast as the new Commander 114 by Blacksquare until you get into the middle of the 114's yellow arc.) Very capable autopilot (once you get the control mappings down correctly), trim system, and while I wish that an EFIS was an option, the ability to have a GTN 750/650 avionics suite available adds a lot too. Honestly, it's more useful and versatile to me than the vast majority of light aircraft available for the sim currently - just takes some learning of the systems, flight control settings (such as disabling fly through for spring-centered sticks), and adept control mapping. Discord outlines all the tips and tricks for a smooth flight experience. As someone who has some time in the real thing, two thumbs up on this model.

Excellent thank you! There used to be a freeware Upolu but the author had removed it months ago for unknown reasons. I'm also hoping for a two more significant airports that remain without good representations in Hawaii: Hilo (PHTO) - recently covered by FlyNdrive4D payware Hawaii Landmarks Extension product which isn't bad at all, but a higher fidelity version would be great. I contacted Northern Sky about this one at least a year ago but they don't have enough reference material to make it, and efforts to reach out to the airport administrators were met with silence. Kalaeloa Airport - used to be Barbers Point NAS. Still has the ever-busy US Coast Guard air station on premises, and the rest is a quieter GA field now. There is or was a version on .to for 2020, not sure if removed, but a high quality version presumably by Northern Sky would be very welcome. I haven't reached out about this one, but images may be more obtainable. With Upolu covered, if we can just get the above two done in higher fidelity than current available, every major airfield will be covered in Hawaii besides the two Army Air Fields (AAFs...one on Oahu and one on the Big Island), and the tiny little grass fields that may or may not even exist anymore.

I hope so and almost expect that as an option. Project Tupolev had an abundance of crew status callouts throughout all flight regimes from pre-startup through shutdown, and what they did in the manual was add an appendix (from what I remember) that listed the callout in Russian (in Cyrillic), then they provided a transliteration using English letters (so you know what the Russian sounds like and can pick it out), and next to that was an English translation. I'm thinking if FSS introduces a Russian speaking crew (with an English option) this would be a good way to do it in the manual. Russian phrase in Russian, translit using English letters, and then also provide an English translation of what they're saying (and what it means). What I'm also curious about is who they are seeking advice from from a flight dynamics perspective. There used to be a "Flight School" section on the Project Tupolev forums, where one could basically send a virtual black box recording of their flight and have the PT team analyze it and provide advice on how to more realistically conduct the flight in the future. They were extremely particular when it came to detail, looking for engine parameters down to single percentage points, control surface movements measured in a range of millimeters, speeds within a couple of kilometers, etc etc. It took extreme precision to meet their standards for what was considered to be a well executed route. Finally, RSBN navigation. I never learned to tackle it manually and instead relied on their accompanying calculation software, but it's a whole new world that to me was dissimilar from everything else, including INS procedures. Calculating sine and cosine to determine headings, converting one map format to the NVU's computer, etc etc. Lots of math and complexity, and that doesn't include the peculiarities of the system on the center console unit itself. This aircraft is going to be intimidating, exciting, and a whole new world for many.

I was very (extremely?) pleasantly surprised to see it announced as an FSS endeavor. I remember when the original author (who is still involved in some capacity) said he passed off the model to an anonymous company, and I thought "vaporware". It'll be nice to have an old friend back in the latest sim. No connection to Russia or the Soviet times otherwise, but I'm fascinated by their tech. :) Also, this thing coming out with almost two dozen liveries just to start? Awesome!

Hopefully a great successor to the Project Tupolev Tu-154 from the FSX/early P3D era for those who enjoyed their stuff. It seems like FSS is taking this seriously and is aiming for realism and complexity, which is a good thing. This is a 1960's-70s (through 90s and early 2000's) era tri-jet with a wide customer base and which has been seen globally. No ETA but I'm wildly guessing at early 2027. MSFS AddonsFlightSim Studio shares first development update on its T...The first development update since the FSExpo reveal tackles EFB, tail geometry, and a 22-strong livery list, though a release date remains off the table.I'm really hoping they get this right, while also providing assists and calculators akin to what Project Tupolev did in the past, notably to assist in using the NVU for RSBN navigation. Sounds like they intend on a wide selection of liveries representing operators in Europe and Asia, and are also seeking additional technical references and expertise to ensure they get things correct. I suspect that this addon once released may be met with some hostility since it's very much Russian (vs the Ukrainian-based Antonov) but we'll see how it goes. It's exciting to me as a years-long user of the Project Tupolev models (and another lesser known but equally high fidelity payware model from a Russian provider) who has missed the 154 for years now.