Well then I guess we have 2 users who have magical RTL's then since everyone else in the thread has noticed degradation.. Maybe I'll keep having Garmin send me replacements until I get a magical unit as well.. :p
And no I'm sorry but using Apple and Google maps and trying to say the results were accurate is kind of laughable but to each their own I suppose..
I'm not disputing your findings I am just saying the method and tools uses could be better..
This thread is going in circles now so I guess I am out. We can go round and round till the next update (and hope it solves the issues for the masses) but why bother? We are all going to keep saying the same thing over and over. The people with problems will keep saying there is a problem and the 2 who don't see issue will keep stating that...
In my mind, testing and real world usage ---> 3.4 is one of the worst updates in Garmin history (cycling computers included)..
You keep saying only two people are happy but isn't that perfectly normal for the internet, happy users have no reason to post on this thread or even know of it's existance.
And as for "one of the worst updates in Garmin history", you can't have been using Garmin products for long.
Been using Garmin products for 10-years and YES this is one of the worse updates in their history! They took a product that was perfectly fine (for me on 3.0 it is) and destroyed it.. This is NOT a bug this update is a safety hazard...
Sure the ole' happy people don't post routine huh? Well okay... I guess if you say so..
And like I said we all just keep going round and round with NO input from Garmin or new ideas and / or thoughts on the matter so this thread has ran it's course for me.. Garmin says my unit is defective and they want to replace it.. LOLOLOL
They never answered as to why it's NOT defective on 3.0 but what the heck.. I'll let them replace it and replace it and replace it. I guess if they want to keep sending me new units until the next update come out then so be it...
I would think firmware that caused the Edge 810 to crash at roundabouts would be worse, but have it your own way.
One unhappy user posting lots of words on an internet forum doesn't mean everyone's unhappy.
One unhappy user? LOL Read the thread, there at least 4 I believe who have said they are unhappy or wanted to go back to version 3.0.. Also, I dd not start this thread so how can I be the only one? LOL
At any rate, now you are playing games and making things up to try and discredit people so I won't respond to you again.. Have a nice day or evening depending on your location in the world....
And no I'm sorry but using Apple and Google maps and trying to say the results were accurate is kind of laughable but to each their own I suppose..
I'm not disputing your findings I am just saying the method and tools uses could be better..
You may have overlooked reading in my previous post (directly above yours) where I indicated that I verified the Apple and Google Maps distances using a rollout test:
Rollout* - 508 feet
So if it's "each to their own", my data is verified and supports the conclusion that the detection distance of fw ver 3.40 is 500 feet or greater; as contrasted to anecdotes.
Your data is verified by what? I would not say the tools you used count as verified..... I used a certified digital roller tape that the city uses for mapping... The tool I used makes the tools you used look primitive..
Now let's look at the "data" you provided:
First Location: - number of vehicles - 20 - Google Maps - 525 feet - Apple Maps - 500 feet
Second Location: - number of vehicles - 25 - Google Maps - 550 feet - Apple Maps - 525 feet
Are you saying that all 20 vehicles @ the 1st location registered at the same exact distance? And are you saying that all 25 vehicles @ the 2nd location registered at the exact same distance? Multiple vehicle detection included as well in this lump data? If so then this will discredit the testing you did even more as detection distance is effected by the size and shape of the vehicle. More, or less, mass effects the detection distance. Or are you saying that a motorcycle or small smart car will be detected at the same distance as a bus?
Additionally: What was used as visual markers for the distance? It's hard to see the point a moving car crosses at that distance and even more so at varying distances. I used tall bright orange cones and even then it was hard..
I mean come on now.. You are trying to throw out that your data is accurate and verified when it is anything but that.. Your testing was primitive, the tools used were lacking and the lump data you provided is vague at best..
I guess we will just have to agree to disagree...
Garmin is sending me a replacement so when it arrives I'll try 3.4 on it. If it behaves the same then it will go back for another replacement. Rinse, lather, rinse, and repeat.. Hopefully for their replacement team, the next update comes soon as I think I will have a revolving door of units coming and going..
And like I said previously, they still refuse to answer the question as to why my until is only defective when 3.4 is put on it..
You keep saying only two people are happy but isn't that perfectly normal for the internet, happy users have no reason to post on this thread or even know of it's existance.
And as for "one of the worst updates in Garmin history", you can't have been using Garmin products for long.
Your point is well taken and has bothered me as well. One poster stated that 4 are critical of V3.4 but only 2 openly stated degraded performance but I will give the other two the benefit of a doubt. If V3.4 is the worst ever update why have not more people come forward to express their misgivings. This thread has had over 1200 views and on another thread no mention of detection issues. My many years of participating in computer and bike forums it is the individuals with issues that come forward looking for help or stating dissatisfaction.
This thread has had over 1200 views. If V3.4 is the worst ever update why have not more people come forward to express their misgivings
Or to put it another way:
"This thread has had over 1200 views" so why are more people not jumping in to verify that 3.4 is the greatest update in the history of updates?
LOL
Guess we will see when my replacement comes. Who knows maybe my unit (and the others voicing dissatisfaction) is only defective on 3.4.. If that's the case I will certainly post that fact here. If it's not the case and the replacement acts in the same manner then it will go back for another and the process will be repeated until I either get a magical unit or the firmware is fixed, whichever comes 1st.. :D
