User:Fim
From OpenSimulator
| Line 11: | Line 11: | ||
*** Movement control and camera control panels. | *** Movement control and camera control panels. | ||
*** HUD functionality | *** HUD functionality | ||
| + | *** No inventory access | ||
| + | *** No login required | ||
*** Ability to load different teleport locations into a fixed teleport HUD | *** Ability to load different teleport locations into a fixed teleport HUD | ||
*** Region map with teleport capability | *** Region map with teleport capability | ||
*** Runs from local install/USB key | *** Runs from local install/USB key | ||
*** Settings menu / autodetection draw distance | *** Settings menu / autodetection draw distance | ||
| + | *** Chat (Text) functionality | ||
*** Open Source licence | *** Open Source licence | ||
* Please participate! | * Please participate! | ||
=====This is how the web-based viewer could work===== | =====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. | + | Every X (24) hours a snapshot (.oar) of the current region state will be created, which is then converted to a format WebGL/three.js can render. The data of avatar locations can be provided via xml-rpc. A possibility for text chat on the webpage is given - which could be relayed to the corresponding simulator region, in-world chat could be forwarded to the chat client on the website 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. | 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. | ||
| + | |||
| + | ''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. Also shown is a 2D Region map utilizing JavaScript to 'teleport' to another spot. Movement control, camera control panels, the Region map and a setings menu icon are overlaying the scene - but can be folded up. | ||
=====Step Two would be===== | =====Step Two would be===== | ||
| Line 33: | Line 36: | ||
[http://threejs.org/ three.js]<br /> | [http://threejs.org/ three.js]<br /> | ||
| − | [http://opensimulator.org/wiki/User_talk:Fim feed back here!] | + | [http://opensimulator.org/wiki/User_talk:Fim - feed back here! -] |
Revision as of 23:45, 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 (static)
- Movement control and camera control panels.
- HUD functionality
- No inventory access
- No login required
- 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
- Chat (Text) functionality
- 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 WebGL/three.js can render. The data of avatar locations can be provided via xml-rpc. A possibility for text chat on the webpage is given - which could be relayed to the corresponding simulator region, in-world chat could be forwarded to the chat client on the website 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.
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. Also shown is a 2D Region map utilizing JavaScript to 'teleport' to another spot. Movement control, camera control panels, the Region map and a setings menu icon are overlaying the scene - but can be folded up.
Step Two would be
Writing a parser/converter for '.oar' files to use the extracted data with three.js
