Jump to content

Andrew Heath

5,097 views

 Share

On April 1st, 2020 we officially began approving invites to the POSCON Invite-Only Beta. We are now almost two months into our release and it still brings me great excitement every time I see a new user experience POSCON features for the first time. We learned a great deal in the first few days and weeks after the initial release. One thing that became abundantly clear was that we need to have a central location to refer users to in regards to what features are functional, what features are still in development, and what features are planned for the future. In addition, there still seems to be some confusion surrounding the invite process, so I am going to attempt to clarify all these items in this development update.

Before I began, I think it is worth mentioning that we created a Frequently Asked Questions (FAQ) area that may contain answers to some of the questions that may not be answered in this blog post.

While there is no doubt that we have deviated from the FSExpo 2019 Roadmap to Release timeline, we are doing our best to keep on track. Right now, I think it is safe to say we are in Invite-Only Beta, Phase 2. Here is a quick recap on the original plan for Invite-Only Beta, Phase 2 and what may or may not have changed since the announcement was first released:

  • Pilots will require an invite code and subsequent approval in order to participate
    • Status Update: This is still the case. Currently, any approved member with access to the network also has the ability to invite two additional registered users to the service by clicking here. Once invited, those members will be placed into a holding pattern until they are approved by the POSCON staff. There is no set time frame on when these approvals are distributed - we approve people when the team feels comfortable to receive additional members. This two-step process was designed to meter the flow of incoming members and minimize the amount of support requests we receive. More information on the invite process is discussed below.
       
  • ATC will be hand-picked by POSCON staff and will be required to sign an NDA
    • Status Update: This is still the case. We have been testing ATC regularly now, but we rarely advertise when or where we will be conducting these testing sessions. This strategy is employed on purpose in order to not overwhelm the controllers as they test new features. On a few occasions, we have given some advance notice of when ATC will be online, but right now those instances are rare.
       
  • Operating times will be schedule limited
    • Status Update: This is no longer true. Before we released, we separated the network into a development environment and a production environment which enables us to minimize interruptions to the users as we add new features. With the exception of a few hot-fixes in the early days after releasing, we have made considerable effort to inform all beta testers of scheduled maintenance well in advance of a server restart. In order to facilitate this, we created a System Status Monitor page which can be used to view the status and scheduled down times of our applications: https://status.poscon.net/
       
  • ATC coverage will be limited to areas selected by POSCON
    • Status Update: This is still the case. ATC testing has been limited to the areas where the facility data is most developed; however, our Facility Data Team has been tirelessly working on other areas around the world as well. Here is just a brief overview of what they have done:
      • 170 FIRs have been worked on.
      • 7856 independent ATC sectors have been created.
      • 7053 independent VHF transceiver sites have been located and entered into our database.
      • 1801 independent radar sites have been located and associated with 73 different radar types.
      • In addition to the above, below are just a few images of the FIRs that have been worked on:

POSC.thumb.png.d42154b9976d3fc10592c7eb052a41fd.png

1756128805_unknown(5).png.ac0d191d19aa5d8a40f2e3f4cd001207.png

1146374016_unknown(6).thumb.png.717a35b499e35d6d690654371fef7aa0.png

1283809566_unknown(5).thumb.png.4576d569db1ca90a9cb896965b3d4fda.png

FIR_LPPC_LPPO.thumb.png.d834256c6dfa3969b4ce13dd3c48c0f9.png

1d46e539283cb2736aaefb63c87233c3__01.thumb.png.edee1cc2ac83b286a0f9e9851c154d85.png

CANADA.png.8661221da2fc676c1136fe08668d5b18.png 

357923746_unknown(2).thumb.png.088420ffa33a7ff5d58d301ed19bb34b.png

840845642_unknown(1).thumb.png.7b1c11c17517e321690c5ee905a22609.png

587418646_unknown(4).thumb.png.44a78330ec89a312f7f6d10ecebde687.png

MILANO_FIR_POSCON.thumb.jpg.e12fb9468ccdb9952b9a7bb38f09e962.jpg

 

  • Number of users was planned at between 1000-2000
    • Status Update: This is still the case. As of May 23rd, 2020 we have invited and approved 1278 registered users.
       
  • NDA is not required for Invite-Only Beta, Phase 2
    • Status Update: This is still the case. You are not required to sign a non-disclosure agreement (NDA) unless you are hand-picked to be an ATC. We will continue to maintain a select group of NDA pilot beta testers to test new features in our development environment.

 

