Public transport routing doesn't work in OpenGL rendering

HamousOnWheels commented 3 weeks ago

Description

If rendering engine v2 is enabled, public transport routing consistently doesn't work. Switching back to v1 and restarting the app makes it work again. Only realized recently since i didn't need it often lately, but i believe it's been broken every time i've tried it this year. Maybe my phone or android version is too old to support the opengl engine?

Steps to reproduce

Enable map rendering engine version 2 in settings (enabled by default since some time afaik)
try public transport navigation to any point regardless of distance

Actual result

"Unfortunately, Osmand could not find a route suitable for your settings."

Changing any routing settings such as "number of changes" does nothing. The only thing that restores routing is changing the rendering engine back to version 1 and force quitting the app.

Expected result

Routing works as it always has

Your Environment (required)

OsmAnd Version: osmand~ 4.8.6
Android version: 11
Device model: motorola moto g8 power
Crash-Logs: no crashes

yuriiurshuliak commented 3 weeks ago

The bug was not reproduced. To test, select OpenGL rendering and a public transport profile, then try to build point-to-point navigation.

The navigation will be built correctly, showing options with walking times and public transport routes, including route information such as time, distance, transfers, and public routes.

For more detailed information, you can refer to our documentation: Public Transport Navigation

OsmAnd~ 4.9.0#3148m, released: 2024-09-09

https://github.com/user-attachments/assets/853d7abf-0ec9-49fe-9133-d8d1e68ad21c

DmitryAlexei commented 2 weeks ago

@HamousOnWheels Please try to increase the number of intersections in the Public transport navigation settings Moreover, make sure that transport routes in your location are mapped with Public Transport Version 2 (PTv2) scheme

If this doesn't work, please provide the start and end points of your routes. We will try to reproduce your issue

HamousOnWheels commented 2 weeks ago

Increasing the number of intersections doesn't help. Here are my navigation settings:

I don't know how to check the public transport version. The area is Belgrade, Serbia. A route for example could be here to here (apologies if this isn't the proper way to share routes)

Other things i've tried:

tested with a few other European cities (Prague, Berlin, Riga)
disabling all plugins. The plugins i have enabled are online maps and OSM editing, if it matters.
wiping and reinstalling 4.8.6
installing 4.9.0 beta

I need to repeat it's crucial to force stop the app between changing rendering modes, since immediately after change navigation will still work, until the point the os itself kills the app.

HamousOnWheels commented 2 weeks ago

Update: after some more testing, i got it to work under following steps:

start the app in opengl mode, under public transport profile by default. Try to calculate a route. Navigation doesn't work.
switch to a driving or cycling profile. Route is calculated normally.
switch back to public transport. Route is calculated as expected.
after these steps, every subseqent public transport route calculation works normally.
after the app is restarted, public transport is back to not working until the profile shuffle is done again.

Confusing to say the least! This is still version 4.8.6 to be clear.

contrapunctus-1 commented 2 weeks ago

A number of Indian users have also faced this issue. I haven't tried the rendering engine workaround, but I've often (successfully) used the switching-navigation-profile workaround.

To add another example, try navigating by bus from Vijaylakshmi Apartment geo:28.62896,77.30901?z=21 to Mandi House geo:28.62550,77.23391?z=20

TobiPeterG commented 3 days ago

I thought I had this issue, but increasing the number of maximum changes fixed it for me. I don't need to switch profiles etc., I live in Germany.

Why does the setting for maximum changes even exist?

osmandapp / OsmAnd