Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I guess1.7M triangles is way too much for 2017 phone XD
1: for i from 1 to 1000
2: -- Walk one small step of about 40cm
3: -- for j from 1 to 4
4: ---- take one shot by clicking on a button, turn about 90 degrees
I take two synchronized 4096*1344 videos at 30hz by walking about 400m during 509 seconds for this 3D model.
Now assume that i redo the same trajectory with a second acquisition method that needs to rotate the camera by myself:
1: for i from 1 to 1000
2: Walk one small step of about 40cm
3: for j from 1 to 4
4: take one shot by clicking on a button, turn about 90 degrees
Assume that line 4 takes about one second (and neglect the walk time).
Then the second method takes about 4000 seconds and i need to click/rotate 4000 times.
The first method is not only faster but also less tiring than the second one.
Note that
- 2330 keyframes are automatically extracted from the video for the 3D computations, which equivalent to a step of about 17cm (instead of 40cm).
- small enough (but not too small) steps are needed for the computations