Invite Process - How does it work?

As mentioned earlier, the invite process consists of two steps: INVITED and APPROVED. Here is how it works:

  1. Lets assume you joined the POSCON Public Discord first and then realize you are interested in joining the network. If this is the case, you are considered an "Enthusiast" and will be assigned that tag automatically in our Discord server.
  2. Now you decide to register at https://www.poscon.net and complete the checklist items which include: ensuring your birthday is set correctly and your Discord ID is connected to your POSCON account. At this point, you are now considered a "Registered User".
  3. If you are lucky, you may be invited by an approved member as their guest and you will receive an email from POSCON. If this happens, you are still considered a "Registered User".
  4. Please wait patiently until you are approved by POSCON staff. When approved, you are now a "POSCON Member" and have access to our HQ website and are able to download the Launcher Client. This is the point at which you can now connect to POSCON.

The time between steps 3 and 4 is an unknown. It could be a matter of days, weeks, or even months. It all depends on where we are at with our development and whether we are ready to accept new members.

If you find yourself in limbo, the best thing you can do is join our Public Discord and participate in the discussions until you are invited and/or approved.

 

What is working, what is in development, and what are the future plans?

Voice System

Working Features:

  • Ground-based transceiver locations have been added for most ATC facilities.
  • Auto gain control.
  • Propagation of transceiver locations to the Radar Client.
  • Our voice library supports the option for separate PTTs per radio (e.g. VHF #1 and VHF #2), separate volume controls per radio, and separate audio devices per radio.
    • NOTE: The pilot clients do not currently support this yet.
  • Full VHF simulation including:
    • 8.33 kHz and 25 kHz spacing.
    • Terrain line-of-sight processing.
    • Beat simulation.
    • End-of-transmission popping tones.
    • Wavelength simulation.

In Development:

  • ATISAWOS, and ASOS automatic audio broadcasts on the proper frequencies.

Future Plans:

  • HF and UHF.
  • There are many more features planned, but we are going to keep those a secret for now.

Website, Training, & Administration

Working Features:

  • Fully GDPR compliant.
  • Integrated support system.
  • Basic flight statistics.
  • ICAO 2012 formatted flight plan form includes:
    • An integrated help tutorial provided on the page.
    • The form validates while entering data.
    • Auto-fill from SimBrief output.
  • Feedback and generic points system works.
  • Live Map used to view online traffic (updates every 2 seconds).
    • Users can leave feedback about each other using the map.
    • Moderators can initiate ghosting, disconnects, and bans using the Live Map interface.
  • Pilot Client Web UI, which can be accessed on any device with an internet connection (see below for more details).

In Development:

  • Converting HQ to a new language and framework.
  • Moving elements of the ICAO 2012 flight plan to the server.
  • Live Map version 2.0 will use custom tiles and our own tile server. The map will also contain a 2D option for performance reasons.
  • Various upgrades to user-interface and user-experience throughout the HQ.

Future Plans:

  • Upgrades to the user profile, including notifications.
  • Pilot and ATC scheduling system.
  • Advanced statistics center.
  • Additional ways to earn and lose POSCON points.
  • Additional CBTs with progression quizzes.
  • Airport Advisory Page system. This system will allow Divisions and Sub-Divisions to create informational pages about their airports that will be viewable by all pilots.

Pilot Clients & Web UI

Pilot Clients

Working Features:

  • Both pilot clients support a high refresh rate. Models will update 15 times a second for a smooth visual experience.
  • Enhanced ground-clamping using various methods for a smooth experience regardless of differences in terrain.
  • Model matching. Here is how we handle model matching with the various platforms:
    • For X-Plane, the models are distributed with the pilot client itself and contain custom model matching logic.
    • For FSX/P3D, we have integrated the FLAi model set through our Launcher Client application (see below for more details).
  • ICAO equipment and airline code validation.
  • Accurate ground speed monitoring (X-Plane Only).
  • VHF push-to-talk activation indications.
  • VHF volume sliders on the native user-interfaces.
  • AI model sounds and controls (X-Plane Only).
  • The ability to control the maximum number of AI planes that will be displayed.
  • In-game notification of ghosting and disconnects with explanations.
  • The ability to manually toggle ghost mode or request to unghost.
  • Automatic detection of change in aircraft.
  • X-Plane 11.50 Vulkan support.
  • Moderator messaging directly into the pilot clients.
  • Automatic ghosting for:
    • Sim rate increase, entering slew mode, using replay mode, or deliberate pausing (this can also sometimes be triggered by accessing a sim menu).
      • If you are on the ground and not moving, pausing is allowed.
    • Connecting on or re-positioning to a runway (through a menu) will prevent connection or disconnect the user as applicable.

In Development:

  • We are fixing various issues with models and model matching (X-Plane).
  • A new multiplayer library is being integrated (X-Plane).
  • A new native user-interface is being added (X-Plane).

Future Plans:

  • We plan to make full use of the voice system by adding separate PTTs per radio (e.g. VHF #1 and VHF #2), separate volume controls per radio, and separate audio devices per radio.
  • HF and UHF integration.
  • There are many more features planned, but we are going to keep those a secret for now.

Here is an Easter egg for those who have gotten this far in the blog: If you can name all the FIRs (the colored ones) depicted above correctly, then you can get an instant invite and approval to use POSCON. DM your answers to me directly. Offer expires May 27th at 2359 UTC.

Web UI

Working Features:

  • Some functions of CPDLC (Controller-Pilot Data Link) are operational such as the login function and automatic squawk code assignment.
  • Real-world FAA D-ATIS (Digital Automated Terminal Information Service) broadcasts are integrated and can be requested in real-time by pilots.
    • The voice portion of D-ATIS is not working yet, only the text portion.
  • METAR and TAF reports can be requested in real-time by pilots.
  • Radio syncing.
  • Ghost and unghost toggle.
  • Disconnect.

Future Plans:

  • Additional CPDLC functions, including heading, speed, and altitude changes.
  • Full pilot report functionality.
  • Approaching online ATC awareness messages.

Launcher Client

Working Features:

  • The ability to download, install, launch, and update all available network software.
  • Token authentication. Once you enter your username and password once, the Launcher Client will take care of the rest.
  • image.png.f38b09c14b39359d078f8229fff838cf.png We added some new functionality to these buttons. The button on the left refreshes the Launcher Client, the middle button minimizes the Launcher Client, and the button on the right will send the Launcher Client to the system tray.
  • Once in the system tray, right-clicking on the Launcher Client icon will bring up a menu that will allow users to: reload, clean temp files, and quit the application.

In Development:

  • Adding libraries that will utilize a new content delivery method through a download server.
  • Converting the application to a different framework.
  • Working on moving away from our web dependent set up.
  • User-interface changes such as adding a download progress bar, information display, and a direct link to Discord from the title bar.
  • Working on integrating Live Map version 2.0 through the Launcher Client.

Future Plans:

  • The plan is to embed the Pilot Client native user-interfaces directly into the Launcher Client. There will be no need to launch a the Pilot Clients anymore after this is completed.
  • Once the back-end work is completed for the above, a new user-interface will be needed to accommodate the integration.

 

Next steps?

The next step for the POSCON team is simple: we will continue to work hard on bringing you the next-generation flight sim network.

While we do that, we encourage you to join our Public Discord and participate in the discussions there. Typically, the most up-to-date information about the project is released on our Discord first.

That's it for now! If you have any questions that have not been answered in the FAQ or in this blog post, feel free to comment below.

 

  • Like 2
  • Thanks 2
 Share

0 Comments


Recommended Comments

There are no comments to display.

Guest
Add a comment...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • More Blogs

      • 0
        entries
      • 0
        comments
      • 645
        views

      No blog entries yet

    1. Airline Talk

      • 1
        entry
      • 0
        comments
      • 74
        views

      No blog entries yet

    2. Director's Office

      • 3
        entries
      • 5
        comments
      • 905
        views

      Recent Entries

      Andrew Heath
      Latest Entry

      By Andrew Heath,

      Back in September of 2019, I was browsing through X-Plane community downloads in order to find additional models to enhance the POSCON X-Plane Pilot Client model distribution. During the course of my search, I came across the X-CSL model package and reached out to the X-CSL team via their Contact form to obtain authorization to use their package in our software. The X-CSL team granted POSCON permission back then, but as of January 2022, they have unilaterally revoked that permission.

      The main reason for this blog post is to inform POSCON users that the X-CSL package is in the process of being removed from our distribution and should be fully removed by the end of the week. Once this package is removed, the next time you reinstall your X-Plane Pilot Client via the Launcher Client, the models will be automatically deleted from your computer.

      An equally important reason for this blog post is to shed light on what transpired to get us to this point, a point where we are taking a drastic step backwards regarding user experience. The reason for this decision is because the founder of the X-CSL model package, a man named Aleksandr (Almik) Mikitas, revoked permission to use these models after our "Out of Beta" announcement was made public. He wrote to me shortly after the announcement and claimed that permission was never granted to use these models, even though a senior developer from his team clearly granted us permission over two years ago (see the email exchanges). As mentioned earlier, I originally wrote X-CSL via their Contact form in September of 2019 to ask for permission and Aleksandr responded and handed me off to his senior developer who subsequently granted permission to use the models with the stipulation that we give credit to X-CSL, which we did: https://forums.poscon.net/docs/support/manuals/acknowledgements/

      Despite my best efforts to convince Aleksandr that the lack of communication was isolated internally within his team and not at all POSCON's fault, he has decided to take punitive action against POSCON members by requiring us to remove the models. This action only serves to hurt you, the user, by making it more difficult to use the X-CSL package (i.e. you now have to go download it from their website and use scripts to get it to work with POSCON, which is hardly worth the time). While I have many theories about the timing and reasons behind this new requirement, I want to stick to the facts here as much as possible.

      Speaking of facts, here is an important one: Aleksandr Mikitas now works as the MTL Designer and Membership Assistant Coordinator - Eastern Europe and Northern Asia for the International Virtual Aviation Organisation (IVAO). To my knowledge, Almik did not hold this position with IVAO at the time I approached X-CSL in September of 2019.

      I have put together an evidence package in case POSCON users want to dig deep into what was said and by who. Publicly releasing my personal correspondence is not something I take lightly, but I find it entirely relevant to the current situation. An important note about the email exchanges is that all respective parties were always CCed on every email so anything said was guaranteed to be seen by both Almik and myself.

      Based on the email exchanges with X-CSL, my lawyer concluded that X-CSL and Almik implicitly allowed POSCON to distribute these models. Why else would Almik have referred me to his developer in order to give us technical information which would enable POSCON to include these models in our software? Our intentions were clearly outlined from the very first email sent to X-CSL. Almik and his developer never said, “yes include the package in your installer” directly, but they also never said “no.” Even though Almik was CCed on all the emails from the beginning, I recently reminded him that he was the one who referred us to his developer and as a result, his developer told us how to include the model package in our software. The POSCON developer programmed software based on this representation. The X-CSL developer's role in this was perpetuated by Almik — Almik referred POSCON to his developer, so it implies that Almik knew what this was about, and approved of it.

      What's also interesting to note is that Almik says he created this package for the benefit of all X-Plane users, "Each our model is a our free time, effort and even money to give the best results for all XP users as free," but by revoking POSCON's authorization he actually has made it harder for X-Plane users to use the X-CSL package on their preferred network of choice, unless of course that network is IVAO.

      At the end of the day, POSCON will comply with X-CSL's demands, but I think it is important to shed light on what sometimes happens behind the scenes in this "community" and why we can't have nice things.

      Reflecting back, this whole situation seems eerily familiar to the recent debacle between AIG and FLAi (click here for additional reading material). Bottom line, this type of behavior in our community needs to be called out and more importantly, it needs to stop.

      What Happens to the POSCON X-Plane Model Package?

      To be honest, this doesn't really affect our model package too badly. There was approximately 70% overlap between BlueBell and X-CSL, so there will be a few unique models that will disappear in addition to some liveries. If you are interested in helping the POSCON model project recover from this loss, please reach out to Jeffory Beckers, our Model Asset Manager.

    3. Guest
      Latest Entry

      By Guest,

      I'm sure you've seen those four letters before - RVSM - and you may have a fundamental knowledge about the airspace, but do you know why it exists? Here are the answers to the most basic questions:

      1. Where do we find RVSM airspace? Higher cruising altitudes.
      2. What happens in RVSM airspace? Airplane separation is reduced vertically.
      3. Why does RVSM airspace exist? To allow more aircraft in the sky.

      There you have it... the simple definition of RVSM. Now, let's get technical:

      179238233_rvsmexample.thumb.jpg.7dec5a890cb6b0df0630858cc6783e10.jpgRVSM stands for Reduced Vertical Separation Minima and it's located between FL290 (29,000ft) until FL410 (41,000ft) inclusive. To understand RVSM, you must first understand what the vertical separation requirements were above FL290 before 2005. Prior to RVSM, aircraft were required to be separated by 2,000 feet vertically above FL290 due the possibility of altimetry errors at the higher flight levels. RVSM airspace allows for a reduction in vertical separation between qualifying aircraft in order to allow more aircraft to operate in crowded enroute airspace thereby allowing for more efficient traffic flows. Airplanes of course move a lot faster at higher altitudes though, so it is only natural that this little amount of separation may make even the most vigilant pilot a little nervous. However, it is important to note that before implementing RVSM, aviation authorities instituted a required set of parameters that must be met in order to operate in RVSM. If any of these parameters cannot be met before entering or while operating within RVSM airspace, the aircraft is required to advise ATC and exit RVSM.

      Before we get into other details about RVSM lets recall that in many countries, the East ODD and West EVEN rule applies to vertical separation. This practice ensures that two airplanes are never assigned the same altitude flying in opposite directions. In some regions that are geographically more north/south split such as Italy or Florida for example, they have elected to modify the rule to favor North ODD and South EVEN as the determining factor for vertical separation. Either way a region chooses to separate traffic, it is important to recognize that these rules exist are crucial to establishing a baseline for high altitude vertical separation.

      Now that we have covered the basic rule for opposite direction vertical separation, let's talk about what makes an aircraft RVSM approved. In order for an aircraft to operate in RVSM airspace, a certification is required from the governing agency of that nation (FAA, local CAA's, etc.), but the basic equipment that an aircraft should have operational include: an autopilot, two independent altimeters, a transponder with an altitude reporting capability, and an altitude alerting system. During flight in RVSM airspace, pilots will cross check their two independent altimeters to ensure the difference does not exceed a specified tolerance, which could range anywhere between 50ft to 200ft.  If any of these items malfunction during flight in RVSM airspace, notification to air traffic control is essential.

      Let's talk about air traffic controller's responsibilities in regards to RVSM airspace. Aircraft will have an equipment code in their flight plan assuring ATC that they are RVSM compliant and capable. If an aircraft alerts that they are no longer RVSM capable, ATC will have to either ensure separation of 2,000ft with that aircraft at all times or descend the aircraft outside of RVSM (below FL290).  However, just because an aircraft is not RVSM capable does not mean they can never fly between those altitudes. Many corporate jets are not RVSM capable but still request to cruise above RVSM airspace (e.g. FL430). In this scenario, the controller will climb the aircraft through RVSM airspace while ensuring 2,000ft separation is maintained between other traffic at all times. 

      On a final note, RVSM aircraft require a maintenance certification as well. The next time you start up your flight sim and connect to POSCON for IMG_20190825_235257469.thumb.jpg.8e83b29248a45ce99a0d2db21142efb2.jpgyour online flight simulation experience, take a look at the outside of your aircraft. Depending on the quality of the aircraft in terms of realism and study level, you should see what's called an RVSM critical area (see image to the right). Aircraft maintenance technicians must run specific tests and certify that everything located within this box meets the required RVSM tolerances, which are often stricter than in flight checks accomplished by pilots. Static ports, pitot tubes, and AOA vanes are small examples of what can be found in these boxes, of course, these are important functions that will assure RVSM tolerances when in flight. Pilots check this box during preflight inspections to ensure this critical area is free of residue, damage, dents, or other non-normal appearances on the components in the boxed lines.

      On POSCON, our air traffic controllers are well trained on RVSM procedures. When flying online, ensure your aircraft is RVSM capable and make sure you indicate it properly in the flight plan equipment code section ("W" is the letter identifying that the aircraft RVSM capable). If you do not include "W" and are offered an RVSM altitude (it happens), simply say to ATC "Negative RVSM". And of course if you are having issues with your autopilot, now you know you are required to tell air traffic control.

      After reading this article, you should be confident answering when and why the "W" equipment code is required in your flight plan. It is true, there are far too many acronyms in the aviation world, but at least you got RVSM down! See you on POSCON in RVSM and don't forget the whiskey! (get it?)

    4. Network Technology

      Andrew Heath
      Latest Entry

      By Andrew Heath,

      CAPTAINS,

      (if you have been in the flight simulation community long enough, you will understand the "Captains" reference)

      The last technology blog post was published in May of 2020, and what a long journey it has been for our team since then! Thankfully that long arduous development journey has come to an end and users will be able to benefit from our hard work.

      I want to start off by answering some common questions and clearing misconceptions.

      Is POSCON dead?

      Absolutely not! We are very much alive and well!

      We may not seem like a major player in the online flight simulation network arena right now, but rest assured that our technology is far superior to that of our peers and we will be a significant force to reckon with in the near future.

      So, where have you been?

      The short answer is, we have been here all along. . . quietly developing.

      As a result of feedback from early beta testers, we took the drastic step of essentially shutting down POSCON's forward progress in order to rewrite the voice software. This decision was made when we realized that the voice software was not going to be able to sustain our projected growth using the protocol it was developed to use. Making a change to the protocol basically required a complete rewrite, which I am pleased to report is now complete.

      The good news is that the rewrite only occupied one developer for past last year. While he worked tirelessly to bring users a better voice experience, our other developers have been making significant feature upgrades to their components. I am going to take some time to highlight those major developments later in this post.

      Why haven't you posted development updates over the past year?

      To answer this question, we need to address two major issues in the flight simulation community: the hype train mentality and the copying problem.

      1. The hype train mentality. A very common tendency in the flight simulation community is to over-hype a product. Some developers do this on purpose by dropping little nuggets of information or photos on social media regarding a new and exciting product they are working on in order to build hype, then one of two things happens; either the product never gets released (it was vaporware all along) or the product is released, but does not live up to the hype. This community loves to ride the hype train and it is not something that the POSCON team thinks is a professional approach to software development and marketing. We don't want to build up hype around a product that doesn't live up to expectations. We feel it is better to stay quiet and develop rather than to make promises we cannot keep.
      2. The copying problem. No, I am not referring to the people who like to pirate software (and yes, that is a problem too). What I am referring to the issue of other developers/networks (you know who you are) taking our great ideas and benefiting from them. This is something Robert Randazzo of PMDG actually brought up in his recent interview with Jeff Turner over at Sky Blue Radio in regards to Global Flight Operations. I couldn't agree more. Competition is a great thing, but competition means being innovative and developing new ideas.

      Anyway, enough of my rant. . . but those are the main reasons we are careful not to provide too many details about what we are working on now.

      Okay, so what are you willing to share?

      First, I think it is important to point out that all recent updates to our software can be found in the changelogs which are located on the POSCON HQ. I certainly have no intention of covering everything that has changed over the past last year, so I encourage all users to browse through the logs if you are interested in learning more.

      Having said that, there are some main points I want to cover in this blog post.

      Let's first talk about the voice software, since this is what has been the major barrier to our forward progress. The voice software is now using a new protocol which will prevent a lot of the issues that users were experiencing with the previous iteration such as issues with wireless headsets, sample rates, garbling, etc. In addition to changing the protocol, we moved all the voice settings (push-to-talk, audio device selection, volume control, etc.) from the Radar Client and Pilot Clients into the Launcher Client in order to centralize these settings. This means that users will now only need to modify the voice settings once for all POSCON clients. This integration of the voice software into the Launcher Client enables us to expand the capabilities of the voice software in the future to perhaps support web-based pilot and ATC clients. You can find all the new voice settings by clicking cog wheel in the bottom right-hand corner of the Launcher Client:

      Screenshot_5.png.233b7bd6159573869caec8565bfaa21a.png

      Here are the new settings that you will see after clicking on the cog wheel:

      image.png.24cf5c391f784324358d73faaa88b80d.png

      Under the "Volume Controls" setting, we now allow users to control squelch which adds an extra layer of realism to the VHF simulation. You can adjust the squelch by moving the slider left (lower) and right (higher).

      Screenshot_7.png.4b948da02750b6cd27ec1ad89a64ad62.png

      The Launcher Client also incorporates a new voice status icon located in the upper right-hand corner of application which gives users an indication of the microphone and the radio configuration. Here are the different states:

      "No Radio" - Red Mic Icon
      You are not connected to POSCON (or the voice server) or your airplane radios are not powered (perhaps your avionics are turned off).
      image.png.14922fcee062490205836485f1163ec2.png 

      "Radio Ready" - White Mic Icon
      Your radios are configured correctly, but you are not currently transmitting.
      image.png.6fc970f4668d91b15aae646e93e6f588.png

      "Transmitting" - Green Mic Icon
      You are transmitting and listening on a frequency.
      image.png.80bd29a673f8a009740e97191396653e.png

      "No Reception" - Yellow Mic Icon
      Your radios are set up to transmit, but not to listen.
      image.png.85572bc011d5741ec7b7db75230a3243.png

      image.png.72490d8c38a6ad7ebc85c24ae3ed29e7.png (push-to-talk button/key pressed)

      "No Transmission" - Yellow Mic Icon
      Your radios are set up to listen, but not to transmit. This can happen when you are in Ghost mode or if you don't have your radios configured to transmit on a frequency.
      image.png.ea5a031f16b4b0efe8a6af70a4905828.png

      image.png.b0d7aa827616c5a21b3f0d6499f60fd9.png (push-to-talk button/key pressed)

      In all cases, remember you can use the Pilot Client Web UI ("RADIOS" page) to get better insight into what is happening with the configuration of your radios.

      Other changes to the voice software include:

      • Upgrades to the radio-frequency physical model which helps to better simulate real-world radio interference
      • Antenna position now varies by aircraft type and thus improves ground effects near the airport surface
      • Server-side memory optimization and multi-threading
      • New stuck-mic protection (35 second timer, then mic cuts out)

      The Launcher Client itself has been re-versioned to 1.0.0 and is officially out of beta testing. We upgraded it to the latest dot NET framework and changed the cloud location where it downloads client software from. The long term goal (version 2.0.0) for the Launcher Client is something we are referring to as the "Unified Launcher Client". The Unified Launcher Client will integrate the SimConnect (FSX/P3D/MSFS) Pilot Client, voice software, and authentication all into the same code-base so that multiple applications need not be opened simultaneously to run POSCON.

      One important user-experience note about the new Launcher Client (version 1.0.0) is that when you click the "X" in the top right-hand corner, it will now minimize the Launcher Client to the system tray. In order to completely quit the Launcher Client, you must right-click on the icon in the system tray to quit.

      image.png.c58a5b1661dac7f44a2b86e0781b2600.png

      The HQ has undergone a significant number of upgrades and improvements over the past year. . . far too many to mention here so I encourage you to go view the HQ specific changelog. Our most recent changes (i.e. in the past month or so) include the addition of a brand new Virtual Operators section. Virtual Operators are essentially organizations that are commonly referred to as "virtual airlines" in the community. These organizations can join POSCON and benefit from an integrated connection that will ensure members only fly with approved aircraft, callsigns, routes, and more!

      Also, the HQ development team has been slowly improving the ATC Division pages including a re-design of the Overview and Members pages to offer a better user experience to view information and activity in the division. Speaking of re-design, your User Profile has also been re-designed to offer a better user experience that compliments all your activity!

      The Radar Client has had many updates and improvements as well, please see the Radar Client specific Changelog for more details.

      The Pilot Clients and Radar Client have been stripped of all voice-related items. The software should still work normally, but the voice now is handled by the Launcher Client.

      Wow, that's amazing stuff, but how do you plan on attracting more users?

      Sorry, but this is a Technology blog! Can't answer that!

      In all seriousness, we will be sending out marketing materials soon. We plan on making 2022 a big year for POSCON and we want to thank those who have kept the faith throughout the years. Without you and your encouragement, this wouldn't have been worth it! 

      Happy Holidays to all!

      🎄🥳

×

Important Information

By using this site, you agree to our Terms of Use, Privacy Policy, and Guidelines.