| Аутор |
Тема: Live Race |
18 одговора
|
|
|
Is it working?
---------------------
Sistema
|
|
|
|
Ok, in a mobile is running, slow but running.
The problem is in an Android tablet.
---------------------------------------------------------
Sistema
|
|
|
|
The mobile experience is pretty terrible for me, at least on the mobile chrome browser
|
|
|
|
It was very slow for me today, at least on mobile...same here with chrome on Android.
|
|
|
|
It was very jumpy on Chrome on the laptop as well.....
|
|
|
|
On my Android phone it was very bad, and also the same when I checked on my iPad when I got home. Sure Vlad is aware and will sort it.
|
|
|
|
I can,t watch the race in the tablet even now in the last race replay
---------------------------------------------------------
Sistema
|
|
|
|
I seem to recall the same issue the last time we were at this track.
|
|
|
|
In my pc is working good too.
---------------------------------
Sistema
|
|
|
|
This seems to be track related, we will investigate it. It is strange because Valencia is not the most heavy track, but somehow it is hard on the GPUs, especially on mobile devices. If someone has any clues, let me know.
|
|
|
|
|
It's probably the high level of details of the track surroundings. The track image size is quite big (but not the direct cause as there are bigger ones). The resolution of it is also probably not helping.
PS: I didn't have any issues with it on my devices though.
|
|
|
|
My phone is with Snapdragon 870 and Adreno 650. Genshin Impact runs smooth as butter. I dont believe it is hardware bottleneck
|
|
|
|
Valencia tops all circuits in width (and comes in 2nd to Austin on total canvas size). Anyone know about that in relation to causing memory problems while resizing on mobile devices?
And the detail might be the cause as well, since Austin is maybe easier for the downsize algorithm on mobile devices?
On my mobile valencia runs with roughly a frame per second.
Baku runs oaky, but has some short freezes.
Austin runs smooth.
Singapore is usualy a bit jerky for me as well btw.
|
|
|
|
Can those of you that have poor performance in the Valencia replay test something for me? Reload the replay, but don't start it. Switch to a previous replay on a track that runs smooth (Paul Ricard for instance), play that replay and make sure it is running smooth. Then select the Valencia replay again (without reloading the page) and start the Valencia replay. Is it running smooth now?
|
|
|
|
Sorry. No change after replaying BuenosAires and back to Valencia. Same fps as before.
edit: there is something interesting (or obvious maybe) that I noticed. When zoomed out the frame rate seems normal, but as soon as I zoom in there seems to be a linear relation between the detail and the gap the car jumps tot he next frame. When I speed up * 5 the gap also goes * 5.
So the fps seems to be fixed, regardless the speed and zoom.
tested on a Huawei P smart - 32GB with 3GB ram, Android, Chrome webbrowser
|
|
|
|
|
|
Replay at Paul Ricard worked fine, even zoomed all the way in. Valencia, when zoomed in, was still jumping all around. When I zoomed all the way out at Valencia, the frame rate was normal. Anything less than the max zoom oon Valencia and the frame rate was still jumpy.
I'm using a Samsung Galaxy Tab S4, Android, Chrome.
|
|
|
|
In track details we have the old layout meanwhile we have the new layout on the live race screen?
|
|
|
|
When im watching race on OLD race screen, live standings shows P31 as first one in relegation zone ( as it should) , switching to NEW race screen standings shows P33 as first one in relegation (incorrect)...
|
|
|
|
Quote ( Hans Barf @ July 1st 2021,19:24:38 ) edit: there is something interesting (or obvious maybe) that I noticed. When zoomed out the frame rate seems normal, but as soon as I zoom in there seems to be a linear relation between the detail and the gap the car jumps tot he next frame. When I speed up * 5 the gap also goes * 5.
So the fps seems to be fixed, regardless the speed and zoom.
Commenting this since I'm here for the olympic prediction games.
The fully zoomed out image is cached in code, so if it works well with that, then it is not due to car position calculations but due to resizing/drawing the image.
The code tries to figure out the optimal frame rate. So it measures 10 steps in the beginning of race how long they take. Thus, if it starts with zoom, then it will stay slow even when zoomed out. And it indeed uses the same rate also when speeded, just the time steps are longer.
Also, nowadays, if it can't keep up the frame rate, it recalculates the time step. A long time ago, the time step was calculated from frame rate. Thus, if it couldn't keep up with frame rate, the race was running too slow.
|
|
English
Deutsch
Español
Română
Italiano
Português
Português
Français
Polski
Русский
Български
Македонски
Nederlands
Vlaams
Suomi
Lietuvių
Čeština
Magyar
Eesti keel
Slovenčina
Türkçe
Shqip
Ελληνικά
Hrvatski
Bahasa Melayu
Dansk
Pirate
