User:Fim
From OpenSimulator
| Line 25: | Line 25: | ||
The location of in-simulator avatars can be transmitted into the '3D Snapshot' and they would be represented by a prim or by a textured mesh. The location of a 3D Snapshot avatar can be represented inside the simulator via prim or 'npc' which contains the chat relay script. | The location of in-simulator avatars can be transmitted into the '3D Snapshot' and they would be represented by a prim or by a textured mesh. The location of a 3D Snapshot avatar can be represented inside the simulator via prim or 'npc' which contains the chat relay script. | ||
| − | =====Step Two===== | + | =====Step Two would be===== |
Writing a parser/converter for '.oar' files to use the extracted data with three.js | Writing a parser/converter for '.oar' files to use the extracted data with three.js | ||
| + | |||
| + | =====Possible Resources===== | ||
| + | [https://github.com/Katharine/AjaxLife AjaxLife] (via Blake)<br /> | ||
| + | [http://en.wikipedia.org/wiki/WebGL WebGL]<br /> | ||
| + | [http://threejs.org/ three.js]<br /> | ||
Revision as of 16:55, 11 June 2015
I am a Virtual World Developer living in Frankfurt/Main,
playing with OpenSimulator on a Raspberry Pi2
and do some DIY Hardware stuff.
Contents |
My Current Projects Related To OpenSimulator
"A walkable 3D map"
The idea for this approach, to develop some kind of OpenSimulator Web-based viewer, emerged by a conversation on the OpenSimulator Educator's Mailinglist
- Step One | Wording a Functional Specifications Document (FSD)
- Utilizing a "3D Snapshot" of an OpenSimulator Region (.oar archive file)
- Walk through via web browser -> WebGL / three.js
- Ability to display 3D content
- Movement control and camera control panels.
- HUD functionality
- Ability to load different teleport locations into a fixed teleport HUD
- Region map with teleport capability
- Runs from local install/USB key
- Settings menu / autodetection draw distance
- Open Source licence
- Please participate!
This is how the web-based viewer could work
Every X (24) hours a snapshot (.oar) of the current region state will be created, which is then converted to a format three.js can render. The data of avatar locations can be provided via xml-rpc. In-world chat can be forwarded to a chat client on the website too.
Visiting the regions web-based viewer page would show a window into the '3D Snapshot' region, the size of the window would be determined by the performance of the users client. The draw distance can be set manually too.
The location of in-simulator avatars can be transmitted into the '3D Snapshot' and they would be represented by a prim or by a textured mesh. The location of a 3D Snapshot avatar can be represented inside the simulator via prim or 'npc' which contains the chat relay script.
Step Two would be
Writing a parser/converter for '.oar' files to use the extracted data with three.js
