![]() |
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
![]()
On Mar 23, 7:01 pm, Greg Arnold wrote:
Doug Haluza wrote: On Mar 20, 5:53 am, "Doug Haluza" wrote: You should always use the latest version of your software. As problems are discovered, the vendors make updates, and there is no sense having problems that are already solved. SeeYou is also testing a beta version to deal with a strange data transmission issue with the new OLC interface where "+" signs get corrupted in transmission, causing validation to fail. This affects C302+ users, but could also randomly affect anyone if there is a "+" sign in the digital signature. SeeYou just released version 3.65 today, presumably with the fix for the C302 OLC upload from the beta version. Be sure to download it if you are a SeeYou user with current upgrade support. The web site shows this as V3.62 on the download page, but will show v3.65 when you install it. Doug Haluza SSA-OLC Admin SeeYou still appears to be doing the OLC optimization different from the OLC software. For purposes of the 1000 meter rule between the start and end of the flight, OLC appears to take the height between the start and end of the scored flight, while SeeYou appears to take it between release from tow and the end of scored flight. Most of the time, this doesn't matter. However, it does matter under the right conditions. I had a flight about a month ago (February 16) where the OLC score (direct upload) was more than 20 points less than the SeeYou optimization. And today, the OLC score (direct upload) was slightly higher than the SeeYou optimization. Neither software appears to be consistent with the OLC rules: The minimal finish altitude is 1000 metre below the start altitude. The start altitude the lowest altitude after the begin of free flight and before reaching the start point. The start time is the time at which the start altitude is reached. The finish altitude is the highest altitude after reaching the finish point and before end of free flight. The finish time is the time at which the finish altitude is reached after the finish point is reached. Where the OLC and SeeYou programs differ, I believe the "more correct" score will be whichever is the higher. But it appears that both softwares can give a score that is lower than what the OLC rules require -- this will happen if the 1000 meter rule affects the result, and if there is a point after release from tow and prior to start that is lower than both tow release and start height (or if there is a point after finish that is above the finish height).- Hide quoted text - - Show quoted text - Below is a link to my flight on Saturday. I flew for over 4 hours, but my OLC scorable time was around 14 minutes. I'm pretty sure I know what caused it (me messing with the iPAQ) to cut off, but I don't have any software to analyze what it did to the .igc file in the Cambridge 302A datalogger. The entire 4 hour flight is shown, just not scored. My flight on Sunday had no issues, so I know it's not an OLC issue, it's an operator/user interface problem. Also, where can I find a "legend" for the graph that appears below the flight trace? I see some bits of yellow here and there. http://www.onlinecontest.org/olc-2.0...Id=-2034543116 Thanks for any help! |
#2
|
|||
|
|||
![]() Below is a link to my flight on Saturday. I flew for over 4 hours, but my OLC scorable time was around 14 minutes. I'm pretty sure I know what caused it (me messing with the iPAQ) to cut off, but I don't have any software to analyze what it did to the .igc file in the Cambridge 302A datalogger. The entire 4 hour flight is shown, just not scored. My flight on Sunday had no issues, so I know it's not an OLC issue, it's an operator/user interface problem. Also, where can I find a "legend" for the graph that appears below the flight trace? I see some bits of yellow here and there. http://www.onlinecontest.org/olc-2.0...Id=-2034543116 Thanks for any help! You did the direct upload to OLC? The OLC software guessed wrong about the end of your flight. You need to click Edit Flight, then change the ending time on the screen that comes up. |
#3
|
|||
|
|||
![]()
On Mar 26, 9:52 am, Greg Arnold wrote:
Below is a link to my flight on Saturday. I flew for over 4 hours, but my OLC scorable time was around 14 minutes. I'm pretty sure I know what caused it (me messing with the iPAQ) to cut off, but I don't have any software to analyze what it did to the .igc file in the Cambridge 302A datalogger. The entire 4 hour flight is shown, just not scored. My flight on Sunday had no issues, so I know it's not an OLC issue, it's an operator/user interface problem. Also, where can I find a "legend" for the graph that appears below the flight trace? I see some bits of yellow here and there. http://www.onlinecontest.org/olc-2.0....html?flightId... Thanks for any help! You did the direct upload to OLC? The OLC software guessed wrong about the end of your flight. You need to click Edit Flight, then change the ending time on the screen that comes up.- Hide quoted text - - Show quoted text - That was it!! I knew it cut my flight off, I DIDN'T know I could change it so easily! Thanks. Also, thanks for the info about the yellow on the graph. |
#4
|
|||
|
|||
![]() Below is a link to my flight on Saturday. I flew for over 4 hours, but my OLC scorable time was around 14 minutes. I'm pretty sure I know what caused it (me messing with the iPAQ) to cut off, but I don't have any software to analyze what it did to the .igc file in the Cambridge 302A datalogger. The entire 4 hour flight is shown, just not scored. My flight on Sunday had no issues, so I know it's not an OLC issue, it's an operator/user interface problem. Also, where can I find a "legend" for the graph that appears below the flight trace? I see some bits of yellow here and there. http://www.onlinecontest.org/olc-2.0...Id=-2034543116 Thanks for any help! The green is the terrain, and the yellow is the noise recorded by the ENL sensor. |
#5
|
|||
|
|||
![]()
One thing I miss in the new OLC is the map details. The only waypoint
now is the takeoff airport. What happened to all the waypoints? It is very hard to figure where and how far one flew from looking at the map. Any chance we can have the waypoints back? Ramy |
#6
|
|||
|
|||
![]()
On Apr 1, 1:48?am, "Ramy" wrote:
One thing I miss in the new OLC is the map details. The only waypoint now is the takeoff airport. What happened to all the waypoints? It is very hard to figure where and how far one flew from looking at the map. Any chance we can have the waypoints back? Ramy Waypoints???? Hell, I'd be happy if they'd just figure out how to get my WinPilot flights posted! It's only been since February. In the last week my flights have gone from a yellow V to a red V for no apparent reason.... Bill |
|
Thread Tools | |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Broken P lead? | Jim Burns | Piloting | 16 | October 27th 06 08:06 PM |
surviving a broken wing | Kyler Laird | General Aviation | 0 | August 3rd 06 04:31 PM |
Broken window in jet plane | Eduardo K. | Piloting | 17 | April 13th 06 10:19 PM |
Broken wing | Stubby | Piloting | 27 | January 1st 06 03:04 AM |
Looking for broken Garmin | Larry Goddard | Soaring | 3 | July 5th 04 12:46 PM |