WinPilot PRO Questions

I've been flying WinPilot PRO V12 in Condor for a while now, and I'm trying to make sense of its ETE (ETE To Final Destination) NavBox parameter. I have 'Time Left' and ETE displayed on the map screen, and one would think that the difference between these two numbers would equal the time differential number shown in the chevron area. My experience so far is that sometimes it does, and sometimes it doesn't. Anyone know how the ETE number is computed?

On another issue, I screwed up yet again on a TAT and forgot to hit the 'Next WP' button at the turn in a circle, and didn't notice the omission until I was outside that circle and on the way to the next. Clicking on 'Next WP' at this point causes WP to put the mobile turnpoint at my current location, rather than back where I turned, and of course this completely screws up all the timing and speed information. Anyone have a good idea how to recover from this situation (besides getting a better pilot)?

Anyone had any luck getting Jerry to respond to bug reports and/or feature requests?

TIA,

Frank

On Monday, January 14, 2013 11:42:18 PM UTC, wrote:
I've been flying WinPilot PRO V12 in Condor for a while now, and I'm trying to make sense of its ETE (ETE To Final Destination) NavBox parameter. I have 'Time Left' and ETE displayed on the map screen, and one would think that the difference between these two numbers would equal the time differential number shown in the chevron area. My experience so far is that sometimes it does, and sometimes it doesn't. Anyone know how the ETE number is computed?



On another issue, I screwed up yet again on a TAT and forgot to hit the 'Next WP' button at the turn in a circle, and didn't notice the omission until I was outside that circle and on the way to the next. Clicking on 'Next WP' at this point causes WP to put the mobile turnpoint at my current location, rather than back where I turned, and of course this completely screws up all the timing and speed information. Anyone have a good idea how to recover from this situation (besides getting a better pilot)?



Anyone had any luck getting Jerry to respond to bug reports and/or feature requests?



TIA,



Frank

Have you tried communicating via the Facebook page?

On Monday, January 14, 2013 5:42:18 PM UTC-6, wrote:
I've been flying WinPilot PRO V12 in Condor for a while now, and I'm trying to make sense of its ETE (ETE To Final Destination) NavBox parameter. I have 'Time Left' and ETE displayed on the map screen, and one would think that the difference between these two numbers would equal the time differential number shown in the chevron area. My experience so far is that sometimes it does, and sometimes it doesn't. Anyone know how the ETE number is computed?



On another issue, I screwed up yet again on a TAT and forgot to hit the 'Next WP' button at the turn in a circle, and didn't notice the omission until I was outside that circle and on the way to the next. Clicking on 'Next WP' at this point causes WP to put the mobile turnpoint at my current location, rather than back where I turned, and of course this completely screws up all the timing and speed information. Anyone have a good idea how to recover from this situation (besides getting a better pilot)?



Anyone had any luck getting Jerry to respond to bug reports and/or feature requests?



TIA,



Frank

Frank,
Let me add to your squawk-sheet:
After changing to the Vertica/Avier device, the Task Manager in WinPilot Pro doesn't allow me to create/edit the task anymore, this was a very useful feature. Changing the zoom level with the IPAQ hard button is no longer an option and it takes now multiple clicks to do that. Finally, the 4 hard buttons on the IPAQ were really helpful for assigning often used functions. They are still available in the Menu but it takes now more clicks to get there. Jerzy could easily display those buttons at the bottom of the map view, I believe. I have written to Jerry but he only responds to requests for passwords and to business transactions.
Herb

On Monday, January 14, 2013 3:42:18 PM UTC-8, wrote:
I've been flying WinPilot PRO V12 in Condor for a while now, and I'm trying to make sense of its ETE (ETE To Final Destination) NavBox parameter. I have 'Time Left' and ETE displayed on the map screen, and one would think that the difference between these two numbers would equal the time differential number shown in the chevron area. My experience so far is that sometimes it does, and sometimes it doesn't. Anyone know how the ETE number is computed?



On another issue, I screwed up yet again on a TAT and forgot to hit the 'Next WP' button at the turn in a circle, and didn't notice the omission until I was outside that circle and on the way to the next. Clicking on 'Next WP' at this point causes WP to put the mobile turnpoint at my current location, rather than back where I turned, and of course this completely screws up all the timing and speed information. Anyone have a good idea how to recover from this situation (besides getting a better pilot)?



Anyone had any luck getting Jerry to respond to bug reports and/or feature requests?



TIA,



Frank

Unfortunately, he has abandon the Windows CE/Mobil versions for the IOS version. Unfortunately the IOS version does not have access to instrument data, and so it hasn't really the same capability. I have communication from him confirming that no further work is expected on the Windows versions.

On Tuesday, January 15, 2013 10:34:06 AM UTC-8, jfitch wrote:
On Monday, January 14, 2013 3:42:18 PM UTC-8, wrote:

I've been flying WinPilot PRO V12 in Condor for a while now, and I'm trying to make sense of its ETE (ETE To Final Destination) NavBox parameter. I have 'Time Left' and ETE displayed on the map screen, and one would think that the difference between these two numbers would equal the time differential number shown in the chevron area. My experience so far is that sometimes it does, and sometimes it doesn't. Anyone know how the ETE number is computed?







On another issue, I screwed up yet again on a TAT and forgot to hit the 'Next WP' button at the turn in a circle, and didn't notice the omission until I was outside that circle and on the way to the next. Clicking on 'Next WP' at this point causes WP to put the mobile turnpoint at my current location, rather than back where I turned, and of course this completely screws up all the timing and speed information. Anyone have a good idea how to recover from this situation (besides getting a better pilot)?







Anyone had any luck getting Jerry to respond to bug reports and/or feature requests?







TIA,







Frank



Unfortunately, he has abandon the Windows CE/Mobil versions for the IOS version. Unfortunately the IOS version does not have access to instrument data, and so it hasn't really the same capability. I have communication from him confirming that no further work is expected on the Windows versions.

FWIW I was in the same boat a year ago. I had been using Winpilot since it's inception. At the time it was the only software, and was still the best option for nearly a decade, but slowly started lagging behind other software in functionality, bug fixes and support. I finally decided it was time to make the leap and upgraded my iPaq to a Dell Streak 5 and the software to XCSoar. It was well worth it. The cost is only $200-$300 for the hardware (software is free) although the most significant investment is time to read the manual, learn how to use it, understand it's quirks (like any other software) and configure it correctly to your liking (crucial).

Ramy

On Tuesday, January 15, 2013 9:06:49 PM UTC, Ramy wrote:

I finally decided it was time to make the leap and upgraded my iPaq to a Dell Streak 5 and the software to XCSoar. It was well worth it. The cost is only $200-$300 for the hardware (software is free) although the most significant investment is time to read the manual, learn how to use it, understand it's quirks (like any other software) and configure it correctly to your liking (crucial).


Just to avoid any possibility of confusion: XCSoar still supports Windows CE devices (including Pocket PCs such as iPAQs, navigators such as Mios etc), and the Windows CE releases of XCSoar are updated at the same time as the releases for other platforms, including Android. So there's no requirement to upgrade your current hardware to use XCSoar, and there are no plans for XCSoar to retire Windows CE support.

Between 2009 - 2011 XCSoar was extensively rewritten for version 6.0 - mainly by Max Kellermann and Tobias Bieniek - with portability between platforms in mind. Because of this, all releases of XCSoar are now compiled from the same set of code (codebase). Maintaining two dissimilar codebases is more time consuming than maintaining one codebase, which is why vendors dealing with that situation may have to make tough decisions about continuing support for the Windows CE versions of their programs.