Transition to CloudAhoy 3

The Beta stage of CloudAhoy 3 is coming to its successful close, and we are getting ready to switch everybody to use CloudAhoy 3.

If you are still using CloudAhoy 2, expect to be switched automatically to 3 starting next week.  Of course, you don’t have to wait – you are welcome to switch to  3.0-beta immediately!

At this point we are unaware of  problems with 3.0-beta: neither missing features nor bugs. If there’s anything that does not work like you’d expect, please let us know ASAP.  The option to switch back to 2.x will be available for a little longer as a safety net.

Check out the new 3 features:

  • Greatly enhanced flight sharing capabilities.

  • Everything you can on the web’s CloudAhoy you can now do in the CloudAhoy app, except for 3D (the iOS app only supports 2D).

A Huge Thank You, dear 3.0-beta users who have sent us problem reports!   All the problems have been fixed, and we highly appreciate your help.

As alway, any feedback is most welcome and highly appreciated, either by sending an email to dev@cloudwhoy.com or by posting in the Forum.

Screen Shot 2013-09-02 at 3.34.21 PM

 

 

2 comments on “Transition to CloudAhoy 3

  1. Big fan of Cloud Ahoy, and have been using it throughout my IFR training. I have a few suggested enhancements (for your next big release?)
    1) add the ability to pop up a cockpit instrument window. As I debrief an instrument approach, hold, unusual attitude work, etc, it would be helpful to see the steam gauges I saw while flying. Even better would be the LOC/GS needles, but that would be more of a challenge.
    2) add some sliders to the playback box to allow the user to zoom in on a particular segment. This would be quicker and easier that having to create a custom flight segment. Don’t get me wrong, custom flight segment is still a good feature, but there are plenty of times I just want to quickly zoom in and have a look at a short segment.
    3) save some screen real estate by relocating the NAV menu. I bet not too many people want to look up the actual lat/long.

  2. Hi Joe,

    Glad you like CloudAhoy!

    Thanks for your comments! Probably the single most important help for IFR debrief is the 3D published approach overlay.

    Debriefing instrument approaches is available in 3D from Windows or Macintosh machines, and in 2D on the iPad. You can add 2D/3D published approaches to a flight debrief by opening the “Procedures Used” bar and clicking add/mod. The caveat is that each approach needs to be entered once to CA’s database, to make it available to anyone using CA. If you need approaches which are not already in the system, then either I can enter them for you (I’d be delighted to do so, just tell me which), or you can do it yourself by using a special language (contact us for more information). If you define approaches yourself, please email me your first attempts. From experience, it helps a lot to have me review them and help fix beginner errors.

    Debriefing with 3D published approaches is useful both in picket mode, where you can see how well you maintained lateral position and altitude, and in cockpit view showing you an “approach in the sky”.

    Re your #1, I agree that it would be useful. Note however that different planes have different instrumentations, e.g., glass. But your point is well taken though and we’re thinking of ways to improve the numeric display that is currently available.

    Re your #2, simply clicking / tapping the segment zooms on it. In 3D mode you can also use the 5 controls at the upper-right to quickly rotate the point of view.

    Re your #3, you can always close any panel that you don’t need, including NAV, by clicking / tapping on it. But actually you may find NAV useful – click/tap “Define Target #1” and type the name of the VOR or LOC used for the approach. It will display numerically the aircraft’s location relative to it. Clicking on “On” or “+10000” will display a vector from the aircraft to the nav aid.

    Best,
    Chuck

Leave a Reply

Name and email are required. Your email address will not be published.