mapbox / mapbox/mapbox-maps-android
Unexpected Camera Jump in 3D Mode When Interacting with Mountain Areas
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 578
- Forks
- 161
- PR merge metrics
- No merged PRs in 30d
Description
## Environment
- Android OS version: any
- Devices affected: any
- Maps SDK Version: 11.11
```
val DEM_SOURCE = "mapbox-dem"
val TERRAIN_URL_TILE_RESOURCE = "mapbox://mapbox.mapbox-terrain-dem-v1"
mapView.mapboxMap.addOnRotateListener(this)
it.addSource(rasterDemSource(DEM_SOURCE) {
url(TERRAIN_URL_TILE_RESOURCE)
tileSize(514)
})
it.setTerrain(terrain(DEM_SOURCE) {
exaggeration(1.0)
})
```
## Observed behavior and steps to reproduce
When 3D mode is enabled, I’ve noticed that the camera exhibits a strange jump the first time I touch near mountain regions (this appears to affect almost all mountains). It looks as if the camera's altitude is changing, even though the zoom level remains constant. However, after removing my finger from the screen and touching it again, the issue seems to resolve temporarily.
Is this a known issue? Are there any recommended workarounds or fixes?
Additional details:
Steps to Reproduce:
Enable 3D mode.
Interact with mountain regions on the map (touch on mobile or equivalent interaction).
Observe the unexpected jump in the camera view.
## Expected behavior
camera stable like i move the second times
## Notes / preliminary analysis
## Additional links and references
https://drive.google.com/file/d/15sDB_KQSRpvQr9JTRj5x4F2XW0rAfKtv/view?usp=drive_link
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with the shown mapView.mapboxMap rotation listener, DEM source, terrain setup, and 3D mode on Android. Compare the first touch on mountain areas with subsequent touches and use the linked recording for expected behavior; done means the camera remains stable during the initial interaction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100