JPSMAN

I just upgraded to Navi V3.6 (Orange) for a 2004 TL. Previously I had V3.3. On this version, Interstate 66 within the DC beltway isn't mapped (or only exists as a line on the map but isn't recognized when driving or planning a route). This was not the case on the 3 year old version I was previously using.

How does a major road in a metropolitan area all of a sudden disappear from the mapping database when previously included in older versions?

Has anyone else experienced this?

I will be returning this disc and also complaining to Alpine. I'll report back with anything interesting.

CobraGuy

You know, the database company that Acura uses just isn't that good. Pioneer uses a different company for theirs...and it's a whole lot better. I have both...and I'm not impressed with the company Acura uses. However, the nav system itself is outstanding!

funkymint

hey JPSMan, while you still have the DVD, can you check where 395s Meets 495 and see if they have all the new on-ramps there?

Juts curious..

EMF9

I have noticed very similar things. I have 3.50, although I was promised 3.6 from the dealership (they lied). I live near the Fairfax and Glebe exit of 66. No matter what the GPS will NEVER take me on the entrance to 66 (or 66 in general) and drives me all over the place to avoid it. Do you still have the disc?

-Eric

JPSMAN

I still have both discs; I'm planning on calling to get an explanation, but will probably just be told to report the error to navtec regardless. Its really bad, that stretch of I66 just doesn't exist anymore in the database. In fact, when driving, Nav thinks I'm on parallel roads or just starts dropping breadcrumbs right on top of the red interstate line.....its very odd. The other major roads seem fine.


In summary: if you live in the DC area, don't buy the V3.6 update.

EMF9

It's completely missing? I actually have been on the phone with them several times trying to figure out what is wrong with it. They claim it is because I-66 is an HOV route. Personally I think it is BS since it uses parts of 66 which are also HOV. From my address to another address in MD it fails to actually pick a reasonable route. From the same address in MD it actually takes the correct path back... so I think they just screwed up the map.

EMF9

JPSMAN: Can you email me efaden@gmail.com? I want to ask you a few questions off-line, but can't PM yet.

Dave04TL

If anyone finds a fix for this problem - Please post. I am about to return 3.6 and go back all the way to 3.3G.

cjt2005TL

I experienced the exact same problem w/ version 3.6. It also doesn't recognize VA 267 (Dulles Toll Road) inside the beltway. I had no problems with my previous version 3.4. In addition, neither version recognizes Rock Creek Parkway in the District, but I can at least deal with that. As far as I-66/VA 267 is concerned, it's hard to get around NoVA, especially North Arlington, without those two roads in the database.

If their excuse is that I-66 is HOV, that's bull because I-66 has been HOV for over 20 years, and it wasn't a problem with version 3.4.

I returned 3.6 for a refund, and went back to 3.4 with no problems.