[Bug] Weird behavior when loading/in transition

[christaikobo]

Describe the bug

Video_2026-03-16_103914.mp4

A couple of weird things here:

1. At the beginning, clicking on disable terrain does not work, terrain is still shown. Sometimes after a while, enable terrain and then disable works, sometimes that button is straight up bugged and does not work at all.
2. Clicking on some place to zoom, I was automatically forced to zoom out around 20s.
3. As you can see around 18s, even with 2D view, buildings are still shown. The view angle makes me believe that it has been successfully switched to 2D mode, because default 3D is a tilted 45 degree angle.

2nd video:

Video_2026-03-16_105507.mp4

enable terrain and then disable button is straight up bugged, have to zoom in for it to work.

3.mp4

3rd video:

Either 2D/3D switch is bugged, or enable building is bugged.

To Reproduce
Steps to reproduce the behavior:

1. I think you need a slow connection to the server to reproduce this, it happens mostly at the beginning, or during transition and loading.
2. Just open incognito window, login and try the options at the beginning.

Expected behavior
Buttons should correctly work.

[dgraf-gh]

Thank you for the videos.

Yes, the transition handling needs a little bit of work. I also noticed that when switching between days with and without data it does not arrive at the desired end state. For example: selecting a date without data zooms to the home location, if during that zoom animation another day is selected, the data is loaded, but it will not zoom to the boundaries of that newly selected date.

The idea: immediately stop all animations when selecting something, then go on like normal.

I sometimes noticed also the thing with the terrain layer but could never pin it down and thought it was my mind which went crazy.

And switching between 2d and 3d propably worked. At the moment the pitch is not altered when going back to 3d and it looks like it does nothing. It only enables rotation and changing the pitch when holding the right mouse button.

[dgraf-gh]

Steps to reproduce:

• make sure that the map starts in globe mode and terrain is enabled
• disable globe mode
• clicking on terrain does not switch the layer of now

It also breaks when switching to globe mode, and then disabling or enable the terrain layer

Also, we should rewrite the wording on the buttons. After initially thinking it was a good idea to display what will be the next state when clicking on it like "Enable 2d" when currently in 3d mode. It is kind of confusing. We could either use checkboxes for 3d, satelite, buildings and terrain or have the wording like "Enabled 3d view"/"Disable 3d view" or "Enable Terrain","Disable Terrain"

[christaikobo]

I agree 100% the current wording is confusing.

Check boxes can work. Or we can simply show the current status, like:

View angle: 2D (this means we are currently using 2D view)
click on it, then it changes to
View angle: 3D (this means we are currently using 3D view)

Map Mode: Globe/Flat
Terrain: Enabled/Disabled
Building: Enabled/Disabled
etc.

[christaikobo]

Steps to reproduce:

• make sure that the map starts in globe mode and terrain is enabled
• disable globe mode
• clicking on terrain does not switch the layer of now

It also breaks when switching to globe mode, and then disabling or enable the terrain layer

Also, we should rewrite the wording on the buttons. After initially thinking it was a good idea to display what will be the next state when clicking on it like "Enable 2d" when currently in 3d mode. It is kind of confusing. We could either use checkboxes for 3d, satelite, buildings and terrain or have the wording like "Enabled 3d view"/"Disable 3d view" or "Enable Terrain","Disable Terrain"

I don't think that is the only problem, you can try starting reitti in incognito mode, every setting is default, it still happens.

Video_2026-03-18_093710.mp4

As shown in the video, terrain and building setting simply does not work at all, no matter if I use 2D or 3D, globe or flat.

My rudimentary feeling is that the interaction between frontend and backend probably needs some kind of overall change.