Thanks everyone for the feedback. A number of these issues have now been resolved and we'll be posting an updated beta this afternoon, hoping for general release this weekend. The swiping gestures weren't purposefully removed, that was a bug.

The size of the runway end buttons is defined in inches and should be just right, unless you've set a DPI for your device which is not its actual DPI. By all means post screenshots of any such issues to give us some more insight.

Map rendering now happens in the background to keep the map responsive, and this will lead to a very slight slowdown. I suspect the slowness you're seeing is much larger, though, and is because in the current beta we still had one important optimization left to turn on. This has now been done, so in this afternoon's beta you should see a speed improvement.

We may add selection of a specific circuit direction in a future release if lots of people are after that feature.

Hi Tim,

2.3 Beta 23/2/2012

Are you sure you haven't included a wet hire rate in the aircraft properties? If so, then fuel usage won't affect the price, only the time of the flight. I can't reproduce what you're seeing.

Regarding the size of the circuit depiction, SkyDemon only draws it if there's enough room. If you're zoomed right out to look at a long runway then there may well not be enough room to draw a circuit around a small runway.

I quite like the way the garmin 296/496 series depicts runway circuits with a left/right arrow at end of runway. Less cluttered (& less clutter is a SD hallmark). Current SD depiction is rather clunky.

But the feature to select runway in use is great . . I wd like to be able to specify L/R (or take from approach plate with ability to override somehow).

D

I'm not familiar with the way Garmin do it. We don't attempt to draw circuits to scale at all; I'm sure they'd be unflyable if you were to actually attempt it. However when you're zoomed out such that the length of the smaller runway is only an inch long, then by the time we've drawn the line with the arrows on it would just be a mess (we did lots of experimentation when designing the feature). Perhaps you could illustrate with a screenshot of when you think we should be drawing but we aren't?

Hi Tim,