In the current implementation for each video fragment a separate <video> element exists in the A-Frame assets list. This causes all videos to be loaded at the same time, which may cause an excessive memory usage especially for larger number of videos or longer/higher quality (i.e. 4K) videos. This may cause problems especially on weaker devices.
In the current implementation for each video fragment a separate <video> element exists in the A-Frame assets list. This causes all videos to be loaded at the same time, which may cause an excessive memory usage especially for larger number of videos or longer/higher quality (i.e. 4K) videos. This may cause problems especially on weaker devices.