Installer Steam
log på
|
sprog
简体中文 (forenklet kinesisk)
繁體中文 (traditionelt kinesisk)
日本語 (japansk)
한국어 (koreansk)
ไทย (thai)
Български (bulgarsk)
Čeština (tjekkisk)
Deutsch (tysk)
English (engelsk)
Español – España (spansk – Spanien)
Español – Latinoamérica (spansk – Latinamerika)
Ελληνικά (græsk)
Français (fransk)
Italiano (italiensk)
Bahasa indonesia (indonesisk)
Magyar (ungarsk)
Nederlands (hollandsk)
Norsk
Polski (polsk)
Português (portugisisk – Portugal)
Português – Brasil (portugisisk – Brasilien)
Română (rumænsk)
Русский (russisk)
Suomi (finsk)
Svenska (svensk)
Türkçe (tyrkisk)
Tiếng Việt (Vietnamesisk)
Українська (ukrainsk)
Rapporter et oversættelsesproblem
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