Route disappears when moving on map

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create OsmDroid MapView
2. Create two Geopoints and calculate a route
3. Display route on MapView
4. Move Map or zoom in on route and move on map

What is the expected output? What do you see instead?
Route stays always visible.
Route disappears sometimes

What version of the product are you using?
osmbonuspack v3.1
osmdroid v3.0.8

Please provide any additional information below.
When I move on the map or zoom in on the map to see the route, the route 
disappears. What can I do to let the route always stay visible?
For examples, see attached files.

Thanks in advance.
Greetings

Original issue reported on code.google.com by fbo%huma...@gtempaccount.com on 10 Jan 2013 at 4:29

• Merged into: #68

Attachments:

• 01_route_visible.png
• 02_route_invisible.png
• 03_route_active.png
• 04_route_invisible.png

[GoogleCodeExporter]

I never got this behaviour on the demo app. 
Is it using the demo app, or following exactly the tutorial, or using your 
specific code? 
In last case, can you provide code?
What are version of the Android SDK and AVD?

Original comment by mathieu....@gmail.com on 14 Jan 2013 at 11:25

[GoogleCodeExporter]

Have you got an "shape path too large exception" ?
Try disabling hardware acceleration :
mMapView.setLayerType(View.LAYER_TYPE_SOFTWARE, null);

Original comment by jerome.m...@gmail.com on 24 Jan 2013 at 9:29

[GoogleCodeExporter]

Thanx, jerome!
Your workaround solved the large pathes' problems for me. Unfortunately, the UX 
became a bit worse and this method only works on android 3+ :-(

Original comment by riwnoden...@gmail.com on 26 Feb 2013 at 2:40

[GoogleCodeExporter]

Does it possible to work with RoadOverlay without disabling hardware 
acceleration ? In my app, routes disappear sometimes and cause crash at higher 
level zoom. With hardware acceleration disabling, everything is ok, but the map 
isn't smooth. Any fix/hack possible ?

Thanks in advance.

Original comment by vinc...@djmweb.be on 13 Mar 2014 at 4:11

[GoogleCodeExporter]

Same issue than Issue 68. 

2 workarounds: 

- Either target SDK < 3 (meaning no HW acceleration)

- Or if SDK >= 3 is needed, explicitely disable HW acceleration. The best way 
to do that is: mMapView.setLayerType(View.LAYER_TYPE_SOFTWARE, null);
(as it only disable HW acceleration for the mapview, and for nothing else)

Original comment by mathieu....@gmail.com on 25 Jul 2014 at 4:22

• Changed state: Duplicate