Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

3 Neutral

About mSparks43

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. XP11 shaders were completely rewritten over the last 6 months. XP's graphics "out of the box" target the minimum system requirements (notably a DirectX 11-capable video card with only 512MB ram) + supporting payware scenery designers If you want to get a taste for what scenery designers can do and dont want to dig into your wallet, have a fly round the propstrike fisheries example, or the recent KMGM "payware for free"
  2. If you want to skip the lua stuff you can put all these values in resources/settings.txt which are where the defaults come from (keep a copy of the original and your modified version because it gets replaced when you run the updater) also quite a few can be modified "on the fly" (not all) via https://developer.x-plane.com/tools/datarefeditor/ then plugins->Dataref editor->"show art controls"
  3. Version 0.8.7b1


    This is the AutoATC Beta branch. Version 0.8.7b1 adds: Better android integration (power control, frequency list, flight model etc) Support for multi PC cockpits with AutoATC Pro android app (set extended cockpit in Plugins->AutoATC->Settings for external views) Fix for multiple Java plugins (see https://forums.x-plane.org/index.php?/forums/topic/175706-sharing-the-jvm/)
  4. Just a quick progress report of the 0.8.7 Beta update, and a place to discuss any issues. Android companion applications for 0.8.7 rolled out last weekend and now seem stable. If you spot a layout issue, please post a screenshot so I know where to look to fix it. There were a lot of layout issues in landscape mode which are hopefully fixed now, but I may not of caught all of them. An updated plugin is ready, just needs some more testing against the new AI Server to make sure nothing is badly broken there when I make the switch. new AI server is now completing its unit tests - not passing all of them, but at least not breaking on long runs. Both the plugin and the phone app need to be on 0.8.7 before I can make the switch to the new AI Server. Even if I don't have the new AI server passing all its tests this week I'll put the current plugin build online this weekend since there are already numerous improvements over 0.8.69 against the existing AI Server.
  5. There is no registration as such, I have no interest in your personal details, don't want or need your email address and certainly dont require any password system. There is however a "special way" to register your callsign when you first connect:
  6. Why I dont see any options to register a username or define my aircraft?
  7. Move to payware: Once 0.8.7 is out of Beta, AutoATC will be moving to a payware model, similar to that of X-Plane. The flight model for AI aircraft will be additionally be bundled the plugin, (voice recognition will still require the android companion app), but without purchasing a key (or connecting via the paid android application), plugin run time will be limited to 15 minutes.
  8. AutoATC is a fairly complex piece of software that is not yet quite perfect. You can follow known issues and add new ones you find on the GitHub issues page: https://github.com/mSparks43/XPlane-11-AutoATC-plugin/issues
  9. Somethings not right, its not working, help!
  10. Could you possibly link me those posts, I've seen the "don't harass developers" mantra banded about a few times, but not actually seen any examples of what this means. That said, as a developer, I would absolutely HATE the idea that someone who has an interest in something I developed - even freeware - might keep their mouth shut for fear of "being harassing". If something is broken, I need to know, If something isn't clear, I need to know. If something is a super desirable feature I definitely need to know. I simply cannot imagine how any situation can arise where a developer feels "harassed" that isn't entirely the fault of the developer, in which case everyone needs to know - especially if its payware.
  11. Version 0.8.69rc1


    This is the latest stable release of the AutoATC plugin for Xplane 11
  12. This has been by far the most commonly asked question. There are three common places things go wrong. Not using a 64bit JVM. This is most obvious if you are setting a path that includes "Program Files (x86)". This [windows] directory is for 32 bit programs. Missing msvcr100.dll. This is a windows component included in the "Microsoft Visual C++ Redistributable Package (x64)" (quick download) Otherwise a wrong file path, for example a wrong version number (Java installs each version in a different directory) The original installation tutorial can be found below. However you should use the files available here on ThresholdX rather than searching google, and you can now set the path directly from the AutoATC->Settings menu from within X-Plane.
  13. The plugin refuses to start with a popup error message "Can't find JVM"
  14. Android support was "accidental". AutoATC started life a fairly simple idea for an X-Plane plugin: A cross platform tool to practice ATC read backs in spoken form. Android turned out to be the most efficient way to achieve high quality universal voice recognition at an acceptable cost (both for users and for development). The plugin itself runs on Windows, Linux and MacOS. Developing for iOS would require starting completely from scratch, whereas most of the code for Android was a simple copy paste from code already in the plugin. Starting from scratch to support a $1000 device for a plugin doesn't seem like a good use of time.
  15. Why is the phone application only available for android?
  • Create New...

Important Information

Please read the Terms of Use