安装 Steam
登录
|
语言
繁體中文(繁体中文)
日本語(日语)
한국어(韩语)
ไทย(泰语)
български(保加利亚语)
Čeština(捷克语)
Dansk(丹麦语)
Deutsch(德语)
English(英语)
Español-España(西班牙语 - 西班牙)
Español - Latinoamérica(西班牙语 - 拉丁美洲)
Ελληνικά(希腊语)
Français(法语)
Italiano(意大利语)
Bahasa Indonesia(印度尼西亚语)
Magyar(匈牙利语)
Nederlands(荷兰语)
Norsk(挪威语)
Polski(波兰语)
Português(葡萄牙语 - 葡萄牙)
Português-Brasil(葡萄牙语 - 巴西)
Română(罗马尼亚语)
Русский(俄语)
Suomi(芬兰语)
Svenska(瑞典语)
Türkçe(土耳其语)
Tiếng Việt(越南语)
Українська(乌克兰语)
报告翻译问题









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