Skyview 17.4 bug?

kurtfly

I love flying!
Joined
Jun 21, 2014
Messages
321
I noticed today that my “Next Wpt” data block is always showing ————-. This used to work. What am i missing? Is this a new feature of 17.4?
It is also missing on the HSI IFD540 data block.

IMG_1441.png
 
Last edited:
Mine is doing the same thing. I just got my HDX back from Dynon after a repair and they updated it to 17.4. Now the Next Wpt is shown as ----- but the distance and ETE to waypoint are correct (IFD-440)
 
Good question. Is your next waypoint the destination? Maybe it doesn't show that if there's not another intermediate waypoint?
 
Is your next waypoint the destination? Maybe it doesn't show that if there's not another intermediate waypoint?

I thought the same thing, but DTW and DIST TO GO are not the same value, indicating that there is indeed another waypoint between the plane and the destination?

If I recall, NEXT WPT should be showing the name/designator of the waypoint, not a calculated value, correct?
 
Yes it should be showing the name of the waypoint.
I sent an email to Dynon on this as it appears to be a bug in the latest version.

kurt
 
I have the same issue. Just updated today and the Next Wpt is blank no matter what I put in for a flight plan. My Garmin 650 screen that the data is coming from is perfectly fine.
 
And, i had put in and flown an approach and it put the hold waypoint for the missed approach as the final destination. Pretty sure that shouldn't be there until after you've gone missed.
 
Crickets from Dynon on this issue. Hmmm...
They ran out of bullfrogs.

I would imagine they're looking into it. They probably figure there's not much point in commenting until they have something to report.
 
They ran out of bullfrogs.

I would imagine they're looking into it. They probably figure there's not much point in commenting until they have something to report.
Right. they probably imagine that we imagine they are looking into it. 😆
 
Or they imagine that some of us are engaged in conspiracy theories.
 
Or they imagine that some of us are engaged in conspiracy theories.
nope. just irresponsible non-response in dealing with this issue. after this much time since these events they can't at least say they are looking into this?
 
An ack, yo we know, wink & nudge, a grail signal, white smoke….. anything that could pass as a true response from a company we all have some serious $$$$ invested in, not to mention our lives that fly behind their gear would ”transparent “ and appreciated.
 
You should have that knee looked at. It's jerking really bad. Could be serious.
 
Last edited:
An ack, yo we know, wink & nudge, a grail signal, white smoke….. anything that could pass as a true response from a company we all have some serious $$$$ invested in, not to mention our lives that fly behind their gear would ”transparent “ and appreciated.
My guess is they do not want to admit there's a screw up in their software for fear of litigation, in case there was an accident and someone blamed them because of this bug. Although this is a pretty minor bug, you'd still think they would admit it and notify users, which you could argue would lower the risk of a lawsuit.
 
New software releases that are bug free are almost unheard of, so there's pretty much zero chance of a liability issue. You're being paranoid. We get it. You hate Dynon and only come here to malign them. Please give it a rest. This one of the few forums on the internet that has some decent decorum. Don't ruin it for everyone.
 
New software releases that are bug free are almost unheard of, so there's pretty much zero chance of a liability issue. You're being paranoid. We get it. You hate Dynon and only come here to malign them. Please give it a rest. This one of the few forums on the internet that has some decent decorum. Don't ruin it for everyone.
 
You're full of crap rhino. I like Dynon and I like the Skyview system that I purchased, but I also like corporate responsibility. You apparently don't give a damn about that.
 
New software releases that are bug free are almost unheard of, so there's pretty much zero chance of a liability issue. You're being paranoid. We get it. You hate Dynon and only come here to malign them. Please give it a rest. This one of the few forums on the internet that has some decent decorum. Don't ruin it for everyone.
Yeah you're right. We should all be perfectly satisfied with Dynan's silence on this software problem. Also, I'm not "paranoid" about anything. I was just curious as to why Dynon was taking so long to address this issue. I'm giving them a pass on this due to the holidays and this not being a critical error in latest HDX release.
 
Last edited:
Back
Top