Users experiencing this will see the below error within VR.World:
This is almost always a result of frame-dropping - VR.World always disregards the first 35 frames of any uploaded capture, as iSTAR Pulsar is often still identifying the appropriate exposure value to use at this stage. If a capture consists of less than or equal to 35 frames, these will all be dropped and there will be no additional frames to be processed.
This is particularly common when users capture using distance spacing or with a relatively slow rate of image count spacing, for example:
Data captured at 4 meter spacing x initial 35 frames = 140 meters
So if a user captures at 4 meter spacing the first 140 meters of the capture are going to be lost to frame-dropping. As such, the user should commence capturing at least 140 meters prior to the intended start of the captured route to ensure that these frames are retained.
Data captured at 1 fps x initial 35 frames = 35 seconds
So a user capturing at 1 fps will lose the first 35 frames of their capture to frame-dropping. To avoid this, users may wish to consider commencing capture, remaining stationary for 35 seconds, and then moving off - the initial 35 frames that are dropped will not then be required.
- Users can find further information on configuring rate of capture within this article.
- The dropping of 35 frames at the beginning of every capture is how VR.World works currently, however this will be modified in a future update so as to be more context-based.
- If a user believes that a preview has failed to generate for reasons other than frame dropping, they may raise a support request providing device serial number, capture ID, and as much additional detail as possible, and our support team can investigate further.