Possible Walking Mode Bug

[gavspav]

We've been testing walking mode today.
I've set the radius to 7m in the project settings and dropped a load of assets in our garden.
It generally seems to work but there is one consistent problem which may or may not be to do with our settings.
When you move and a marker leaves the 7m radius are around you the asset fades out nicely as it should but the marker stays red.
When you go to the spot where another marker is, it will not play. At least not until the previous asset has finished playing when it goes black again, then the nearest marker turns red and it starts playing. It's as if the first clip fades out but still carries on playing. This behaviour does not happen in map mode. Dragging the large circle around seems to work perfectly.

Hopefully the image below helps explain what I mean. I walked to the red marker in the bottom left. It started to play and then faded out but remained red. I then walked to the marker visible in the greyed out circle. This will not play for a significant amount of time (we are using clips of around 3 minutes) which we think is the first clip playing silence until the end of the clip. Eventually the one within the circle goes red and plays back.

I'm not sure if this is something to do with our audiotrack or project settings, by design or a bug.

[hburgund]

Interesting...I have not experienced this and am not able to reproduce but that is because it would require some setting up of an analogous situation nearby to me. I tried to reproduce in the mobile browser in walking mode on my laptop, but again, that is a non-ideal situation.

The only thing that comes to mind regarding settings is that you have banned the audio from repeating for a certain period of time and that is what delays the subsequent playback, but unless you have already played the asset you are moving to, this shouldn't be an issue. And if all is working fine in map mode, I am skeptical...but that's the only guess right now.

Have you tried different mobile browsers and devices just in case there is some weird caching or user-specific issue?

@shreyas-jadhav do you have any thoughts as to why this might be happening? It is definitely not by design as you've described it, but there is a possibility that a setting adjustment could remedy it. I generally don't use asset audio as long as what you are using, so it is certainly possible it is a bug that I simply haven't noticed due to my assets being generally quite a bit shorter...

[gavspav]

This behaviour, it turns out is intermittent. I went for a walk in town today and tested some assets out. It was exhibiting the behaviour I describe above. As I approached an asset marker the web app froze and wouldn't respond. About a minute later I noticed it was working again and checked for this bug again. It started behaving perfectly. Really hard to work out what's going on sometimes, especially when you are walking around town with no headphones looking like a nutter!